Leading Teams

Your Jira board shows process bottlenecks. It won't show you the approval chains, implicit rules, and leadership behaviors killing your team's throughput.

Most software engineering teams swing between chaos and bureaucracy. Here's a framework to find the edge where scaling actually happens.

Stop fighting the rumor mill and start using it. Learn why talking behind your team's back can be a good way to build trust and morale.

Tech leaders: Build an environment where engineering teams can experiment freely, driven by clear intent and strong trust.

Discover why starting every project with a clear purpose prevents wasted effort and how to ensure your team truly understands the why behind the work.

Discover why building reliable systems outperforms motivation hacks every time and how to create the infrastructure your team actually needs.

Discover why every persistent team problem reflects leadership choices and how taking ownership transforms both leaders and their teams.

Learn to recognize when your team is merely complying rather than committed, and practical steps to build the trust needed for honest feedback.

Good managers make progress easier by removing friction, clarifying goals, and clearing obstacles out of the team’s way.

Why strong managers rely on the team's collective judgment instead of acting like the smartest person in the room.

Your team doesn't hear what you say nearly as clearly as they see what you do. Learn why leadership by example isn't optional—it's everything.

Great leaders don’t fake certainty—they navigate ambiguity with confidence. Learn how saying "I do not know" can make you a stronger, smarter leader.

Learn why team loyalty must be earned through consistent actions, not demanded through authority or bought with perks.

A practical guide to understanding and resolving engineering team conflicts using the Thomas-Kilmann model. Turn arguments into productive outcomes.

Learn how knowledge silos are slowing down your engineering teams and get practical strategies to break them down. Based on real experience scaling engineering organizations.

Discover how the Johari Window can transform your tech leadership. Learn to boost self-awareness, improve team dynamics, and unlock hidden potential. Master the human side of tech for better communication and innovation.

How to run the Starfish retrospective to examine what to start, stop, keep, do more of, and do less of.

How to use the Mad Sad Glad retrospective to surface team emotions, patterns, and practical follow-up actions.

Learn 3 effective, non-confrontational scripts to regain control of derailed meetings. Boost productivity and keep your team focused without sounding like a jerk.

Learn how to manage tech challenges without escalating drama. Discover Stoic-inspired strategies for calm leadership, maintaining perspective, and fostering a drama-free culture in high-pressure tech environments.

How to run the Sailboat retrospective to surface momentum, obstacles, and risks in a more visual team conversation.

A practical guide to the Start Stop Continue retrospective: when to use it, how to run it, and what it helps teams surface.

Three practical one-on-one agendas for your first conversations as a new manager.

Learn from great leaders: unlock effective leadership by creating a safe environment for your team. Learn how personal growth fosters innovation, trust, and mutual respect.

Explore research on the impact of office spaces on employees' psychological and physical states. Learn why a one-size-fits-all approach to workspaces may be counterproductive, and discover how designing diverse, inspiring environments can boost productivity, well-being, and creativity.

In Agile software development, retrospectives help teams identify areas for improvement. However, certain behaviors known as antipatterns can undermine their effectiveness. Here are some common antipatterns to avoid.

You might have heard of the (in)famous Dunbar's number, about the limit of the number of stable relationships we can maintain.

Learn how to onboard engineers with an empathetic and structured approach. Includes a 30-60-90-day check-in template.

What makes high-performance teams stand out? What sets these teams apart from the rest? How can you build outstanding teams? Dive in for the answers.

Ten observations on team leadership from a seasoned team coach and manager.

Kindness is a hidden superpower for software engineers. It helps your peers feel safe, and if they feel safe people take the risks that enable efficient, honest communication and thus real collaboration.

Hero engineers can be deadly to team culture, it's time to retire those capes.