Skills and strengths

I work in the space between different roles, responsibility levels, organizational units, and perspectives, turning friction into patterns, and patterns into solutions that scale.

What I do

• Sit with a team long enough to find where the friction actually is, not where people say it is.
• Ask the questions nobody thought to ask, until the room lands on the same understanding.
• Translate between engineering, product, and business until everyone’s using the same words for the same thing.
• Facilitate workshops that turn “kind of clear” into something everyone actually agrees on.
• Spot the pattern across scattered conversations and turn it into a standard that scales.
• Lead by doing — people follow the work, not a title.
• Write and structure documentation and architectural guidelines that hold up as a product grows.
• Mentor technical writers and young talent as well as build communities around documentation and knowledge management.

How I work

• I ask a lot of questions, not because I don’t get it, but because I want everyone to land on the same page.
• I translate between ways of working. I don’t force one on everyone.
• I like pioneering: the role nobody’s had before is often where I do my best work.
• I’ve learned as much from people I was supposed to be teaching.
• The questions I keep coming back to when a team scales fast: Where is growth creating friction? What feels harder than it did a year ago?

More of this, in writing

• My blog
• Talks and publications

For the roles and timeline, see my CV.