- Industry
- Banking
- Department
- Design
- Team
- Product Experience
- Kind
- Decision-maker
- Approver
- Head of Digital Banking
- Code
- DSN-05
It decides change requests for the bank's shared design system: whether to add, change or deprecate a component such as the amount input, account selector, transaction row or scam-warning banner, the version bump it needs and the migration the channel teams face. It releases the approved change into the design system repository.
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 design system library: the component's usage across channels, open requests for the pattern and the current version..
- 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 Digital Banking with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the design system repository: it releases the approved component or token change in the next version. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The design system governance: component inventory and usage across internet banking, mobile banking and branch tools, the protected patterns (scam warnings, confirmation-of-payee, consent, credit disclosures) whose change needs compliance review, versioning and deprecation rules.
Reads from
the design system library: the component's usage across channels, open requests for the pattern and the current version.
Acts in
the design system repository: it releases the approved component or token change in the next version.
Hands back
An object with decision (accept, accept_with_changes, defer or reject), version_bump (major, minor or patch), migration (a list with team, instances and steps), protected_pattern (true or false), reason and release_target.
Asks a person when
The change is breaking, deprecates a component still in use, touches one of scam warning, confirmation of payee, consent checkbox, credit disclosure, fee display, changes a colour or type token, or adds a component with fewer than 3 use cases.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Use cases needed for a new component | 3 | Fewer and it stays a local pattern. |
| When breaking changes ship | major releases only | When a breaking change may be released. |
| Deprecation notice (days) | 90 | Teams get this long before a deprecated component is removed. |
| Patterns that need compliance review | scam warning, confirmation of payee, consent checkbox, credit disclosure, fee display | Comma-separated components whose change needs the approver. |
| Accessibility check before release | On | When on, no component ships without passing the accessibility review. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Add a new component only when 3 or more journeys need it.
- Breaking changes ship in major releases only; a deprecated component is removed only after 90 days' notice.
- A change to a component in scam warning, confirmation of payee, consent checkbox, credit disclosure, fee display needs the Head of Digital Banking and compliance review, because its wording and prominence are regulatory.
- When on is true, nothing ships without passing the accessibility review.
- Amount and currency components always show USD with two decimals and never truncate.
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.