UX Ops & Team Enablement
Your design team has grown but your ways of working haven't kept pace. Reviews are inconsistent, onboarding is slow, and too much depends on whoever has time. This workshop builds the operating system your team needs.
Format: 1 day · in-person or remote. Audience: Heads of design, design managers, product leaders managing a growing design team.
Duration: 1 day. Group size: Up to 20 participants. Delivery: In-person or remote. Languages: English.
What you will learn
- A weekly and quarterly cadence your team can run themselves
- A design review model that raises craft without slowing delivery
- An onboarding kit so new designers ship in week one
- A weekly and quarterly ritual cadence — from standups to retrospectives — your team can run independently.
- A design review model that raises craft quality without becoming a blocking process.
- A new-designer onboarding kit that gets people shipping in their first week.
- A shared quality bar your team can reference when giving and receiving feedback.
- A template library that reduces duplicated effort across the team.
- A design ops roadmap — what to build now, what to build in six months, what to defer.
Why this matters now
- Design teams that grow from five to fifteen people hit the same wall. The informal ways of working that held together in a smaller team stop scaling: ad hoc reviews, onboarding by osmosis, quality that varies depending on who reviewed it.
- The problem is rarely the people. It is the absence of shared infrastructure — no agreed quality bar, no reliable review cadence, no onboarding that doesn't depend on whoever happens to have time that week.
- This workshop builds that infrastructure in a day. Not a generic playbook. A set of rituals, templates, and a prioritised ops roadmap built around your team's actual structure and specific gaps.
Ops models built at Adobe, Alibaba, National Bank of Canada
Your design team has grown but your ways of working haven't kept pace. Reviews are inconsistent, onboarding is slow, and too much depends on whoever has.