Choose a value stream, build its steps from your own process library or an uploaded framework, record what you observe at each step, and the map, timeline and improvement signals build themselves.
Process library None loaded
Example values are loaded so you can see the model working. The first example is Harbourline Services, a fictional IT company: its handover from go-live to steady service, 9 weeks in the current state and 4 in the future state. Replace the times, %C&A and staffing with what you observe on the gemba walk.
Value stream map
Queue / waitImprovement signalInformation flow
Step data
Ref links a step to an entry in your process library, such as a PCF element ID, and can be left blank. Team is the team that owns the step; a change of team between steps marks an interface between teams. Task time is the hands-on work on one unit, excluding any time it sits waiting. Cycle time is task time divided by the people doing the work, and is what the tool compares with takt. Wait is elapsed time the unit sits before the step starts; enter in Of which external any part of that wait outside the organisation's control, such as a client's own legal review. %C&A arriving is the share of work that arrives at this step complete and accurate. Handoffs counts transfers into the step between people, teams or systems. A working day is taken as 7.5 hours.
Improvement signals
Save, share and exchange
Files
Diagnostic scope
What this map hands to the Diagnostic. Exported with the model.