Yellow Belt Improve Phase Walkthrough Tools Steps SMART Goal and Tollgate Questions

The Improve phase is where a Yellow Belt team stops explaining the problem and starts changing the process. The risk is moving too fast. A team can jump to a favorite fix, train people on the wrong behavior, or install a new step that helps one metric while hurting another.

A strong Improve phase keeps the team focused on the verified root causes from Analyze. The team creates solution ideas, chooses the best ones, tests them, measures the results, and prepares the process for Control.

This walkthrough uses one SMART goal throughout:

By June 30, 2026, increase the same-day shipment rate for eligible technician parts orders at the main parts warehouse from 82% to at least 95% by implementing improvements and staffing training to enhance operational efficiency and customer satisfaction.

The Improve phase starts where the work actually happens.

What the team does in the Improve phase

In the Improve phase, the team turns root cause findings into tested process changes. The main question changes from “Why is this happening?” to “What change will close the gap without creating new problems?”

For the same-day shipment goal, the team has already defined the problem and measured the baseline. The process ships 82% of eligible technician parts orders on the same day. The target is at least 95% by June 30, 2026.

During Improve, the team typically does the following work:

• Confirms the highest-impact root causes from Analyze

• Creates possible solutions for each root cause

• Screens solutions for impact, effort, cost, risk, and speed

• Runs small pilots before full rollout

• Updates work instructions, staffing plans, and training

• Measures pilot results against the SMART goal

• Chooses final improvements for Control

  
  

A Yellow Belt team should keep the scope tight. If the main parts warehouse is the scope, do not redesign the entire supply chain. If eligible technician parts orders are the order type, do not mix in every order category unless the data supports it.

The Improve phase tools Yellow Belts use

Yellow Belts do not need complex statistical tools to lead useful improvement work. The best tools make choices visible and prevent guesswork.

Common Improve phase tools include:

Tool	What it helps the team do	How it applies to the shipment goal
Brainstorming	Create solution ideas	Generate ways to reduce missed same-day shipments
Root cause and solution matrix	Link each solution to a verified cause	Prevent fixes that do not address the real problem
Impact and effort matrix	Sort quick wins from major projects	Choose changes that can lift the rate before June 30, 2026
Pugh matrix	Compare solution options against criteria	Select the best staffing or picking method
Prioritization matrix	Score ideas using weighted criteria	Balance shipment impact, cost, training time, and risk
Pilot plan	Test changes on a small scale	Try a new order cut-off review for one shift
Standard work	Make the improved process repeatable	Define how eligible orders are picked, packed, and staged
Training plan	Build staff capability	Train warehouse staff on order priority rules
Mistake-proofing	Reduce the chance of errors	Use visual flags for eligible same-day orders
Before and after data chart	Track whether the change works	Compare same-day shipment rate before and during pilot

The tools are simple, but the discipline matters. A team should not pick solutions based only on who speaks first or whose area owns the process.

Analyze phase tollgate questions before Improve

Before moving into Improve, the team should pass an Analyze tollgate. This review confirms the team understands the problem well enough to start testing solutions.

Use these questions to check readiness:

1. Has the team confirmed the problem with data?

   The baseline should be clear. In this example, the same-day shipment rate is 82% for eligible technician parts orders.

   
   

2. Is the defect or failure clearly defined?

   Define what counts as a missed same-day shipment. For example, an eligible order that was received before the cut-off but did not ship that day.

   
   

1. Has the team verified the main root causes?

   Root causes should come from data, process observation, and team input, not opinion alone.

   
   

2. Does the team know where in the process the failures occur most often?

   Misses may happen during order release, picking, packing, staging, carrier handoff, or staffing handoff.

   
   

1. Has the team segmented the data?

   The team should review patterns by shift, order type, part location, day of week, cut-off time, and staffing level if available.

   
   

2. Are the root causes within the project scope?

   If the root cause is a supplier shortage outside the warehouse, the team may need a separate project or escalation.

   
   

1. Has the team identified which causes have the largest effect on the goal?

   The Improve phase should focus on the few causes that explain the biggest share of missed shipments.

   
   

2. Are customers and process stakeholders aligned on the goal?

   For this project, stakeholders may include warehouse leads, technicians, dispatch, customer support, inventory control, and shipping staff.

   
   

1. Are data collection methods reliable enough to compare before and after results?

   If the team cannot trust shipment timestamps or eligibility flags, pilot results will be hard to judge.

   
   

10. Has the team documented risks or constraints?

Examples include labor availability, carrier pick-up times, system limitations, and training windows.

Visible process flow helps the team connect causes to missed shipments.

Decision matrix for moving from Analyze to Improve

The decision matrix below helps a Yellow Belt team decide whether it is ready to move forward. Score each item as 0, 1, or 2.

• 0 means not ready

• 1 means partly ready

• 2 means ready

  
  

A practical rule is to move to Improve only when the total score is 16 or higher out of 20, with no score of 0 on root cause verification, data reliability, or project scope.

Readiness criterion	0 points	1 point	2 points	Score
Problem statement is clear	Vague or debated	Mostly clear but needs edits	Clear and agreed upon
SMART goal is documented	Missing or incomplete	Present but not fully measurable	Clear, measurable, dated, and scoped
Baseline is verified	No trusted baseline	Baseline exists with some questions	Baseline is trusted and repeatable
Root causes are verified	Based on opinion	Some data support	Strong data and observation support
Process map is complete	Missing key steps	Shows main steps only	Shows key inputs, handoffs, and failure points
Data is segmented	No segmentation	Some segmentation	Segmented by useful categories
Scope is controlled	Too broad or unclear	Mostly clear	Clear boundaries and exclusions
Stakeholders are aligned	Major disagreement	Minor open concerns	Agreement on problem and next step
Constraints are known	Not discussed	Some constraints listed	Key risks, limits, and dependencies listed
Improve team is ready	No owner or capacity	Partial team availability	Owners, time, and pilot area identified

For the warehouse shipment example, the team should not move to Improve if it only knows that “orders ship late.” It should know which orders, when they miss, where delays occur, and which causes are most likely to prevent the 95% target.

Step by step Improve phase walkthrough using the SMART goal

Step 1. Restate the goal and the verified root causes

Start the Improve phase by restating the goal in plain language.

The team wants to raise the same-day shipment rate for eligible technician parts orders from 82% to at least 95% by June 30, 2026.

Then list the verified root causes from Analyze. For this walkthrough, assume the team found these causes:

• Eligible orders are not always flagged clearly in the warehouse system

• Pickers do not always know which orders must ship the same day

• Staffing dips during the afternoon shipping window

• Some high-demand parts are stored far from the packing area

• Training on eligibility rules varies by shift

  
  

Each potential solution should connect to one or more of these causes.

Step 2. Brainstorm targeted solutions

The team should brainstorm fixes without judging them too early. The goal is volume first, then selection.

Possible solutions may include:

• Add a visual priority flag for eligible same-day orders

• Create a dedicated same-day order lane

• Move high-demand technician parts closer to packing

• Assign a trained same-day order coordinator during peak hours

• Cross-train backup staff for afternoon shipping

• Create a short standard work checklist

• Add an hourly review of unshipped eligible orders

• Adjust lunch and break coverage during the shipping window

• Build a daily missed shipment review

  
  

This is where the Yellow Belt Improve Phase Walkthrough Tools Steps SMART Goal and Tollgate Questions become practical. Every tool should help the team choose and test changes that support the target, not just create more documentation.

Step 3. Link solutions to root causes

A root cause and solution matrix keeps the team honest.

Verified root cause	Possible improvement	Expected effect
Eligible orders are not clearly flagged	Add visual and system priority flag	Fewer orders missed because staff can identify them faster
Pickers do not know same-day priority	Train staff on priority rules and order flow	Better decisions during busy periods
Staffing dips in afternoon	Adjust coverage and cross-train backup staff	More capacity before carrier cut-off
High-demand parts are stored far away	Relocate top technician parts closer to packing	Shorter pick time for common orders
Training varies by shift	Standardize work instructions and training checklist	More consistent performance across shifts

If a proposed solution does not connect to a verified cause, set it aside.

Step 4. Prioritize solutions with an impact and effort matrix

Next, sort ideas by expected impact and effort.

Solution	Impact	Effort	Decision
Visual priority flag	High	Low	Pilot first
Hourly review of unshipped eligible orders	High	Low	Pilot first
Cross-train backup staff	High	Medium	Plan pilot
Relocate high-demand parts	Medium	Medium	Test with selected parts
Build new warehouse software feature	High	High	Consider later
Redesign full warehouse layout	Unknown	High	Out of scope for this project

The team should favor changes that can improve the metric before the goal date. A full system rebuild may help one day, but it may not be the right Improve phase action for this Yellow Belt project.

Pilots work best when changes are easy to see and measure.

Step 5. Select the best package of improvements

Most process problems need a small package of changes, not one isolated fix. For the shipment goal, the team may choose this improvement package:

1. Add a clear same-day eligibility flag in the order queue and on printed pick documents

2. Create a dedicated staging area for eligible technician parts orders

3. Start an hourly review of eligible orders not yet shipped

4. Move the top high-demand technician parts closer to the packing area

5. Train all relevant staff on the new flow, priority rules, and escalation steps

6. Adjust afternoon coverage so trained staff are available near the shipping cut-off

   
   

This package addresses visibility, flow, part location, staffing, and training.

Step 6. Build a pilot plan

A pilot tests the improvement before full rollout. Keep it small enough to manage but large enough to learn from.

A good pilot plan includes:

Pilot element	Example for the warehouse project
Pilot area	Main parts warehouse, eligible technician parts orders only
Pilot duration	Two to four weeks, depending on order volume
Start date	Set after training and materials are ready
Owners	Warehouse lead, Yellow Belt project lead, shipping lead
Measures	Same-day shipment rate, missed eligible orders, pick time, rework
Data source	Shipment timestamps, order eligibility flag, daily review log
Success target	Improvement toward 95% without added quality issues
Stop condition	Errors rise, staff cannot follow the process, or customer impact worsens

The team should collect before and after data the same way. If the baseline used end-of-day shipment data, use the same method during the pilot.

Step 7. Train staff on the new standard work

Training should focus on the few behaviors that matter most.

For this example, training should cover:

• How to identify eligible technician parts orders

• Where same-day orders are staged

• When hourly checks happen

• Who handles escalation if an order may miss the cut-off

• How backup staff support the process

• How to record missed shipments and reasons

  
  

Keep training practical. Walk through real orders. Show the priority flag. Let staff practice moving an order from release to shipment.

A simple checklist helps:

Standard work step	Done
Check eligible order queue at the start of the hour
Pick flagged same-day orders before nonurgent work
Stage completed orders in the same-day lane
Review unshipped eligible orders before carrier cut-off
Escalate blocked orders to the shift lead
Record any missed same-day shipment reason

Step 8. Measure pilot results and adjust

During the pilot, the team should review data often. Do not wait until the end to notice that the process is not working.

Track:

• Daily same-day shipment rate

• Number of eligible orders

• Number of missed eligible shipments

• Top reasons for misses

• Staff coverage during peak hours

• Any quality or picking errors

  
  

If the rate rises from 82% to 90%, the team has progress but not yet enough. The missed shipment reasons will guide the next adjustment. Maybe flags work, but afternoon coverage still fails. Maybe training improved one shift but not another.

Improve is an active phase. The team tests, learns, changes, and tests again.

What readiness for Control looks like

The Improve phase is complete when the selected changes are proven, documented, and ready to hold.

For the shipment example, the team may be ready for Control when:

• Same-day shipment performance is trending at or near 95%

• Staff can explain and follow the new process

• Missed shipment reasons are tracked consistently

• Standard work is updated

• Training records are complete

• Process owners accept responsibility for ongoing monitoring

• A control plan is drafted with response actions

  
  

Control becomes easier when the improved process is visible and repeatable.

Key takeaway

A Yellow Belt Improve phase should be practical, data-based, and tightly connected to the goal. For the warehouse shipment project, the team does not need a large redesign to make progress. It needs verified causes, focused solutions, a careful pilot, clear training, and steady measurement.

The best next step is to use the Analyze tollgate questions and readiness matrix before launching Improve. If the team scores well, begin with a small pilot tied directly to the SMART goal. If the score is weak, fix the gaps first. That discipline prevents wasted effort and gives the team a better chance of reaching 95% same-day shipment performance by June 30, 2026.