Quantum Accountability for Engineering Managers

Taking ownership of invisible forces can transform your team's performance.

👋 Hey, it’s Stephane. I share lessons, and stories from my journey to help you lead with confidence as an Engineering Manager. To accelerate your growth see: 50 Notion Templates | The EM’s Field Guide | CodeCrafters | Get Hired as an EM | 1:1 Coaching

Paid subscribers get 50 Notion Templates, The EM’s Field Guide, and access to the complete archive. Subscribe now.

Most engineering managers blame their team's problems on external factors such as unrealistic deadlines, poor project requirements, insufficient resources, or difficult stakeholders. But after coaching dozens of managers through similar challenges, I've discovered something uncomfortable: the biggest barriers to team performance aren't in your organization. They're in your mindset.

Your beliefs about developer motivation, your emotional reactions to missed deadlines, your assumptions about what constitutes "good management" operate beneath conscious awareness. You can't see them directly, but their effects impact every sprint planning session, every one-on-one conversation, and every technical decision your team makes.

Taking accountability for these hidden forces isn't just leadership theory. I think it's the difference between managers who constantly firefight and those who build high-performing teams.

Your Leadership

Two managers leading teams with identical technical capabilities can produce completely different outcomes. The difference isn't team size, budget, or technology choices. It's their mental approach to engineering leadership.

If you constantly think "my developers are always behind schedule" you'll manage in ways that make delays more likely. If you believe "engineers hate meetings" you'll avoid necessary communication and create alignment problems. These are management assumptions that become team reality.

I learned this during my first management role when I spent months thinking that "unmotivated developers" were the reason for poor sprint performance. My belief that engineers needed constant oversight created a micromanagement culture that actually demotivated the team. I needed the wake up call my manager gave me to move away from that thinking to "how can I remove their blockers".

Action for you: Track your assumptions for one week. Note your thoughts about individual team members, their capabilities, and their motivations. You'll start recognizing patterns that either empower or undermine your team's potential.

The forces that shape your team’s performance

Your mindset consists of five interconnected elements that most engineering managers never examine consciously:

1. Your beliefs about motivation

What do you believe drives engineers? Money, autonomy, technical challenges, or recognition? These beliefs determine how you structure work, conduct one-on-ones, and design career growth paths.

I used to believe that "good engineers are self-motivated and don't need much direction". This in the past led me to under-communicate context and priorities, leaving my team feeling confused about business goals. When I shifted to believing "engineers are motivated when they understand the impact of their work" I started spending more time explaining the why behind tasks.

Challenge your assumptions. If you believe engineers hate documentation, you'll never invest in proper knowledge management. If you believe remote work reduces productivity, you'll micromanage distributed team members.

2. Your emotional reactions to challenges

How do you respond to challenges? When engineers push back on requirements? When stakeholders demand impossible timelines? Your emotional patterns either escalate conflicts or defuse them.

Expand your emotional awareness. Instead of just feeling "frustrated" when deadlines slip, get specific. Are you feeling disappointed, anxious about stakeholder perception, or worried about team capability? Different emotions require different responses. Disappointment might call for retrospective analysis. Anxiety can suggest better stakeholder communication. Worry about capability indicates a need for skills development.

3. Your values

What matters most to you as a manager? Team autonomy, organisational alignment, individual growth, collective performance, or innovation velocity? Your values should guide your management decisions, especially when facing competing organisational pressures.

Most engineering managers never consciously define their leadership values, which leads to inconsistent decision-making. When you're clear about what you stand for, you can navigate complex organisational dynamics.

Consider these common management dilemmas where values matter:

When your VP wants to implement stack ranking for performance reviews, but you believe in collaborative development, do you push back or find ways to protect your team while complying? If you value psychological safety above competitive metrics, you'll advocate for alternative evaluation methods.

When you’re asked to take on additional scope with the same headcount, do you accept the challenge or negotiate for resources? If you value sustainable work practices over short-term heroics, you'll clearly communicate capacity constraints and their consequences.

Write down your top five management values. Use them as your decision-making compass when organizational pressures conflict with team needs. Values-driven decisions feel more authentic to your team and create consistency they can rely on, even when external circumstances change rapidly.

4. Your communication

How do you approach difficult conversations, performance feedback, and conflict? Your communication mindset shapes team psychological safety more than any other single factor.

Managers with abundance mindsets see every difficult conversation as a chance to strengthen relationships and solve problems. Managers with scarcity mindsets see them as zero-sum conflicts where someone will lose. The difference in team performance is dramatic.

5. Your growth philosophy

Do you believe senior engineers should manage their own development? That certain people are "naturally good" at leadership? That some team members will never be senior? These assumptions become performance prophecies.

If you believe growth happens automatically with experience, you won't invest in mentorship or skill development plans. If you believe leadership is innate, you won't help promising engineers develop leadership skills.

Finding your purpose beyond delivery metrics

As engineering managers we need to have a deeper purpose beyond just shipping features and hitting sprint goals. This purpose acts as a compass for difficult decisions.

Maybe your purpose is developing the next generation of technical leaders. Maybe it's building inclusive teams where every engineer can do their best work. Maybe it's creating sustainable engineering practices that prevent burnout.

Reflect on these questions:

• What type of team culture energises you to build?

• What management challenges do you enjoy solving?

• How do you want to impact the engineers you lead?

• What legacy do you want to leave in the teams you manage?

Your purpose becomes your filter for management decisions. When you feel pressured to make difficult decisions, refer back to your purpose. If building sustainable practices matters most to you, you'll find creative ways to meet deadlines without burning out your team.

The bottom line

You can't control your company's strategic direction, your stakeholders' priorities, or market pressures. But you can control your responses to these factors. You can choose to see difficult team members as development opportunities rather than performance problems. You can take ownership of your team's growth instead of waiting for HR to provide training.

You need to recognise that your mental approach to leadership shapes your team's reality in measurable ways. Managers who understand this principle deliver better results while building stronger, more resilient teams.

That’s all, folks!

See you in the next one,
~ Stephane