If You're the Person Who Always Gets the Hard Project, Read This

There's a specific type of professional that most organizations have at least one of, though they rarely acknowledge them explicitly. They're the person who gets called when the thing is complicated. When the stakeholders are difficult, or the timeline is unrealistic, or the previous three people who tried this didn't get very far.

They don't always have the most senior title. They don't always have the largest team. What they have is a track record of getting things across the line in conditions that discourage most people from trying.

If you're reading this and recognizing yourself, this post is for you.

The pattern that produces this reputation

The hard-project person almost always got there the same way: they said yes when others said it was too complicated, they delivered when others said it wasn't possible, and they did it enough times that the organization learned to reach for them when the stakes were high and the path wasn't clear.

That pattern has a compounding effect that's both a reward and a trap. The reward is that you get to work on the most interesting problems. The trap is that interesting problems are often thankless ones — the kind where success is hard to measure, failure is visible, and the conditions are stacked against you before you start.

What actually makes the difference

I've spent nearly two decades being the person organizations reach for when the change is complicated — systems that span 50 countries, teams that resist for reasons that aren't in any playbook, timelines that were optimistic before they were compressed further.

The thing I've learned about what actually makes the difference in those situations isn't something that shows up clearly in credentials or methodology training.

It's the ability to read the actual situation — not the situation as it's been described to you in the briefing, or as it appears in the project charter, but as it actually is once you're inside it. The stakeholder who signed off on the plan but doesn't actually believe in it. The process change that has a workaround everyone knows about and nobody mentions. The timeline that's based on a best-case assumption that's already not true.

Reading those things clearly, early, and being willing to name them — to the project sponsor, to the team, to yourself — is what separates a recovery from a failure. Not methodology. Not framework. The willingness to look at the situation honestly and act on what you see.

What nobody tells you about being the hard-project person

The thing that doesn't get said clearly enough: being the person who gets the hard project isn't the same as being the person who gets the credit for it.

Hard projects are hard partly because the conditions going in are poor. When they succeed, the success gets attributed to the project. When they struggle — even if they struggle for reasons that were baked in before you arrived — the struggle is visible in a way that easier successes aren't.

This is worth knowing before you build your career around it, not as a reason not to do it, but as context for why the reputation matters more than the individual outcome. The organization learns to trust you based on a pattern across projects, not a single result. Any one project can go sideways for reasons that have nothing to do with your judgment or capability. The pattern is what's durable.

A few things worth knowing if this is you

Get clear on what you can actually control, early. Hard projects have a lot of variables that aren't in your hands — organizational politics, resource constraints, stakeholder dynamics, legacy decisions that were made before you arrived. The practitioners who exhaust themselves trying to control everything in sight usually produce the same results as the ones who ignore the things they can't control. The ones who get clear early about what's actually in their scope, and spend their energy there, tend to have more left at the end.

Make the real situation visible, even when it's uncomfortable. The most useful thing you can do for a struggling project is to give the people responsible for it an accurate picture of where it actually is, not where the plan says it should be. This is harder than it sounds, particularly when the people responsible for it are optimistic or invested in a narrative that's no longer accurate. It's almost always the right thing to do.

Don't mistake the hard-project identity for a career strategy. Being good at difficult things in difficult conditions is a real skill. Building your entire professional identity around unavailability for the easy stuff is a different thing, and it has a ceiling. The practitioners who end up with the most options are the ones who can work at both ends of the spectrum — who are trusted for complicated situations and also trusted for straightforward ones.

Why I'm writing this

I'm at a point in my career where I've been the hard-project person long enough to have a perspective on what it's built and what it's cost. This is the kind of post I would have found useful fifteen years ago — not a methodology guide, not a framework for change management, just a practitioner being honest about what the work actually looks like from the inside.

If you're earlier in building this kind of career, I hope some of it is useful. If you're in the same place I am, I'm curious what your version of this looks like.

Peter Dameski is a Change Management and L&D strategist based in Ontario, with nearly two decades of experience leading complex organizational change across financial services, logistics, and technology. He works with growing businesses in an advisory and fractional capacity through The Learning Plan.

Connect with Peter on LinkedIn or reach out through The Learning Plan if your organization has a hard project.