2606: The Compass, Not the Map

 One month ago I filed the paperwork and became a company. I didn't have a clean plan for what came next, just a hypothesis that the project management consulting I'd been doing informally would find its footing as something formal. What I didn't expect was how fast the scope would move. A month in, the work has already stretched beyond project management into process engineering consulting, because that's where the actual conversations with clients kept going. Nobody asked me to expand the offering. The clients did, just by talking to me about what was actually breaking in their organizations.

That expansion taught me something I thought I already knew but hadn't really tested: you cannot apply project management by the book. I mean that literally — take the textbook, take the framework, lay it over a real organization, and watch how much of it doesn't fit. Not because the principles are wrong. PMBOK, agile, lean, whatever lineage you draw from, the underlying logic holds up. But the actual company in front of you has its own history, its own scar tissue from past failures, its own unspoken rules about who can say what to whom in a meeting. A framework applied without translation just sits on top of that reality, technically correct and practically useless.

What I've been doing instead — and what I only fully understood by doing it for a month straight — is holding the principled version of "how this should work" in one hand, and sitting down with the client's own internal members to build the version that actually fits their company in the other. That second part isn't optional or secondary. It's the actual consulting. Anyone can hand over the ideal process on a slide. The harder, more valuable work is doing the tailoring together with the people who have to live inside that process every day, so what comes out the other end is recognizably theirs, not mine.

Here's the part that surprised me most: the clients I'm fortunate enough to be working with are genuinely excellent at this. I bring the navigation — here's the principle, here's why it exists, here's the direction — and instead of waiting for me to hand them a finished template, they take that and do the interpretation themselves, quickly and well. They ask the right clarifying questions, they push back where the principle doesn't map cleanly onto their reality, and they land on a tailored version faster than I could have designed it alone. I've started to think my actual job isn't delivering the process. It's pointing true north clearly enough that a capable team can chart their own route to it.

That's the broader lesson from month one: the value of this work was never going to be in how faithfully I could reproduce the textbook. It's in how well I can navigate — hold the principle steady, translate it into something workable in coordination with the people who'll own it, and trust that the more capable the client, the less I need to build for them and the more I need to build with them. A month ago I thought I was starting a project management consultancy. What I'm actually building is a practice in navigation, one client's tailoring at a time.