Lean Business Analysis

Lean Business Analysis is the application of Lean thinking to business analysis. It focuses on delivering customer value, reducing waste in analysis activities, and promoting continuous improvement. It encourages just-in-time requirements, fast feedback, and aligning analysis efforts directly with business outcomes.

🧠 Lean Thinking

Lean Thinking is a management philosophy derived from the Toyota Production System, focused on maximizing customer value while minimizing waste. It emphasizes continuous improvement, respect for people, and optimizing the flow of value through systems.

🌟 The 5 Principles of Lean Thinking

1. Specify Value
   Define value from the customer’s perspective — what are they truly willing to pay for?
2. Map the Value Stream
   Identify all the steps (both value-adding and non-value-adding) in the process, and eliminate waste.
3. Create Flow
   Ensure that work moves smoothly and continuously through the system without delays or interruptions.
4. Establish Pull
   Let customer demand drive the work — deliver just-in-time, not too early or too late.
5. Pursue Perfection
   Continuously improve processes to eliminate waste and deliver ever-increasing value.

🗑️ The 7 Lean Wastes (originally from manufacturing, but widely applied in knowledge work and business analysis):

1. Overproduction
   Doing more than is needed or earlier than needed (e.g., writing requirements no one uses yet).
2. Waiting
   Delays between steps or dependencies (e.g., waiting for stakeholder feedback or approvals).
3. Transportation
   Unnecessary handoffs or movement of information (e.g., excessive email chains, tool switching).
4. Overprocessing
   Doing more work than necessary (e.g., creating excessive documentation or redundant analysis).
5. Inventory
   Work that has been started but not finished or delivered (e.g., backlog of incomplete requirements).
6. Motion
   Unnecessary movement within the process (e.g., switching between systems or meetings without value).
7. Defects
   Errors and rework (e.g., incorrect requirements, misaligned stakeholder understanding).

🗑️ The 7 Lean Wastes in Business Analysis

1. Overproduction

Creating more analysis than needed or too early

• Writing full specs or models for features that may never be built
• Producing excessive documentation no one uses
• Gathering requirements for far-future work that may change

2. Waiting

Delays between analysis activities or stakeholder inputs

• Waiting for stakeholder availability, approvals, or decisions
• Delays in getting feedback on requirements or models
• Development waiting on BA to finish specs

3. Transportation

Unnecessary handoffs or movement of information

• Re-entering requirements into multiple tools (e.g., from Word to Jira)
• Sharing knowledge inefficiently (e.g., emailing instead of collaborative tools)
• Moving artifacts between roles or teams without adding value

4. Overprocessing

Doing more analysis work than is necessary

• Creating highly detailed models or documents for simple features
• Formatting and refining deliverables beyond what’s useful
• Holding excessive workshops or reviews

5. Inventory

Unfinished or unused analysis work

• Backlogs filled with unrefined or outdated requirements
• Large queues of unvalidated or unprioritized items
• Analysis sitting idle due to lack of stakeholder input

6. Motion

Unnecessary effort due to poor tooling or process

• Jumping between multiple tools or systems to gather information
• Redundant manual updates to status reports or documentation
• Searching for the latest version of a requirement or document

7. Defects

Errors in analysis that lead to rework or confusion

• Ambiguous, conflicting, or incomplete requirements
• Misunderstood business rules or acceptance criteria
• Rework due to misalignment between BA, stakeholders, and developers

✅ Why This Matters in Lean Business Analysis:

Recognizing these wastes helps BAs:

• Focus on just-in-time, just-enough analysis
• Improve flow and collaboration
• Continuously deliver value to stakeholders
• Reduce rework, delay, and miscommunication

Other Business Analysis Articles: