📍 Bath, UK
🌐 http://pixelpioneers.co
✅ Core Systems
✅ Components
✅ Design Tooling
✅ Education & Communication
✅ Research & Documentation
✅ Culture
He also explains how to map them to business outcomes and how this scales for any team size.
This article dives into why that breaks down at scale, and the 6-pillar operating model that fixes it.
Check it out 👉 https://hubs.li/Q04w4rDL0
✅ Core Systems
✅ Components
✅ Design Tooling
✅ Education & Communication
✅ Research & Documentation
✅ Culture
He also explains how to map them to business outcomes and how this scales for any team size.
Kardo Ayoub presented an incredibly personal talk about becoming a visually impaired designer. It's an essential watch about accessibility and inclusive design: youtu.be/aP89uEMDGUI
AI is making it easier for more people to participate in design, but that's not the same as inclusion.
Read the final part of Thomas Shillingford's trilogy on AI ethics in enterprise #designsystems:
Closing out the 3-part AI ethics series: can AI-augmented design systems genuinely democratise design?
Read part 3 👉 https://hubs.li/Q04vHZTd0
AI is making it easier for more people to participate in design, but that's not the same as inclusion.
Read the final part of Thomas Shillingford's trilogy on AI ethics in enterprise #designsystems:
Well, at least design systems as we know them. In this talk from our June event, @lurkmoophy.bsky.social argues for positioning them as core product infrastructure rather than a separate, magical discipline.
👉 You can watch it now, for free: youtu.be/sa_IJRjPtJw
Well, at least design systems as we know them. In this talk from our June event, @lurkmoophy.bsky.social argues for positioning them as core product infrastructure rather than a separate, magical discipline.
👉 You can watch it now, for free: youtu.be/sa_IJRjPtJw
In the 2nd part of Thomas Shillingford's series on AI ethics in enterprise #designsystems, he explores the accountability gap in AI-assisted design.
Part 2 of Thomas's series digs into how AI design output can look credible while missing things like accessibility labels or quietly reinforcing bias from training data.
👉 https://hubs.li/Q04tqlSb0
In the 2nd part of Thomas Shillingford's series on AI ethics in enterprise #designsystems, he explores the accountability gap in AI-assisted design.
👉 Watch the video of the talk on YouTube: www.youtube.com/watch?v=KO02...
👉 Watch the video of the talk on YouTube: www.youtube.com/watch?v=KO02...
In the first part of Thomas Shillingford's series on AI ethics in enterprise #designsystems, he argues that clear ethics guardrails aren't a brake on speed — they're what make AI safe to scale.
Thomas explores why the fastest AI adopters are often the least governed - and what that means for design teams.
Read the first of the 3-part series: https://hubs.li/Q04t226q0
In the first part of Thomas Shillingford's series on AI ethics in enterprise #designsystems, he argues that clear ethics guardrails aren't a brake on speed — they're what make AI safe to scale.
👉 Watch Nick Lewis's digital sustainability talk, now free to watch on YouTube:
In his talk on digital sustainability, @sustainable-dev.bsky.social explains how designers and developers can reduce the footprint of the products and services they create for clients.
Watch it here: 👇
👉 Watch Nick Lewis's digital sustainability talk, now free to watch on YouTube:
And argues that naming these patterns openly is what lets teams push back on under-resourcing.
Read the article on the @zeroheight.com blog:
There's also the reality - told on Reddit and Discord after hours.
Nathania surfaces the truths practitioners know but assume aren't worth sharing officially. ⬇️
https://hubs.li/Q04sc_yJ0
And argues that naming these patterns openly is what lets teams push back on under-resourcing.
Read the article on the @zeroheight.com blog:
In this talk, @morganepeng.bsky.social examines the Developer x Designer x PM trio. She covers how teams can spend less time translating each other, with or without AI, and more time working together effectively. 👇
In this talk, @morganepeng.bsky.social examines the Developer x Designer x PM trio. She covers how teams can spend less time translating each other, with or without AI, and more time working together effectively. 👇
In her latest article on the @zeroheight.com blog, Charlotte MacInnes explains how to measure design system impact with metrics that really help teams make better decisions:
But not all of them are useful.
Some make us feel productive. Others help us make better decisions.
Charlotte makes the case for treating design systems as products, and measuring them like one.
Read the full article here ➡️ https://hubs.li/Q04rvwHS0
In her latest article on the @zeroheight.com blog, Charlotte MacInnes explains how to measure design system impact with metrics that really help teams make better decisions:
Check out TJ Pitre's excellent 3-part series on the future of #designsystems for the @zeroheight.com blog.
In part 1, TJ examines the product your design system is actually building: zeroheight.com/blog/the-fut...
Check out TJ Pitre's excellent 3-part series on the future of #designsystems for the @zeroheight.com blog.
In part 1, TJ examines the product your design system is actually building: zeroheight.com/blog/the-fut...
Check out TJ Pitre's excellent 3-part series on the future of #designsystems for the @zeroheight.com blog.
In part 1, TJ examines the product your design system is actually building: zeroheight.com/blog/the-fut...
A gap remains: what happens when a team hits a pattern the system didn't anticipate?
Read how to close that gap before it becomes accessibility debt 👇
https://hubs.li/Q04qQC5Y0
Rachel's talk was such a great way to kick off this year's event:
I talk about Baseline, polyfills, progressive enhancement, and cover a bunch of interesting web platform features along the way.
Rachel's talk was such a great way to kick off this year's event:
Mobile accessibility is usually not one of them.
This blog digs into the accessibility barriers and what mobile-first accessibility looks like in a design system.
Check it out 👉 https://hubs.li/Q04pR--50
The goal is not to make Figma mirror code perfectly. It's to help teams understand the system well enough to use it effectively.
Check out Ron’s take here 👇
https://hubs.li/Q04p0B6B0
The goal is not to make Figma mirror code perfectly. It's to help teams understand the system well enough to use it effectively.
First up is this great post by @iknowdavehouse.bsky.social, in which he introduces us to his favourite analogy for design system contribution:
👇👇 👇
Many ways up, many ways down - and it gets very steep at the top.
Read about Mount Contribution - a framework for more effective design system contributions👇
https://hubs.li/Q04n4Bq80
First up is this great post by @iknowdavehouse.bsky.social, in which he introduces us to his favourite analogy for design system contribution:
👇👇 👇
In this article, @amyrogers.design explores how we can make our design documentation stronger, for both human and agentic development, and why she thinks now is the best time to start. 👇
Amy Rogers explores how AI agents could be the answer 👇
https://hubs.li/Q04mCSPN0
In this article, @amyrogers.design explores how we can make our design documentation stronger, for both human and agentic development, and why she thinks now is the best time to start. 👇
Read it on the @zeroheight.com blog: 👇
With AI working inside design systems, undocumented reasoning is a gap the model will fill on its own.
Great piece by Kevin Muldoon on the three kinds of truth every system needs: hubs.li/Q04f6BFv0
Read it on the @zeroheight.com blog: 👇
If there's one photo that sums it all up, it's this one. 😀 Special thanks to @heydonworks.com, and their dancers @letorey.co.uk and @brucel.bsky.social, for such a memorable closing talk. 🕺
If there's one photo that sums it all up, it's this one. 😀 Special thanks to @heydonworks.com, and their dancers @letorey.co.uk and @brucel.bsky.social, for such a memorable closing talk. 🕺
Looking forward to seeing everyone at the warm-up at JET tonight!
Looking forward to seeing everyone at the warm-up at JET tonight!
Most design system contribution models have great documentation. Almost none have momentum.
The difference isn't process. It's ritual. 💡
A great read for anyone working on design systems: hubs.ly/Q04dSNBz0
www.debugbear.com/blog/which-e...
www.debugbear.com/blog/which-e...