A paper value stream map captures a moment. Then the gemba walk ends, the sticky notes are transferred into a slide deck, and the map begins to age. The finished image may still support a presentation, but the evidence behind each number becomes difficult to inspect, update, or reuse.
That is the central difference between a map as a drawing and a map as a working improvement asset.
Inside Ci Flow, the value stream mapping tool is designed to keep the current state editable, connected to its operating data, and available for the next stage of the improvement journey. The map can begin with observations from the floor, support future-state design, and be rebuilt after implementation so the future state becomes the next current state.
For practitioners who already understand VSM theory, the important question is not whether digital mapping is possible. It is what becomes possible when the map lives inside the project workspace instead of in isolation.
What the Value Stream Mapping Tool Does
Ci Flow provides a value stream mapping workspace for creating a current-state map with the operating data and information flows needed to expose waste and prioritise the future state.
The tool supports:
- Connected value-stream symbols
- Process-time and lead-time fields
- Editable process evidence
- Material and information-flow representation
- Saved project evidence for review and presentation
- A pathway from current-state mapping to future-state improvement
This matters because a VSM is more than a visual sequence of activities. It is a structured representation of how value, information, inventory, time, and decisions move through a product family.
The map should help the team answer practical questions:
- Where does customer value enter the process?
- Where does work wait?
- Which process step controls flow?
- How much time is value-adding?
- Which data requires validation?
- What future-state change would produce the greatest benefit?
A digital workspace gives the team a stronger foundation for answering those questions consistently.
Why Connected Symbols Matter: A Worked Manufacturing Example
Consider a manufacturing value stream producing a standard industrial component. The team maps six process steps from receiving through final packing. The figures below are illustrative, but they reflect the type of operational data captured during a structured mapping session.
| Process step | Process time | Lead time | Uptime | Changeover | Batch size | Inventory after step |
|---|---|---|---|---|---|---|
| Receiving and kitting | 18 min | 0.50 days | 98% | 20 min | 100 | 120 units |
| Cutting | 12 min | 0.25 days | 92% | 45 min | 100 | 80 units |
| Machining | 36 min | 1.50 days | 88% | 60 min | 50 | 150 units |
| Surface treatment | 8 min | 2.00 days | 95% | 30 min | 200 | 200 units |
| Assembly | 22 min | 0.75 days | 97% | 25 min | 50 | 90 units |
| Final inspection and packing | 10 min | 0.50 days | 99% | 15 min | 50 | 60 units |
The connected map provides an immediate operating picture.
Process time
The total process time is:
18 + 12 + 36 + 8 + 22 + 10 = 106 minutes
This is the time during which work is actively performed on the component.
Lead time
The total lead time is:
0.50 + 0.25 + 1.50 + 2.00 + 0.75 + 0.50 = 5.50 working days
If one working day contains 480 minutes, total lead time is:
5.50 × 480 = 2,640 minutes
Process Cycle Efficiency
Process Cycle Efficiency is calculated as:
PCE = Value-Added Time ÷ Total Lead Time × 100
Therefore:
PCE = 106 ÷ 2,640 × 100 = 4.02%
Only about 4.02% of the total elapsed time is active process work. The remaining time is associated with queues, storage, transport, scheduling, inspection, or other forms of delay.
That is precisely the type of relationship a connected VSM should make visible. In a paper exercise, the practitioner may manually add the figures on a whiteboard, calculate the percentage separately, and then copy the result into a presentation. Inside Ci Flow’s value stream mapping workspace, connected symbols and entered operating data allow the map to total the lead-time ladder and process-time values in the project record rather than relying on a separate calculation sheet.
The map also highlights where to investigate first. Surface treatment carries the longest lead time at 2.00 days, while machining combines 1.50 days of lead time, 88% uptime, and the longest changeover at 60 minutes. Those conditions make machining and surface treatment strong candidates for deeper analysis, but the team should validate the causes at the gemba before selecting countermeasures.
Evidence That Stays Attached to the Map
A number on a map has limited value if nobody can explain where it came from.
The cycle time might have been copied from a standard operating procedure. The lead time might have been estimated by a supervisor. The uptime figure might have come from a monthly report. The inventory count might represent a single moment rather than a typical condition.
These distinctions affect the credibility of the current state.
Inside Ci Flow, each process box remains editable. The practitioner can update the entered value, refine the description, and keep the evidence within the project workspace. A reviewer can then examine the project record and ask:
- Was the time observed or estimated?
- What date was the observation completed?
- Which product family was mapped?
- Was the measurement taken during normal operation?
- Does the value represent one cycle, an average, or a range?
- Has the process changed since the original observation?
This is the difference between a map as a drawing and a map as a data model.
A drawing communicates the shape of a process. A data model preserves the relationships between process steps, queues, information flows, timing, inventory, and evidence. When those relationships remain editable, the map can support analysis instead of simply illustrating it.
For a broader baseline, practitioners can also use the Process Cycle Efficiency Calculator to examine the relationship between value-added and non-value-added time.
From Current State to Future State
The current state is not the final deliverable. It is the factual starting point for improvement.
Once the team has identified the largest queues, the most significant flow interruptions, and the information delays affecting the product family, it can design the future state around measurable conditions such as:
- A smaller production batch
- Point-of-use inventory
- A supermarket pull system
- Reduced changeover time
- Improved first-pass yield
- More reliable information release
- A better production rhythm aligned to customer demand
For example, the team might propose reducing the surface-treatment queue from 2.00 days to 0.75 days through scheduling changes and a defined replenishment rule. If machining changeover falls from 60 minutes to 30 minutes, the team may also be able to reduce the batch size from 50 units to 25 units, lowering work in process and improving responsiveness.
The future-state design should state the expected effect clearly:
| Measure | Current state | Future-state target |
|---|---|---|
| Total lead time | 5.50 days | 3.00 days |
| Process time | 106 min | 98 min |
| Work in process | 700 units | 380 units |
| Process Cycle Efficiency | 4.02% | 6.81% |
| Machining changeover | 60 min | 30 min |
| Surface-treatment lead time | 2.00 days | 0.75 days |
These are targets, not proof. The team must implement the countermeasures, measure the revised process, and rebuild the map using actual results.
That is where an editable workspace becomes particularly valuable. The future-state design can remain connected to the same project record. After implementation, the team can create the next current state and compare the observed result with the original baseline.
The map also becomes part of the stakeholder narrative. Ci Flow’s tollgate presentation capability allows saved tools, charts, process maps, and explanations to support a structured review. Instead of presenting a static picture detached from the project evidence, the team can show:
- The observed current state
- The verified performance gap
- The selected future-state design
- The countermeasures and owners
- The measured result after implementation
For complex improvement work, this approach complements the structured project discipline developed through Lean Six Sigma Green Belt training and Black Belt training.
Five Habits for a Usable VSM Data Model
A productive mapping session depends on disciplined observation. Use these five habits to create a current state that can support decisions.
1. Map the product family, not the department
A value stream follows a product or service family from demand to delivery. It should not simply reproduce the organisation chart. Select products that share similar process steps, equipment, information flows, and customer requirements.
2. Time the process instead of asking for the standard
Standards are useful references, but direct observation reveals variation, interruptions, and actual waiting. Time multiple cycles where possible and record the conditions surrounding the observation.
3. Capture information flow separately from material flow
Production may move forward while schedules, approvals, specifications, or replenishment signals move through a different route. Represent both flows so the team can see how decisions influence physical work.
4. Record the queue, not only the activity
A process box without the queue beside it gives an incomplete view. Record inventory, waiting time, batch size, and the conditions that release work to the next step.
5. Date the map and identify the observer
Every current state has a reference date. Add the observation date, product family, shift, location, and participant names. This gives later reviewers the context required to interpret the evidence.
Who Benefits Most from an Editable Current State?
The value stream mapping tool inside Ci Flow is especially useful for:
- Black Belts and Green Belts running structured mapping sessions
- Improvement leaders who need a defensible current state for governance
- Operations managers investigating flow, capacity, and work in process
- Project teams designing future states with shared evidence
- Practitioners who have mapped before and want the map to remain useful after the workshop
The fundamental advantage is continuity. The gemba walk produces evidence, the workspace organises it, the future state uses it, and the follow-up map tests whether the change landed.
Explore Value Stream Mapping Inside Ci Flow
If your current-state map is ready to become a working improvement asset, explore Ci Flow with example projects included.
Start a 14-day free trial with no credit card required. Build a map, enter the operating data, connect the process flow, and see how an editable current state can strengthen your next improvement project.
Start your 14-day free trial at ciflow.app and turn your next gemba walk into evidence your team can use.
Kaizen. Kai-Care. Kai-Done. Lean Six Sigma
