Book · In progress
Kaizen vs. Gantt
The Japanese and the American way of managing projects, and which one works better in practice.
In progress
The idea
Project management speaks with two accents. One grew in American construction, defense and software, with schedules, baselines, formal roles and standards such as the PMBOK Guide. The other grew in Japanese manufacturing and construction, with kaizen, lean thinking, visual management and decisions built on consensus.
Both claim to deliver. Both have famous successes and famous failures. Most books pick a side or treat the other as a curiosity. This one sets them next to each other, project by project, and asks the question that matters to anyone who has to deliver something: which habits actually work in practice, and when?
It is written by a practitioner, not a historian. Every idea has to pass one test: does it survive contact with a real project, a real budget and a real team? The book is in progress. This page is its cover and its promise, and the chapters will follow.
What it explores
Questions the book will answer
Plan or adjust?
How much should you plan before you start, and how much should you learn along the way? A detailed baseline against small, continuous improvement.
How decisions get made
One accountable owner who decides fast, or a group that builds agreement first (what Japanese organizations call nemawashi) and then moves together.
Where quality lives
Inspect at the end, or build quality into every step and let anyone stop the line when something is wrong.
Contract or relationship?
How much a project leans on the written contract and change control, and how much on long-term trust between the parties.
Bad news
Escalation paths and risk registers against the habit of reporting, informing and consulting early and often.
Tools of the trade
Gantt charts, baselines and earned value on one side; kanban boards, daily huddles and visual management on the other.
A note on generalizations: neither country is one thing. The book treats "Japanese" and "American" as two styles, not as stereotypes, and shows where each organization breaks the pattern.
Who it is for
- Project and operations managers who want a wider toolbox
- Founders and owners who run projects without a formal method
- Teams that work across cultures, contractors and clients
- Anyone curious about why two successful traditions disagree
Status
The outline is taking shape and the cover is ready. "Kaizen vs. Gantt" is a working title, and early readers will help shape the chapters.
Be first
Get the first chapter when it is ready.
One email when there is real news. No spam, no noise.
Keep exploring
Related reading and services.
Agile, Waterfall or Hybrid? Choose the Method That Fits the Work
There is no best method, only the one that fits how much you know and how costly change is. A simple way to choose, with real project examples.
Interactive tool: Which method fits your project?
12
Project Governance for Small Teams: Just Enough Structure
Governance sounds heavy, but a small team needs five things: clear roles, a decision rhythm, decision rights, simple gates and a record of choices.
Interactive tool: Governance check
15
Project Closeout and Lessons Learned That Actually Get Used
Most projects end with a party and a forgotten document. How to close properly, hand over cleanly and make lessons change the next project.
Interactive tool: Closeout countdown
Next step
Let's find the project that moves your business.
Tell me where things are stuck. I will tell you which project I would start with.