From map to signed-off process
How a workspace goes from nothing to signed-off processes that people use and that stay current. Click through the stages; each says what happens, where it is in Twiggy Modeller, and who does it.
The journey
1. Map the landscape
List what the business does: enterprise processes, then the process areas inside them, each with an owner. Names and owners only.
Discuss, review, sign off
Three ways to bring other people in, from informal to formal. Each lives in a tab of the review panel, and each can repeat.
| Discuss | Review | Sign-off | |
|---|---|---|---|
| For | Questions on specific steps, any time | Checking the whole model is right | Approving it |
| Who | Members you choose (suggested from lanes and owners) | SMEs, by link, no account needed | The folder’s Accountable people |
| They get | An email and Questions for you on their dashboard | A link to the model to comment on | A link to approve or ask for changes |
| Changes the model? | No: you work answers in | No: items to accept | Locks and publishes it |
What a status means
- being built; only people who can open it see it.
- SMEs are commenting; the model can still change.
- sent to approvers; their decision is on this version.
- an approver asked for changes; work them in and send again.
- approved and locked; readers see it. A change starts a revision, and readers keep this version until the revision is signed off.
- its re-certification date is near or past.
On a map, a dot on each process shows whether its flow is signed off; the Sign-off and coverage lens (View › Lens) colours the whole map by it.
Who sees what
| Draft | Draft shared with readers | Signed off | |
|---|---|---|---|
| Modellers, reviewers, approvers | Yes, and edit if they may | Yes | Yes, plus any revision in progress |
| Readers (Viewer role) | No (unless the workspace shows everything) | Yes, marked as a draft | The signed-off version only |
| Sign-off and review links | The version sent to them, for as long as the link is open | ||
Admins decide what readers see: Administration › People › What readers see, a folder's Drafts for readers, or one process's Share with readers. Folders can also be restricted to the teams named in them. More in How it fits together.
Risk sets the cadence
When a process is signed off, its next review date follows the highest-rated risk linked to its steps: every 6 months if it touches a critical risk, at least every 12 for a high one, otherwise the workspace's cycle (Administration › Sign-off and review). Rate a risk up, and every process it touches comes due sooner. The dashboard lists what is due; the approver re-certifies (still right) or starts a revision.