01 — An engagement
What patchley produces in each phase.
Nothing about the engagement itself changes: you still run the workshops, ask the questions and own the client relationship. What changes is the time between the meetings, and what you can show at the end of each one.
THE ENGAGEMENT IS YOURS · THE MODELLING TIME BETWEEN MEETINGS IS WHAT CHANGES
02 — In the room
The client sees the process while describing it.
Run the workshop as you always do, with patchley listening through live audio, or paste the Microsoft Teams, Zoom, Webex or Google Meet link and let patchley join the call. The BPMN 2.0 diagram forms while people talk: roles in lanes, decisions as gateways, the systems and documents they mention, the control steps marked.
That changes the dynamic of the room. Instead of a flip chart that will be interpreted later, the client sees the current understanding on the screen and corrects it on the spot: "no, the underwriter sees it before the handler", "there is a second path when the policy file is missing". The questions you would have had to ask in a follow-up call get asked and answered while everyone is still there. With responses switched on, patchley asks follow-up questions while the client describes, and you decide which proposals go into the diagram.
Interviews and documents between workshops
One-on-one interviews work the same way, live or from an audio recording (MP3 or WAV). Handbooks, policies and existing documentation go in as PDF or DOCX, one file of up to 50 MB with an optional focus on the process you need from it. Existing BPMN files from the client's tool are imported and stay editable.
The client corrects the diagram while everyone is still there. The follow-up call becomes a review, not a reconstruction.
03 — Between the meetings
Analyses that follow the diagram, a deck that fills itself.
Once the diagram stands, the analyses are written per step: the SOP view for documentation, pain points for the improvement case, compliance for the control steps, quantitative figures where the client has them, or your own template, the questions your practice asks about every process. When the client changes a step in the review, the analyses follow; what you have written by hand is kept.
The deck for the steering committee is built from the diagram and the analyses: process map, findings per step, control steps, in the client's colours, font and logo. It is a real PowerPoint file, with text, tables, chart and diagram editable in PowerPoint; what you change in patchley's deck editor is kept when you refill the deck after the next review round.
Per client, per organisation
patchley works per organisation. The org chart that supplies the lanes, the analysis and slide templates and the look of the decks belong to the organisation they are set up in, so one client's templates do not appear in another client's deck.
SOP view
For the documentation deliverable: purpose, performer, inputs, outputs per step.
Pain points
For the improvement case: where cases wait, what breaks, what people work around.
Compliance
For the control framework: control steps, their objective and evidence.
Your template
The questions your practice asks about every process, answered per step.
04 — Deliverables
What the client keeps.
05 — Working together
A tool, and a conversation.
patchley is a tool that you use in your projects, and we are happy to talk about how it fits your practice:
- which phases it helps with,
- what your consultants need to know on day one,
- how an organisation set-up per client works.
The best way to find out is the same as for any client: bring one real process to a 30-minute call. We model it live with you, and you see what your team would see in the room.
06 — Read on