If you have to chase it, you don’t have commitment infrastructure

A manager I worked with kept a mental list of things people had promised. Not a spreadsheet, not a board. A list in her head, and every few days she'd work through it: did you send that, is that done, where are we on the other thing.

She thought the problem was the people on the list. Some of them were reliable and got asked anyway, which stung: they'd done the work, and now they were being checked on like they hadn't. Some of them weren't reliable, and being asked was the only reason anything happened at all. Over time the unreliable ones learned they didn't need to remember their own commitments. She'd remember for them. Why hold two copies of the same information in your head?

That split matters more than it looks. Ask a reliable person the same question twice and you've told them, without meaning to, that their word wasn't good enough the first time. Ask an unreliable person the same question twice and you've confirmed that nothing bad happens if they wait for the ask. The chasing trained both groups, just in opposite directions, and neither direction was the one she wanted.

Here's the tell: her own team's task board was empty. Not because nothing was happening, but because nothing that happened had ever been written down anywhere except her memory. The commitments existed. The infrastructure to hold them didn't.

Chris Argyris had a name for the gap this creates: the difference between what an organization says it values and what it actually rewards, moment to moment. She said she valued trust and autonomy. What she rewarded, in practice, was proximity to her attention. The people she chased hardest were the ones she trusted least, and everyone on the team could see the ranking even though nobody had said it out loud.

Chasing feels like management. It produces motion: a message sent, a status pulled, a box that can be mentally checked. But chasing is where leadership's attention goes to die. Every minute spent asking "did you do the thing" is a minute not spent on the ten things only she could do. And it doesn't scale. The list in her head could hold maybe fifteen open items before things started falling off it silently, which is worse than never asking, because now the drop looks intentional.

The team read the chasing as distrust. It wasn't, exactly. It was the absence of anywhere else for a commitment to live. When there's no visible place for "I said I'd do this by Thursday," the only enforcement mechanism left is a person asking another person, repeatedly, and that always reads as surveillance even when the intent is care.

The fix isn't a lecture about ownership. It's a place. A visible board, physical or digital, doesn't matter which, where commitments get written down when they're made, not when someone asks about them. And the board has to start with leadership's own items, publicly, before anyone else's items go on it. Ask a team to make their promises visible while yours stay in your head, and you've just built a surveillance tool with your name off it.

This is the part most managers skip, because it's uncomfortable in a way process changes usually aren't. Putting your own open items on a public board means the gap between what you promised and what you delivered is now visible too, to the same people who used to only see yours enforced on them. Most of the resistance to visible-commitment systems isn't the team resisting. It's the leader realizing the board cuts both ways.

Once commitments are visible, chasing changes shape. Most of it disappears, because a glance at the board answers the question that used to take a message. What's left is real: something that's overdue with no explanation on the board is now data, not a hunch. That's a conversation worth having, and it's a completely different conversation than "hey, did you get to that" for the ninth time.

The manager rebuilt her team's board that quarter and put her own five open items on it first. Two things happened. The reliable people stopped feeling watched, because the board answered for them before she had to ask. And the unreliable pattern got easier to see and name, because for the first time it wasn't buried inside her memory. It was sitting on a board where everyone, including her, could see who kept their word and who needed the system to remember for them.

None of this required new software or a framework with a name. It required one thing to exist that hadn't existed before: somewhere other than a manager's head for a promise to live.

If you're maintaining a mental list of who owes you what, that list is the whole problem. It's not a discipline issue on their side. It's an infrastructure gap on yours.

---

Not sure whether this is your pattern? The fit-check takes two minutes, no email required.

Everything Breaks at 3 and 10

There's a restaurant I work with that grew from three people to five and fell apart.

Nothing dramatic happened. Nobody quit, nobody stole, the food didn't change. The owner just noticed, over about two months, that everyone was exhausted, quality was slipping, and the team that used to feel like a kitchen felt like a queue. Everything routed through him. It always had. That was the point: at three people, the owner is the operating system, and it works beautifully.

At five, it doesn't. And the cruel part is that nobody changed anything, which is exactly the problem. The system that made the place good stopped fitting the place it had become.

Hiroshi Mikitani, who built Rakuten, put a number on this: everything in a company breaks every time headcount roughly triples. At 3, at 10, at 30, at 100. Not the people. The invisible stuff: who decides what, how information moves, what gets rewarded, what a meeting is for. The coordination you got for free at one size becomes the thing quietly taxing everyone at the next.

The tell is always the same sentence: "it used to just work."

It did. Osmosis worked. Everyone heard everything because everyone was in the room. Approval was a look across the pass. Priorities didn't need writing down because there was only one, and everyone was staring at it.

Then you tripled, and osmosis died, and nobody held a funeral. So people fill the gap the only ways they can: they wait, or they silently absorb. When work is quietly absorbed it sneaks up on you. It's always just a little outside of your scope at a time until your scope becomes something unrecognizable. You're a few "can you justs" away from a total mental and physical collapse.

When teams wait for the founder, the founder absorbs every decision to keep things moving, and "nothing is stalled" becomes technically true while everything gets slower. The founder reads their own exhaustion as personal inadequacy. It almost never is. It's an operating model built for three, running at ten.

Two things worth doing the week you notice this.

Name the threshold out loud. "We tripled, so our old ways expired" is a diagnosis nobody has to be ashamed of, and shame is the main reason founders fix the wrong thing. Name the problem and you can predict it.

Then rebuild the two or three mechanisms the old size gave you free. Who can say yes to what, written on one page. Where information lives when it's not in your head (which pays exponential dividends). What the team would say the priorities are, without checking.

The restaurant did this. The owner kept her morning market run and insisted on a "family shift meal", wrote the routine decisions onto one page and handed them to her second, and got back the hours that made him good in the first place.

If some version of "it used to just work" has been rattling around your head: it's not you. It's probably the system needing an update.

---

Not sure whether you're at a threshold? The fit-check takes two minutes, no email required. — linked as above.