~ 675 words | ~ 4 minute read
You’ve been doing strong work. Leadership has noticed. And now you’ve been asked to lead a project.
It feels like recognition, and it is. You earned this through the quality of your contributions, your reliability, and the trust you’ve built. The fact that you haven’t formally managed a project before, or haven’t been trained in project management, doesn’t change the confidence others have in you.
The instinct is to move. Set up meetings. Build a timeline. Show momentum. Leadership is watching. The team is waiting. Activity feels like progress.
That instinct makes sense. And in most organizations, it’s rewarded. The person who starts fast looks like the person who has things under control.
But there’s a difference between starting fast and starting well.
What often gets missed
When the pressure to move is strong, the thinking that should come before the plan often gets compressed or skipped entirely.
Timelines get built before the initiative is fully understood. Meetings get scheduled before the right questions have been asked. Structure takes shape before the team has a shared understanding of what the project needs to accomplish and how success will be measured.
This is understandable. Most people stepping into project leadership for the first time haven’t been given a reason to pause. The expectation, spoken or unspoken, is to demonstrate progress. And without formal training or a shared framework to guide early decisions, starting feels like the responsible thing to do.
So the plan gets built. It looks complete. It has dates, milestones, owners.
But underneath, assumptions haven’t been tested. Gaps haven’t been surfaced. And what “success” means for this particular initiative hasn’t been made specific enough to steer by.
A few honest questions first
Before building the plan, build the foundation. Start with questions like these:
- What do I actually know about this project? What don’t I know yet?
- What could derail us? Where can I already see risk forming?
- Who has subject matter expertise I need to lean on early?
- What does success look like, specifically? How do we know when we’re done?
- How does this project connect to what the organization cares about most?
These aren’t complicated. They don’t require a special tool or a formal process. They require a willingness to slow down just enough to think before building.
The answers won’t all come at once. That’s fine. The act of asking surfaces gaps early, while there’s still room to address them.
The house you’re about to build
Think of a project like a house. The plan is the structure: walls, rooms, roof.
But the structure only holds if what’s underneath it is solid.
A weak foundation doesn’t announce itself right away. The house looks fine for a while. Progress feels real. But when pressure builds, when scope shifts, a risk becomes an issue, or a dependency surfaces late, the cracks start to show.
A strong foundation doesn’t prevent every problem. Projects are complex, and conditions change. But it gives you something stable to stand on when those problems arrive. It gives the team a reference point for decisions, a shared understanding of what matters, and the confidence to adapt without losing direction.
The time spent building that foundation is measured in hours. The cost of skipping it is measured in weeks.
What changes when you start here
When the foundation comes first, clarity follows.
Conversations with stakeholders become more focused because you’ve already thought about what you need from them. You walk into those meetings with specific questions rather than open-ended discovery.
Risks get surfaced when there’s still time to plan for them, rather than when they’ve already turned into issues requiring immediate attention.
The plan you eventually build is stronger because you understood what it needed to support before you started assembling it.
And when things shift, as they will, you have something to orient around. Decisions feel less reactive. Course corrections feel less disruptive. The team stays grounded because the early thinking gave them something to anchor to.
The discipline here is quiet and straightforward. A willingness to ask a few honest questions before the work takes on a life of its own. A small investment in early thinking that changes everything that follows…
Want more like this?
If you’re responsible for guiding complex work, setting direction, and being accountable for outcomes, you can subscribe to receive occasional insights on project leadership and delivery.
Thoughtful notes. Practical ideas. Unsubscribe anytime.
Interested in taking this further?
If you’re responsible for the success of critical initiatives — or you’re developing the project leadership skills to support them — I’d be glad to connect.
“The time spent building that foundation is measured in hours. The cost of skipping it is measured in weeks.” This is my favorite takeaway from the article.
Coming from a Sales background, initiatives are often reckless and profit driven vs value focused. Getting to the root problem goes beyond marketing and looking at the foundation, being able to have pillars to gauge navigational changes is critical in not making up more tasks as we go. Often times a critical path was never established, this becomes the glaring roadblock at the bottleneck.
Great read, thanks for the added insight!
Thank you for taking the time to leave a comment, Hamilton. The sales lens you brought to this is spot on. Profit-driven urgency is one of the most common reasons the foundation gets skipped. When the critical path is never established, the bottleneck you described is almost inevitable. Glad it resonated.