Leadership Philosophy
Talent is rarely what a team is missing. Trust and clarity usually are. I build teams where people want to come to work.
Psychological Safety First
What it means
Creating an environment where people can take risks, admit mistakes, and ask questions without fear. This isn't about being "nice" - it's about being honest and creating space for growth.
How I do it
- Run weekly 1:1s where people feel safe discussing failures and uncertainties
- Lead by example: openly discuss my own mistakes and learnings
- Create retrospectives where blame is off the table, learning is the goal
- Encourage experimentation and celebrate thoughtful failures
Results
- Teams that self-organize and solve problems without waiting for permission
- Higher retention, more innovation, faster incident response
- Engineers who grow faster because they're not afraid to try
Technical Credibility as a Manager
What it means
Staying hands-on enough to understand the work, review architecture, and debug production issues. Technical enough to lead well, without trying to be the best engineer in the room.
How I do it
- Write Go scripts and occasional production code
- Review infrastructure changes and participate in architectural discussions
- Monitor production dashboards and participate in on-call rotation
- Stay current with team's tech stack and tooling
Results
- Earn team's respect through technical understanding, not just title
- Make better decisions about scope, timeline, and technical debt
- Can credibly represent team's needs to leadership
Using AI Deliberately
What it means
AI removes mechanical work. It doesn't replace judgment. I use it every day, and I'm just as specific about where it stops: I automate my own work, not my thinking about people.
How I do it
- Automate the repetitive parts of the job - drafts, summaries, research, scripts, internal tooling
- Use it as a thinking partner to structure a problem, then verify the output before acting on it
- Keep confidential and personal information out of tools that have no business holding it
- Write feedback, reviews, and career conversations myself - those are the job, not overhead
- Help the team adopt it where it helps, and say plainly when it doesn't
Results
- More time for the work that needs a human: coaching, hard conversations, judgment calls
- A team that treats AI as a normal tool, not a threat and not a magic trick
- Output I can stand behind, because I understand and check what I ship
Autonomy Over Micromanagement
What it means
Hire smart people, give them context and goals, get out of the way. Your job: remove blockers, provide context, coach when asked.
How I do it
- Delegate with clear outcomes, not detailed instructions
- Trust the team to make technical decisions within their domain
- Focus on removing organizational blockers
- Ask "How can I help?" instead of "Why didn't you do it this way?"
Results
- Motivated teams that take ownership and pride in their work
- Faster decisions, less bureaucracy
- People grow faster with real responsibility
Sustainable Development
What it means
High performance comes from a pace people can keep up. Balance delivery with technical debt, learning, and team health.
How I do it
- Push back on unrealistic timelines and unsustainable roadmaps
- Allocate time for refactoring, learning, and technical debt
- Protect team's time and encourage work-life balance
- Measure success over quarters and years, not just sprints
Results
- Lower burnout, higher retention
- Better long-term velocity (less technical debt drag)
- Teams that can sustain high performance for years, not months
Career Development as Core Responsibility
What it means
Delivery is half the job. Growing people is the other half. Understanding each person's goals and actively coaching toward them.
How I do it
- Weekly 1:1s focused on growth, not just status updates
- Have clear career conversations about paths (IC → Staff, IC → EM, etc.)
- Create stretch projects that challenge people appropriately
- Provide honest feedback and coaching
Results
- Team members who get promoted
- People who stay because they're growing
- Strong internal mobility (not losing people, but helping them move up)
When This Doesn't Work
This approach requires hiring well, giving clear context, and organizational support. It won't fix broken hiring or toxic culture by itself.
Autonomy requires trust, which takes time to build. A pace people can keep means saying no sometimes. None of it is a shortcut, and none of it pays off quickly.
I've used all of this while building teams at startups and scale-ups. If you want to build teams like this,let's talk about advisory, workshops, or speaking engagements.