Most teams already know how to grind. The hard part is figuring out which work actually matters, and who gets paid to do it. A short story published on swizec.com earlier this month puts a neat frame around a familiar frustration: when routine work isn't possible, experts make more money per hour because they pick the right problem before they touch a tool.
It is not really about bikes. It is about positioning, judgment, and the slow climb from generalist to specialist. For project managers and scrum masters, the lesson lands right in the middle of sprint planning, stand-ups, and the daily scramble to keep delivery on track.
The short version:
- The piece uses a motorcycle clutch story to compare a generalist mechanic with a Triumph specialist.
- The generalist quoted three hours of diagnostic work and asked for an appointment.
- The specialist fixed the same fault in about ten seconds with a pocket wrench, then charged nothing.
- The core argument: experts earn more because they do the right work, not more work, and they pick a niche to get there.
How we got here: the long climb to senior
Generalists are everywhere, and for good reason. Early in any career, breadth is how you survive. You learn to fix the clutch and the brakes, run a stand-up, write a user story, and calm down an angry stakeholder, often in the same afternoon. Breadth feels like value. It also keeps you busy.
Then something changes. Years in, the same problems keep showing up with different costumes. The stand-up that runs thirty minutes. The retrospective where nothing actually gets fixed. The roadmap that everyone argues about instead of shipping. Breadth alone stops paying a premium.
This is the moment when people start asking a different question. Not "how do I do more?" but "how do I do the right things, faster?" That shift is what separates a steady mid-career professional from a senior one, in engineering, in project management, in scrum mastery, or in leadership.
What changed now: the right work, not more work
The swizec.com piece draws a sharp line between two mechanics on the same problem. The first mechanic ran a wide diagnostic, guessed at a three-hour teardown, and asked the customer to come back. The second mechanic walked up, recognized the factory quirk, pulled out a keychain wrench, and solved it in seconds.
Neither outcome is about raw skill. Both mechanics can wrench. The difference is pattern recognition built inside one niche. The Triumph specialist had seen that exact fault enough times to know the cause before pulling it apart. It is the same pattern behind a senior scrum master who can hear a blocker description and already know which ceremony is broken.
The uncomfortable truth hiding in the story is that experts often do less work and charge more. That feels unfair until you remember how long it took to build the pattern library in the first place.
Our analysis: why this matters for agile teams
So what does a clutch lever have to do with sprints and stand-ups? Quite a lot, honestly.
In agile project management, the daily temptation is to pack the sprint. More tickets, more meetings, more status updates. It feels productive. It usually is not. The senior voice in the room is often the one who says, "we are not solving the right problem here." That is the pocket wrench moment.
Think about leadership tips in this light. Most leadership advice is just generalist mechanics quoting three-hour jobs: try this framework, run that workshop, hold a daily huddle. Useful, sometimes. But the specialists on your team are the ones who already know which framework fits which team, which retrospective format will actually surface the real blocker, and which stakeholder conversation to have before, not after, the sprint review.
Who loses when this stays invisible? The generalist. Not because they are worse, but because their work is easier to commodify, easier to outsource, and easier to replace with a YouTube tutorial. Who wins? The person with a clear niche and a backlog of judgment, in other words, the senior.
What to watch next
Watch for the moment your team stops asking "how do we do more?" and starts asking "what should we stop doing?" That is the same shift the Triumph mechanic represents. The sprint that suddenly drops three low-value stories to make room for the one thing that unblocks everyone is a pocket-wrench fix.
Watch also for how you position yourself. The article's punchline is a positioning statement: who you help, how, and to achieve what. Pick a niche. Scrum for regulated teams. Agile project management for hardware-adjacent software. Servant leadership for newly remote crews. The narrower the niche, the faster the pattern library grows.
A practical scenario for your next sprint
Say you are a scrum master running a fortnightly retrospective. The team is stuck in the same loop every iteration: long discussions, no real actions, and a "we will monitor it" that nobody monitors. A generalist fix is to switch retrospective format, rotate facilitators, and add a follow-up slot. Three hours of work, low odds.
A specialist fix is to spend five minutes before the retro reading last retro's actions, mark which ones were touched in this sprint, and start the meeting with one quiet question: "what stopped us from doing this?" That is the pocket wrench. Same retro, sharper opening, real signal in minutes.
Try the specialist move once. See how the room shifts.
Key takeaways
- Experts charge more because they pick the right problem before they pick up a tool.
- In agile project management, the senior voice is the one that drops low-value work, not adds more.
- Pick a niche, then build a pattern library inside it. Positioning is a sprint-sized commitment, not a weekend one.
- Next retro, try one specialist move: read last retro's actions and lead with "what blocked us from doing this?"
Frequently asked questions
What is the main point of the swizec.com piece?
It argues that senior experts earn more because they do the right work in seconds, thanks to deep niche experience, rather than doing more work than everyone else.
How does this connect to agile project management?
The same pattern shows up in sprint planning and retros: senior practitioners cut low-value work and run sharper ceremonies, instead of packing more in and hoping something sticks.
I'm a mid-career project manager, not an engineer. Does this still apply?
Yes. The lesson is about positioning and judgment, not tools. Pick a niche such as scrum for regulated teams or agile delivery for hardware-adjacent software, and build a pattern library there.
What is the fastest way to start acting like a specialist?
Pick one recurring meeting, usually a retro or stand-up, and prepare a single sharp question in advance. Replace breadth of input with depth of pattern recognition.
How do I know if I am still doing generalist work?
If your week is mostly routine tasks that a YouTube tutorial or junior colleague could handle with time, you are still in generalist mode. Specialists spend most of their week on judgment calls.