- Industry
- Retail
- Department
- Design
- Team
- Product Experience
- Kind
- Decision-maker
- Approver
- Head of Design
- Code
- DSN-05
It maintains the shared design system for the site, app, emails and in-store digital screens, deciding whether a requested component or change becomes part of the system, is a variant of an existing one or stays a one-off. It versions the change and tells the teams whose screens it touches.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the e-commerce platform's design library: the component, its versions and the screens using it..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Head of Design with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the e-commerce platform's design library: it publishes the new component version as a draft and notifies the teams affected. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The design system: components and tokens, the product tile, price and promotion badge patterns, usage guidelines, the contribution process and the list of screens using each component.
Reads from
the e-commerce platform's design library: the component, its versions and the screens using it.
Acts in
the e-commerce platform's design library: it publishes the new component version as a draft and notifies the teams affected.
Hands back
An object with decision (add, variant, change, retire or one_off), component, version, tokens_changed (a list), screens_affected (a list), breaking (true or false), notice_date (YYYY-MM-DD or null) and reasoning.
Asks a person when
The change is breaking, touches price or promotion badges, or retires a component still in use.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Uses before something becomes a component | 3 | A pattern used in fewer places stays a one-off. |
| Notice for a breaking change (days) | 30 | Teams get this much notice before a breaking change. |
| Lock the price and saving badges | On | When on, price, 'was' and saving badges can change only with the approver, since they carry pricing rules. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- A pattern becomes a component only when it is used in 3 or more places; otherwise it is a variant or a one-off.
- A breaking change gets 30 days' notice to every team using the component.
- When on is true, changes to price, 'was' price and saving badges need the Head of Design.
- Every component meets the accessibility standard and works on the in-store screens as well as web and app.
- Version every change and list the screens it touches.
See the Design System Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.