There is a particular kind of exhausting week that seniors know well. You did not draw much. You were not in many meetings. And yet you were busy from nine to seven, because every twenty minutes somebody needed something unblocked, clarified, or decided.
That week is a symptom, not bad luck. It happens when the work arriving at your team is still in outcome form, and you are the live translation service converting it into actions, one interruption at a time.
The translation is the job
A principal hands you something like get the DD set ready for issue. That is a legitimate instruction and completely unactionable for a junior. Between it and someone opening a file sits a set of decisions only you can make: what has to be resolved first, what can run in parallel, what is not worth doing at all this round.
Making those decisions once, in writing, is the single highest-leverage hour in a senior's week. Making them repeatedly, verbally, on demand, is how the week disappears.
How small is small enough?
The useful test is not hours, it is ambiguity. A task is small enough when the person can start it without asking a question and will know for certain when it is done. Under that test, produce the DD set fails and mark up the ground floor RCC against the latest architectural plan and list the clashes passes — even though the second might take a full day.
| Too vague | Actionable | What changed |
|---|---|---|
| Work on the facade | Produce two facade options at 1:100 — one exposed concrete, one rendered | A definite output and a definite count |
| Sort out the RFIs | Draft responses to the four open structural RFIs for my review | Bounded scope, named reviewer |
| Check the drawings | Run the title block and revision check on sheets A-101 to A-118 | You know exactly when you are finished |
| Help with the presentation | Lay out slides 4–9 using the approved template and drop in the latest renders | No judgement call left for the junior to guess |
Sequence it, then hand it over
Once the tasks exist, put them in order before anyone sees them. The order carries information the tasks do not: it tells a junior what depends on what, and it stops them from starting the piece that has to wait for the consultant.
This is also where you prevent the most expensive kind of rework, which is not a mistake — it is correct work done in the wrong order and thrown away when an upstream decision changes.
The rework you cause
Most rework in a studio is not a quality failure. It is somebody doing a good job on something that was not ready to be done yet. Sequencing is how a senior prevents it.
Write the standard down once
If you find yourself correcting the same things every issue — the revision cloud, the layer purge, the naming convention — that is a checklist waiting to be written. Not a document nobody opens. A short list attached to the task itself, where the person is already working.
This is how a studio's standard actually propagates. Not through onboarding, and certainly not through a manual, but through the sequence of steps sitting in front of someone at the moment they are doing the thing.
Reviewing without becoming the bottleneck again
Set the review point when you hand the work over, not when it lands on you. If a task needs your eyes before it goes further, say so up front and make it a visible step — otherwise you will be pulled in at random moments, which is exactly the pattern you were trying to escape.
Where Spreadbox fits
Spreadbox gives this workflow a shape. The outcome your principal set arrives as a Goal. The part you own is a Block with your name on it — and inside it, you write the Tasks. Those tasks are ordinary tasks: they carry an owner, a deadline and a position in the queue, and they show up on the boards and the timeline alongside everything else in the studio.
- A block is yours, so the accountability for a chunk of the outcome is unambiguous.
- Tasks can carry several named checklists, so the studio standard travels with the work.
- Ordering the tasks inside your block is how you transmit dependency without a meeting.
- Discussion sits on the task, so the answer to a question is findable later by the next person.
- Drawings and references attach to the goal, the block or the task, wherever they belong.
You still make every judgement call you made before. You just make each one once, where the team can see it, instead of twelve times across a week of interruptions.