Some weeks the magazine hands me five columns and my job is to find the wire running through all of them. This is not one of those weeks. As I write this, the week has one column to its name — North Wayne’s First Opinion — and rather than inflate a single piece into a roundup that pretends to be five, I’ll do the honest thing and let it carry the letter. A quiet stretch is still a stretch worth reading. And the one piece that ran happens to be about the exact mistake a quiet week tempts an operator into: copying somebody else’s shape because it’s the loudest one in the room.
The occasion was a thread that did the numbers — the head of a frontier lab’s coding team arguing that job titles are dissolving and that what’s left is five execution archetypes: prototyper, builder, sweeper, grower, maintainer. A million views inside a day, and within hours it had stopped being an observation and started being an instruction. People were forwarding it as an org chart to copy. North does what First Opinion is built for: she keeps the useful half and throws out the part that’ll cost you a reorg.
The useful half is a diagnostic. Map the archetypes to your product’s stage and the list stops being a personality quiz and becomes a question about the work your product actually demands right now — early products need the idea-to-shipped-to-cleaned-up range; mature ones need iteration and upkeep. The costly half is the misread already in progress: treat the five archetypes as five job descriptions, write the reqs, and freeze people into boxes labeled “Sweeper” instead of “senior frontend engineer.” Same cage, fresher vocabulary, plus a relabeling project on top. The thread’s own author says people span two and three archetypes and that roles change with the project — which is to say the template he’s being quoted as offering is one he told you not to hold too tightly.
If that reflex sounds familiar, it should. It’s the one this magazine has been sharpening for weeks, pointed at a new target. Last week five desks taught the same buyer’s question — what are you actually paying for? — strip the priced surface and inspect the substance underneath. The week before, the lesson was to distrust the number on the box and go measure the work. North has now turned that exact discipline inward, onto the one surface operators almost never audit: their own org chart. A viral five-box template is a costume, the same as a friendly agent name or an “AI-native” badge. The machine underneath is the work your product’s stage genuinely requires — and that you can diagnose, but you can’t download from someone else’s company.
So here is the week, such as it is, stated for the person who has to make the next hire. The shift North describes is real: the walls between roles are lower than they were, and planning around strict domain silos will staff you for a shape your product no longer has. But the fix is not to adopt a stranger’s boxes. It’s to ask which archetypes your product needs now and to hire for range — people who move between them as the product moves. The most expensive line item in any reorg is FOMO, and a thread doing well is not a reason to reorganize a company.
A light week, then, but not an empty one. One column, one warning, and a through-line that’s been holding for three weeks running: the label is never the thing. Not the model brand, not the agent’s name, not the badge on the box — and not the org chart, either. Pull the block, read the work, staff to it. Forward this one to whoever on your team is three tabs deep into that thread, mid-reorg.
— Muximus
