RSS Amplifier

Project Management Matters · Aug 19, 2026

Close Enough, But Not Quite

0
Sign in to vote or save

Philip Diab · Project Management Matters

Years ago, I interviewed for a job I wanted badly, at an organization with the kind of reputation that makes you say yes before you’ve thought it through. On paper, I was close to exactly what they were looking for.

I had the background and the track record in the exact kind of work they were trying to build out. The early rounds went well, well enough that I let myself get ahead of things, picturing the offer before it existed. By every conventional measure people use to judge a candidate, experience, credentials, subject matter knowledge, this wasn’t a stretch. It was a legitimate fit, and it felt like one.

Then came a single moment in the process that derailed everything. I won’t dwell on it in detail because that’s not the point. Needless to say that moment and the mechanics around resulted in a tough rejection.

For a long time I let that outcome shape my understanding of that event. I told myself I did not get the job because I stumbled. But the more distance I got from it, the less that explanation made sense. Even if that single moment had gone differently, something else was already off, something no interview process was ever going to catch.

What I learned later, well after the fact, was that the organization’s own attempt to achieve what they wanted to do never materialized. Also, separately from that, the culture underneath the reputation was a mismatch for how I actually work, regardless of how any hiring process went.

Earlier this week I spoke about mindset in the PMO and today I will take it one level down. Monday was about a PMO: an operating model can be right, the processes can be right, the structure and systems and services can all be right, and the whole thing still fails, because none of that tells you whether the mindset underneath it is there. The same is true of a person. Skills, knowledge, and experience can line up almost completely, close enough that everyone in the room, including you, assumes it’s a match, and it still isn’t enough, because none of those things determine whether the mindset holds once the fit is actually tested.

It’s not just that a mismatched mindset can sink an otherwise qualified person. It’s that a mismatched mindset, at the individual level, sets up the same failure I described before at the organizational level: a PMO with a beautiful operating model and the wrong mindset behind it will still lose its footing. A person with every credential and no mindset match for the environment sets both themselves and the organization up the same way.

A quick reminder of what SERVE actually is.

On Monday I introduced five elements of the same mindset, built from what I’ve watched work, and fail, inside real PMOs. Split-focused. Embedded. Results-Driven. Value-Centric. Evolving. Here’s the shape of it again:

The story above isn’t really about an interview or a hiring process. It’s about what happens when everything measurable lines up and the mindset doesn’t, at any level, a person or a PMO.

So here's the actual question worth asking, whether you're the one being evaluated or the one doing the evaluating: not "did I pass their test," but "is this a place where the way I think is the asset, not just what I know how to do." The first question can be answered in a single room, on a single day. The second one is the only one that tells you whether close enough was ever going to be close enough.

No posts

Read the original on philipdiab.substack.com

Comments

Nothing yet. Say the first thing.

    Sign in to join the conversation.