Quick summary
- Problem: offices swamped by emails and tasks, with no idea whether the load is feasible.
- Approach: factory concepts (flow, capacity, WIP, standard) applied to knowledge work.
- What you get: a simple framework and a load simulator to see whether you run in “factory mode” or “firefighting mode”.
- Time: a 7-minute read + 3 minutes to simulate your situation.
1) What “industrial method” means in an office
This is not about turning the office into an assembly line, but about copying what works in industry:
- Flow: a clear path from intake to delivery.
- Capacity: knowing how much the team can ship per day without burning out.
- WIP: limiting work in progress to avoid gridlock.
- Standard: defining the "normal way" of doing things.
When these four points are clear, chaos drops and completions rise.
Grounded in an office: flow is a simple board where every task knows its column; capacity is your team's real focus hours (not contract hours); WIP is how many files are open at once; and the standard is the template or checklist that stops three people doing the same thing three different ways.
2) Where to apply the industrial method
In a typical office, almost all work can be grouped into three main flows:
Intake
Emails, calls, tickets... everything that "lands" and opens a new front. Without a filter, everything looks urgent and ends up straight on someone's desk.
In Progress (WIP)
Open files, half-finished reports. This is where everything jams. Every open file consumes attention even when nobody touches it: it is stock taking up mental space.
Delivered
What creates real value: reports sent, files closed. If you don't measure what goes out, you'll never know whether the team has headroom or is at the limit.
3) Practical steps to industrialize your office
- Draw your flow. 3-5 columns (Intake, In progress, Review, Done). A board on the wall, in Excel or in Notion: the tool doesn't matter, seeing the same thing does.
- Count your WIP. How many things are open right now? Open the list and count them without drama: that number is your inventory.
- Estimate time per task. Real focus hours per file? Ask the team or measure for a week: between meetings and interruptions it is usually far less than it seems.
- Calculate capacity. Use the simulator below. Daily capacity = people × focus hours ÷ hours per task.
- Set limits. If more comes in than goes out, intake has to slow down. Limiting intake isn't saying no to the client: it's negotiating deadlines with data in hand.
Capacity Calculator
Enter your team's data and see whether you are in a comfortable zone, at the limit, or in firefighting mode.
The rest is meetings and interruptions.
Team Status
0% Load
An orientative reading to frame the conversation, not a diagnosis.
Enter your data to see the analysis. The preloaded values are examples and the thresholds (70% / 100% / 140%) are orientative, not a validated standard.
Illustrative example: from firefighting to planning
Imagine a 4-person services office: unanswered emails, 18 open files at once, overtime at every month-end and a permanent sense of chaos.
What changes: they draw the flow in 4 columns, limit work in progress to 3 files per person, measure their real focus hours (4 a day, not 8) and match new work intake to that capacity: what doesn't fit goes in next week, with the deadline communicated.
In a made-up case like this, WIP drops from 18 to 12, deadlines are met without heroics and month-end overtime disappears. It's an example to illustrate the mechanism, not a customer result.
Two-week mini plan
Week 1: Measure
- Draw the flow in 3 columns.
- Count current WIP.
- Estimate hours per task and use the simulator.
Week 2: Limit
- Set WIP limits per person.
- Block meeting-free focus slots.
- Review the board 10 min a day.