Reflection Quest — Part 2 of The Watchmaker's Dilemma
The promotion announcement arrives on a Tuesday, buried in the middle of a company-wide email that also covers parking policy changes and a reminder about the quarterly team lunch. Priya reads it at her standing desk, coffee untouched, her face doing something I've learned to recognize — that particular stillness that happens when someone is deciding, in real time, which feeling to let reach the surface.
The role went to Marcus.
Marcus is good. I want to be clear about that, because what follows isn't a story about incompetence being rewarded. Marcus is articulate, visible, and strategic in the way the word is used in rooms where budgets get decided. He presents well. His slides have a rhythm to them — problem, insight, recommendation — that makes complex things feel navigable. He's built relationships across four departments. People know his name before they know his work, which is itself a kind of work, though not the kind anyone writes a job description for.
Priya is better. At the actual thing. The engineering. The system design. The quiet, load-bearing work of making architecture decisions that won't become someone else's emergency in eighteen months. She's the person other engineers go to when the problem isn't political but genuinely hard — when the abstractions break down, and you need someone who can hold the whole system in their head and find the fault line. She's written more architecture decision records than anyone on the team. She's mentored three engineers into senior roles. Her code reviews are legendary — not for their harshness, but for their precision. She finds the structural problem hiding behind the surface fix, every time.
She didn't get the role.
"I don't understand," she says, later, in the one-on-one that wasn't scheduled but happened anyway — the kind that starts with a question about a pull request and ends somewhere neither of you planned. "I did everything right. I got better. I kept getting better."
She's not wrong. That's what makes this hard.
I've been thinking about Omega. Not the abstract concept — the actual company, the Swiss watchmaker that made some of the most precise mechanical movements ever manufactured. During the golden age of watchmaking — roughly 1945 to 1970 — Omega was the engineers' engineers. Their movements won accuracy competitions. Their chronometers went to the moon. They were, by every technical measure that mattered, among the best in the world at the thing watches were supposed to do.
Then the world changed. Japanese manufacturers caught up on precision. The Swiss franc's value nearly tripled, making Swiss watches expensive without making them better. And quartz arrived — cheap, thin, devastatingly accurate — rendering the entire competition for mechanical precision irrelevant. The thing watches were supposed to do could now be done by a five-dollar digital display.
The watchmakers who survived — Patek Philippe, Audemars Piguet, Rolex — survived by shifting. They redesigned their cases. They made their brands visible, their watches larger, their names louder. They stopped competing on mechanism and started competing on recognition. They understood, faster than Omega, that the rules had changed.
Omega did what Omega knew how to do. They made better movements.
When Japanese watches got more accurate, Omega responded by engineering a movement that ran at 45% higher frequency. In theory, this should have improved precision. In practice, the new mechanism was so fragile that it destroyed their reputation for reliability. They'd solved the wrong problem — brilliantly, precisely, with all the technical excellence they were famous for — and it broke them. They even tried to make a superior quartz movement, but that road led nowhere except a race to the bottom against manufacturers who could do it cheaper.
By 1981, Omega was insolvent. Taken over by creditors. The company that had timed the Olympics, that had gone to the moon, that had been synonymous with precision — gone. Not because they got worse. Because they got better at something the world had stopped paying for.
I think about that when I think about Priya.
There's a particular kind of advice that circulates in organizations like a folk remedy that nobody's tested — "do great work and it'll be noticed." It carries the authority of something that should be true, that we want to be true, that was probably true once. And like most folk remedies, it works just often enough to maintain its reputation while failing in ways that are hard to attribute.
The advice isn't wrong. It's golden age advice. It assumes a world where the mechanism is the signal — where the quality of the work is itself the thing that gets recognized, where doing better is synonymous with being seen. In the golden age of watchmaking, this was literally true. The best watches won observatory trials. The precision was measurable, comparable, and visible to anyone who cared to look. The substance was the visibility.
But Priya doesn't work in the golden age. She works in an organization that has — without announcing it, without deciding it, without anyone signing a memo — shifted from evaluating substance to evaluating signal. Not entirely. Not cynically. The technical work still matters, the way the mechanism inside a luxury watch still matters — it has to be good enough. But "good enough" is a threshold, not a competition. Once you've crossed it, what differentiates you isn't the quality of the mechanism. It's the size of the case.
Marcus understood this. Not because he's shallow — I want to resist that reading, because it's too easy and it misses the real pattern. Marcus understood it the way a watchmaker in 1975 might have understood that the game had changed: not with joy, not with cynicism, but with the practical clarity of someone who noticed the tide before it reached their ankles. He built relationships because relationships are how decisions get made in organizations that have outgrown the stage where a single person's technical output can be evaluated by the people making promotion decisions. He presented well because presentation is how complex work becomes legible to people who don't have time to read the architecture decision records. He made himself visible because, in a system that can no longer tell who's doing the best work by looking at the work itself, visibility is what fills the gap.
Priya made a better movement. Marcus redesigned the case.
The cruelty of this isn't that Priya was wrong to focus on substance. The cruelty is that she was right — in a world that's moved on from rewarding rightness in the way she understood it. She followed the golden age playbook in a brand age organization, and the playbook worked exactly as advertised, producing exactly the results it promised: she became genuinely excellent at the thing that used to matter most.
I've watched this pattern enough times to notice where the pain actually lives. It's not in the disappointment of being passed over — that heals. It's in the epistemological vertigo that follows. The moment when someone who has built their entire professional identity on the premise that quality is self-evident is forced to confront the possibility that quality, past a certain threshold, is invisible. That the very thing they're best at has become, in organizational terms, infrastructure. Essential but unseen. Load-bearing but unremarkable. The brick underneath the marble.
The dojo had its Omegas. I remember them — the students whose technique was immaculate, whose katas were textbook-perfect, who could explain the physics of a throw with the precision of an engineering diagram. They trained harder than anyone. They knew the forms better than anyone. And when it came time for the instructor to choose who'd demonstrate at the regional showcase, the nod went to the student whose technique was merely good but whose presence filled the room. Whose movements had a quality that wasn't precision but something adjacent to it — something closer to expression, or charisma, or that indefinable thing that makes you unable to look away.
The Omega students didn't understand. They'd done everything right. They'd followed the rules — the actual rules, the technical ones, the ones that were supposed to be the point. What they hadn't noticed was that the room had changed. The showcase wasn't an observatory trial. It wasn't measuring precision. It was measuring something the precise students hadn't been trained for, because nobody had told them the criteria had shifted. Or rather, nobody had told them because nobody had decided it - it had just happened. The way tides happen. The way golden ages end.
I feel this tension in myself more than I'd like to admit. The instinct to make the work better rather than make the work visible — to refine the mechanism rather than enlarge the case. To write one more draft instead of publishing. To deepen the analysis, instead of presenting the summary. To trust that the substance, if it's good enough, will find its way to the surface without help.
It won't. Not reliably. Not anymore. And sitting with that realization is its own particular kind of discomfort — not the clean discomfort of being wrong, but the muddier discomfort of being right in a way that no longer helps.
Something the Greeks might have called sophrosyne — that quality of occupying oneself completely, of being sound in one's own mind — lives in Priya's approach to engineering. She is fully present in the work. Undivided. The mechanism and the maker are inseparable. But sophrosyne in a world that's stopped looking at mechanisms becomes something quieter and sadder: a perfection nobody has the attention span to witness.
I'm not going to tell you that Priya should learn to self-promote. That would be too clean, too prescriptive, and it would miss the real tension. The real tension is that both paths cost something. Omega died being right. Patek survived by becoming less of what originally made them great. The engineers' engineers went insolvent. The prestige-first watchmakers are now managing asset bubbles and policing their own customers. Neither is a clean win. Neither is a story you'd want to tell as advice.
What I can tell you is what I told Priya — or rather, what I asked her, in that unscheduled one-on-one that had long since left the territory of pull requests:
"What if the work being excellent and the work being recognized are two different skills — and you've been treating them as one?"
She was quiet for a long time. Not the uncomfortable silence of someone who disagrees. The heavier silence of someone rearranging furniture in a room they thought they knew.
"That would mean I've been playing one game while they've been scoring another," she said.
Yes. That's exactly what it would mean.
The late afternoon has turned the glass walls of the meeting room into mirrors. Priya's reflection overlaps with the whiteboard behind her, where someone's architecture diagram — her architecture diagram, I realize — is still drawn in blue marker from last week's design review. The diagram is elegant. Clear. The kind of thinking that holds a system together without anyone noticing it's there.
She looks at the diagram. Then, in her reflection. Then, at the space between them, where the two images blur into something neither clean nor legible.
"I need to think about this," she says.
I nod because the thinking is the point. Not the answer — there might not be an answer that doesn't cost something. But the recognition that the game changed, that the golden age ended, that the observatory trials are over, and the mechanism alone isn't enough — that recognition is where something new begins. Even if the new thing is uncomfortable. Even if it means accepting that the world doesn't owe you an audience for your precision.
Omega made the best movements ever built. The moon wore its watch. The observatories recorded their accuracy to fractions of seconds. And the world moved on.
The mechanism still matters. It always will. But the mechanism alone, in a world that's stopped looking inside the case — the mechanism alone is a secret kept from an audience that never asked.
Priya's architecture diagram is still on the whiteboard. Nobody's erased it. Nobody's looked at it either. It just holds the system together, quietly, the way a brick holds a city.
Some things are like that. Essential and invisible. Load-bearing and unremarked. Excellent in a way that only the people close enough to read the half-millimeter type will ever see.
The question is whether that's enough.
I don't think Priya knows yet. I don't think I do either.
If you recognized the vertigo — the moment when doing excellent work and being recognized for it stopped being the same thing — send this to the Omega in your organization. The one whose architecture diagram is still on the whiteboard. They might not know the game changed.
