What does a high-functioning UX team actually look like day to day?

Overview

• Built and led a UX team offering end-to-end research, design, and strategy services

• Designed a repeatable team rhythm that balanced execution with exploration

• Served as the connective tissue between UX, leadership, and the broader organization

How We Were Structured

When I built this team, I wasn’t just hiring for skills — I was designing a function. Every role had a clear lane, and every person had a counterpart they could hand work to without losing momentum. I operated as the “point person” model: one owner per workstream, so nothing fell into the gap between Research and Design, or between Design and Engineering.

We ran on a Shape Up-influenced PM system, which gave us the structure to take on 2-3 projects per cycle (WCs 3-8) without overextending. Work was scoped into manageable chunks, and we built in cooldown periods — Weeks 1-2 of each cycle — to reflect, reset, and explore ideas before the next push.

Our team was comprised on 4 people, including myself:

• 2 Product Designers

• 1 User Researcher

• 1 Researcher/Leader

Our Weekly Rhythm

The team ran on a weekly check in meeting and a design review that kept work visible and feedback consistent. Check in meeting was the opportunity for the point person for each project to discuss progress, ask for help or collaboration, and support each other through awareness of the tasks for the week. Design review wasn’t a status meeting — it was a working session where we pressure-tested ideas, caught misalignment early, and made sure design decisions were grounded in what we knew about users.

Planning weeks were intentional. The first one or two weeks of each cycle were dedicated to intake and leadership alignment — making sure we understood priorities before we started executing, not after. During this time, the rest of the team completed work that often fell to the wayside, such as:

• Updating the design system

• Exploring a new design idea

• Researching a topic

• Testing a tool

• Maintaining the research recruitment pool

• Checking in with colleagues

• QA evaluation

What We Offered

The team provided a full suite of UX services, which I scoped and staffed based on project needs:

• Customer & Client Empathy Workshops — bringing stakeholders closer to user perspectives

• Prototyping — translating research into testable concepts

• Design Research — grounding product decisions in user behavior

• Exploratory Research — getting ahead of the roadmap to understand emerging needs

• Metric Development — defining how we’d know if something was working

This range meant we could support a project at any stage, from early discovery through post-launch evaluation.

Staying Connected to the Organization

One thing I prioritized was making sure UX wasn’t operating in a silo. I built communication structures that extended beyond our immediate team — regular touchpoints with stakeholders, clear documentation of decisions and findings, and an AI tooling practice we tested and iterated on together to stay efficient and current. The “point person” model helped here too. Stakeholders always knew who to go to, and our team always knew who owned the relationship.