Design Operations and Leadership

The design-ops and leadership work I keep coming back to - the operating system around the design, not the screens. Across teams and companies the specifics changed; the conviction didn’t: a handful of operational decisions quietly decide whether good design actually ships.

Make the process legible - then keep cutting it

• I wrote down how we actually work - plans, checklists, the design-review format - so quality stopped depending on who happened to be in the room.
• Then I treated the process itself as a product: reviewed it on a cadence, kept what earned its place, and removed the rest.
• Ran design reviews open to the whole company, so feedback compounded across teams instead of staying inside design.

Communication is a system, not a vibe

• I set up the meetings, workshops and channels that kept design aligned with the rest of the org - and cut the ones that didn’t earn their slot.
• Ran monthly “product TV” sessions - talks and takeaways from conferences - to build a shared vocabulary and a steady learning habit.
• Invested in real relationships with stakeholders, so their input shaped the work early instead of arriving as late surprises.

Grow the people, not just the output

• I built development and mentoring for the team, and stayed close enough to actually help people grow in role - not just point them at a course.
• Taught CS and Sales how to collect and use customer feedback, which turned into a centralized research database the whole company could draw on.

Adopt new tools deliberately, not reflexively

• I tested new tools and methods against real work before rolling them out - the bar was efficiency and quality, not novelty.
• Pushed async-first documentation (Loom, written decisions) so distributed teams kept a record and lost less to time zones.