What is a lean stack? Choosing tools by practice

A lean stack is the small set of tools a team uses to run its lean practices, from boards to audits.

Most teams accumulate tools rather than choosing them. A board here, a spreadsheet there, an audit app someone bought for one site. Later, nobody can say which tool holds the truth.

A lean stack is the opposite. It is a small, deliberate set of tools, each chosen for a lean practice your team actually uses. Anything that adds no value is waste, and that includes software.

Start from practice, not from features

A common mistake is shopping for features. Vendors will show you dashboards for practices you don't run yet. Instead, list the practices you already do or are about to start.

For each practice, ask whether paper, a whiteboard or a shared spreadsheet still works. If it does, keep it. Software earns its place when the manual version starts to fail.

That usually happens when the team spreads across sites, when you need history, or when someone spends hours a week on manual reports.

Which lean tools and techniques each practice needs

Daily huddles start on a whiteboard and move to daily management software across shifts or sites.

5S audits start on a checklist and move to 5S audit software when many areas need scheduled checks.

A3 problem solving starts on paper. Kaizen ideas start on an idea board and move to kaizen software when many teams submit ideas.

OEE starts on an hourly tally sheet and moves to OEE software when minor stops matter. Kanban starts on a wall and moves to kanban software for remote teams.

The five layers

Visual management, so everyone can see the work and its status.

Flow measurement, so you know how fast work moves and where it waits.

Problem solving, so issues are fixed at the root.

Standard work, so the agreed method is easy to follow. See standard work.

Improvement management, so ideas and projects are tracked to results. You don't need all five on day one. A team can start with visual management and add the rest as the practice matures.

Example stacks

A small machine shop might run a whiteboard huddle, paper A3s, an OEE tally sheet and a CMMS for maintenance.

A software team might run a kanban tool, a flow metrics add-on and a retrospective tool. A service team might start with a kanban board and a shared spreadsheet for improvement ideas.

Fewer tools, better connected

Every extra tool adds a login, a data model and a place where information can go stale. Before adding one, check whether something you own already covers the practice.

When you do add a tool, make sure it shares data with the rest of the stack. Native integrations help, and clean exports are the minimum.

A useful rule: each piece of information should have one home. If an action from a gemba walk lives in the audit app, the huddle board should link to it.

Pilot, scale or retire

Run any new tool with one team for a few weeks first. Agree in advance what success means, such as shorter huddles or faster responses to ideas.

If the pilot works, write the standard way to use the tool, then scale it. If it doesn't, stop. A sunk cost is not a reason to keep a tool. The lean management guide covers the routines the tools support.

Frequently asked questions