Let Go to Level Up: 6 Ways to Empower Your Team (and Yourself)

This Week's Top Insights: Stop Managing, Start Leading

Jul 03, 2025

Control is a tempting trap.

It feels productive to check progress, approve code, and write policies. But this week’s top notes remind us:

The best engineering teams don’t need tighter management—they need better systems, safer space, and leaders who get out of the way.

Here’s what resonated most:

1. Ditch Parent Mode

This one actually went wild on LinkedIn and not on Substack, but I want to include it because I feel it’s important.

When managers play parent, engineers act like kids. That kills trust and initiative.
→ Use “adult-adult” language: ask for judgment, offer support, share accountability.

2. Management May Be the Bottleneck

Micromanagement shrinks autonomy. Bureaucracy stunts mastery. Overcontrol kills purpose.
→ Lead like a gardener: set the environment, then step back and let people grow.

3. Your Vulnerability Builds More Trust Than Your Victory Laps

You don't create disciples by being flawless—you do it by showing your real-time thinking.
→ Show your debug process. Invite people into the uncertainty. Trust beats polish.

4. Code Debt Reflects Org Debt

Spaghetti architecture isn’t random. It mirrors communication breakdowns, unclear ownership, and shifting priorities.
→ Fix the system before the syntax. Organizational cleanup is tech debt prevention.

5. Shipping Code Is a Lot Like Publishing Writing

In both cases, perfection is the enemy of momentum. Bold ideas matter more than polish.
→ Encourage teams to ship like writers: read broadly, write (and code) bravely, and share early and often.

6. Build Your Own Scorecard

Standard metrics are seductive—and misleading.
→ Stop measuring what’s easy. Start tracking what actually matters: resilience, transfer of knowledge, systems that outlive you.

This Week’s Core Message

Management isn’t about control. It’s about designing systems where people can thrive, own outcomes, and grow without needing you.

Actionable Experiments to Try This Week

Audit your language: Replace “Are you on track?” with “What outcome are you owning?” See how the tone shifts.
Model vulnerability: In your next retro or demo, share a live failure. Invite learning, not blame.
Score the week on real impact: Did your team ship, learn, and support each other without waiting for your green light?