From Future State Map to Kaizen Plan: Turning a Value Stream Map Into Projects

Disclosure: M365.FM host Mirko Peters works at iFAKT GmbH. This page describes the company factually; paid partnerships and links are labelled as advertising.

By Mirko Peters · 2026-11-11

Turn a future state map into a value stream improvement plan: capture kaizen bursts, order by dependency, set owners and dates. Includes an invented example.

A value stream improvement plan turns the future state map into a short list of actions with owners, dates and measures, so that the map leads to change and not to a poster. This article is for continuous improvement managers who have finished a mapping workshop and now face a wall of ideas. It explains how to capture kaizen bursts, group and order them, split them into events and daily work, rank them, and plan the first 90 days, with an invented example.

Key points

• A value stream improvement plan is the last mapping step: Learning to See asks for an implementation plan that describes, on one page, how you plan to achieve the future state.
• Kaizen bursts capture improvement ideas on the current and future state maps; group them, order them by dependency and give each one an owner, a measure and a date.
• Learning to See separates flow kaizen, management improving the stream across departments, from process kaizen, teams improving one process.
• The Lean Enterprise Institute says kaizen events commonly last five days and should not be the only form of kaizen, because daily kaizen builds frontline problem-solving.
• Rank ideas by impact and effort, but respect dependencies: a smaller batch needs a faster changeover first.

What is a value stream improvement plan?

The Lean Enterprise Institute (LEI) workbook Learning to See treats the plan as the final mapping step. It asks for an implementation plan that describes, on one page, how you plan to achieve the future state, so that the team ends up with a few sheets of paper: the future state and a plan to achieve it. The value stream manager maintains and periodically updates the plan and monitors all aspects of implementation.

The workbook does not prescribe the contents in detail. In practice, many teams call the result a value stream improvement plan or a kaizen plan, and the name matters less than the one-page form. A useful page for a manufacturing stream has five columns: the improvement, the part of the stream it affects, the measure it should move, the owner and the date. Keep it on one page, as the workbook says, so that it can hang next to the map at the board. Use value stream mapping to identify areas for improvement first, and use the page to say who does what within each stream.

How do you turn the future state map into projects?

Work in seven steps. This is my working method, built on the workbook's idea.

1. Capture the bursts. While drawing the current and future state maps, note each improvement idea at the place it applies. A kaizen burst is a marker for this. An Enna training page, from a provider of mapping training material, describes it as a way to capture improvement ideas while you develop your current and future state maps, by identifying areas for improvement on the map, documenting a simple idea and placing it on the map.
2. Compare the two maps. For each gap between the current state and the future state, check that at least one burst covers it. Gaps without ideas need more thought.
3. Group the bursts. Put related ideas together, and separate value-added and non-value-added activities, such as waiting: pull and flow, levelling, changeover and batch size, quality loops, information flow, supplier links.
4. Find the dependencies. Some ideas need others first. A smaller batch size needs a faster changeover. A pull system needs a stable rhythm of release.
5. Size each item. Is it a daily kaizen, a one-week event, or a project of several weeks?
6. Set the measure, owner and date. Every item moves one stream measure, such as lead time, inventory days, first pass yield or on-time delivery, and has one named owner.
7. Schedule and review. Put the items on a 30-60-90 day calendar and review them weekly with the stream measures. Each of the value streams in a plant needs its own calendar, but the value streams can share one review slot.

Flow kaizen or process kaizen?

Learning to See separates two kinds of improvement. Flow kaizen is "management doing kaizen": it improves the value stream across departments and is led by management. Process kaizen works at the level of the shop-floor team, on people and process flow. The workbook notes that improvement in one improves the other.

For the list, tag each item. Flow items change how material and information move through the stream: a pull signal between two areas, a levelled release, a shared supplier rhythm. Process items change what happens inside one step: a changeover, a workplace layout, a quality check. A list with only process-level items fixes steps while the stream stays slow. A list with only management-level items misses the daily ideas of the people who run the process.

Which items are events, and which are daily work?

Kaizen is a lean practice of small, practical improvements made close to the work. The LEI defines a kaizen event, also called a kaizen workshop or blitz, as commonly lasting five days. In it, a team identifies and implements a significant improvement in one process. The LEI adds that leaders should not rely on events alone, because daily kaizen develops frontline problem-solving. Use this rule of thumb for sizing:

• Daily kaizen: small fixes the team can make in a shift or a few days, such as moving a tool or changing a sheet.
• Kaizen event: a focused one-week change to one process, with a mixed team and a clear target, such as a changeover.
• Project: a change that needs several weeks and other functions, such as a supermarket with pull signals between two areas.

Give events a follow-up date, so that the gain does not fade. Improvement within a single process can then be repeated by daily work.

How do you rank the ideas?

Score each item for impact on the stream measures and for effort, both from 1 (low) to 5 (high). Divide impact by effort. Then adjust for dependencies and for risk. A high-score item that depends on a slow one should wait.

Include customer value in the impact score: does the change reduce wait times, add value, or remove a non-value-adding activity in the eyes of the customer? Ideas that only make a step look better but leave the lead time unchanged rank low.

Where does the plan fit in lean management?

Value stream mapping, or VSM, is a lean management tool for process mapping at the level of the whole stream, with the flow of information and material on one page. Plain process mapping shows the steps of a business process, while mapping value streams shows the whole flow; VSM adds cycle time, lead time, wait times and inventory, so that you can identify waste and separate value-added from non-value-added activities. Using VSM this way, a team can visualize the current state, optimize the workflow and describe the future state. Mapping the current state with a current state map comes first, and the plan follows from it.

The improvement plan is the bridge from picture to practice. It is where lean methodologies meet daily work, and where a culture of continuous improvement becomes visible. In a plant with several value streams, each of the value streams gets its own one-page plan, and the value streams share one template. Each item is process improvement tied to a measure, and the sum of the items is an optimization of the whole flow, not of single steps. Here people see their ideas on the map, then in the plan, then in the stream measures. Teams that also use Six Sigma may link plan items to their own problem-solving projects; check how your company defines them. Software development teams use similar plans for work items, but this article stays with products that are made. The aim is the same: improve efficiency and deliver value to the customer, whether the output is a product or service.

Example: six bursts, one 90-day plan, invented numbers

This example is invented. The numbers are not from a real plant.

The future state map targets a lead time of 6 days, down from 12. The team has six kaizen bursts, scored as impact divided by effort:

• A. Cut the changeover at the press from 60 to 20 minutes. Impact 5, effort 3, score 1.7.
• B. Halve the batch size at the press. Impact 4, effort 1, score 4.0, but it depends on A.
• C. Pull signals between press and assembly. Impact 5, effort 4, score 1.25.
• D. Release orders daily, not weekly. Impact 3, effort 1, score 3.0.
• E. Fix the rework loop at final test. Impact 3, effort 3, score 1.0.
• F. Standard work at packing. Impact 1, effort 1, score 1.0.

The schedule: in the first 30 days, D (a quick win, no dependency) and A as a one-week event, because B waits for it. In days 31 to 60, B once A holds, and the start of C as a project. In days 61 to 90, finish C, then E, with F as daily kaizen for the packing team. Each item has an owner and a date. Flow items are D, B and C, and process items are A, E and F. The weekly review checks lead time against the target of 6 days, and the stream owner updates the page when A is done and the changeover figure on the map is changed.

Common mistakes

• Too many projects at once. Six to eight active items is a lot for one stream.
• Ideas without owners. An idea that belongs to everyone belongs to nobody.
• Ignoring dependencies. Cutting batches before changeovers costs capacity.
• Events with no follow-up. The gain fades within weeks.
• Only process kaizen. The steps get better, and the stream stays slow.
• No link to the measures. Without a target measure, you cannot show that an item worked.
• Forgetting the map. When items are done, update the map. When the future state is reached, draw a new one.

How software can help

A one-page plan works on paper. When many value streams, owners and items are involved, a shared model helps to keep the plan close to the map and the data. iFAKT's Polaris VSM is a module of iFAKT Polaris for data-based value stream mapping. It models material and information flows collaboratively and makes waste and bottlenecks visible. The plan itself still needs owners, dates and a weekly review.

Next step

A value stream improvement plan works when it is one page, ordered by dependency and owned by named people. This week, list the kaizen bursts from your future state map, score them for impact and effort, and write the first 30 days on one page.