Rekon system.
The Design Cortex map
Design Cortex connects company knowledge, the design system and research to prototyping. Select a point on the map to see its role.
02 / Core
Design Cortex
I connect relevant sources and product rules to the task. The team reviews the result before release.
01 / Source
Company knowledge
Documentation and past decisions carry forward what the team already knows.
01 / Source
Design system
Components, tokens and guidance help choose a pattern for the task.
01 / Source
Research and customer needs
Research observations and their sources establish who we’re designing for and which task needs to get easier.
03 / Output
Prototypes
An interactive HTML prototype gives the team flows and states to walk through and review.
03 / Output
Consistent communication
A shared product vocabulary can make labels, messages and interface copy more consistent.
03 / Output
Decisions about changes
Review leads to a decision to change the prototype, update a rule or gather missing evidence.
How I work on a project
Choose a stage to see what comes out of each step.
Stage 01 / 05
Understand the goal
I ask what the user needs to do and how we’ll tell whether the design helps.
After this stage: A goal and a success criterion.
Stage 02 / 05
Check the evidence
I gather available research, decisions and constraints. I identify what still needs an answer.
After this stage: Sources and a list of questions still open.
Stage 03 / 05
Choose the rules
I match the task to product rules, suitable components and a skill for the work.
After this stage: Rules and components matched to the task.
Stage 04 / 05
Build a prototype
I build something the team can try using examples close to their everyday work.
After this stage: A prototype and a scenario to try.
Stage 05 / 05
Review the result
I check the prototype against the brief and decide what to improve and hand over.
After this stage: A decision on what to fix, approve and hand over.