"Lean Solutions" is an article by mary-poppendieck and tom-poppendieck exploring the application of lean thinking beyond the development team to the full product lifecycle — from concept through delivery, support, and retirement.
Extending the Lean Frame
The article appeared between lean-software-development-agile-toolkit-2003 and implementing-lean-software-development-2006, during the period when the Poppendiecks were developing the ideas that would become their second book. Where the first book focused on translating lean principles into development team practices, "Lean Solutions" pushed the optimize-the-whole principle further: if the development team is only part of the value stream from concept to customer, optimizing development alone is a form of local optimization.
The lean manufacturing tradition, rooted in taiichi-ohno's Toyota Production System, had always treated the entire production system — from raw material to delivered vehicle — as the unit of optimization. The Poppendiecks applied this frame to software: the value stream includes requirements definition, development, testing, deployment, customer support, and feedback — and waste (in the sense of eliminate-waste) accumulates across all of these, not just in coding.
Scope and Argument
The article examined how lean principles apply at the product level: what does deliver-as-fast-as-possible mean when deployment infrastructure, support processes, and customer onboarding are all part of the delivery cycle? What waste accumulates in the handoffs between development and operations, between product management and development, between customer success and product? These questions anticipate what the DevOps movement — later developed by gene-kim and others — would identify as the deployment pipeline problem.
The value-stream-mapping-for-software technique, which would receive fuller treatment in implementing-lean-software-development-2006, is relevant here: mapping the full concept-to-cash value stream makes visible the waste that accumulates outside the development team's direct control but within the organization's responsibility.
Position in the Corpus
"Lean Solutions" is a supporting work rather than a major contribution. Its significance is as a bridge document that shows the Poppendiecks extending their frame beyond development team practice toward the organizational and systems-level analysis that characterizes implementing-lean-software-development-2006 and leading-lean-software-development-2009. Practitioners interested in lean product management rather than lean development methodology will find the article's framing useful as a complement to the main books.