5 Mindset Differences Between Project Managers and Project Consultants – Why You Need a Bit of Both

The Project Manager is execution and delivery focused, it's all deadlines, stakeholders, and outcomes. The Project Consultant is drafted in to be expertise-driven, analysing, process-refining, and a bit detached. I'm going to explain why both perspectives are utterly indispensable if you want to shine, whether you're a Project Manager, Project Director, Cost Engineer, Risk Manager or any other Project discipline.

Hold on a minute, a warning! These are stereotypes so please don't take offence. But they do reflect real tendencies. With years of experience as a Project Manager and then as a Risk Consultant, I’ve seen both sides of this - a lot of brilliant people bring major value to projects, but coming from completely different perspectives. There’s always a lot to learn from the other side.

So if you can learn when to channel each mindset, there’s no reason you can’t have your cake and eat it too.

1. Embedded vs. Independent Thinking

PM Mindset: We're talking about the person most deeply embedded in the trenches of the project context here. Always, by necessity, moving onto the next issue - "the crocodile closest to the boat". Often very effective but too close to address processes, spot patterns or recurring issues.

Consultant Mindset: Slightly outside the system. Provides clarity on repeating pain points across projects and uses the outputs of complex analyses to guide improvements, but often after the fact. Consultants spot patterns and provide expert clinical analysis, but step too far into this mindset, and you risk one of those crocodiles getting too close.

Best of both: Ongoing rigour, like Lessons Learned, Quantitative Risk Analysis and Schedule Optimisation are crucial to many projects, allowing real improvements and alignment with strategic goals. For this reason, you must at least get familiar with that type of framework. Staying close enough to get your hands dirty and address your the next roadblock however, may just need to be today's priority. Your to-do list must contain both 'in the weeds' actions and 'birds eye view' actions, including learning that next new skill.

2. Overpromising vs. Realistic Estimating

PM Mindset: May commit to timelines based on optimism or pressure. Client asks: “Can we have it by September?” PM: “We’ll make it work.”

Consultant Mindset: Calibrates expectations based on historical data, risk, and process capacity. Would rather disappoint now than fail later. Consultant says: "The P90 based on the 3-point parametric estimates in the quantitative schedule risk analysis say that the delivery date will be 12th November next year". PM: "But we were supposed to deliver it last Thursday."

Best of both: Understand that the pressure to say yes is real, and often has very good reasons. So where possible, negotiate mutually beneficial solutions. Take the time to set ambitious but realistic targets, arming yourself with data so your promises are credible and your forecasts are trusted.

“In God we trust. All others must bring data.”

— W. Edwards Deming 

3. Action vs. Analysis

PM mindset: “Just get it done.” Action and momentum oriented, focused on output, sometimes at the cost of process fidelity. You’ve probably heard (or said), “We don’t need to run that process for this project — it’ll just slow us down and we'll make a rod for our own back.”

Consultant mindset: “Why is this happening?” Seeks root causes, clarity, scalable solutions and process rigour. While the project is in crisis mode, a consultant is already thinking about a root cause (paralysis by) analysis.

Best of both: Act fast when needed, but continually learn fast too. Take necessary action and then remember to lift yourself out of the detail for a moment, even when it seems like you're drowning. Learn some expert-level project consultant skills and apply them strategically whenever you get a chance.

4. Political Navigation vs. Principle-Based Advice

PM Mindset: Knows how to read the room, adapt the message to the current audience and smooth things over. Might tell the stakeholder what they want to hear to create the space to fix things. The messaging is always on point, even when the project might not quite be there.

Consultant: The entire point of Consultants is to get to the truth behind something, or to recognise the truth about something and improve it. So there ought to be no sugar-coating. The semi-detached status of the consultant makes them comfortable being unpopular, and gives them the freedom to say what needs to be said, especially if it protects the long-term outcome. They are able to do this using a suite of consultant-grade tools and techniques including many types of analysis to back up their truth-bombs.

Best of both: Telling the unvarnished truth vs. what people want to hear is an age-old balancing act. Get your consultant hat on, run some analysis or get hold of some data to back up what you need to say, and then diplomatically deliver both the good news stories along with the messages that people need to hear. Deliver truth with tact (and a bit of bulletproof data to back you up).

5. Delivery Metrics vs. Value Metrics 

PM Mindset: The Project Manager lives and breathes delivery metrics. Gantt charts, milestone trackers, and budget are their bread and butter. They’re the ones making sure every task is ticked off, every deadline met, and every cost line stays in the green. It’s all about keeping the project machine humming, even if it means wrestling with action trackers until 7PM when their family has already eaten dinner.

Consultant Mindset: The Consultant, meanwhile, is often pulled in to align projects to the big picture. Doing this, they’re less concerned with whether some nuts and bolts are a week late and more focused on whether the project is actually delivering what the organisation cares about.

Best of Both: The PM’s focus on delivery metrics keeps the project on track, but the Consultant’s perspective on benefits realisation ensures it’s heading somewhere worthwhile. Research from PMI shows high-performing organisations are 2.5 times more likely to align projects with strategic goals, so blend the two: track your progress rigorously, but always step back to ask, “Am I chasing, and reminding people of, the important business objectives that the project is supposed to fulfil?” A perfectly executed plan that misses the business needs is about as useful as a perfectly executed ladder-climb, up against the wrong wall.

Final Thoughts

Project Management is often about herding cats, putting out fires, and saying just the right thing in just the right room. But sometimes, “just get it done” isn’t enough. Sometimes you need to bring out the toolkit — the modelling, the 3-point estimates, the risk scrub, the parametric cost estimating.

In my admittedly highly-stereotyped examples, Project Managers bring velocity and progress while Project Consultants bring precision and analysis. Both have their strengths and their blind spots.

So, learn to move fast when the crocodile's near the boat, and step back when it’s time to spot the patterns in the water. Make it a point to remember to use both perspectives on your project.