Key Takeaways
Count the unpaid work hidden between buying a product and solving a problem
Buying is only the start. Consumption is the chain of actions needed to solve a problem: researching, purchasing, installing, combining, maintaining, repairing, upgrading, and disposing of goods and services. The authors call a better-designed version of this process lean consumption. Their computer example makes the hidden workload visible. A purchase that seemed to require about three and a half hours instead consumed 11.5 hours over seven days, including software conflicts, help-line calls, and two experts. Only four of the eleven steps helped create value; the rest were wasted effort or delay.
Time belongs in the bill. A low sticker price can conceal substantial costs in customer time, uncertainty, and frustration. Owning a computer was not the real goal; getting reliable tools for writing and image work was.
What's striking is how self-service can make a provider's accounts look lean while shifting work onto customers. The same pattern appears whenever users must configure, troubleshoot, or coordinate products from separate suppliers. Measuring only labor inside the firm misses this transferred burden. Yet customer time is not a uniform unit: an hour of predictable, convenient activity differs from an hour spent waiting for an uncertain repair. Good service design therefore needs to track both elapsed time and the stress, uncertainty, and effort that make time costly.
Map both sides of the repair to expose where good people get trapped
Follow the whole journey. A consumption map records the customer's steps; a provision map records the provider's work. Together, they show the full value stream, meaning the connected actions that must occur to solve the customer's problem. In the book's car-repair example, Bob spent 210 minutes across 16 steps, including a return visit because the first repair failed. Just 58 minutes created value; 152 minutes were wasted. The dealer's staff spent 220 minutes across 29 steps, but only 35 minutes directly helped fix the car.
Blame hides the mechanism. Customers may see incompetent or dishonest employees, while staff see demanding customers. The maps reveal a shared process full of queues, handoffs, missing parts, and rework. Those defects frustrate both sides and invite mutual blame.
This is a practical application of systems thinking: outcomes often reflect the structure of work more than the character of the people inside it. A map makes invisible handoffs discussable and gives different teams a shared object to improve. The method is strongest when observation includes customers and frontline staff, not just managers describing how work is supposed to happen. A map can still mislead if it treats every customer's priorities as identical, so measures should include reliability and experience as well as minutes and cost.
Reward problems prevented, not complaints repeatedly processed by the help desk
Fix the source of failure. Intelligent feedback means using each reported problem to identify its underlying cause, correct it, and prevent the same failure from recurring. At airline BMI, printer faults caused 26 percent of help-desk calls because check-in staff could not print boarding passes and baggage tags. Fujitsu Services traced the repeated complaints to printers poorly suited to their actual setting. After replacement printers were introduced, calls about them fell by more than 80 percent, and repair response time dropped from ten hours to three.
Change the incentive too. Fujitsu shifted from charging for each call handled to an annual fee based on the number of potential users. As recurring problems disappeared, total calls fell 40 percent in 18 months, while staff turnover dropped from 50 percent to 8 percent. Employees could solve causes instead of racing through scripts.
The case shows how a metric can quietly define the work. Pay by the call, and every recurring complaint generates revenue; pay for coverage, and prevention becomes economically sensible. This is a classic incentive-design problem: people respond to what a contract rewards, not only to what a mission statement says. The approach also improves job quality by giving frontline staff a route to technical decision-makers. A caveat is that call volume alone is not proof of resolution. Independent measures of service quality are needed to ensure fewer calls mean fewer failures, not harder access to help.
Treat customer time as a cost your process must eliminate
Make work predictable. The authors argue that pushing employees to work faster can create mistakes and repeat work. Better results come from understanding why people wait, then preparing the right information, tools, and parts before a job begins. At Portugal's Grupo Fernando Simao, technicians diagnosed vehicles before repair, assembled parts into job-specific kits, and scheduled work in smoother flows. The company cut the average customer's time nearly in half, reduced service costs by 30 percent, and needed 75 percent fewer loaner cars. Repairs completed correctly and on time rose from about 60 percent to more than 80 percent.
Give patients access, too. Physician Mark Murray's open access approach let patients request a same-day appointment with their own doctor instead of joining a long queue for a future slot. Longer appointment windows also reduced delays and after-hours paperwork.
The important shift is from managing utilization to managing flow. A busy technician or doctor is not automatically productive if patients and jobs accumulate in queues. This connects lean service design to queueing theory, where high utilization can produce sharply longer waits when demand varies. Same-day access is not a universal answer: emergencies, specialist capacity, and clinical judgment still matter. But the example asks a useful question: is a backlog evidence of too little capacity, or of a scheduling system that simply pushes today's work into tomorrow?
Let checkout data trigger small, frequent replenishment loops upstream
Follow actual purchases. A pacemaker is the single point in a provision system that sets the pace for replenishment. Tesco used checkout sales to signal how much cola to restock, rather than letting separate forecasts and batch orders compete across the supply chain. Goods moved from the bottling plant through the distribution center toward stores in frequent, smaller deliveries. Product handling fell from 150 touches to 50, and the supplier-to-store journey shortened from 20 days to five. Availability rose from 98.5 percent to 99.5 percent.
Measure the basket, not the shelf. Basket fulfillment is the chance that a shopper can find all the items needed on one trip. In a typical 40-item grocery basket, 92 percent availability per item implies only about a 4 percent chance of finding everything. Tesco's approach aimed to raise basket fulfillment as the system expanded across products.
The core insight resembles the bullwhip effect in supply chains: small fluctuations in customer buying can become exaggerated orders as each organization forecasts and protects itself. A direct replenishment signal reduces guesswork and makes responsibility clearer. The system depends on dependable production, frequent transport, and cooperation between firms; it is not simply a command to carry no inventory. Small buffers can protect service when supply or demand is volatile. The relevant comparison is total system cost and availability, not whether any single warehouse or delivery route appears more expensive.
Serve changing circumstances with several formats, not fixed customer stereotypes
The same shopper changes context. A person may want a low-price bulk shop one day, a nearby store the next, and home delivery during a busy week. The authors call attention to circumstances, not just demographic categories, when designing retail services. A Tesco Extra carried more than 80,000 stock-keeping units, while a household typically bought fewer than 300 distinct grocery items in a year. The vast majority of the assortment was irrelevant to that household on any given trip, and the distant store consumed time to navigate.
Share the supply system. Tesco developed large, medium, small, and online formats, backed by common purchasing and replenishment. That let customers choose convenience or range without forcing the company to build a separate supply chain for every format. The store should fit the shopper's situation, rather than dictate it.
This reframes segmentation as a changing decision rather than a permanent identity. A customer is not simply a price shopper or a convenience shopper; time pressure, task, and location alter what counts as value. That insight supports service design across retail, transport, and healthcare. It also raises a modern concern: detailed purchase histories can make services more relevant while concentrating sensitive information in the retailer's hands. Personalization earns trust only when customers understand what is collected and retain meaningful control over its use.
Price the customer's wait so planners and urgent buyers can both win
Not everyone needs it now. For major purchases, people often think ahead but have no way to share those plans with providers until they are ready to buy. The authors propose two clear options: a lower price for delivery scheduled in advance, and a higher price for a faster, priority slot. The advance notice lets providers smooth production, avoid costly expediting, and reduce finished-goods inventory. Customers with urgent needs can still request speed, rather than being pushed toward whatever happens to be in stock.
Do not promise magic. A custom car could not realistically be made and delivered in three days using the industry's existing designs and supply networks. The book estimates that even regional production requires at least a month. Honest lead times and a real choice are better than an instant-delivery promise the system cannot keep.
This is a useful match between capacity planning and consumer choice: time-sensitive customers pay for scarce flexibility, while planners receive information from customers willing to wait. The airline industry's advance-purchase fares offer a familiar analogy, though the authors adapt the idea to delivery timing. The fairness question matters. Dynamic pricing can make urgency expensive precisely when a customer has little choice, such as after a breakdown. A sound version needs transparent terms, reliable promised dates, and a reasonable service option for people unable to plan.
Put a process owner above silos, and give employees the map
Start with observed work. The authors argue that improving a department in isolation can leave the customer's overall problem untouched. A small, senior-backed team should walk the process from the customer's first need through delivery and support, document what actually happens, and design a better future process. The people doing the work need to help create it so they can see the whole system and understand why changes matter.
Make improvement visible. Toyota's A3 Report condenses a problem, current conditions, a proposed future state, assigned actions, and timing onto one sheet. The book also stresses candor about job consequences. Efficiency gains should support growth where possible; if layoffs are unavoidable, managers should say so clearly rather than letting employees expect each round of cuts to be the last.
The proposal is less about adding another improvement department than giving someone authority to connect work across departments and firms. It also addresses a common weakness of reorganizations: employees are asked to follow a new process without seeing its logic or having a voice in its design. A one-page report can focus attention, but it cannot substitute for authority, resources, or honest leadership. Cross-company processes pose the hardest test because no single manager controls every participant or incentive.
Bundle recurring needs into solutions, but preserve choice and exit
Sell the outcome, not the pile of parts. The book's proposed solution economy shifts the focus from buying separate products and services to having a provider manage a recurring problem. It identifies six broad needs: communication and information, shelter, healthcare, mobility, financial management, and routine shopping and delivery. A mobility provider, for example, could coordinate vehicles, maintenance, insurance, and replacement rather than leaving each task to the driver. In industry, engine makers already offer aircraft operators maintenance and power by the hour, taking responsibility for more of the asset's life cycle.
Coordination has a price. A solution provider can reduce the customer's research, handoffs, and upkeep, while using long-term knowledge to prevent failures and plan demand. But the model requires trust, reliable performance, strong privacy protections, and a practical way to switch providers. Without those safeguards, convenience can become dependence.
The ambition is to make comprehensive service available beyond wealthy households that can hire personal staff to coordinate everything. The economic logic is plausible: a provider responsible for long-term performance has an incentive to reduce failures and waste, rather than profit from selling replacements or repairs. Yet bundling shifts power as well as workload. Providers may control customer data, service access, and the terms of exit. Portability, transparent pricing, and alternatives are not decorative protections; they determine whether an integrated solution remains a partnership or becomes a captive relationship.
Analysis
Lean Solutions changes the unit of analysis from the object sold to the full sequence of work needed to make that object useful. That shift matters because a transaction can appear efficient to a provider while consuming hours of customer effort after the sale. The book's distinctive contribution is to connect two processes usually treated separately: consumption, the customer's effort to solve a problem, and provision, the organization's effort to deliver value. Mapping both makes the costs of waiting, rework, poor availability, and handoffs visible to parties who otherwise blame one another.
Its strongest cases turn abstract lean principles into changes in incentives and flow. Fujitsu's help desk improved when it earned from coverage rather than call volume. Tesco's supply chain improved when checkout sales guided replenishment. The Simao dealerships reduced customer burden and operating costs together. These examples support a persuasive thesis: service quality and efficiency need not be opposing goals when the process itself is redesigned.
The book is also more than an operations manual. Its proposed solution economy asks who should bear the work of coordinating complex modern life. Bundled, lifecycle services could reduce duplicated effort and reward durability, but they also concentrate information and control. The authors recognize privacy and lock-in, yet these are structural issues, not minor implementation details. A provider with more knowledge and fewer rivals can become difficult to discipline.
Some projections, including near-instant replenishment and broad consumer solutions, depend on cooperation, reliable data, and infrastructure that the book's 2005 examples do not establish as universally available. Nor is every customer burden waste: some people value browsing, ownership, repair, or hands-on control. The lasting lesson is therefore not that every activity should be outsourced or automated. It is that firms should distinguish chosen effort from imposed effort, measure the entire journey, and make the party best positioned to prevent a failure responsible for doing so. Lean provision is compelling when it reduces avoidable work without taking away meaningful choice.
Glossary
Lean consumption
Problem-solving with less burdenA way of organizing consumption around the complete problem a person wants solved, rather than around the purchase of one product or service. It seeks to reduce the customer's time, effort, and hassle across the full sequence of searching, obtaining, installing, maintaining, repairing, upgrading, and disposing.
Lean provision
Delivering value with less wasteThe provider-side process for supplying what customers need, where and when they need it, without making them perform unnecessary coordination. It includes all steps required to deliver value, often across several departments and companies, and aims to reduce wasted labor, delay, excess inventory, and customer burden.
Consumption map
A map of customer stepsA visual record of the steps a customer takes to solve a problem, from initial search through use and eventual disposal. It can show time spent, which activities create value, where waiting occurs, and how the customer experiences each step. Paired with a provider map, it reveals the complete process.
Intelligent feedback
Use failures to remove causesA method of treating each customer complaint or support request as information about the underlying process. Skilled staff investigate the customer's actual purpose, connect the reported failure to its source, and help the organization make a permanent correction rather than repeatedly resolving the same symptom.
Basket fulfillment
Availability of the whole shopping listThe likelihood that a shopper can obtain all the items needed for a particular shopping trip, rather than the availability rate of any single item. Because a basket contains many products, even a high in-stock rate for each product can still yield a low probability that the full basket is available.
pacemaker
Single point setting replenishment paceThe one point in a provision stream where actual customer demand sets the schedule for upstream replenishment. In retail, checkout sales can serve this function: each stage replaces what the next stage has just used, limiting conflicting forecasts and unnecessary stock.
Open access
Same-day access to one's doctorA healthcare scheduling approach in which patients who need their own physician can request an appointment for the same day, rather than joining a long queue for a future date. The approach requires managing demand and appointment lengths so that current work is handled promptly and delays do not accumulate.
A3 Report
One-page process improvement planA Toyota-associated format that summarizes a process problem, the observed current state, a proposed future state, specific responsibilities, and timing on one sheet of paper. It is intended to make analysis and planned changes visible to everyone involved, rather than keeping improvement knowledge inside a specialist department.
Solution matrix
Compare options against customer needsA comparison tool that assesses available ways to solve a customer's problem against dimensions such as completeness, time and hassle, desired features, location, timing, simplicity, and cost. When existing options perform poorly, the gaps can help managers or entrepreneurs imagine a better service configuration.
solution economy
Ongoing provision of complete solutionsThe proposed shift from consumers coordinating many separate products and services toward a small number of providers managing major recurring needs. Providers would coordinate solution elements over time, aiming to lower total cost and customer effort while taking greater responsibility for service, maintenance, and lifecycle performance.
water spider
Frequent delivery to points of useA materials handler in a lean factory who follows a regular route to deliver needed parts and supplies to workstations and remove completed goods or waste. The book extends the idea to personal logistics, imagining coordinated pickups and deliveries to homes and offices that could replace many separate errands.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.