As a UX Lead

Ceremonies are recurring meetings that facilitate specific milestones in the workflow.

Figma Admin Guides

Research

User Testing Support

Frequency	Bi-weekly
Duration	1hr
Purpose	This meeting is with Research Lead and the UX team.
Desired Outcome	This is the time for the UX team and Research Lead to collaborate around any evaluative work that is being done, where teaming up on prototypes and tests is important.
Invite Holder	UX Lead
Attendees	Research - Accountable and Consulted

Product Area Research Strategy Sync (Bi-Weekly)

Frequency	Bi-weekly
Duration	1hr
Purpose	This meeting is with Research Lead and Product. It is to take a holistic look at research initiatives, prioritize them against the business goals, and understand how much collaboration will be needed in future sprints.
Desired Outcome	Shared understanding of which initiatives are in focus now and what is coming next, as well as a shared understanding of anything that needs to be deprioritized.
Invite Holder	Research Lead
Attendees	UX - Consulted and Informed

Research Sync

Frequency	Bi-weekly
Duration	1hr
Purpose	This call is for Discovery level planning discussions with Research Lead. We primarily focused on generative efforts here, or efforts tied to the landscape.
Desired Outcome	Alignment with research on generative initiatives and how they might impact production timelines.
Invite Holder	Research Lead & UX Lead
Attendees	TBD

• • •

UX Community

The team is managed through a system of rituals that provide focus windows for recurring tasks that are pivotal to the design process. Rituals are scheduled in two week sprints. Each Sprint consists of a system of ceremonies:

UX Pairing

Frequency	Ad-hoc
Duration	1hr
Purpose	This meeting is for the UX team to have reserved time to collaborate with each other on open stories
Desired Outcome	UX designers support each other in the completion of their stories
Invite Holder	Ad-hoc
Attendees	UX Owns this. DX is Accountable and Consulted. Could drop to just the lead but sometimes gets into resourcing for MHP which impacts everyone so it’s been opened up to everyone for the moment

UX Guild

Frequency	Weekly : Wed
Duration	1hr : 3-4pm
Purpose	This meeting is for the UX team to have reserved time to collaborate with each other on open stories
Desired Outcome	UX designers support each other in the completion of their stories
Invite Holder	Program Manager Debelnogich
Attendees	MMO UX

UX Collaboration Sessions

Frequency	Bi-weekly \| Mon-Thurs
Duration	1hr
Purpose	This meeting is for the lead to socialize designer work with stakeholders.
Desired Outcome	This meeting facilitates moving ideas from discovery into delivery and packaging them for handoff. (Done so in 1H increments) 3 things: 1. What can we package and hand off for development story mapping? 2. Does anything need to be de-scoped or paused? 3. What needs additional UX stories for us to continue exploration?
Invite Holder	UX Lead
Attendees	Product Area UX, Optional: UX/Dev
Playbook	Attendance varies by story being workshopped and may include DX, Dev or all. UX is Responsible for holding this meeting and circulating the results. Results are packaged as : - Screens and flows in the Demo Board - Screens and flows in Development Files - New stories for UX or Dev in Jira DX is accountable for the priority of what we talk about and getting the right cross line of business representation Dev is accountable for supplying technical SMEs under the direction of Product Cross Line of Business stakeholders are accountable/consulted/informed depending on their relationship to a given story. Guardrails: 1. Generate delivery stories 2. Control scope-creep and allows us to pivot 3. Generate discovery stories (sometimes research) If you ask these questions with this method in mind at the end of every session you as a lead can come away with 2-4 sprints worth of stories to add for every sprint full of these you run.

• • •

Scrum

The team also supports a system of development ceremonies that are held and maintained by DX and Development. UX is Consulted and Informed in these calls. Attendance is sometimes divided among SMEs in UX to account for the realities of time.

Development follows a system of agile ceremonies alongside UX

We Amigos - Based on ~this~
Product Sprint Review
Daily Standup
Grooming/Backlog Refinement
Review Product Area Backlog and Stories
Code Reviews
Product Sprint Review/Demonstration
Sprint Retrospective
Sprint Planning

UX Sprint Planning & Backlog Refinement

Frequency	Bi-weekly
Duration	1hr
Purpose	This meeting is with the UX team and DX
Desired Outcome	This is when we prioritize the order of stories in the backlog with DX and make sure we know what is being committed to for the next sprint.
Invite Holder	Program Manager Debelnogich / UX Lead
Attendees	UX Owns this. DX is Accountable and Consulted. Could drop to just the lead but sometimes gets into resourcing for MHP which impacts everyone so it’s been opened up to everyone for the moment

UX Refinement

Frequency	Bi-weekly \| 2-3pm
Duration	1hr
Purpose	Align team around what needs focus for next sprint
Desired Outcome	This is when we build out and point stories together
Invite Holder	UX Lead
Attendees	Product Area UX

Daily Standup

Frequency	Daily
Duration	15-30mins
Purpose	Align team around what needs focus for today
Desired Outcome	Parking lot items addressed, blockers identified, initiative statuses up to date
Invite Holder	Program Manager Debelnogich / UX Lead
Attendees	Product Area UX
Playbook	Gather individual updates - What happened yesterday - What’s happening today - Any Blockers? - Any Parking Lot Items? *Try to timebox this to 15-20 min — do not support more than 7 people for a standup on an ongoing basis, if the team gets that big you need two standups Parking Lot This is where you address parking lot issues people bring up. Bring your own topics as lead to this to keep work moving in ceremonies.

Retro

Frequency	Bi-weekly \| 4-5pm
Duration	1hr
Purpose	Chance for the team to talk about lessons learned and action items
Desired Outcome	Swim lanes discussed openly and action items identified
Invite Holder	UX Lead
Attendees	Product Area UX
Playbook	We have the conversation in a FigJam file with pages for each sprint.

Design System

Depending on organization availability of a design system or lack of, may determine the appropriate focus. If a design system is not present, small gradual steps to document usage to be more consistent is an immediate opportunity to quantify cost savings be reusing components and design styles.

DS Sync

Frequency	Bi-weekly
Duration	1hr
Purpose	This meeting is to sync with Product Area Leads about Design System
Desired Outcome	Update Figma + Zeroheight
Invite Holder	Program Manager / UX Manager
Attendees	UX Leads

DS Governance Committee

Frequency	Monthly
Duration	30min
Purpose	To review progress on the design system.
Desired Outcome	In the current phase we will be reviewing new updates and additions to the documentation.
Invite Holder	UX Manager
Attendees	UX Leads / DX / Dev