Catalyze Collaboration

Transparency and openness are the key ingredient to high functioning design teams. There is no substitute for open regular communication. Short of an established process, two meetings a week with key partners will make a huge difference. It’s all about collaboration and bringing people along the journey. I’ve found it helpful to get teams aligned on defining the purpose of each meeting and consideration for who needs to attend.

As design leaders we can help crystalize some of these magic moments for our team by standardizing meeting names across parallel design teams and defining goals for each meeting.

My team meetings and their purpose:

Discovery Brainstorms

Sketching, card sorting, cross team investigations. This is a highly collaborative phase early in the sprint. All key stakeholders, UX/UI/Copy/Animation/Product/Dev partners converge to kick it off.

Co-Design Sessions

Designers can co-design or work independently with frequent check-ins to realize design solutions and prepare for user testing.</li><li>Research Planning – UX/UI work with Research to establish learning goals, create prototypes, observe research, act on user data, and participate in read out sessions.

Design Reviews

Present work in progress – Share project overview, design goals, user scenarios, and a design walk through. Design Team Review is held every Thursday. product pods may also hold their own reviews.


UX/UI to attend as many product pod standups together as possible. The Design team holds its own Standup on Mondays. Come prepared with bulleted items, what you are working on, and any important information to share.


Handoff meetings should be the last of a series of meetings with the development team in a sprint. The design specs should cover all use cases/edge cases and provide guidance on UI patterns and interactions.

Backlog Grooming

Product Pods decide how frequently they run Backlog meetings. UX/UI should have jira tickets written ahead of the meetings, so the product manager can help prioritize and scope tasks along the roadmap.


Retros give us the opportunity to address what’s working, and what we need to improve in our process or approach. They help inform and identify follow up items for the next project or sprint. Stepping back as a team provides the opportunity to align and be proactive together.

Sprint Planning

Jira tickets should be scoped and well defined. A cross functional team reviews the tickets for the upcoming sprint. By attending together, UX/UI designers will establish a shared awareness for sprint priorities and product direction.