Jon Aizlewood · Agile and design — How to avoid Frankensteining your product

A 5 day sprint with Clear Left exploring library self-service machine software – Leon Paternoster

Myself and Batesy spent last week in Ipswich doing an intense design sprint with Suffolk Libraries. Leon has written up process from his perspective as the client—I’ll try to get a case study up on the Clearleft website soon.

This is really great write-up; it captures the sense of organised chaos:

I can’t recommend this kind of research sprint enough. We got a report, detailed technical validation of an idea, mock ups and a plan for how to proceed, while getting staff and stakeholders involved in the project — all in the space of 5 days.

Get it shipped — building better relationships with Devs

This advice works both ways:

1. Collaboration
2. Communication
3. Respect

Five Key Milestones in the Life of a Design System - daverupert.com

Five moments in the lifecycle of a design system. They grow up so fast!

1. Formation of the Design System Team
2. First Page Shipped
3. Consumable Outside the Main Product
4. First Non-System Team Consumer
5. First Breaking Change

Dave makes the observation that design systems are less like open source software and more like enterprise software—software you didn’t choose to use:

Often, in my experience, for an internal Design System to have widespread adoption it requires a literal executive mandate from the top floor of the building.

Also: apparently design systems have achieved personhood now and we’re capitalising them as proper names. First name Design, last name System.

“Please, call me Design. Mr. System was my father.”

Level of Effort | Brad Frost

Brad gets ranty …with good reason.

Nicole Fenton | Words as Material

If we want design to communicate, we need to communicate in the design process.

I might get that framed.