New Project Leaders often assume credibility comes from having every answer, when the opposite is true. Credibility comes from asking the right questions early enough that problems never become surprises, and from understanding how an organisation defines success before trying to lead within it. Together, this raises a much bigger question: how should organisations prepare leaders for scale before the gap between title and readiness becomes a delivery risk?
Table of Contents
“What if they realise I have never led something like this before?”
Nobody says it out loud.
Most Project Leaders will never admit they have asked themselves this question.
I remember having just accepted a role that looked exciting during the interview. The title was bigger. The budget was larger. The stakeholder landscape was more complex. The team was bigger than anything I had previously led.
Then the reality started to sink in.
“Did I overestimate myself?”
“Will the team realise I do not know everything?”
“Will leadership think they hired the wrong person?”
Those thoughts do not make it into project reports, yet they shape how many leaders behave during the first few months.
For me, it was not just once.
Several times throughout my career.
Every significant opportunity required me to lead something I had never done before. Larger budgets. Different industries. Bigger teams. More complex governance. More stakeholders. Every step felt uncomfortable before it became familiar.
It took me a long time to figure out how to navigate the scenes, and not pretend I had all the answers.
It was learning to observe, and not absorb those emotions to get into my own head.
It was learning how to understand the environment before trying to control it.
That approach has become the framework I still rely on today.
What This Article Covers
This edition looks at what happens the first time you lead something bigger than anything you have done before, and the framework I return to whenever everything feels unfamiliar.
Why This Matters
We spend a lot of time developing technical capability. But very little time is spent preparing for the emotional side of leadership.
The expectation becomes:
“You have the title now. Figure it out.”
Without a mentor, you can spend months reacting to problems you could have understood in the first few weeks. That is where the pressure builds, decisions slow down and confidence starts to slip. Moving into a larger project is not simply doing more of what you already know. It is about learning how to lead confidently while you are still learning yourself, and learning how to read the environment before trying to control it.
The Hidden Risk
A lot of new leaders believe they need to have all the answers to be credible. The opposite is true.
Your first responsibility is to understand the organisation before trying to lead the project. In my experience, credibility comes from asking the right questions early enough that problems never become surprises.
Every organisation has an operating rhythm that is never written down.
Every project has its own rhythm.
Until you understand both, every decision is simply an assumption.
The Leadership Response
When I step into a project that is larger than anything I have previously delivered, I deliberately slow myself down and take this approach, because understanding always saves more time than reacting.
1. Understand the organisation before trying to understand the project
One lesson I learnt early is that organisations do not all measure success the same way.
Some value speed over perfection. Others would rather extend a programme by several months if it reduces operational or safety risk. Some expect every dollar to be justified. Others are prepared to invest more if it improves long-term outcomes.
If you do not understand how your organisation thinks, it becomes very easy to solve the wrong problem.
Before diving into schedules and delivery plans, spend time with your sponsor, Executive Director or reporting manager.
Ask questions such as:
- What does success look like here?
- How flexible are programme budgets?
- How much contingency does leadership expect?
- Is finishing earlier more important than finishing perfectly?
- What would make the CEO uncomfortable?
Those conversations will shape every major decision you make afterwards.
2. Borrow experience before trying to create your own
Every organisation leaves clues.
When I transitioned from delivering traditional capital works into a rail infrastructure environment, I quickly realised they were not simply different versions of the same work.
Rail projects operated with different governance, different approval pathways, significantly higher safety requirements and far more dependencies.
Had I approached them using the same assumptions I had developed elsewhere, I would have set unrealistic expectations from the very beginning.
Instead, I spent time reviewing previous project documentation, reading lessons learnt, understanding where programmes slowed down and speaking with people who had already delivered similar projects.
Those conversations gave me months of experience before I had made my first significant decision.
Ask questions such as:
- What similar projects have been delivered?
- Which contractors consistently performed well?
- Where were the biggest governance failures?
- What level of risk is considered acceptable?
- What would concern the executive team most?
- How are difficult decisions normally escalated?
You are not starting from zero.
You are standing on someone else’s lessons.
3. Listen until the project starts making sense
One of the quickest ways to lose credibility is to arrive with solutions before understanding the problem.
Every discipline sees the project differently.
Engineering focuses on technical delivery.
Commercial sees contractual risk.
Finance sees budget pressure.
Operations worry about business disruption.
Contractors often understand delivery constraints that internal teams cannot see.
Whenever I join a new project, I deliberately spend time listening before leading.
One question I often ask is:
“If you were sitting in my chair, what would you be paying attention to first?”
The answers are rarely the same.
Somewhere between all of those conversations, the real project begins to appear.
4. Connect the dots before making promises
Once I have gathered those perspectives, I analyse to understand,
“Does the project being reported reflect the actual project scenario people are actually experiencing?”
This is where patterns begin to emerge.
Dependencies become clearer.
Critical path activities start revealing themselves.
You identify where one contractor may be carrying disproportionate delivery risk, where resources are stretched too thin, or where approvals will become bottlenecks months before they appear on the programme.
Only after building that complete picture do I begin discussing revised timelines, additional resources or changes to delivery strategy.
5. Reset expectations with evidence, not emotion
One of the hardest conversations for any leader is telling leadership that the original plan may not be achievable. The instinct is to protect them from bad news.
Even after leading many projects and programmes, I still catch myself doing this every time I step into a new leadership role. There is a part of me that feels responsible for getting the project across the line, and that makes it hard to be the one delivering news that might disappoint leadership.
Over the years, though, I have noticed that the best leaders have this conversation early, so there is clarity before it becomes a problem.
In reality, executives are rarely frustrated by bad news. They become frustrated when they receive bad news too late.
If additional resources are required, explain why.
If the programme needs more time, demonstrate the dependencies.
If specialist contractors are better positioned to deliver part of the work, present the evidence.
Transparency, when supported by facts and options, builds trust.
It also gives leadership the opportunity to make informed decisions before issues become crises.
Thinking by First Principles
The larger the project becomes, the less your role is about having every answer.
It becomes about reducing uncertainty for everyone around you.
Leadership is not about demonstrating that you know everything.
It is creating enough clarity that your team, stakeholders and executives can make better decisions together.
They all bring their own expertise. Your role is to create the environment where the right people can solve the right problems at the right time.
The ‘Settle Before You Steer’ Framework
Whenever I step into unfamiliar territory, I return to these six questions.
| Step | Question |
| Understand | How does this organisation define success? |
| Learn | What have similar projects already taught us? |
| Observe | What is really happening versus what reports say? |
| Connect | What story emerges when all those perspectives come together? |
| Validate | What assumptions need evidence before action? |
| Align | Does leadership have the same understanding of reality as the delivery team? |
I still work through these questions today.
Not because I lack experience.
Because experience has taught me never to assume.
Looking Beneath the Surface
Confidence does not come from knowing everything.
It comes from knowing how to learn quickly, and how to pivot in the right direction.
The strongest Project Leaders I have worked with were never the people with all the answers.
They were the people who stayed curious long enough to ask better questions than everyone else.
Key Takeaways
- Every new leadership role comes with private doubts. That does not mean you are unqualified.
- Learn how the organisation makes decisions before trying to change them.
- Borrow experience from previous projects instead of starting from scratch.
- Listen across every discipline before forming conclusions.
- Build your credibility through transparency, curiosity and evidence, not by pretending to know everything.
Questions Worth Asking
Before taking ownership of your next project, ask yourself:
- Do I understand how this organisation defines success?
- What assumptions am I making because of my previous experience?
- Which people have already solved problems I have not encountered yet?
- Have I listened to every discipline involved in delivery?
- Does leadership have the same understanding of the project’s reality as the team delivering it?
- What conversation should I have now that will prevent a much harder conversation later?
Closing Thought
The best Project Leaders are not the ones who know the most on day one. They are the ones who learn the fastest before everyone else realises how much there is to learn.
— Renie Fernandes