UX Brighton: Design decisions & discovery development
Do you want to…
- record and recall your design decisions more efficiently?
- improve your discovery process?
Join us on Tuesday 10 October for an evening of insightful talks by industry experts. Learn about the significance of recording design choices and commemorating project milestones. Gain insights into effective methods and tools for decision recall. Delve into the realm of design discoveries and gain practical strategies for navigating challenges. And, leave with actionable insights to elevate your discovery process.
Time team: Documenting decisions and marking milestones – Paul Robert Lloyd
Exercise regularly; eat plenty of vegetables; floss your teeth. Tasks that feel like chores are often the most beneficial in the long run. The same is true of writing documentation.
Documenting decisions, recording design iterations and explaining commonly used terminology means everyone on a team can have a shared understanding of a product’s design and evolution. Making this information public can increase accountability and build trust. Deliberately building institutional memory can prevent mistakes being repeated and lessons needing to be learnt over and over again.
In this talk, we’ll look at how to record and recall design decisions and consider the role designers play in cultivating a fun yet inclusive culture within a team, and the potential pitfalls to avoid when doing so.
Murder on the dancefloor: The death of disco – Jon Roobottom
Discoveries are crucial to a designer’s toolkit, but why do they sometimes feel like a slog?
Dive into the ins and outs of the discovery process, learn to navigate everyday challenges, and pick up practical strategies to guide your teams toward effective results.
The Agile Comms Handbook: How to Improve Team Collaboration and Boost Clarity – Giles Turnbull
“Agile comms handbook” author Giles Turnbull takes a look at how some teams remember, and what that means for them: better connections with leaders, stakeholders, and colleagues in other teams. Better clarity. More understanding. Less *mis*understanding. He’ll look at real life teams, and a fictional one – and wonder out loud about what team memory could look like for the rest of us. Why is it good to amplify agile working with agile comms? How does it contribute to an atmosphere of safety and trust? And on a more practical note: What needs to change? Who needs to change it? Whose job is that going to be?