Stay in the room

I look for operators who can write the constraint down: who owns this, what it may touch, what the approver sees, and what happens when it is wrong. I do not hire for a demo. I also do not let the people who wrote that constraint leave when the build starts.

That sounds obvious. It is the thing that disappears first. Design hands over to delivery. Delivery hands over to a partner. The partner hands over to a runbook. By the time the write is real, nobody in the room can change the gate, and nobody who can change the gate is in the room.

What I got wrong

On the lending line I let the platform look finished before risk and operations had shaped it. On the cloud migration I let the visible tier move before the people who knew the cache were driving the sequence. Both times the design left the room too early. Both times we paid for it in the second half.

What I do now

The people who designed the work stay while it is delivered. Not as a steering committee. As the people who can still say no to a write that drifted. If a partner is building, they are in the same room as the approver, not in a weekly with a status rag.

I have led organisations of 120 across platform, mobile, data and security. Size is not the issue. Distance is. A system that cannot wait for a person is usually a system whose person left in week four.

If you want me in an engagement, that is part of the price. I will not write the gate and vanish. The gate is only real while someone who remembers why it exists can still stop a write.