What is it?
A meeting to align everyone on the project — including goals and next steps.
Why do we do it?
Keeping everyone involved from the beginning stops us from working in silos. It also expands our thinking and allows others to give feedback/advice on what we’re working on.
Things to prepare
An audit findings overview presentation.
Example presentation
- Why are we doing this? What problem do we need to solve?
- Audit of the component in use, including any other areas where it could/should be used
- Customers impact
- Why now?
- Any additional supporting data/evidence?
Who should be there?
This depends on your team, but a good rule of thumb is —
Developers
If you want to ship and ship fast, you’ll want to involve your Developers from the beginning. Not only will they feel like they’ve been part of the process, they’ll be bought in, so they’ll more likely be engaged to work on this project.
It also eliminates this idea of a ‘handover’ where they’ve not seen anything until they’re told to build it — yuck.
Be sure to include any Developer working on this project or has some investment in it. If you have multiple platforms, including a representative from each platform is essential.
Other Designers
Any other Designers, Content Designers or Researchers in your team that will be involved in this work.
Key stakeholders (optional)
Any stakeholders for this project, including Product/Program Managers, Delivery Managers, or even external team members who will be using this component/have expressed interest in this work.
Example agenda
This depends on how your audit has come together and who you have in your session.
- Introduction to the component & walkthrough of your presentation/playback
- Any existing issues cross-platform
- Current platform implementation — if any
- Feedback and ideas
- Next steps
Outcomes
- Team alignment
- Cross-platform awareness
- Additional areas to investigate
