A team lead posted to Hacker News recently with a problem I hear constantly:
"I'm responsible for a small team including an industry veteran of 30 years. We want to adopt Claude Code, but I'm not sure how to approach it without creating friction."
The responses were mostly "just let them explore" and "get buy-in first." Useful, but vague.
Here's what actually works — especially when your most experienced engineer is the skeptic.
Why the Veteran Resists (And It's Not What You Think)
Senior engineers don't resist AI tools because they're stubborn. They resist because they've seen this pattern before:
- The "transformative" tool that turned into shelfware
- The productivity gains that only worked for toy examples
- The enthusiasm that crashed against real legacy codebases
Their skepticism is calibrated by experience. That's not a problem to overcome — it's a signal to respect.
The mistake: Framing Claude Code as "this will make everyone faster."
The fix: Let the skeptic define the test.
The Four-Week Skeptic Onboarding
Week 1: One honest experiment
Don't ask the veteran to "try it and see." Give them a specific task they already find tedious — writing test cases for an existing module, documenting a gnarly function, reviewing a PR for obvious issues.
Ask them to do it once with Claude Code, then tell you what happened. That's it.
No requirement to adopt. No judgment. One experiment.
Week 2: The junior-senior pair
Your junior developer will be using Claude Code enthusiastically and sloppily. Pair them with the senior for one code review session.
Ask the senior to catch what Claude got wrong.
This does two things: it gives the senior engineer a valued role (the expert catcher), and it naturally surfaces where Claude Code is weakest — which makes the senior more confident, not less.
Week 3: Let them set the rules
If the veteran is coming around, have them draft the team's "Claude Code guidelines" — what it's good for, what it shouldn't touch, when to double-check its output.
Senior engineers want to shape the process. Let them. Their guidelines will be better than anything you'd write anyway.
Week 4: Measure it together
Pull the data. Time saved on test writing. PR turnaround time. Lines of boilerplate generated vs. reviewed.
Review it together as a team. Let the data speak. The veteran who ran the experiment gets to interpret the results — which makes the findings credible to everyone.
The Mistake That Tanks Adoption
The fastest way to lose your best engineer is to make Claude Code a mandate.
"Everyone uses it now" kills buy-in from exactly the people whose buy-in matters most. A 30-year veteran who feels steamrolled becomes a vocal skeptic. And vocal skeptics are contagious.
Earn the adoption. It takes four weeks. It sticks.
What the Teams With 65%+ Utilization Have in Common
In our work with engineering teams deploying Claude Code, the teams that hit strong adoption share one thing: they let senior engineers lead the adoption process, not just participate in it.
The veteran becomes the expert. The junior learns from their guidelines. The manager facilitates, not mandates.
That's the difference between a tool everyone's using and a tool that's sitting in the dock.
If you're trying to figure out where your team actually stands before rolling out Claude Code, we built a free AI Readiness Assessment — async, no prep, you get a report back with specific recommendations.
Top comments (0)