2026-06-29
Start improvement by department: build a PDCA culture without waiting for company-wide rollout
Company-wide improvement tends to stall. Run report-linked PDCA in one department first, then expand once results show — a small-start, by-department approach.
Why company-wide rollout stalls
Trying to start improvement across the whole company at once eats time in consensus-building and process design, and gaps in enthusiasm between teams are unavoidable. Burning all your energy on preparation and tiring out before you begin happens at many companies. A company-wide rollout piles up work: choosing tools, aligning rules, running briefings. Meanwhile nothing changes on the ground, and enthusiasm often cools. Learning while moving tends to get you further faster in the end.
Run it small, in one department
Start with a manager and a few people running PDCA from the daily report. With a small scope, decisions are fast and it's easy to verify what worked and what didn't. Starting small is not the same as doing it sloppily. A rule of thumb for choosing the first department: it has an eager leader, its daily work is relatively stable, and its impact on others is not too large. Before starting, decide the period and what to watch — for example, 'did we keep up the reports?' and 'did preparing for 1-on-1s get easier?'
Expand after showing results
Prep for 1-on-1s got easier; evaluation felt fairer — these lived experiences are the best argument for moving other departments. Spread it by example rather than by decree and expansion is easier to accept. When passing on examples, share honestly not only what went well but also where you stumbled. Other departments can avoid the same failures, and the story becomes more credible. A meeting of department heads is a suitable place.
Culture takes root through repetition of the shape
An improvement culture takes root not from a fine slogan but from the daily repetition of P, D, C and A. As you keep running the shape department by department, improvement stops being a special activity and becomes an everyday given. To keep the shape going, make it a form that survives changes of the person in charge. Briefly writing up how to write and how to look at reports makes handover easier.
Common stumbles and how to avoid them
Common stumbles are the burden concentrating on the first department until it is exhausted, and rushing for results by demanding only numbers. Check results first from what is easy to see, such as felt improvements and changes in what reports contain. Also, treating the first department too specially can make other departments feel it has nothing to do with them. Keeping it in a form that ordinary departments could do is a good rule of thumb.
The smallest first step to try
Starting next week, have just a few people in one department write P, D, C and A in their reports, and once a week read and reply to them. If it proves light to keep up and feels like it works, widen the period and the scope little by little.
Related articles
- Turning Construction Daily Reports from Paperwork into Tomorrow's Plan: Designing Field PDCA
- Rolling Out Daily Reports Without It Feeling Like Surveillance — From Handling Pushback to Explaining It to Leadership
- Evaluation for small teams: start from daily facts rather than a complex system
- An organization where improvement ideas rise from the field: draw up A (improvement) from the daily report
A tool for a culture of improvement and fair evaluation that implements these ideas.