WTF is a Principal Operator?
I spent twenty minutes today on a form that takes ninety seconds. Name. Company. Email. Job title.
The job title is where it stalled.
“Principal Consultant” is what the field wanted. It’s what the field always wants. It’s tidy, it’s legible, and it would have printed onto a lanyard without incident. I typed it, looked at it, and deleted it.
Because I know exactly who that man is. He arrives late in an M3, borrows your whiteboard, uses the word framework four times, leaves behind a deck nobody opens, and invoices in the high five figures. He was never going to be there when the thing broke. He was never meant to be. That was the arrangement.
That is not the arrangement I’m offering, and I’ve stopped pretending the word doesn’t matter.
The word is a promise about the deliverable
Consultant means advisor. That’s not a slur — it’s the definition, and it’s honest about what’s being sold. You buy an opinion. A good consultant sells a very good opinion, informed by pattern recognition you don’t have and can’t build in-house, and there are engagements where that’s exactly the right purchase. Some of the sharpest people I know are consultants and I’d hire them tomorrow.
The problem is what happens at the end. The recommendation lands, the invoice lands, and the consultant leaves. The client is now holding a document and a gap. Everything hard — the build, the migration, the twelve people who don’t want to change how they work, the vendor who lied about the API — all of that is still theirs.
The document was never the hard part.
What an operator sells instead
An operator sells the working thing.
Not the plan for the thing. Not the readiness assessment. The thing, running, in production, with someone still holding the pager on day forty.
The distinction matters because it changes where the risk sits. If I recommend a system and walk away, the risk of that recommendation being wrong belongs entirely to you. If I recommend it, build it, and then run it for a quarter, the risk of being wrong is mine — because I’m the one who’ll have to unpick it at 11pm on a Thursday while you’re asking why the report is empty.
That’s the whole argument. An operator is someone who has to live inside their own advice.
Every operator I respect has run a P&L. Not modelled one — run one. Made payroll. Held a wage line through a bad quarter. Told someone their role was gone. The scar tissue from that is not transferable via slide deck, and it changes what you recommend, because you’ve felt what it costs to be wrong.
The obvious objection
“Principal Operator” is a bit much. It has a faint whiff of tactical nylon about it, and I’m aware that if I lean on it too hard I end up sounding like a man who owns a plate carrier he has never worn outdoors.
Fair. Here’s the test I apply, and you can apply it to me.
Ask the person what they leave behind. If the answer is a document, they’re a consultant, and they should say so — there’s no shame in it and the work is legitimate. If the answer is a system that runs without them, and they can name the date they stopped touching it and why, they’re an operator.
It’s a falsifiable claim, which is the point. Titles that can’t be checked are decoration. This one can be checked by asking me for the URL.
Why I bothered changing it
Because the word was pre-loading the wrong conversation.
When I introduced myself as a consultant, the next question was always what’s your day rate — which is the correct question to ask a consultant, and the wrong question to ask me. Day rate implies the deliverable is my time. It isn’t. The deliverable is the thing working, and how long that takes is my problem to solve, not a lever to price against.
Change the noun and the second question changes with it. What do you actually build? is a conversation I want to have. What’s your day rate? is a negotiation about how thin I can be sliced.
Twenty minutes on a ninety-second form, and I got a better opening line out of it.
The lanyard
So the badge says Principal Operator, and at some point on the night someone will squint at it and ask what that means, and I’ll get to say:
I build the systems, and then I stay until they work.
Which is a sentence that survives contact with the invoice. Consultant never quite did.
Alex Hender is the founder of Abundant Kindling, a systems studio that builds and runs technology, operations, and sustainability infrastructure for founders and leaders. He is, on the appropriate forms, still a Director.