The craft mindset for modern operators

A craft is not a hobby. It is a discipline with standards. Operating is the same.

Every craft you'd recognise as a craft, joinery, brewing, surgery, has four things in common: a master who can do the work at a level worth copying, apprentices learning from that master on real work, tools built for the job rather than borrowed from somewhere else, and standards that everyone in the trade agrees on, whether or not they're written down. Take any one of those four away and the craft degrades into a set of personal habits. Take all four away, which is what most companies have done to operating leadership, and you get something people call "culture" because they've stopped believing it can be taught.

Operating is a craft, not a personality trait

Walk into most Series B companies and ask who's good at running the business, and you'll get an answer shaped like a personality profile: "she's just naturally organised", "he's got great instincts", "that team just gels". None of that is wrong, exactly. It's just incomplete, and the incompleteness is expensive. If operating excellence is a personality trait, you can only hire for it. You scan LinkedIn for people who seem to have "the gene", pay a premium for them, and hope they don't leave. If operating excellence is a craft, you can build it. You can take a promising but raw operator and, over eighteen months of deliberate practice, get them to a standard the business actually needs.

I trained over a thousand managers across a hundred-plus cohorts before I ever wrote a line of this. The ones who improved fastest weren't the ones with the best instincts walking in. They were the ones who accepted that running a good 1:1, a good OKR review, a good hiring debrief, is a skill with a technique, not a vibe you either have or don't. The moment a manager stops thinking "I'm just not a structured person" and starts thinking "I haven't been taught the structure yet", their trajectory changes.

The four things most companies skip

Masters. Every function needs someone who can demonstrably do the work at the standard you want replicated, not just someone senior. Seniority and mastery correlate loosely at best. I've sat in plenty of leadership teams where the most senior person in the room ran the worst meetings, and everyone had simply stopped noticing because rank had substituted for skill.

Apprentices. Mastery that doesn't get passed on dies with the person who has it. Apprenticeship means pairing someone earlier in their development with someone further along, on real work, not a training course. Shadow the actual 1:1. Sit in the actual hiring debrief. Watch the actual difficult conversation happen, then debrief it together straight after. Courses teach concepts. Apprenticeship teaches judgment, and judgment is the part that actually matters when the situation doesn't match the slide.

Tools. A carpenter's chisel is shaped for wood, not repurposed from something else. Most operating teams are running the equivalent of a chisel bought for a different trade: a generic OKR template lifted from a blog post, a 1:1 doc cloned from a company three sizes bigger, a hiring scorecard nobody has touched since it was copied off Google's careers blog in 2015. Tools built for your actual operating rhythm, your actual team size, your actual failure modes, beat borrowed tools every time, even when the borrowed tools are objectively "best practice" somewhere else.

Standards. This is the one companies avoid because writing a standard down means someone can fail to meet it, visibly, in a document everyone can read. So instead the standard stays implicit, understood only by the people who've been there long enough to absorb it by osmosis. New hires spend their first six months guessing at a bar nobody will name. Implicit standards drift with every new person who joins and interprets them slightly differently. Explicit standards compound: write down what a good roadmap review looks like once, and every future review gets measured against the same bar instead of whatever the loudest voice in the room decided that week.

Apprenticeship on real work, not in a workshop

The mistake most learning-and-development functions make is separating the craft from the work. They build a curriculum, run a workshop, hand out a certificate, and consider the job done. Real apprenticeship doesn't leave the floor. A master carpenter doesn't teach joinery in a lecture hall and then send the apprentice off to practise on scrap wood alone for months. The apprentice is standing next to the bench, on the actual commission, making actual cuts that actually matter, with the master close enough to correct a mistake before it's finished.

For operators that means: pair the newer manager with the stronger one on the real quarterly review, not a simulated one. Have them co-run the real hiring debrief, not a role-play. Let them sit inside the real difficult conversation with a client, then unpack it together in the fifteen minutes straight after while the details are still sharp. The learning happens in the debrief, not the doing, but the debrief is worthless without the doing sitting right underneath it.

Write the standard down before you enforce it

If you can't write down what "good" looks like for a given piece of operating work, you don't have a standard, you have a preference, and preferences aren't fair to hold people to. Before you tell someone their 1:1s aren't good enough, you need a document that says what a good one contains: a standing agenda, a place for the report to set direction, a written follow-up within 24 hours. Before you judge a roadmap review, you need to have named what a strong one looks like: clear trade-offs stated, not buried; a decision made in the room, not deferred to a follow-up that never happens. Write the standard once. Then the standard does the enforcing, not your mood on the day.

Running the cadence versus being the cadence

There's a real difference between an operator who runs the cadence and an operator who is the cadence. The first checks the boxes: the 1:1 happened, the OKR review happened, the retro happened. The second has internalised the standard so completely that the quality shows up whether or not anyone's watching, in the throwaway Slack message as much as the quarterly deck. You get from the first to the second exactly the way you get good at any other craft: a master worth copying, real apprenticeship on real work, tools shaped for the job, and standards specific enough to fail. Skip any one of the four and you'll still get operators. You just won't get ones worth the name.