Many founders notice this pattern. You ask about the project status—team says they’ve been
working hard all week. But when you check the milestone tracker, nothing moved forward. Site
visited twice. Three vendor calls made. Two meetings conducted. Plenty of activity. Zero
milestone progress. How does everyone stay busy while the project stands still?
I’m Milind Bibikar, and I work with mid-sized B2B engineering and project companies.
Why does this happen?
First, activity is visible and measurable. Hours spent on site can be logged. Calls made can be
counted. Meetings attended can be reported. “Poora din kaam kiya, dekho kitna busy the.” But
whether that activity moved the needle toward project completion? Nobody tracks that. Teams
confuse motion with progress because motion is easier to demonstrate.
Second, milestones require decisions that feel risky. Moving to the next phase means
committing that the current phase is truly complete. What if something was missed? What if
there’s a problem later? Safer to do one more check. One more round of review. “Ek baar aur
confirm kar lete hain, fir aage badhte hain.” The milestone deadline passes while everyone
stays busy preparing to be ready.
Third, daily urgencies override milestone priorities. A vendor calls with a pricing issue—that’s a
fire to put out. A client emails with a question—that needs an immediate response. Site reports a
minor delay—someone must investigate. “Yeh urgent tha, pehle yeh kar diya.” By evening, the
team handled fifteen urgent items. None of them were on the critical path to the next milestone.
Fourth, there’s no clear owner for milestone completion. The project manager coordinates. The
site engineer executes. The design team supports. When the milestone is missed, who exactly
was responsible for hitting it? Everyone contributed their part. Everyone stayed busy. But
nobody owned the outcome. “Humne toh apna kaam kar diya, baaki ka pata nahi.”
One founder’s weekly review is a report of activities completed—site visits, vendor meetings,
and documentation prepared. Another founder’s team reports which milestones moved from red to
green and what decision unblocked them.
Same project scope. Entirely different definition of progress.
Here’s what happens in the activity-focused company. Projects that should take six months take
nine. Not because the work is harder. Because three months get consumed in being busy
around the work instead of completing it. Buffer time disappears into untracked activity. When a
real problem emerges, there’s no cushion left.
The question isn’t “Why isn’t my team working hard enough?” The better question is: “What
would have to be true for busy teams to produce stalled projects?” Because if activity and
outcomes have become disconnected, growth just means more people being busy while
timelines keep slipping.
