5 projects. Only 1 team. What to do first?
A motion design case study: how an electrical engineering firm arbitrates priorities when five projects compete for the same resources.
2026-05-11 · updated 2026-05-11
A concrete problem, not an abstract question
Five projects are running. One team carries them all. Deadlines are tightening on several fronts at once. And the question everyone is thinking but no one dares to settle remains the same: what do we do first?
This case study illustrates that situation through the daily reality of an electrical engineering firm. Engineers juggle complex technical files, plan revisions, pending validations, and clients calling back. The pressure is real. The trade-offs, however, often stay implicit.
What the case reveals
The video follows a project manager's reasoning as they arbitrate in real time. It surfaces three realities that are often misread in this type of situation.
The perceived priority
The hidden constraint
The decision to structure
Why intuition is not enough
In an engineering firm, the temptation is to respond to the loudest pressure of the moment. The client who calls back. The project with the nearest deadline. The manager who insists. These signals are real — but they don't necessarily tell you where the true priority lies for the overall flow.
The right reflex
Before deciding who goes first, identify which resource is most loaded across the entire portfolio. That resource is your constraint. Priority should be organized around it.
When five projects draw on the same engineers, the same validation steps, or the same critical skills, the question is not which project matters most — it is which project should go first so the others can move forward.
What KairoProject makes visible
KairoProject is built to make this kind of trade-off explicit. The portfolio view lets you see at a glance:
- which projects are pulling on the same resources at the same time
- where the constrained resource sits across the whole portfolio
- which project should be prioritized to unlock flow
The goal is not to produce a fixed ranking. It is to give teams and decision-makers a shared reading of the situation — so that trade-offs are grounded, not improvised.