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.

Not the LEANSTACK company

The phrase is also a brand. LEANSTACK is the company of Ash Maurya, author of Running Lean and creator of the Lean Canvas, a one-page business model for startups. If you came for the canvas, the Lean Canvas template guide covers it.

This guide uses lean stack in its plain sense: the set of tools behind a team's lean practices. lean-stack.io is an independent directory and is not connected with LEANSTACK.

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.

That last cost is easy to underestimate. The McKinsey Global Institute estimated that interaction workers spend nearly 20% of their time looking for internal information or tracking down colleagues who can help with a task.

Research backs putting the practice first. In a 2012 American Economic Review study, Nicholas Bloom, Raffaella Sadun and John Van Reenen found that US multinationals got higher productivity from IT than non-US multinationals, mainly because of their people management practices.

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.

Tools are only one part of the stack

Which lean technique fits which problem

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.

A startup testing a product idea might run a lean canvas, interview notes, an assumption list, landing page tests and a weekly learning review. A marketing team trying a new campaign might keep message tests, campaign metrics and a short decision log, so it scales only what works.

A worked stack decision

An illustrative case shows the order of decisions. A 60-person plant wants better OEE numbers.

Step 1, the practice: shift leads already record downtime by hand, so the practice exists. Step 2, the failure: three spreadsheets give three different totals, and someone spends an hour each Monday merging them.

Step 3, the smallest fix: one shared sheet with fixed reason codes, owned by the production manager, tried for a month. Step 4, the check: if the total is trusted and the Monday hour is gone, stop there.

If minor stops still go unrecorded, because nobody can log a 2-minute stop by hand, that is the point where OEE software with machine signals earns a pilot. The OEE guide shows the hourly sheet to start from.

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.

Audit the tools you already have

Before buying anything, list what you already run. A one-page tool audit has five columns: the tool, the practice it supports, its owner, where its data lives, and a decision to keep, replace or retire it. Fill one row per tool, including spreadsheets and whiteboards.

An illustrative audit for the same 60-person plant: a whiteboard for huddles (keep), three OEE spreadsheets kept by different shift leads (replace, because nobody trusts the totals), a 5S audit app that only one area uses (retire, or roll it out properly), a CMMS for maintenance (keep), and an idea box emptied twice a year (replace with a weekly idea board review).

Rows with no owner, and two tools holding the same data, are the first to fix.

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.

Common lean stack mistakes

Signs your lean stack is working

Frequently asked questions