Present and share

Showing processes to people: presenting them full screen, demos and workshops, collecting feedback, taking staff through how the work is done, and the procedure guide (SOP) that Twiggy Modeller writes from the model. One model behind all of them, so what you show is what was signed off.

Which way, for what

You want to…	Use	Where
Walk a room through a process or the map	Present mode	Present, at the top of the model or in its … menu
Capture what people say in a workshop	Present › Workshop	Notes on the element on screen, applied with the AI afterwards
Ask specific people specific questions	Discuss	Right-click › Comment…; Review › Discuss › Ask people…
Have experts check the whole model	Review	Review › Request a review (a link, no account needed)
Give staff the steps to follow	Procedure guide	… › Procedure guide, on a process or an area; print or PDF
Let people read it themselves	Readers	Viewer role: signed-off versions, search, the procedure guide

Present mode

The model full screen, with a panel across the bottom that says what you are looking at. It works on a map, a chain and a flow.

Step through with ◀ ▶ (or the arrow keys): each element is centred and what follows lights up. Decisions are read out as their conditions. The panel shows the description, how it's done, where the work comes from and what happens next.
Follow the work across processes. At an end that hands over to another process, carry on into it; Back returns. From a map, double-click an area to open its chain, and a process to present its flow.
Answer a question with a view. Lanes by role, by system or by one of your properties, and lenses (risk rating, systems, time and cost, sign-off) work in Present too.
For projectors: the contrast button darkens lines and text; drag the panel's edge to give the diagram more room. Esc ends.

Demos

Start on the map with the Sign-off and coverage lens (what is modelled and signed off), double-click into one area's chain, then present one flow end to end and follow its hand-off into the next process. Keep to the main path; open a step's detail (a sub-process, its controls) only when someone asks. The example workspaces (File › Examples…) give you something to show on day one, and Twiggy in your organisation has playbooks to pitch from.

Getting feedback

In the room: turn on Workshop in Present. Type what people say; each note is pinned to the element on screen. Afterwards, the notes are waiting in the AI assistant: apply them all, or one by one.
Afterwards, from the people who know: Discuss sends specific questions to specific people (answers come back as comments); a review sends the whole model to experts by link. Neither changes the model until you work the answers in.
Things the AI wasn't sure of are marked ?: put them to the people in the room first.

Taking staff through

For new starters and changes to how work is done: present the signed-off flow and step through it, reading how it's done from the panel; then give them the procedure guide for the area to keep. Lanes by role show each person where their part is. With the reader role, staff can come back to it themselves: search for a step, a system or their role and read the guide.

Procedure guides (SOPs)

Twiggy Modeller writes the procedure guide from the model: nothing is typed twice, so it can't drift from the flow. Open it from a process or an area (… › Procedure guide).

What it holds: document control (version, sign-off, next review, who is accountable), purpose and scope, a RACI built from the lanes and owners, inputs and outputs, the numbered steps with how each is done, checks and exceptions, and an appendix of the controls, risks and systems used.
Published or working draft: the published set reads every process at its signed-off version, with its flow beside the steps (point at a step to find it on the flow). Readers only ever get the published set; editors can switch to the working draft and edit the guide in place.
Print or PDF for the controlled copy, with an optional “uncontrolled when printed” footer. Administration › Modelling › Procedure guides sets the sections and their names.

More: the procedure guide.

People with the Viewer role read signed-off processes (and drafts an admin chose to share), from a home page with search and the procedures of each area. They don't need a seat. What they see is set in Administration › People › What readers see, per folder, or per process (Review › Share with readers…). See who sees what.

What's next

Presenting and the procedure guide are two halves of the same thing today. Where we are taking them:

The SOP inside Present. The bottom panel becomes the step's guide card: how it's done, who is responsible and accountable, its checks, controls and exceptions, as the procedure guide shows them. A button opens the full guide for the process you are on.
Present a published set. Present an area as its procedures in chain order, each at its signed-off version, as a training session or an audit walkthrough.
Training by role. Pick a role and present only its steps across the processes (“my procedures”), with a short check at the end and read and acknowledge recorded per person.
Present from a reader's home. Readers present the published set themselves, for self-paced learning.
Hand-outs. A slide or PDF per step (the flow with that step lit, and its guide card) to send after a session.