The Managers' Guide β 141
The Managers' Guide
June 9, 2026
STRESS TEST your email server by ordering a single item from AliExpress.
PJ Evans
Verification Debt Is Your Next Headache
- π A different kind of debt: The concept of βverification debtβ goes beyond standard technical debt β it specifically refers to the growing, hidden burden of manually testing and validating software due to a lack of proper automated systems.
- π’ The illusion of speed: Skipping automated tests initially makes an engineering team feel like they are moving fast. However, this creates a dangerous trap β every new feature exponentially increases the time it takes to manually verify that the entire system still works.
- π Compounding consequences: Just like financial debt, verification debt compounds over time. As a product scales, the manual regression testing phase becomes a massive bottleneck, leading to painfully slow releases and a higher likelihood of βunexplainedβ bugs slipping into production.
- π‘ Automation is an enabler: To escape this vicious cycle, teams must shift their mindset and prioritize paying down this specific debt. Automated testing isnβt a tax on delivery β it is the essential infrastructure that allows teams to maintain their velocity and confidence as they grow.
Say the Thing You Want
- π£οΈ Say what you want out loud β Keeping career desires to yourself gives them no "surface area" for others to help you achieve them
- π° Fear holds us back β We stay quiet because asking feels presumptuous, risky, or too exposing β but these fears prevent growth opportunities
- π― Managers can't read minds β Your manager has multiple reports and their own priorities; they can't send opportunities your way if they don't know your direction
- πΊοΈ Get a career roadmap β When you voice your goals, managers can provide specific feedback on gaps and concrete steps to get there
- πͺ Self-assessment has blind spots β You need external perspective to understand your strengths and weaknesses; thinking harder about yourself won't close these gaps
- β‘ Speaking makes it real β Saying your goals out loud gives them weight and makes you start making different choices and taking different actions
- π² The risk is worth it β If expressing career ambitions gets you punished, that's valuable information about your workplace; three years of hinting is worse than one honest conversation
- π¬ Simple phrases work β Try "I've been thinking about the path to senior. Can we talk about where I stand?" or "I'm interested in leading a project. What would I need to show you?"
- πͺ Next 1:1 is your chance β When your manager asks "anything else?" β just say the thing instead of rationalizing why you shouldn't
The difference between Manager and Director
- π― Core Evolution Model : Leadership growth follows a "What β How β Why" progression β early career focuses on tangible outputs (What), management emphasizes processes and team effectiveness (How), and director level prioritizes strategy and purpose (Why)
- π₯ Role Responsibility Shift : Directors become strategic filters between business and tech, co-creating company direction rather than just consuming it β they evaluate and prioritize incoming work based on strategic alignment rather than executing all requests
- π Distance from Work : Directors operate further from day-to-day execution and must develop new ways to collect signals about team health β using metrics, visual management tools, and periodic deep-dives across people, product, platform, and process dimensions
- πͺ Power Transition : Leadership power evolves from expertise (knowing the answers) to influence (relationships and trust) β authority from titles is the weakest form, while influence becomes everything at director level
- π£οΈ Communication as Multiplier : Communication skills become increasingly critical and can be the biggest growth blocker β directors need to influence peers, shape strategy, and build other leaders through clear communication
- π Emotional Rewiring Required : Each transition demands redefining personal impact β from tangible code/features (IC) to team delivery (manager) to abstract business outcomes (director), with longer feedback loops at each level
- β οΈ Common Anti-Pattern : Directors who remain stuck in "What" mode by coding themselves or micromanaging implementation details β this shows lack of trust and prevents strategic thinking
- π Proactive Development Advice : Engage with all three dimensions (What/How/Why) early in your career β build relationships with Why and communication skills before the role demands it to ease future transitions
Startup Engineering Team Organisation
- ποΈ Team Structure Evolution β Startup engineering teams follow predictable patterns as they grow, each solving previous problems while creating new ones
- π» Technical Teams Trap β Organizing by tech stack (frontend, backend, mobile) creates silos where every project becomes a cross-team coordination nightmare
- π― Squad Success & Failure β Business-domain squads improve product focus and team dynamics, but technical debt piles up as "core" engineering work gets deprioritized
- π Chapter Conflicts β Adding technical chapters (communities of practice) helps with knowledge sharing, but creates constant battles between product priorities and technical maintenance
- βοΈ Core Team Complications β Dedicated platform teams solve technical debt but create a "two-class system" where product engineers stop caring about technical quality
- π² Project Approach Problems β One-shot technical projects seem clear but suffer from scope creep, timeline extensions, and knowledge loss when teams disband
- π Staff Engineer Solution β Senior autonomous engineers plus ~20% chapter time provides flexibility, but puts huge pressure on staff engineers and requires rare skill combinations
- π No Perfect Answer β Every organizational structure has tradeoffs β the key is recognizing when current limitations outweigh benefits and being ready to evolve
- π Scale Matters β What works for 18 engineers won't work for 50 or 5 β team structure must adapt to current size and challenges
Three Bad Managers
- π¨ The Artist β A brilliant creative leader who valued art over people, couldn't engage with human management challenges, and required extensive written documentation to even sometimes pay attention to team dynamics
- π The Dictator β A passionate but bulldozing leader who dominated every conversation, ignored expert input, and made terrible decisions because they couldn't stop "litigating" issues that were already solved
- π‘οΈ The Knife β An inexplicably successful yet completely disconnected manager who pulled actual knives out during meetings, talked about unrelated topics, and was impossible to understand or influence
- π Success vs. Management Skills β All three were objectively successful leaders who generated significant shareholder value, proving that leadership ability (strategy/vision) and management ability (operations/people) are completely different skill sets
- π Everyone is an Adjustment β The core lesson is that you must adapt your communication style, preparation methods, and approach for each person you work with β you don't get to pick your bosses, only how you respond to them
- π Adaptation Strategies β With The Artist, detailed written explanations worked sometimes; with The Dictator, doing extensive homework and showing you "care deeply" earned respect; with The Knife, staying out of the way was the only viable approach
- π― You Can't Change Bad Managers β The more senior the leader, the less you can influence them, so focus on adapting yourself rather than trying to fix them
- π§ Intelligence β Good Management β All three were highly intelligent people who simply had no business managing humans, despite being effective at leading organizations toward goals
Thatβs all for this weekβs edition
I hope you liked it, and youβve learned something β if you did, donβt forget to give a thumbs-up, add your thoughts as comments, and share this issue with your friends and network.
See you all next week π
Oh, and if someone forwarded this email to you, sign up if you found it useful π
Sign up for The Managers' Guide
Your guide to engineering leadership
Subscribe
Email sent! Check your inbox to complete your signup.
No spam. Unsubscribe anytime.
Discussion in the ATmosphere