The patterns underneath

What the founder came in believing

The founder was sure the problem was the team. People weren't taking ownership, decisions dragged, and nothing moved until it got chased. The plan was to build a leadership layer in 30 days and hire the problem away.

What the diagnostic found

The team wasn't failing to take ownership. They had learned, correctly, that nothing needed to move until the founder pushed, because the founder always did. The first half of every month was dead. Work shipped only when the founder held the loop tight. Four functions plus the founder's office reported straight in, and the chain snapped at results, so people owned activities while nobody owned outcomes. One creative function was co-owned by two teams, which quietly guaranteed every contested call landed back on the founder's desk.

The pattern: Founder Gravity

Every decision, follow-up and result ran on one person's energy, so the company's ceiling was the size of that person's bandwidth. Drop a senior hire into that field and they would find authority still routed through the founder, then leave. Every structural change reproduced the same shape with new labels, because the gravity underneath it never moved.

The first move

List every decision from the last month, group them into eight categories at most, and transfer each to a single owner in a face-to-face handoff, with one promise attached: their calls won't get reversed publicly, even when the founder would have chosen differently. The signal to watch for is one consequential decision made without the founder, and left standing.

What the founder came in believing

The founder framed it as distribution. A couple hundred users, a few dozen active, and no channel that scaled without organic grind. There wasn't time to build a following on X or Reddit, so the 30-day fix was to recruit influencers who already had an audience and get them to sell the product.

What the diagnostic found

The product was a mismash of use cases, by the founder's own description. Users had arrived through different doors expecting different things, so the active few were probably several small signals wearing one number. Three months of posting had faded out with no kill decision and no scale decision, because no threshold was ever set for either. The operating rhythm was unplanned, so nothing forced a commitment to survive past the moment it was made.

The pattern: The Permanent Pilot

No single use case, channel or user segment had been held long enough to generate signal, so every initiative stayed in pilot indefinitely. The chicken-and-egg framing was accurate, but it was doing a quieter job. It gave the founder permission to avoid the one decision the founder didn't want to make: picking a use case and letting the others go.

The first move

Audit those active users this week: how each one found the product, what job they are hiring it to do, whether a dominant cluster already exists. Then write one paragraph naming the chosen use case, the ICP it serves, and the metric that will call the bet in 30 days. Both founders sign it. Everything downstream, the influencer push included, waits behind that signature.