fatihguner/foreman/kaizen-bpr

Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.

Kaizen & Business Process Reengineering

Two philosophies of improvement emerged from opposite ends of the industrial world, and they could hardly be more different in temperament. From Japan: Kaizen -- the quiet, relentless discipline of making things a little better every day. From America: Business Process Reengineering (BPR) -- the dramatic act of tearing up existing processes and rebuilding them from scratch. One whispers. The other shouts. Toyota embodied the first; Michael Hammer and James Champy evangelised the second in their 1993 manifesto Reengineering the Corporation. The genius lies not in choosing between them but in understanding when each is appropriate -- and recognising that most organisations need both, applied at different times and to different problems.

The Framework

Kaizen: The Continuous Improvement Philosophy

Kaizen (Japanese: "change for better") is not a technique but a culture. Masaaki Imai introduced it to Western audiences in 1986, describing the management philosophy that powered Japan's post-war industrial ascent. The core principle is disarmingly simple: every process can be improved, every day, by the people who do the work.

Before Kaizen:

• Improvement is a management responsibility
• Changes come in large, infrequent projects
• Workers execute; managers think
• Defects are found at inspection
• "Good enough" is the standard

After Kaizen:

• Improvement is everyone's responsibility
• Changes come in small, continuous increments
• Workers observe, suggest, and implement improvements
• Defects are prevented at the source
• "Better than yesterday" is the standard

The Kaizen Cycle (PDCA):

1. Plan -- Identify a specific, measurable improvement opportunity. Define the current state and the target state.
2. Do -- Implement the change on a small scale. Treat it as an experiment, not a commitment.
3. Check -- Measure the results. Did the change achieve the target? What unexpected effects emerged?
4. Act -- If successful, standardise the new method. If not, analyse why and begin the cycle again.

Key Kaizen Principles:

• Go to the Gemba (the actual place where work happens) -- do not improve processes from a conference room
• Eliminate Muda (waste) in all seven forms: overproduction, waiting, transport, overprocessing, inventory, motion, defects
• Respect the expertise of frontline workers -- they understand the process better than any consultant
• Small changes compound; a 1% daily improvement yields a 37x annual improvement mathematically

BPR: The Radical Redesign

Business Process Reengineering rejects incrementalism. Hammer's famous dictum: "Don't automate, obliterate." BPR asks not "How do we improve this process?" but "If we were building this from nothing, how would we design it?"

Before BPR:

• Processes evolve organically over years, accumulating complexity
• Departments optimise locally, creating handoffs and bottlenecks
• Technology is layered onto existing workflows
• The question is "How do we do this faster?"

After BPR:

• Processes are redesigned around desired outcomes, not existing activities
• Cross-functional teams replace departmental handoffs
• Technology enables fundamentally new ways of working
• The question is "Why do we do this at all?"

The BPR Methodology:

1. Identify -- Select the process with the highest impact potential. Focus on processes that are broken, not merely slow.
2. Understand -- Map the current process end-to-end. Quantify cost, time, error rates, and customer impact.
3. Redesign -- Start from the desired outcome and work backward. Ignore existing constraints. Design the ideal process.
4. Implement -- Execute the redesign with full commitment. BPR is not a pilot; it is a replacement.
5. Sustain -- Monitor the new process and apply Kaizen to maintain and incrementally improve it.

When to Use Each

The relationship is sequential, not competitive. BPR creates new processes; Kaizen refines them. An organisation that only does BPR lurches from revolution to revolution. An organisation that only does Kaizen risks polishing a process that should have been replaced entirely.

Prompts

Prompt 1 -- Process Waste Identification (Kaizen):

"Analyse this business process: [describe process step by step]. Identify all seven types of waste (overproduction, waiting, transport, overprocessing, inventory, motion, defects) present in the process. For each waste identified, propose a specific Kaizen improvement that could be implemented within one week by the team that owns the process."

Prompt 2 -- BPR Candidate Assessment:

"Evaluate these business processes for BPR suitability: [list 3-5 processes with brief descriptions]. For each, score on three dimensions: (1) how broken is the current process (1-10), (2) how significant is the business impact of improvement (1-10), (3) how feasible is radical redesign given our current resources and capabilities (1-10). Recommend which process to reengineer first and explain why."

Prompt 3 -- Zero-Base Process Design:

"Ignore how we currently handle [process name]. If we were designing this process from scratch today, with access to current technology and no legacy constraints, what would the ideal process look like? Define the desired outcome first, then design backward. Include the number of steps, roles involved, technology required, and expected cycle time."

Prompt 4 -- Kaizen Event Planning:

"Design a five-day Kaizen event (Kaizen Blitz) for improving [specific process]. Include: Day 1 objectives (current state mapping), Day 2-3 activities (root cause analysis and solution design), Day 4 actions (implementation), and Day 5 deliverables (measurement and standardisation). Specify the team composition needed and the metrics we should track before, during, and after the event."

Use Cases

Early-Traction Startup Reducing Customer Onboarding Time

A B2B SaaS company discovers that customer onboarding takes an average of 23 days -- far longer than the industry benchmark of 7 days. A Kaizen analysis of the process reveals seven handoffs between sales, customer success, and engineering, with an average wait time of 2.3 days per handoff. Rather than reengineering the entire process, the team implements incremental improvements: eliminating two unnecessary approval steps (3 days saved), creating a shared onboarding dashboard that replaces email-based status updates (4 days saved), and automating the technical provisioning step (5 days saved). Onboarding drops to 11 days in 30 days. A subsequent Kaizen cycle targets the remaining gap.

Growth-Stage Logistics Company Reengineering Order Fulfilment

A direct-to-consumer company processing 5,000 orders per day hits a wall. The fulfilment process, designed when volume was 200 orders per day, has been patched and extended so many times that it now involves 34 steps across four systems that do not communicate. Kaizen improvements yield marginal gains, but the fundamental architecture is broken. The company undertakes BPR: redesigning fulfilment around a single integrated platform, reducing the process to 12 steps, eliminating three manual data-entry points, and implementing batch processing for common order types. Fulfilment cost drops 40%, error rate drops 85%, and the process now scales to 20,000 orders per day without additional headcount. Post-launch, a Kaizen programme maintains and refines the new process.

Anti-Patterns

Kaizen Theatre. Running suggestion programmes and improvement workshops without giving teams the authority, time, or budget to implement changes. Kaizen without empowerment is performance art. If management reviews but never approves suggestions, the programme dies within months.

BPR as Euphemism for Layoffs. In the 1990s, BPR became corporate code for headcount reduction. When reengineering is perceived as a vehicle for redundancy rather than genuine process improvement, it poisons organisational trust and ensures that the people who best understand the processes will not participate honestly in redesigning them.

Incremental Improvement of a Broken Process. Applying Kaizen to a process that needs BPR. Polishing a fundamentally flawed workflow yields diminishing returns and frustrates teams who can see that the underlying design is wrong. If the process architecture is the problem, incremental improvement is the wrong tool.

Big Bang Without Change Management. Launching BPR without investing in the human side of transformation. New processes fail not because the design is wrong but because the people expected to execute them were not consulted, trained, or motivated. Hammer himself later acknowledged that BPR's failure rate -- estimated at 50-70% -- was largely attributable to neglecting the human dimension.

Measuring Activity Instead of Outcomes. Counting the number of Kaizen suggestions submitted rather than the measurable improvement in process performance. Vanity metrics in improvement programmes are as dangerous as vanity metrics in product development.

By Stage

At early traction, the primary risk is having no documented processes at all. Kaizen requires a baseline to improve upon. The first step is making the invisible visible: mapping how work actually flows, not how founders assume it flows.

During growth, the signal for BPR is clear: when incremental improvements yield diminishing returns, when workarounds outnumber standard procedures, or when customer complaints cluster around a specific process. These are symptoms of a process that has outgrown its original design.

At scale, the most effective organisations alternate rhythmically between Kaizen (continuous, distributed improvement) and periodic BPR (strategic, concentrated redesign). Toyota calls this the difference between "maintaining standards" and "raising standards."

Output Template

Target Audience: Operations Team / VP Operations

# Process Improvement Assessment
## [Process Name] -- [Date]
 
### Current State
-Process owner: [Name/Role]
-Steps: [Number]
-Average cycle time: [Duration]
-Error/rework rate: [Percentage]
-Monthly cost: [Amount]
-Customer satisfaction with this process: [Score/Feedback]