What design ops means
Design ops covers the tools, processes, and habits that help a design team do good work at pace. In a small team it is not a role. It is a handful of agreements that everyone follows.
Four rituals worth having
| Ritual | What it does | Cadence |
|---|---|---|
| Intake | A single place and format for design requests | Always on |
| Critique | Structured feedback on work in progress | Weekly |
| Handoff review | Confirms designs are ready for build | Per feature |
| Retrospective | Improves how the team works | Monthly |
Tools and structure
- Organize files by product area, with clear names and a status for each.
- Maintain one shared library of styles and components.
- Keep decisions in a searchable log, so people do not relitigate.
- Use the same tracker as engineering where possible.
Roles when you are small
Someone should own the design system, someone the research habit, and someone the intake and priorities. In a team of three, those can be shared. What matters is that each is a named responsibility, not an assumption.
Review and trim
Every quarter, ask: which process is helping, which is just ceremony? Remove what is not useful. A light process that people follow beats a thorough one that people ignore.



