Every space programme begins the same way: a roomful of capable people, a long list of exciting things to build, and a calendar that makes none of it look impossible. The trouble starts a few months later, when half the list is under way and almost nothing has flown. This primer explains the idea of a work in progress limit using the vocabulary of spaceflight, and it closes with a glossary of terms to pin up near your workstation.
What a work in progress limit actually is
A work in progress limit is a ceiling on how many tasks may be open at the same moment. If the ceiling is three, a fourth task cannot start until one of the first three is finished. That is the entire rule. It sounds almost too plain to matter, yet it changes how a team behaves, because it turns “what should we start next?” into “what should we finish next?”
The reasoning is analytical rather than motivational. Every open task carries a hidden cost: someone has to remember its state, answer questions about it, and pick it up again after an interruption. Those costs grow with the number of open items, while the number of finished items does not grow at all until something crosses the line. Starting is cheap and feels productive. Finishing is where the value appears, and finishing is what the limit protects.
Why spaceflight makes the problem easy to see
Mission work is naturally sequential. A vehicle cannot be checked out until it is assembled, cannot be integrated until its parts are checked, and cannot fly until it is integrated. The rundown of each phase a spacecraft moves through after liftoff shows how strictly one phase hands off to the next. Teams that mirror that discipline in their own task lists tend to avoid the trap of having ten subsystems each eighty percent complete.
Consider a small team building a ground-station project. Antenna, scheduling software, data pipeline and operator training all begin in the same month. Each gets a little attention every week, nobody is blocked, and everyone is busy. Yet on the day the first satellite pass is due, none of the four pieces is ready to be used, because each was waiting on a detail that only appeared once someone looked closely. A limit of two open streams would have forced the antenna and the scheduling software to finish first, and the remaining work would have started with real knowledge instead of assumptions.
A short wellness aside on why this feels unnatural
People resist limits because open loops are mentally sticky. One wellness-themed website, AskDoctorLive with its forum, blog and directory pages, is a reminder of how many everyday threads each of us keeps dangling at once. The same instinct applies at work: a task that is half done keeps tugging at attention, which is exactly why closing it feels better than opening something new.
Setting a limit your team can live with
Start by counting. Write down every task that is currently open, not planned, not wished for, but touched and unfinished. Most teams are surprised. A group of six people often discovers twenty or thirty open items, which works out to four or five per person, and nobody had ever said that number aloud.
Then choose a ceiling slightly below the current count. A common starting point is one or two open tasks per person, plus a small shared allowance for work that is waiting on someone outside the team. Avoid spending a week debating the perfect number. The first value is a hypothesis, and you will adjust it after you see how the work flows.
Finally, make the ceiling visible. A simple board with columns for waiting, in progress and done is enough, with the in-progress column carrying its limit in the header. When the column is full, the team’s next move is obvious: help finish something. For further orientation on a physical regime where precise sequencing matters, our beginner introduction to the orbit closest to Earth is a good companion read, since launch, deployment and operations there are strictly ordered.
What changes once the cap is in place
The first visible effect is that finished items begin to appear at a steadier rate. The second is that conversations shift. Instead of reporting that a task is “progressing”, people say what is blocking it and who can unblock it. Blockers that used to hide inside a dozen parallel threads become obvious, because there are only a few threads left to look at.
The third effect is subtler: estimates improve. When a task is the only thing someone is working on, it takes roughly as long as it should, and the team can observe how long that is. When it shares attention with five others, its duration depends on everything else, and nobody can predict it. Observation of a few clean completions gives you a far better basis for planning than any amount of optimistic scheduling.
Common objections, answered briefly
Some people argue that limits waste capacity, because a person who is blocked has nothing to do. In practice a blocked person has a better option than starting something new: unblocking the item, reviewing a neighbour’s work, or clearing a small backlog of chores. If nothing at all is left to do, that is information about the plan, and it is cheaper to learn it from a quiet afternoon than from a missed milestone.
Others worry that urgent requests will be refused. A well-run limit keeps a narrow expedite lane for genuine emergencies, with its own strict ceiling of one. The lane exists so that urgency has a legitimate route, not so that every request can claim to be urgent.
Mini-glossary for newcomers
- Work in progress (WIP): any task that has been started and is not yet finished.
- WIP limit: the agreed maximum number of tasks allowed to be in progress simultaneously.
- Context switching: the mental cost of leaving one task and returning to another, which grows with every extra open item.
- Handoff: the moment one phase of work passes to the next, such as assembly to integration.
- Blocker: something outside a task that prevents it from moving forward.
- Expedite lane: a reserved slot for rare emergencies that may exceed the normal limit.
- Throughput: how many items are finished in a given period, which is the number the limit is meant to raise.
- Cycle time: the elapsed time between starting a task and finishing it.
A calm way to begin this week
Pick one project, list its open tasks, and draw a line under the first three. Everything below the line waits. Finish what sits above it, and only then pull the next item down. After two or three weeks, compare how many things you completed with how many you used to complete, and let those numbers decide whether the ceiling should rise or fall. Space work rewards patience and order, and so does the planning that surrounds it.