Choose whether your system should be fully custom, adapted from a UI kit, or a mix of both. Use this when defining scope or revisiting direction. Some teams need the speed of a kit, others the flexibility of custom work, and many end up with a hybrid. This tactic helps you weigh trade-offs so the system fits your maturity, capacity, and goals.
How to
-
Assess maturity
Run a Maturity Assessment first to understand how much ambition your organisation can realistically support.
-
Define problems
List 2-3 issues driving the need for a system. Use an Audit or System Vision Workshop to capture evidence and align scope.
-
Document existing infrastructure
Review existing design and engineering tooling the system will serve.
-
Review off the shelf UI kits
Research UI kits and note where they align or fall short.
-
Run a spectrum workshop
Draw a Custom–Hybrid–Kit spectrum. Present evidence, then ask participants to place a dot where they think the system should sit. Cluster results, discuss outliers, and capture trade-offs.
-
Record decision
Agree on a position and write down why. Share the rationale so alignment sticks.