AI design engineer. Prev @bayer @qiagen @philips @marsglobal - https://nitter.gq/t.co/drpSbnj48y
Building in public
Joined July 2020
- Tweets4.7K
- Following1K
- Followers5K
- Likes1.3K
Why safety demands retesting new flows in usability engineering.
When I wrote the test scenarios for a pulse oximetry project, I separated the SpO2 tasks carried over from an older product from the new safety behaviours.
And if you change a carried-over task at all, even a label or the order of the steps, treat it as new and retest it.
Need help planning your retests? My two-hour triage is €1,000, and it's credited if you book the full usability engineering readiness review within 14 days.
awolesigideon.com/work-with-…
Make your tokens human readable. Here's why.
Right now, a token called blue-500 only describes the colour. A designer reading the name still has to work out if it belongs on buttons or links, and your coding agent has the same problem.
And when you ask a coding agent for an error message, text-error is an easy match. With red-600, the agent may use a red that's meant for something else, like a delete button.
If you want me to check your tokens before a coding agent builds from them, it's part of my AI-ready design system audit.
awolesigideon.com/work-with-…
ARDS monitoring was split across systems, so I designed one view for the ICU team.
On a medical project I worked on, the monitoring data for patients with ARDS was spread across different systems, and clinicians had to combine it themselves.
When a clinician has to move between systems to understand one patient, they have to connect the data in their head, and they can miss something every time they switch.
If you're designing a clinical product and getting ready for usability testing, I can map your gaps in my usability engineering readiness review.
awolesigideon.com/work-with-…
Making your AI agent a user of your design system.
When you ask your coding agent to build a screen, it's supposed to read your components and your docs to decide how and what to build. It needs four things from your design system.
4. Point the agent at one source of truth when your Figma file and your code don't match.
If someone patched a component in the code and never updated it in Figma, the agent can build from the old Figma version and bring the old design back.
If you want to know if a coding agent can build from your design system, I can test it for you.
awolesigideon.com/work-with-…
