Why is nothing moving in my startup?

Because it's probably not an execution problem, it's a direction problem wearing an execution problem's clothes. Your team is working. Sprints close, tickets move, nobody's idle. But activity and direction are different things, and a team can be fully occupied while agreeing on almost nothing about what a good week actually produces. Effort doesn't compound when nobody's pointed at the same target.

The test that finds it

Ask yourself one question: what does a good week look like for your team? Not a great week, the kind you'd brag about. A normal good week, the baseline you'd expect most weeks to hit.

If you can answer that in ten seconds, ask the same question to two people on your team separately, without telling them what you said. Compare the three answers. If they're roughly the same, you don't have a direction problem. If they're not, you've just found where the effort is leaking, and it isn't leaking through anyone's execution.

What it looks like from the outside

Everyone's busy, and busy in ways that are individually defensible. Engineering shipped what was on the board. Sales had a full week of calls. Marketing published on schedule. And yet nothing from this week is meaningfully closer to done than last week was, because "done" was never actually agreed on, just assumed.

This is the part that makes it hard to see from inside: a direction problem produces the same daily texture as a hard week of legitimate execution. Meetings, output, visible effort. The difference only shows up if you zoom out far enough to ask whether the last month of weeks added up to anything, and most founders are too close to their own week to run that check on themselves.

Why it gets misdiagnosed

The instinctive fix for "nothing is moving" is to push harder. Tighter deadlines, more standups, a better project management tool, sometimes a new hire. All of these make an execution problem better and a direction problem worse, because they add more coordinated effort toward a target that was never actually agreed on. The team gets faster at not arriving anywhere.

Minh at Algomate came in sure this was exactly his problem: his outreach volume was the bottleneck, he just needed to push more of it. The actual pattern, once we pulled the thread, was a niche decision he'd been avoiding making at all. Every message he sent had to hedge around a question he hadn't answered for himself, so more outreach just meant more hedged messages, faster. He said it himself afterward: what he thought was the problem "is like just the branch of the tree, not like the root core problem." The fix wasn't more effort. It was one decision, made.

The test, run for real

This week, ask the ten-second question of your team, separately, and actually compare the answers instead of assuming they'd match.

If they match, your problem is somewhere else, probably genuinely execution, and this essay isn't about you. Go look at what's actually slowing the work down.

If they don't match, don't fix it with a meeting where you restate the direction once and hope it sticks. A direction that has to be restated has usually never been decided cleanly in the first place, only announced. Find the actual undecided thing underneath it before you spend another quarter's effort compounding around a target nobody agreed on.

---

More on the person behind it: About Trung Nguyen · The offer: Founder Bottleneck Diagnostic · Related: Why is everyone still waiting on me for everything? · How do I know if I'm the bottleneck in my company?