Future Product Days / Substack
The system finds its voice
How to teach an agent to choose the patterns it needs.
Read on SubstackMichał Aleksander’s design studio
Design Cortex.
Use AI to prototype with your team’s research, design system and decisions. Test the idea before you build it.
Anatomy of a prototype
Turn what your team knows about the product into a prototype it can test and refine.
-
Product context
The team brings a user task, research findings, earlier decisions and the relevant design system rules.
-
HTML prototype
AI uses the selected material to build an interactive flow the team can try.
-
Team review
The designer reviews the flow. The team decides what to refine, what to test and which rules should change.
Pilot
One product. One task.
Choose a task your team wants to test. We’ll agree the scope, cost and acceptance criteria before we start.
- What you bring
- The task, sample source material and the relevant part of your design system.
- What you receive
- An interactive HTML prototype, a record of the checks and the questions still open.
- Who reviews it
- We review it together with the person your team names.
From the studio
Notes on Design Cortex
Design Cortex / Substack
Who sets the points?
When I change a screen, and when I change a rule used across projects.
Read on SubstackBefore you start
Do we need to switch tools?
We start with the tools and material your team already uses. We agree any connections and access as part of the pilot.
Who can change a shared rule?
The person responsible for the design system approves changes before the team uses them in other projects.
Can we put the prototype into production?
The prototype helps the team test the idea. A release follows a product and engineering review and the tests you agree to run.