Knowledge work pits deep creative focus against constant coordination. That tension peaks when you move from a senior technical role into leadership. If the new job feels abrasive, that friction is often new managerial muscle forming-not failure. You are shifting from additive work (you solve the problem) to multiplicative impact (you design the environment where others win). Mastering the maker schedule and manager schedule is how you become the architect of your own time.
You cannot be a successful leader if your team is not successful.
- Anemari Fiser, Tech Lead Coach
Understanding these two professional rhythms is the first step in moving mindset from I to we.
The invisible wall: maker vs. manager
Management is not the next rung on the engineering ladder-it is often a horizontal career change. Senior IC to lead is a different craft. Makers define success by the how (elegance, implementation). Managers define it by the who and why (alignment, value, people).
| Attribute | Maker's schedule | Manager's schedule |
|---|---|---|
| Primary unit of time | Half-day or full-day blocks | 30–60 minute increments |
| Core objective | Deep concentration and creation | Coordination and decision-making |
| Definition of success | Flow state and technical “how” | Team impact and “who/why” |
| Sensitivity to interruptions | High-one meeting can derail a day | Lower-work is a series of interactions |
Modern leads wear both hats-but only if you avoid the cognitive tax that fragments technical organizations.
The cognitive tax of context switching
Switching from coordination back to deep work is not free. Research on context switching cost often cites roughly 25 minutes to regain full focus after one interruption.
Paul Graham's fragmented afternoon logic still applies: a 2:00 p.m. meeting hurts a maker more than a 9:00 a.m. meeting. It does not only cost an hour-it splits the afternoon into two ~90-minute chunks too small for flow.
Ignore that tax and you risk:
- Burnout from squeezing strategy between pings.
- Reduced productivity-neither alignment nor oversight gets full quality.
- Team frustration when you model a fragmented rhythm and block “we” results you are accountable for.
Managerial grief and the identity shift
The transition includes visceral managerial grief as you release the “expert” identity.
Day-one losses
- The dopamine hit. “Tests passed” was instant; management feedback can take months.
- Expert and peer connection. You hold hire/fire power-professional distance replaces being “just one of the buddies.”
- Beginner again. You were the best coder; now you are novice at people problems and organizational ambiguity.
Long-term multiplier gains
- 10×–20× leverage-one great manager multiplies a whole team.
- Strategic problem solving-culture, strategy, cross-functional friction.
- Compounding influence-mentees become directors and CTOs; impact outlives your commits.
As Steve McDougall and others note: discomfort in a new lead role often means the job is working correctly.
The coding trap and the illusion of productivity
The IDE seduces new leaders because it feels safe. A manager on the critical path is often a liability. In the “IE6 crash” pattern, a well-meaning veteran jumped in during a death march without knowing in-house edge cases-and took the site down for millions of users. If your code blocks a release or creates an emergency because you are not in the daily weeds, you have failed as a manager.
Red flags of the coding trap
- Hiding in code-tickets instead of a hard stakeholder or performance talk.
- Solving vs. coaching-giving the bug answer instead of “what have you tried?”
- Critical-path bottleneck-the release waits on your PR or feature.
Cognitive energy and accountability in the AI era
AI can create a false sense of speed-more output, more noise, more architectural risk. The lead remains the arbiter of accountability.
- Tooling awareness. Which tools help velocity without sacrificing maintainability?
- Alignment on quality. Generated code does not erase accountability for defects.
- Vulnerability in exploration. Safe-to-fail experiments beat dictating tools from on high.
Use AI to reduce admin load-prep for 1-on-1s, summarize meetings-so cognitive energy stays on people strategy.
Mastering hybrid mode: four practical strategies
- Time audit. Track energy for a week. Spot “ungrateful tasks” (docs, CI/CD) that unblock the team.
- Maker blocks-review, don't rewrite. Protect mornings. Teach via PR comments so engineers catch edge cases themselves-slower today, faster next month.
- Manager batches. Cluster 1-on-1s and syncs in the afternoon. Delegate with SMART goals plus a trackable check-in cadence to avoid hovering.
- “Do not disturb” shield. Model boundaries so makers on your team protect focus too.
From IC to multiplier: conclusion
Leadership success is measured by your people's autonomy, not your line count. Become intentionally dispensable.
The stress test: can the team ship and solve problems during a two-week vacation? If yes, you have moved from maker to multiplier-you designed a winning system.
Self-assessment checklist for tech leads
- Autonomy: Could the team pass a two-week stress test without you?
- The why: Does everyone see value beyond the code?
- Boundaries: Did you protect focus blocks for makers this week?
- Coaching: Are you asking more questions than giving answers?
- Accountability: Are PR reviews about alignment-not rewriting for your style?
Related: Mastering the maker-manager divide for engineering leads.