Value Stream Review Meeting: Agenda, Questions and Rules

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

A value stream review is a weekly meeting where the owner and function leads check flow metrics, walk the stream and follow actions. Get the agenda and rules.

A value stream review is a fixed weekly meeting where the owner of a product family and the leaders of the functions check the flow measures, look at the value stream map and follow up the improvement actions. It takes 45 minutes at a board near the shop floor, not in a meeting room. This article is for lean managers who start or repair this meeting. It gives an agenda with timings, questions to ask, rules that keep the meeting short and an example with numbers.

Key points

• A value stream review is a fixed weekly meeting, led by the stream owner, that looks at flow measures, the value stream map and the open action list.
• A 45-minute agenda works: last week's actions, flow measures, a look at the stream, problems and decisions, and new actions with owners and dates.
• Jim Womack's ten value stream walk questions are a good source for review questions, such as who owns the stream and where the pacemaker is.
• Rules keep the meeting short: start on time, bring facts from the floor, assign every action an owner and a date, and escalate what cannot be solved.
• The weekly review complements the daily tier meeting; it looks at the whole stream, not at one area.

What is a value stream review?

A value stream review is the routine of value stream management. Mapping shows how the flow works and how it should work. The review makes sure the plan happens. Without it, the map hangs on the wall and the actions slip.

The review looks at three things:

• The measures. A few flow metrics of the whole stream, such as lead time, cycle time, on-time delivery and inventory.
• The map and the plan. The current state, the future state and the action list that connects them.
• The stream itself. What the owner and the team saw on the floor this week.

The Lean Enterprise Institute (LEI) workbook Learning to See says that the value stream manager leads the maps and the implementation plan, monitors implementation and walks the flow daily or weekly. The review is where that monitoring becomes visible to the functions.

Keep the value stream map at the board. Print the current-state value stream map and the future-state value stream map in A3 size, and mark changes on the value stream map during the review. A value stream map that nobody updates loses trust quickly. In VSM terms, the review keeps the map alive. If your plant runs several value streams, give each of the value streams its own map and its own board. In lean principles, an operational value stream is the set of steps that create value to customers from order to delivery, and every step in the process belongs on the map.

Why does the review matter?

The concept of a value stream helps leaders see the customer experience from order to delivery: how the stream can deliver a product or service on time, and how value delivery looks from the customer's side. It shows the flow of value, step by step, and how long it takes. The benefits of value stream management only show if the routine runs. In lean manufacturing, value streams are improved step by step, and each step needs a check: did the change add value for the customer, and did it reduce a type of waste, such as waiting? A weekly review is that check. It supports continuous improvement and process improvement because it links each action to a result in the stream's metrics, such as lead time and cycle time. It also keeps teams on customer value, not on local numbers.

VSM teams in software delivery run similar reviews, but they track work items. Here the stream delivers a product or service made of material. Over time, the review helps you optimize the value stream map itself: when the stream changes, the map changes. Several value streams in one plant can share the same agenda and board layout, which makes it easier for leaders to move between reviews.

Who attends and how often?

The owner of the stream chairs the meeting. Others attend because they own a part of the flow or an open action:

• Production, planning, quality, maintenance and logistics, one leader each
• Anyone who owns an overdue or due action
• Finance, if you want it, once a month

Keep the group small. If everyone cannot stand around a board, it is too large.

Weekly is a good starting rhythm for a stream with short lead times, because a week shows a trend and does not leave actions to cool. That is my planning suggestion, not an LEI rule. Streams with long lead times can review every two weeks and still walk the flow in between. The LEI ebook on value stream mapping notes that Toyota reviews takt time for each process monthly, with tweaks every ten days, which shows that review cycles can differ by topic.

The review does not replace the daily tier meeting. A tier meeting is short, at a board, in stacked levels from team to plant. The weekly review looks at one product family from end to end.

What is the agenda?

This 45-minute agenda is a sample. Adapt it to your stream.

1. Last week's actions (10 minutes). Go through the action list. Done, not done, new date. Do not discuss solutions here.
2. Flow measures (10 minutes). Compare the actual with the target for lead time, on-time delivery, inventory and quality. Look at the trend of the last weeks, not only the last value.
3. Walk the stream (10 minutes). The owner reports what the team saw on the floor: where material waited, where the wait time was longest, where a handoff failed. Stand at the value stream map and mark the places.
4. Problems and decisions (10 minutes). Name the problems that need a decision from the functions. Decide, or assign an owner to bring a proposal next week.
5. New actions (5 minutes). Write each action with an owner and a date. Read the list back.

Keep one rule for timing: if a topic needs more than five minutes, it becomes an action and moves to a separate session.

Which questions should you ask?

Jim Womack of the LEI describes a value stream walk in which he picks one product family, follows it from the customer back to receiving and asks managers ten questions. Several of them work well as standing questions for a review:

• Who is responsible for the product's value stream?
• How are customer orders received?
• Where is the pacemaker process, and what triggers it?
• How are orders sent upstream from the pacemaker?
• How are materials supplied to assembly and to the processes feeding it?
• How are employees trained and motivated in lean methods?

Womack stresses checking what managers say against what you see on the floor. At the firm in his article, the walk showed that nobody owned the value stream.

Add questions of your own for the weekly rhythm:

• Where did the product wait longest this week, and why?
• Which action would move the lead time most, and is it on track?
• What did we learn from the last change?
• What do we need from another function?

Rules for the meeting

1. Start and end on time. A 45-minute meeting that runs for 90 minutes will lose its attendees.
2. Bring facts from the floor. Numbers come from the stream, and the owner has walked it.
3. One owner and one date per action. "The team" is not an owner.
4. Problems, not blame. The question is "what stopped the flow?", not "who failed?".
5. Escalate what you cannot solve. If a function cannot decide, the owner takes it to site management with the facts.
6. Keep the board current. Update the measures and the map before the meeting, not during it.

Example: week 14 with numbers

This is an invented example for one stream. The numbers are not from a real plant.

The target for the stream is a lead time of 10 days and on-time delivery of 95 percent. In week 14, the actual lead time is 12 days and on-time delivery is 91 percent. Inventory is flat.

The action list has nine open actions. Five were due this week and three were done on time, so the on-time completion of actions is 3 divided by 5, or 60 percent. The two late actions are a changeover standard in the washing area and a new order release time.

On the walk, the owner saw a batch wait two shifts in front of the wash station because its release arrived late. The team puts a mark on the map at that point. The decision for the week: planning moves the release to the first shift, and maintenance reports on the washing line's availability next week. The owner writes three new actions with names and dates. The next review starts with those three.

Common mistakes

• Turning the review into a status report. The review is for decisions and actions.
• Reviewing measures with no link to the map. Always ask where in the stream the number comes from.
• Letting the meeting drift to firefighting. Daily problems belong at the tier meeting.
• Skipping the walk. Without a look at the floor, the review turns into opinion.
• No follow-up. Actions without owners and dates fade.
• Too many attendees. Fifteen people cannot decide anything in 45 minutes.

How software can help

A review works with paper and a board. Value stream management software and VSM software exist for plants too, but treat them as tools for the data, not as a replacement for the routine. Software helps when the data for the measures sits in several systems and takes hours to collect each week. It also helps when the actions of the plan must reach the shop floor and come back with progress, so the review discusses facts and not memories.

iFAKT's Polaris Operator is a module of iFAKT Polaris that brings production plans to the shop floor as time-based tasks and feeds progress back to planning in real time. In a team that works with software development tools, the same idea exists as a workflow board; for a plant, the board must show orders, not tickets.

Next step

A value stream review works when it is short, fixed in the calendar and tied to an action list. This week, book the first 45-minute review for one product family, print the agenda above and prepare the three flow measures and the map.