Engineering Manager Workbook

The challenge for engineering managers isn’t just about technical decisions—it’s about creating systems that help teams work with constraints instead of against them. How do you build leverage when you’re managing competing priorities, resource constraints, and organizational politics? How do you help your team find the smallest changes that create the biggest impact when you’re dealing with complex stakeholder requirements and tight deadlines?

This workbook is designed specifically for engineering managers who want to apply judo engineering principles to their leadership challenges. It uses real management scenarios like team conflicts, resource allocation, technical debt, performance reviews, and organizational change to teach leverage-based thinking.

Level 1: Force vs Leverage in Management Decisions (Weeks 1-3)

Start by building awareness of when you’re using force vs leverage approaches in your management decisions. The “Daily Management Audit” exercise asks you to identify one management decision each day where you defaulted to a force approach, then brainstorm how you could have used leverage instead.

The “Leverage Question Practice” exercise teaches you to ask “What’s the smallest change that creates the biggest impact for my team?” before making any management decision. This simple question shifts focus from activities to impact.

Exercise 1.1: Daily Management Audit

Time: 5 minutes daily Instructions: At the end of each day, identify one management decision where you defaulted to a force approach. Ask yourself:

• What was the problem I was trying to solve?
• How did I approach it (force or leverage)?
• What would a leverage approach have looked like?
• What would I do differently next time?

Real Example - Team Conflict Resolution:

Date: 2025-01-27
Problem: Two senior engineers in a heated disagreement about architecture decisions
Force Approach: Step in and make the decision myself, then enforce it through authority
Leverage Alternative: Facilitate a structured discussion where they present their cases, then guide them to find common ground and make the decision together
Key Learning: Instead of fighting against the conflict, work with the engineers' expertise to resolve it collaboratively

Exercise 1.2: Leverage Question Practice

Time: 2 minutes before each major decision Instructions: Before making any management decision, ask: “What’s the smallest change that creates the biggest impact for my team?”

Real Example - Sprint Planning:

Situation: Team consistently misses sprint commitments
Force Question: "How can I make them work harder to meet deadlines?"
Leverage Question: "What's the smallest change that creates the biggest impact for sprint success?"
Force Answer: Add more process, longer planning meetings, stricter deadlines
Leverage Answer: Reduce sprint scope by 20% to focus on highest-impact work, then gradually increase as team builds confidence

Exercise 1.3: Management Leverage Hunt

Time: 10 minutes weekly Instructions: Identify one area where you’re currently using force in your management approach. Brainstorm three ways to use leverage instead.

Real Example - Code Review Process:

Current Force Approach: Requiring all code changes to go through me for approval
Leverage Alternatives:
1. Establish peer review guidelines and let the team self-manage
2. Create a rotation system where senior engineers lead reviews
3. Use automated tools to catch common issues, then focus reviews on architecture decisions

Level 2: Constraint-Based Team Problem Solving (Weeks 4-6)

Learn to work with team constraints instead of fighting against them. The “Constraint Mapping” exercise helps you identify the real constraints your team faces, then find ways to use them as leverage points.

The “Team Leverage Design” exercise teaches you to design systems that help your team work with constraints instead of against them.

Exercise 2.1: Constraint Mapping

Time: 15 minutes weekly Instructions: Map the constraints your team faces. For each constraint, ask: “How can this constraint become a leverage point?”

Real Example - Legacy System Constraints:

Constraint: 60% of team time spent maintaining legacy system
Force Response: "We need to rewrite everything from scratch"
Leverage Response: "What if we use the legacy system as a learning opportunity and gradually modernize piece by piece?"
Constraint as Leverage: Legacy system becomes a training ground for understanding business logic, then use that knowledge to build better new systems

Exercise 2.2: Team Leverage Design

Time: 20 minutes per team process Instructions: Design a team process that works with constraints instead of against them.

Real Example - Performance Review Process:

Constraint: Limited time for meaningful performance discussions
Force Design: Pack everything into one 60-minute meeting
Leverage Design: 
- 15-minute weekly check-ins for ongoing feedback
- Quarterly 30-minute focused discussions on growth areas
- Annual 60-minute career planning session
Result: More meaningful conversations with less time pressure

Exercise 2.3: Resource Constraint Leverage

Time: 10 minutes per resource decision Instructions: When facing resource constraints, ask: “How can this limitation become an advantage?”

Real Example - Limited Budget for Tools:

Constraint: $500/month budget for development tools
Force Response: "We need more budget to be effective"
Leverage Response: "What if we use this constraint to force better tool evaluation and team collaboration?"
Constraint as Leverage: Limited budget forces team to be more selective, leading to better tool choices and stronger team collaboration on shared resources

Level 3: Momentum-Building Management Strategies (Weeks 7-9)

Develop strategies for building momentum in your team and organization. The “Team Momentum Audit” exercise helps you identify what’s creating or destroying momentum in your team.

The “Management Momentum Design” exercise teaches you to design management practices that build momentum instead of creating friction.

Exercise 3.1: Team Momentum Audit

Time: 15 minutes weekly Instructions: Identify what’s building or destroying momentum in your team. Ask: “What small changes could amplify the positive momentum?”

Real Example - Team Morale:

Momentum Builders: 
- Quick wins on small features
- Positive customer feedback
- Team collaboration on difficult problems

Momentum Destroyers:
- Long, unproductive meetings
- Constant context switching
- Lack of recognition for good work

Leverage Actions:
- Schedule weekly "win sharing" sessions
- Reduce meeting frequency, increase meeting quality
- Create simple recognition system for team achievements

Exercise 3.2: Management Momentum Design

Time: 20 minutes per management practice Instructions: Design a management practice that builds momentum instead of creating friction.

Real Example - Team Standup Process:

Current Friction: 30-minute standups that feel like status reports
Momentum Design:
- 15-minute standups focused on blockers and collaboration
- Rotate who leads the meeting
- End with "What's one thing I can help someone with today?"
Result: Shorter, more engaging meetings that build team collaboration

Exercise 3.3: Organizational Momentum

Time: 10 minutes per organizational challenge Instructions: When facing organizational challenges, ask: “How can I use this challenge to build momentum for positive change?”

Real Example - Technical Debt Pressure:

Challenge: Pressure to deliver features while ignoring technical debt
Force Response: "We need to stop all feature work and fix everything"
Leverage Response: "What if we use technical debt as a way to demonstrate the value of good engineering practices?"
Momentum Building: Start with one small refactoring that improves developer experience, then use that success to build support for more technical debt work

Level 4: Advanced Management Applications (Weeks 10-12)

Integrate all principles into advanced management scenarios. The “Management Judo Moments” exercise helps you identify opportunities to use judo engineering principles in complex management situations.

The “Team Transformation Design” exercise teaches you to design comprehensive changes that work with your team’s natural dynamics instead of against them.

Exercise 4.1: Management Judo Moments

Time: 15 minutes per complex situation Instructions: When facing complex management challenges, identify the judo engineering principles that apply.

Real Example - Team Restructuring:

Situation: Need to restructure team due to changing business priorities
Force Approach: "We need to completely reorganize and reassign everyone"
Judo Approach: "What if we use this as an opportunity to let team members choose their new roles based on their interests and strengths?"
Principles Applied:
- Leverage: Use team members' natural interests as motivation
- Constraints: Work with existing team dynamics instead of against them
- Momentum: Build on existing relationships and expertise

Exercise 4.2: Team Transformation Design

Time: 30 minutes per major change Instructions: Design a major team change that works with natural team dynamics instead of against them.

Real Example - Adopting New Development Practices:

Change Goal: Adopt test-driven development practices
Force Design: "Everyone must write tests for all new code starting Monday"
Leverage Design:
- Start with one enthusiastic team member as champion
- Let them demonstrate benefits through a small project
- Gradually involve other team members as they see the value
- Use peer pressure and success stories to build momentum
Result: Natural adoption based on demonstrated value, not forced compliance

Exercise 4.3: Organizational Leverage

Time: 20 minutes per organizational challenge Instructions: When facing organizational challenges, identify the leverage points that can create the biggest impact with the smallest change.

Real Example - Cross-Team Collaboration:

Challenge: Poor collaboration between engineering and product teams
Force Response: "We need more meetings and better processes"
Leverage Response: "What if we start with one small collaboration that creates a quick win?"
Leverage Point: Identify one small project where both teams can collaborate and see immediate benefits
Small Change: Weekly 30-minute collaboration session on that one project
Big Impact: Builds trust and demonstrates value of collaboration, making future collaboration easier

Assessment and Progress Tracking

Weekly Self-Assessment

Rate yourself on each principle (1-5 scale):

• Leverage Recognition: I can identify force vs leverage approaches in my management decisions
• Constraint Utilization: I use team constraints as leverage points instead of fighting them
• Momentum Building: I design management practices that build team momentum
• Advanced Integration: I can apply all principles to complex management situations

Monthly Team Impact Review

• Team Productivity: Are we getting more done with less effort?
• Team Morale: Is the team more engaged and motivated?
• Problem Resolution: Are we solving problems faster and more effectively?
• Innovation: Is the team more creative and innovative?

Quarterly Management Transformation Review

• Management Style: How has my management approach changed?
• Team Dynamics: How has the team’s approach to problems changed?
• Organizational Impact: What impact have these changes had on the broader organization?
• Personal Growth: What have I learned about leadership and management?

Real-World Management Examples

Example 1: Team Conflict Resolution

Situation: Two senior engineers disagreeing on architecture decisions Force Approach: Make the decision yourself and enforce it Leverage Approach: Facilitate structured discussion, guide them to find common ground Result: Better decision with team buy-in, improved collaboration skills

Example 2: Resource Allocation

Situation: Limited budget for new development tools Force Approach: Fight for more budget or make do with inadequate tools Leverage Approach: Use constraint to force better tool evaluation and team collaboration Result: Better tool choices, stronger team collaboration, more efficient resource use

Example 3: Performance Management

Situation: Team member consistently missing deadlines Force Approach: Increase pressure, add more oversight Leverage Approach: Identify root cause, provide targeted support, adjust expectations Result: Better performance, improved relationship, sustainable solution

Example 4: Organizational Change

Situation: Need to adopt new development practices Force Approach: Mandate change from top down Leverage Approach: Start with champions, demonstrate value, build momentum Result: Natural adoption, better buy-in, sustainable change

Key Management Principles

Work With Team Dynamics, Not Against Them

Instead of trying to change how your team works, design systems that work with their natural tendencies and strengths.

Use Constraints as Creative Catalysts

Limited resources, time, or expertise can force better decisions and more creative solutions.

Build Momentum Through Small Wins

Small successes create confidence and energy that make bigger changes possible.

Focus on Impact, Not Activity

Measure success by the impact on your team and organization, not by the amount of management activity.

Common Management Pitfalls

❌ Micromanaging Instead of Leveraging

Problem: Trying to control every detail instead of creating systems that work Solution: Focus on creating conditions where your team can succeed, not controlling their every move

❌ Fighting Organizational Constraints

Problem: Spending energy fighting constraints instead of finding ways to work with them Solution: Identify how constraints can become advantages and design systems accordingly

❌ Ignoring Team Momentum

Problem: Making changes that destroy team momentum instead of building it Solution: Design changes that build on existing momentum and create positive energy

❌ Focusing on Process Over People

Problem: Creating processes that work against human nature instead of with it Solution: Design processes that work with how people naturally work and collaborate

Success Metrics

Team Metrics

• Productivity: Faster problem resolution, better solutions
• Morale: Higher engagement, lower turnover
• Collaboration: Better cross-team communication and cooperation
• Innovation: More creative solutions and process improvements

Management Metrics

• Decision Quality: Better decisions with less effort
• Team Development: Team members growing and taking on more responsibility
• Organizational Impact: Positive influence on broader organization
• Personal Satisfaction: More fulfilling and effective management experience

The transformation happens gradually, but the impact is profound. When you stop fighting against team dynamics and organizational constraints, and start working with them, everything changes. Your team becomes more productive, more engaged, and more innovative. You become a more effective manager who creates lasting positive change.

Get Started

Ready to transform your management approach? Start with Level 1 exercises and work through each level progressively. Remember: the goal is to change how you manage, not add more management activities to your day.