A Kaizen is implemented in phases or stages. A workflow controls how the Kaizen moves from one stage to the next.
The workflow is attached to the Kaizen when it is created. As the requirements set by the workflow are met, the Kaizen progresses until it is complete.
Note: you can see a Kaizen's workflow from both the side window and the detail view.
Steps
1. Open the Kaizen whose workflow you want to see. See Open a Kaizen after creating it.
2. Click the Workflow icon next to the Attach button. It is in the same place in both views.
Side window
Detail view
Result
The workflow opens in a new browser window, in the workflow editor.
How workflows work
A workflow defines the steps and permissions that must be completed before a Kaizen moves on. In the workflow editor, admins set up:
Statuses, grouped into To Do, In Progress and Done. Each status can allow edits or lock the record.
Transitions from one status to another, including send-back transitions (for example, from Pending Approval back to Proposal).
Rules on each transition, in three parts:
Who can move the Kaizen: the submitter, reporter, assignee or a member, named users, or a role. Set this, or items can get stuck.
When it can move: validations such as the due date being filled, a KPI being filled, or hard savings greater than 0.
What happens when it moves: for example, update a field such as the saving status, and send notifications.
Preferences: conditions such as pillar or type that select the workflow automatically. Users never pick a workflow themselves.
A workflow is created from Workflow → Add New, for a module (Kaizen, EWO or Tags) and a project type. A Kaizen type needs a workflow before Kaizens of that type can move through their statuses.