You get the update every week. Everything's green. There's a demo, some hours logged, a list of things that got done. And you still can't shake the feeling that you don't really know how it's going.

Pay attention to that feeling. It's usually right.

Most teams, when they're deep in the work, track progress by activity. They closed some tickets. They built some components. They solved a few hard problems. That's all real, and I don't want to wave it away. But none of it tells you the thing you actually care about, which is whether this can do what your business needs it to do yet.

A team can be busy, sharp, and working hard while the problem you hired them to solve hasn't budged. It happens because the fun technical problems come first. The plumbing. The framework. The scaffolding nobody ever sees. They dig into that work because it needs doing and because that's where their heads naturally go. Weeks go by. A lot gets built. And you still haven't watched anyone actually do the thing your business needs done.

"On track" hides all of this. On track almost always means on track against a plan, and that plan got written back when everyone knew the least. So when someone says it's on track, they might just mean it still matches a guess from three months ago. That reads fine in a status report. It can also mean nothing at all.

So quit asking whether the team is working hard. They probably are. Ask them to show you the thing doing the thing.

That one change flips what counts as proof. A burndown chart doesn't count. A tour of the architecture doesn't count. Hours don't count. Show me someone finishing the task this whole project is supposed to make possible. Show me something it can do today that it couldn't do last week, described the way a customer would describe it. If the honest answer is "we're still laying the groundwork," you want to hear that in week two, not month six.

I've sat right in the middle of this one. A founder had sunk real money into a team building his platform. The reports looked normal. The demos looked fine. He couldn't tell if any of it was working, and his gut was right, because underneath all that activity there was nothing tying the work back to the business he was trying to build. The effort was genuine. He just couldn't see progress, because in the way that mattered, there wasn't any yet.

We didn't fix it by leaning on the team harder. We changed what "done" meant. Done became "a person can now do something they couldn't do before." The moment that was the bar, everybody could see where things actually stood, the team included, and honestly they seemed relieved.

So here's what I'd take from it. When you can't see progress, don't smooth it over with a nicer status template. That blind spot is the most useful thing you've got right now. Believe it. Then ask for a kind of progress you can watch happen with your own eyes.

A team that's genuinely getting somewhere can always show you. When all they can do is tell you, well, that tells you plenty.