DesignOps

Good process should make product design easier to execute, not heavier to manage.

Much of my leadership work has involved quietly building the operating systems around design: critique habits, documentation expectations, handoff clarity, and team rhythms that help work move with less confusion. DesignOps, for me, has never meant adding ceremony. It means reducing avoidable friction.

Establishing Operating Rhythm

At Foodsmart, this included introducing:

more structured critique conversations
clearer expectations for design artifacts
stronger visibility into work in progress
more intentional review points before engineering handoff

Making Design Visible

One recurring problem in small teams is that important design thinking disappears into conversations. I pushed for systems where decisions could be revisited:

clearer rationale in files
documentation of tradeoffs
shared references for patterns and decisions

Supporting Designers Without Bureaucracy

Small teams do not need heavy frameworks. They need:

predictable habits
useful templates
enough structure to reduce rework

Learning as Team Infrastructure

I also introduced recurring internal learning moments, including a Lunch & Learn series, to strengthen shared vocabulary and sharpen design thinking across the team.

Principles

Clarity over ceremony

Process should earn its existence

Documentation is leadership

Healthy teams need lightweight structure

The goal was always the same: make good design easier to produce consistently without creating systems that collapse under their own weight.