What is lean methodology, and how does it work?

In this article

1. Before you start
2. Why interviewers ask this
3. Lean methodology from first principles
4. Worked example
5. Trade-offs and edge cases
6. How to answer it in an interview
7. Common mistakes
8. Follow-up questions
9. Sources

Before you start

This page sits in the program and project management learning path, part of the wider interview preparation library.

Why interviewers ask this

Lean comes up whenever a candidate says they "improved a process", because the next question is how they knew it was better. Saying "we removed waste" without a measure is the usual place an answer falls apart. A strong answer shows that you can separate real work from waiting, pick one constraint, and prove the change with a number.

A weak answer recites a list of terms and treats lean as cost cutting. A strong answer defines lean from the customer's side, names one concrete waste in a workflow you ran, and states the trade-off of fixing it. A Staff-level answer also says when lean thinking is the wrong tool, for example when the real risk is building something nobody wants. That is where the Lean Startup meaning matters, covered below. Project, program and scrum-master loops all touch this topic; see project manager interview questions and scrum master interview questions.

Lean methodology from first principles

Lean methodology

Lean methodology is a way of thinking and working that starts from what the customer values, looks at the work that creates that value, and keeps removing waste through continuous experiments, so needed value arrives with fewer resources, in factories, offices and product teams alike.

Value stream

A value stream is the full sequence of steps, including the waiting between them, that one piece of work passes through from the customer's request to delivery, written down so that every step can be timed and questioned.

Flow efficiency

Flow efficiency is the share of an item's total elapsed time, from request to delivery, in which someone is actually working on it, found by dividing touch time by lead time. A low value means the item mostly waits.

In plain words

Picture a restaurant order ticket. The cook needs a few minutes to make the dish, but the ticket may sit under a heat lamp far longer waiting for a free pan or a runner. The customer feels the whole time, not the cooking time. Lean asks you to look at the whole journey of the ticket, not at how busy each cook is. The analogy breaks in one place: lean is not only about speed. LEI says lean practice begins with the work and the people doing that work, and describes it as continuous experimentation.

In one precise sentence, lean methodology asks what the customer values, measures how the work flows toward it, and improves that flow by testing changes. Waste is any effort or waiting that adds nothing the customer values. Some necessary work, such as a legal check, adds no visible value either; lean asks you to question it, not to delete it automatically.

Lean grew out of the Toyota Production System (TPS), and the word "lean" was popularised by Krafcik's 1988 article on lean production.¹ Womack and Jones summarised the thinking as five principles: specify value, map the value stream, create flow, establish pull and pursue perfection.² The four steps below follow them in order.

Step 1: Specify value from the customer's side

Lean starts with the customer. LEI says lean thinking always starts there and asks what the customer values, or, stated more concretely, what problem the customer needs to solve. Input: a customer and a request. Output: a plain statement of the outcome the customer wants.

This step matters because waste is defined against value. A report that nobody reads is waste even if it is perfectly formatted, and a review that prevents a defect the customer would have hit is value. Write the value statement before you draw anything else, and write it as a problem the customer has, not as a feature your team wants to build.

You now know what you are measuring against. The next step looks at the work itself.

Step 2: Map the value stream and measure flow efficiency

Mapping the value stream means listing every step from request to delivery and timing two things for each: touch time, the hours someone works on the item, and wait time, the hours it sits idle. Lead time is the total elapsed time from request to delivery, so lead time equals touch time plus wait time.

Then divide. Flow efficiency is touch time over lead time. In the illustrative workflow of the worked example below, work takes 28 hours but the item needs 148 hours to arrive, so flow efficiency is about 18.9%.³ Most of the item's life is waiting, which no amount of "working harder" in a single step would fix. That is the number most candidates cannot produce.

Input: a request and a stopwatch. Output: a timed map where the longest wait is easy to see. You now know where time hides. Next comes changing it.

Step 3: Create flow and establish pull

Creating flow means shortening the biggest waits first. A common lever is limiting work in progress (WIP), the number of items started but not yet finished. A WIP limit is also a pull mechanism: a team starts a new item only when one finishes, so work is pulled by free capacity instead of pushed in. Fewer items in flight means each one waits less in the queue.

The link is Little's Law, a relation from queueing theory (Little, 2011, Operations Research): for a stable system, average WIP equals average throughput times average lead time. Rearranged, lead time equals WIP divided by throughput. Take a separate illustrative team, not the six-stage workflow of the worked example, that finishes 4 items a week. With 24 items in progress its lead time is 6 weeks; cut WIP to 12 at the same throughput and lead time falls to 3 weeks.³ At the same throughput, halving work in progress halves lead time.

Input: the map from Step 2. Output: one chosen change, such as a WIP limit or a faster hand-off. Change one thing at a time so you can tell what worked.

Step 4: Pursue perfection through experiments

Lean treats every change as an experiment. LEI describes lean as a practice of continuous experimentation to achieve perfect value with zero waste, so perfection is a direction, not a finish line. State a hypothesis ("limiting WIP will cut lead time"), run the change, measure with the same stopwatch as Step 2, and keep or drop it. Each change is an experiment, and the loop repeats.

Input: one change and the baseline number. Output: a decision backed by a before-and-after measure, then the next experiment. The loop is why lean is called a practice, not a project: the map you draw is a starting point that you redraw after each change.

1 · Specify value2 · Map the stream3 · Create flow and pull4 · Pursue perfectionReplay

Step-by-step description

1. Start from what the customer values.
2. Time the work and the waits.
3. Shorten the longest wait first.
4. Measure, learn and repeat.

• Lean starts by specifying what the customer values.
• The value stream is mapped and timed, and flow is improved by shortening waits.
• Each change is an experiment, and the loop repeats.

Worked example

A team handles feature requests through six stages. The hours below are illustrative, not measured at any real company. Touch time is 0, 6, 12, 3, 5 and 2 hours across backlog, design, build, review, test and release, a total of 28 hours. Wait time is 40, 16, 24, 20, 12 and 8 hours, a total of 120 hours. Lead time is therefore 148 hours and flow efficiency is 28 divided by 148, or 18.9%.³

The team then attacks the two longest waits it can control: review wait drops from 20 to 4 hours and test wait from 12 to 4 hours. Touch time is unchanged at 28 hours, wait time falls to 96, lead time falls to 124 hours and flow efficiency rises to 22.6%.³

Text description of the diagram

• Touch time totals 28 hours across the six stages.
• Wait time totals 120 hours across the six stages.
• Lead time is 148 hours and flow efficiency is about 18.9%.

Notice what the numbers say. Even after the change, flow efficiency in this illustrative example is only 22.6%, so the item still waits most of the time. A low figure is a place to look, not a score.

Trade-offs and edge cases

Lean has two common meanings, and mixing them up costs points. In operations, lean is about flow and waste in the work. The Lean Startup applies the same spirit to new products: Eric Ries's methodology page describes Build-Measure-Learn, a feedback loop in which a team builds, measures how customers respond, and learns whether to pivot or persevere. It centres on a minimum viable product (MVP), the smallest version that starts that learning, and on validated learning. Validated learning is progress shown by experiments rather than by output.

Text description of the diagram

• Lean thinking starts with the customer.
• The unit of progress of the Lean Startup is validated learning.
• The Lean Startup loop is Build-Measure-Learn.

Edge cases follow. Flow efficiency can look worse after a good change if you start counting waits you used to ignore, so fix the definition before you measure. Little's Law holds for stable averages, so it misleads during a spike or a launch. Pushing flow efficiency to the extreme can leave no slack for urgent work, so lean teams keep a deliberate buffer. And lean is not a headcount plan: LEI defines it as creating needed value with fewer resources and less waste, and says lean practice begins with the work and the people doing that work.

How to answer it in an interview

The spoken structure: define lean from the customer's side, name the measure, give the lever, then state the trade-off.

Common mistakes

• "Lean means cutting costs and people." (wrong) Lean is defined around value and waste, and it begins with the people doing the work. (right) "Lean removes waste from the work so the customer gets value sooner."
• "We removed waste, so it is lean." (wrong) There is no measure. (right) "Lead time fell from 148 to 124 hours in our timed map."
• "Lean and the Lean Startup are the same thing." (wrong) They share a spirit but measure progress differently. (right) "Operations lean tracks flow; the Lean Startup tracks validated learning."
• "Keep everyone 100% busy." (wrong) A busy step can still hold a long queue before it. (right) "I look at the item's journey, not at how busy each person is."

Follow-up questions

What is lean methodology in project management?

It means treating the project as a value stream: define what the customer values, time the stages and the waits between them, and improve the longest wait first. See the wider program and project management guide for the surrounding questions.

What is waste in lean?

Waste is effort or waiting that adds nothing the customer values. Ohno's seven wastes are transport, inventory, motion, waiting, overproduction, over-processing and defects, and many lists add an eighth, unused talent.⁴ In the worked example, 120 of 148 hours are waiting, the biggest candidate for removal.³

What is the difference between lean and Agile?

Lean describes a way of thinking about value, flow and waste, framed by LEI as thinking and practice. Agile is iterative, incremental delivery, as set out in the Agile Manifesto (2001).⁵ Agile approaches such as Scrum add specific roles and routines, while Kanban, a visual board with WIP limits, is a lean-derived practice that software teams use; the scrum master question guide covers those.

What is the Lean Startup method?

It is a loop of Build-Measure-Learn that uses an MVP and validated learning to decide whether to pivot or persevere, as described on the Lean Startup methodology page.

Is lean only for manufacturing?

No. LEI describes lean practice for physical or knowledge work, and for both ongoing firms and startups. A business analyst mapping a request process is doing the same thing; see business analyst interview questions.

Sources

1. What is Lean? — Lean Enterprise Institute, 27 Jan 2023
2. Little's Law as Viewed on Its 50th Anniversary — Operations Research, vol. 59 no. 3, May-June 2011 (J. D. C. Little), 1 May 2011
3. The Lean Startup: Methodology — Eric Ries, The Lean Startup, 26 Oct 2026