PO · Product Lead
Brings the initiative and does the second validation.
Never edits the library.
Workflow
A clear process, from initiative to production.
How I work with Digital Workers. People understand the problem, decide and validate. Digital Workers build with the published design system, and every risky step passes through a human gate before moving on.
At a glance
The whole journey
Five phases. Every initiative starts the same way and only branches when it is time to build: either it is solved with what the design system already has, or a component is created or changed.
People decide and validate. Digital Workers prepare proposals, build and document.
PersonDigital WorkerHuman gate
- Phase 1
Understand
What the problem is, and for whom.
- The initiative arrivesPO · Product Lead
- Analyse the initiativeProduct Designer
- ResearchProduct Designer, supported by a Digital Worker
- Phase 2
Decide
Which proposal solves the initiative.
- Prepare proposalsDigital Worker, led by the Product Designer
- Choose the pathProduct Designer
- Phase 3
Build
With the system, never drawn by hand.
- A · Iterate screensDigital Worker · Iterations
- B · Evolve componentsDigital Worker · Design system
- Phase 4
Validate
Two human reviews before moving on.
- ApproveProduct Designer
- Second validationPO · Product Lead
- Phase 5
Ship
Only when the system has changed.
- Publish the libraryProduct Designer
- ImplementFront end
An iteration on path A ends at phase 4.
Below, the same journey step by step: who does each thing and where a person decides.See the flow in detail
The flow in detail
From initiative to production, step by step
Follow the entry up to the decision and choose a path at the end. The path opens right after it, and from the bar at the top you can go back to the start or switch to the other one. Click any step to see what happens in it.
1 · Initiative
2 · Analysis
3 · Research
4 · Proposals
5 · Decision
Choose a path
What the Digital Workers read
Published library · “DS Library”
The only thing a screen can be composed from. It is imported by its published key.
Custom skill · “/figma-agent”
The iterations Digital Worker's: build hierarchy, the clone-and-detach recipe, the padding rule and the checklist.
Registry and documentation
The design system Digital Worker's: the keys, nodes and axes of each component, and one document per component with anatomy, tokens and accessibility.
Responsibilities
Who does what, and what they never do
That is why the gates are where they are.
Product Designer
Analyses, leads the research, chooses the path, approves every iteration and every change, and publishes.
Never publishes anything unverified.
Iterations
Builds screens with the published library in the team's file and hands back what is missing.
Never touches the library.
Design system
Prepares proposals from the system, builds in the library, verifies and documents in the same task.
Never publishes, renames or deletes without approval.
Front end
Implements against the published key and the written contract.
Never copies values off a screenshot.