

Develop
/_
Who Actually Lead
Tech leadership workshops and structured programs tailored to your team’s actual challenges. Built and taught by a tech leader with 15+ years of industry experience.
# Your Team's Next Bottleneck Isn’t Code
# Your Team's Next Bottleneck Isn’t Code
AI is changing how we work. Code is no longer the bottleneck because AI can generate, refactor, and ship it faster.
You got promoted for your technical expertise but the engineers who thrive from here won't be the best coders. They'll be the ones who deliver outcomes, solve business and customer problems, support and guide their teams towards the same goals.
Our workshops help engineers build the leadership skills AI can't replace - strategy, communication, decision-making, and team dynamics. They’re hands-on, practical sessions, built by an engineer for engineers navigating this big change.
Leadership isn't as clear as code, but it can be learnt.
# Upcoming Workshops
# Upcoming Workshops
| Workshop | Date | Suitable for | Format | Details |
|---|---|---|---|---|
| Tech Leadership: Difficult Conversations, Feedback and Conflict | May 31 | 🇦🇺 Melbourne | In-person | Learn more |
# We Work With:
# We Work With:

Engineering Managers & Tech Leads
Engineering Managers & Tech Leads
New or emerging leaders still figuring out their role, responsibilities, and wanting to bridge the gap between tech and people leadership to focus on the wider business and user problems.

Staff Engineers & Senior ICs
Staff Engineers & Senior ICs
Tech leaders who need to influence without authority, think strategically about roadmaps, and coach others instead of jumping into the code.
OUTCOMES
# Success Looks Like:
# Success Looks Like:
Teams actually working together
Your engineers lead with empathy, work alongside different personalities, and improve team dynamics and collaboration to keep everyone moving towards the same goals.
Autonomous teams
Your tech leaders don’t just take orders, they make decisions. You don’t get pinged for every decision. Your engineers handle problems themselves and only escalate them when it matters.
Delivering outcomes, not output
No more feature factories or bottlenecks. Your engineers tie their work to the why, aligning with business goals and user needs, so you stop wasting time and resources building the wrong things.
Leaders who aren’t bottlenecks
Your engineers delegate work, mentor and coach their team, and build a culture of accountability so delivery doesn’t depend on you being in every meeting. You can focus on the strategy instead.
Clear and confident communication
Engineering leaders create visibility and context for both their teams and stakeholders, sharing updates clearly and raising challenges to maintain confidence and set expectations.
High performing teams
Your engineering leaders build a safe space where their teams are supported, motivated, self-sufficient, and confident to share ideas, collaborate, challenge each other, and grow.
THE EXPERIENCE
# How We Work Together
# How We Work Together

1
Discovery call
Discovery call
We learn about your team, your challenges, and what success looks like. It’s a conversation to explore what you need and how we could help.

2
Tailored program
Tailored program
We design a program around your team's leadership needs (workshops, format, cadence, attendance, budget, and any other needs).

3
Interactive workshops
Interactive workshops
Practical, hands-on sessions run either in-person or remotely as agreed with all the materials provided.

4
(Optional) Ongoing support
(Optional) Ongoing support
Coaching check-ins and follow-ups between workshops to answer any questions and provide support post workshops.
# Meet Andrew Murphy
# Meet Andrew Murphy

Engineering Leader & Educator
Andrew spent 20+ years in tech, starting as a developer and working his way to CTO. Along the way he discovered that being great at code doesn't make you great at leading people, and nobody tells you that when they promote you.
Now he runs workshops for tech leaders, teaching the communication, trust-building and strategic thinking skills he had to learn through trial and error (heavy on the error side!).






