First I observe. I sit in standups and say nothing. I read the wiki — not for content, but for what it tells me about the org: what they think is worth documenting, what's been neglected, how long since anyone updated anything. I talk to the people who brought me in, then to the people they point me to. I report upward weekly and transparently, but I never name names — I describe patterns.
Then I connect. First with people — I set up 1:1s with every engineer. I want their story before their complaints. What brought them here, what motivates them, what success looks like to them personally. The problems surface on their own once people trust that you're actually listening.
Then across the org — I talk to anyone who cares. Not just adjacent teams. Customer support, success, engineering, sales — anyone affected, anyone with an opinion. That's my working definition of stakeholder: anyone who cares.
Then I close the gaps. I collect the small deliverables falling through the cracks between groups and surface them to the people best positioned to act. The work gets done because ownership becomes obvious.
Twenty-five years of org building — open source communities, startup launches, enterprise turnarounds, and growth-stage companies. Every case study here is a situation where an organization had stopped working and needed to be rebuilt.
Engine Yard · Director of Customer Support → Product Lead
I took over a demoralized, 100% remote support org targeted for outsourcing. I diagnosed career stagnation as the root cause, not performance. I rebuilt incentive structures, created engineering rotations, and reframed support as a revenue driver.
I bundled support into every paid customer offering (previously a separate add-on most customers skipped) and negotiated a share of the CFO’s AWS reserved instance discount. Unit economics flipped entirely. Full P&L ownership: budget, headcount, vendor contracts.
Gap Inc. · Director-Level Engagement
Four leaderless teams, a hostile architect, and two years at Gap. I took over four demoralized cloud infrastructure teams after the director departed, turned them around, and earned enough trust that a second director handed me his problem team — the one that had been stonewalling the org’s 130-team observability migration. I delivered the migration before PEAK.
Brontes Technologies / 3M · Support Engineer → Head of Customer Support
Brontes had built a 3D dental scanning device and hadn’t thought about support at all. In a meeting with the CEO and COO, I asked ‘what about support for these?’ They looked at each other. I said I’d run it. That was the entire handoff. I built the function from scratch — hired for disposition over credentials (bartenders, not Linux engineers), scaled across the US and five European countries, and ran our own 1-800 support line out of Lexington, MA. After the 3M acquisition, St. Paul kept trying to shut our line down and centralize support. I fought them on it for three years, eventually negotiating a redirect in their phone tree that routed calls straight back to us. When 3M shut down Brontes, my team was the only function they kept.
New Relic · Senior Product Manager (Growth)
Engineering owned the Instant Observability site — a key acquisition funnel — but didn’t want it. Marketing needed to optimize it but couldn’t touch it. The site was built on a static generator that made every change an engineering ticket. I transferred ownership to marketing by moving the platform to a CMS, created shared KPIs so both teams had skin in the outcome, and got engineering out from under an albatross they’d been carrying for years. Marketing could finally run the funnel. Engineering could finally stop babysitting it.
Gentoo Linux · Core Developer & Developer Relations Lead
This is the same approach that produced every case study above, twenty years earlier, with 250 developers — the largest org I’ve ever built, and it’s still going.