Idea to Impact
Bring us a problem or opportunity. Sixteen working hours later, your users test one workflow from it.
Bring a problem or an opportunity that your organisation wants solved. Behind it sits a value stream of workflows. We map that value stream, build one workflow from it, and your users test it. Four of the sixteen hours are your people's time.
16:00h
sponsor session to user sign-off
The clock runs for each step
Each step gives the next step a finished artefact.
The result is a complete trace from the sponsor's problem to a workflow that your users have tested. Nobody has to assemble the trace afterwards.
A number with a ring is a step that needs people from your organisation. There are four such steps.
-
1:00h01
Sponsor session
1 hour Your time 1:00hMeet the sponsor. Agree the problem to solve, the opportunity, the success measures, and the stakeholders.
Session transcript -
2:00h02
Problem & Opportunity Statement
1 hour 2:00hProduce the statement and the stakeholder artefacts directly from the sponsor session transcript.
Problem & Opportunity Statement Stakeholders & Personas -
3:00h03
Observation sessions
1 hour each Your time 3:00hStakeholders show you the workflows that they run today. You record the pain points and the possible improvements.
-
5:00h04
Current state documented
2 hours 5:00hDocument how the work runs today and the systems that it runs on. Then update the Problem & Opportunity Statement with what you learned.
Current State Workflows Current State System Architecture -
9:00h05
Domain Model and Workflows Value Stream
4 hours 9:00hDesign the domain model that the solution is built on. The workflows of the solution form a value stream. Design that value stream.
Domain Model Workflows Value Stream -
10:00h06
Workflow design and Model Specs
1 hour 10:00hDesign one workflow from the value stream. Create the model specs for the workflow, or update the specs that already exist.
Workflow design Model Specs -
11:00h07
Build and unit test
1 hour 11:00hBuild the workflow and unit test it.
Working workflow Unit tests -
12:00h08
System tests written and run
1 hour 12:00hWrite the system tests. Run the tests and record the results.
System tests Test results -
12:30h09
User guide and video
30 minutes 12:30hWrite the user guide and produce the video of the guide. Then the people who use the workflow can start work on it.
User Guide User Guide Video -
13:30h10
Users review and test
1 hour Your time 13:30hGive the guide and the build to the users. The users review the guide and test the workflow against the way that they work.
Review findings -
14:30h11
Triage, fix, re-test
1 hour 14:30hTriage the findings and fix them. Update each artefact that the fix affects. Then run the system tests again.
Updated artefacts System test results -
15:30h12
Users confirm the fixes
1 hour Your time 15:30hThe users who reported the findings confirm the fixes. The record is current when the users give their sign-off, not one week later.
User sign-off -
16:00h13
Release notes and roadmap
30 minutes 16:00hPublish the release notes and the updated roadmap. Both documents come from artefacts that are already current. For this reason, we measure this step in minutes.
Release notes Roadmap - Run complete 16:00h
Total
16:00h
Two working days from the sponsor session to a workflow that your users have tested. Add one hour for each extra stakeholder that you observe.
Your stakeholder time
4:00h
Only four of the sixteen hours need time from your organisation: the sponsor session, the observation session, the review, and the confirmation. The other twelve hours run without your people.
The clock assumes one observation session. No step in the list is a status meeting, a handover, or a document that updates an old record.
Start with one workflow.
Step one is a one-hour session with your sponsor. Every later step runs from what you agree in that session.