Day three. You're somewhere with a view, and the message comes in at about eleven. The contractor needs a yes on the tile before he sets the next row. There's a photo attached. You look at it for four seconds, type go ahead, and you're back at breakfast before anyone at the table has noticed you picked up the phone.
That's it. That's the whole thing. Which is exactly why it's so hard to call it a problem. Nobody's working through their holiday. There's no laptop, no client calls, no evening lost to drawings. There are eleven of these across ten days, four seconds each, and if you added it all up it wouldn't reach five minutes. You'd feel silly complaining about five minutes.
But something did happen in those five minutes, and it wasn't to you. Eleven times, somebody in your studio came up against a question they couldn't answer, and eleven times the question went away before anyone had to work out what to do about it. You were so quick that nothing was ever stuck. Which means nothing was ever noticed either.
It happens again on day five, and twice on day seven. Someone needs to know whether the client ever signed off the revised layout. Someone else asks which drawing the fabricator should be working from. A supplier wants a colour confirmed. The site engineer sends a photo of a junction and asks if it's alright. Every one of them takes under a minute, and every one gets answered from a phone held at an angle to keep the glare off.
And answering was the right call every single time. That's worth being clear about, because the alternative is worse. Making a contractor wait three days to protect the idea of a holiday
would be silly, and expensive, and the tile question genuinely did need somebody with your judgment on it. Nobody is arguing for slower answers.
But the eleven messages were not all the same kind of thing, and that's the part worth noticing.
Go through them properly. The tile needed you. So did the junction, probably. That's judgment, and it belongs with the person who has made that call two hundred times. The sign-off question didn't need you, it needed the file. The fabricator's question didn't need you, it needed a version number. The colour was in an email from February.
Four of the eleven were architecture. Seven were people trying to find something.
From four seconds away those feel identical, and the person asking is being sensible too. If a question to you comes back in four seconds, and searching the folder takes fifteen minutes and might still end in the wrong answer, they'll ask you. They'd be daft not to. Every fast answer you give teaches the studio, correctly, that you are the shortest route to a fact.
So the studio has never really operated without you. Not because you won't let go of it, and not because the team can't cope. Because the gap never lasts long enough to appear. Ten days is the only chance a practice gets to find out what it can do on its own, and it gets cancelled four seconds at a time, eleven times, by somebody being helpful.
The seven already had answers. The sign-off existed. The version number existed. The colour was in an email from February. Nothing had to be decided and nothing had to be remembered. Every one of those answers was sitting somewhere in the studio. It just wasn't anywhere the person asking could actually reach.
This is roughly what Projectsmate is for. Not the judgment, nobody should want a system making the tile call. Just holding the current stage, the current drawing, and what the client last agreed, somewhere the whole team can get to it without going through you.
You didn't come back to a studio that coped without you. You came back to a studio that was never asked to.