Author
Writes from lived operations — handoffs, guest access, and the unglamorous work of keeping a small team coherent.
Buyer ProblemsThe Manila team hits a fork at 4pm their time. The client who can unstick it is asleep in Chicago. Here is what to leave behind so the work does not just sit there until morning.
Buyer ProblemsSix people don't need a project manager. They need six things a project manager would otherwise do for them — named, written down, and checked on a schedule nobody has to remember.
Buyer ProblemsA new hire does not need your entire wiki on day one. They need eight things, in order, and a first task that proves the environment works.
Buyer ProblemsThe problem is not that your team doesn't write things down. It's that the one sentence explaining why a decision was made lives in a thread that scrolls away in a week.
Lived OperationsWhen status updates go thin, the board isn't lying about small things anymore — it's lying about everything. Here's the order of operations for getting back to shared reality without adding a new layer of process.
Lived OperationsFour words cost you nothing to type and thirty minutes of someone else's context to answer. The shorter message is often the more expensive one.
Lived OperationsA final decision, a changed requirement, and a deployment instruction all disappear the same way in chat: they get buried under the next fifty messages. Here's how to spot them before they scroll away.
Lived OperationsAfter a missed deadline, teams write more: daily standups, longer reports, detailed minutes. It decays faster than what it replaced, and for a specific reason.
Lived OperationsThe exit interview covers laptops and access cards. It rarely covers the fact that the only record of why a client decision was made lived in one person's head, and that head is now working somewhere else.
Lived OperationsA good deployment handoff isn't a status update — it's the minimum information someone needs to keep going if something breaks after you log off. Here's the format that actually survives 2 a.m.
Buyer ProblemsYes, for a while, and longer than most tool vendors want to admit. Here are the four specific moments when a shared sheet stops being enough, in the order they usually hit.
Buyer ProblemsAdoption doesn't fail because people forget or don't care. It fails when updating the tool costs more than the thing it was supposed to replace.
Lived OperationsA developer who has to guess your intent will guess in the direction that's fastest for them, not the one you meant. Here's a task structure that removes the guessing.