Mar 29, 2026
What a Decade of Feedback Taught Me
Patterns from 10+ years of peer feedback — what people value about working with me, and what I'm still getting right.
I've received feedback from colleagues every year for over a decade — engineers, peers, and managers. Most people file feedback away. I turned mine into a map.
These are the patterns that kept showing up across different teams, roles, and stages of my career. I share them because the patterns only matter if I stay honest about them.
How I Show Up
Bringing structure to chaos. One of the most consistent patterns is that I bring clarity to ambiguous, high-pressure situations — defining priorities, organizing work, and giving people a clear picture of what matters.
Crisis mode comes naturally. What's harder is the investment that prevents crises in the first place — career development conversations, team culture during quiet stretches, the slow work that doesn't have a deadline forcing the pace.
Listening first, then acting. When I join a new team or domain, I lead with curiosity rather than prescriptions. I observe, ask questions, and understand the dynamics before making changes.
Patience during onboarding can tip into waiting too long to act. There's a point where continued observation becomes a delay, and the team needs a clear signal that I've seen enough and I'm ready to move. I'm learning to name that transition out loud.
Investing in people individually. I tailor how I manage to each person — who needs autonomy, who needs guidance, who processes by talking vs. reading.
Individualized management is harder to scale. What works with a team of five doesn't always work with a team of ten. I'm learning when to set team-level norms that apply to everyone, rather than customizing every interaction.
Direct and candid. I share feedback in real time. People know where they stand with me.
Directness without enough warmth can feel transactional. I've gotten feedback that my candor lands well when people feel cared for, and falls flat when they don't. The relationship has to come first — the directness only works on top of trust.
Advocating fiercely for the team. People on my teams feel that I fight for them — for resources, recognition, and the space to do their best work.
That advocacy can read as territorial to partners. I'm learning to advocate in ways that feel collaborative, not competitive.
Documentation and organization. Teams I lead become more organized — clear priorities, documented decisions, shared context.
Documentation captures decisions but doesn't guarantee alignment. I've seen teams where everything was well-documented and people were still confused because they never read it or didn't understand how it applied to them. I'm learning that the document isn't the finish line — the conversation about the document is.
The Longer Arc
The gap between completeness and adoption. This is the most persistent pattern in a decade of feedback. I build things well — frameworks, processes, platforms, plans.
But I don't always follow through to ensure full adoption. I'm redefining what "done" means: not whether I built it well, but whether people use it.
Growth across three phases. My career has moved through technical excellence (building tools others wanted to extend), technical leadership (driving direction and strategy), and people leadership (creating conditions for others to do their best work).
Each phase required letting go of what made me successful in the previous one. Growth isn't additive — it's about knowing which strengths to deploy at what intensity.