Time team: Documenting decisions & marking milestones · Paul Robert Lloyd
Here’s the transcript of Paul’s excellent talk at this year’s UX London:
How designers can record decisions and cultivate a fun and inclusive culture within their team.
Prompted by his recent talk at Smashing Conference, Mark explains why he’s all about the pace layers when it comes to design systems. It’s good stuff, and ties in nicely with my recent (pace layers obsessed) talk at An Event Apart.
Structure for pace. Move at the appropriate speed.
Here’s the transcript of Paul’s excellent talk at this year’s UX London:
How designers can record decisions and cultivate a fun and inclusive culture within their team.
What happens if the ‘pace layers’ get out of sync?
A very thoughtful post by Miriam on how tools can adversely affect the pace of progress in the world of web standards.
When tools intervene between you and your access to the web platform, proceed with caution. Ask not only: How well does it work? But also: How well does it fail? Not only: What features do they provide? But also: What features do they prevent?
I like this mashup of two diagrams: Stewart Brand’s pace layers and Stephanie DiRusso’s typology of design thinking.
Katie shared this (very good) piece about service design on Slack at work today, and when I got to the bit about different levels, my brain immediately went “pace layers!”
- The Service
- The Infrastructure
- The Organisation
- The Intent
- The Culture
Here’s the video of the opening talk I gave at New Adventures earlier this year. I think it’s pretty darn good!
The pattern library map is not the design system territory.
I suppose it was inevitable that I would smush these two things together.