01 / The system in its context
Three product lines.
One end-to-end system.
Pebble was a shared design system spanning Mobility, Food Delivery, and Financial Services. Its scope covered foundations, design methods, reusable design and development resources, documentation, adoption, and UX measurement. It supported two established back-office platforms—Magellan and Gattaran—with nearly 100 products combined, while the Financial Services platform was developed alongside the system from the ground up.
PEBBLE DESIGN SYSTEM
Foundations · Methods · Resources · Documentation · Adoption · Evaluation
MobilityMagellan platform with 30+ products
Food deliveryGattaran platform with 50+ products
Financial servicesPlatform/products developed alongside the system
I personally owned
As a project owner, I defined the vision, scope, and roadmap for Pebble; aligned design, product, and engineering teams across three product lines; prioritized shared and product-specific needs; reviewed all the deliverables, and drove the system from foundations and reusable resources through rollout, adoption, and evaluation.
We built together
Two component designers to define the styles and interaction states of the components. Two visual designers to define the visual system (colours, shadows etc.), design the icons, system logo and website cover. Two business designers to collect the requirements from business lines and integrated into the system design and guidelines.
02 / Direction & tradeoffs
Standardise what is shared.
Keep business logic flexible.
Pebble’s direction came from separating repeated cross-product problems from decisions tied to a specific business. We standardized the foundations that were costly to recreate—tiered tokens, core components, common interaction patterns, and guidance for globalization and accessibility. Domain workflows, specialised components, business templates, and local success measures remained flexible. This created consistency where it reduced duplicated effort, without forcing Mobility, Food Delivery, and Financial Services into the same product model.
Standardize first
High-cost, repeatable foundations
An internal estimate suggested that restyling components could consume around 50% of a request’s development cycle. Combined with repeated UI implementation and inconsistent interactions, this made tiered tokens, base components, common states, and high-frequency patterns our first priorities.
Leave room for
Domain-specific decisions
Operational workflows, specialized components, business templates, and measurement definitions depended on local users and business logic. Product teams could build on the shared foundation, while patterns were considered for the shared system once they proved reusable beyond a single product.
The decision I stand behind
We considered standardizing every layer across product lines or building a shared core with product-owned extensions. I recommended the latter because it focused investment on repeated, high-cost problems while preserving domain expertise. We accepted slower convergence in business-specific workflows. Evidence: component restyling was estimated to consume nearly 50% of a request’s development cycle, while specialized patterns varied significantly by product line.
03 / Foundations & token hierarchy
One hierarchy.
Multiple product expressions.
Pebble used a three-level token structure—foundation, global, and component—to create a shared design language without forcing every product to look the same. Product variation was handled through theme mappings, while components continued to follow one consistent structure.
System decision
We chose this hierarchy to make variation explicit and change predictable. Foundation tokens held raw scales; global tokens assigned shared roles and theme mappings; component tokens applied those roles to individual controls and states. A change to a shared value propagated through its references, allowing teams to update a theme centrally while preserving consistent component behavior.
Implementation boundary
In Sketch, the design library and token table defined the hierarchy, naming, and intended mappings. Pebble library implemented the corresponding values and component behavior in code. Design and front-end engineering reviewed mappings together, while engineering owned package implementation and releases. This was a coordinated design-to-code contract, not an automated synchronization pipeline.
04 / One component, examined closely
Standardize the behavior.
Let the content adapt.
The Option list separates selection behavior from item content. The system standardizes focus, states, keyboard interaction, and commit behavior; products define the information users need to compare.
| Decision layer | Show the rule | Show the consequence |
|---|
| Structure | Selection was applied to the shared list-item foundation rather than bound to a fixed option anatomy. The system defined the selectable row, focus boundary, selection control, and optional list regions such as search, grouping, and footer actions.
Products composed the item content, while every item within one list followed the same template and alignment.
| A simple label, an image-supported choice, or an information-rich business object could use the same selection model. Teams could provide the context their users needed without creating a separate dropdown component for every content combination. |
| Behavior / states | Default, hover, focus, selected, indeterminate, and disabled states applied to the entire row, regardless of its internal content. The list also defined loading, empty, error, and no-result states.
Single-select committed immediately and closed the list. Multi-select maintained a draft selection and used an explicit Done action. When secondary actions were needed, they used defined trailing regions and separate interaction rules, so they did not compete with or accidentally trigger row selection. | Users encountered the same selection and keyboard model across products, even when the visible content differed. Richer items did not introduce ambiguous click targets, inconsistent states, or unexpected commit behavior. |
| Content / i18n | The product template owned its information hierarchy, media, metadata, content density, and wrapping or truncation rules. The system required one consistent template within each list and ensured that selection controls, focus behavior, and interaction priority remained stable.
Templates also had to accommodate longer translations and RTL layouts. When content introduced independent actions or required image-first comparison, we switched to a table, card picker, or dedicated browser instead of stretching the Option list beyond its intended role.
| Products could surface the domain-specific information users needed to make a decision without creating locale-specific or content-specific component variants. The pattern remained adaptable without becoming visually or behaviorally ungoverned. |
| Accessibility | The entire item remained one focusable option. Arrow keys moved between options; Enter or Space selected; Escape dismissed the list; and focus returned to the trigger when it closed.
Each product template supplied one accessible name—and an optional description—from the minimum information needed to distinguish the option. Decorative or redundant media was hidden from assistive technology. Single-select used a leading checkmark, while multi-select used checked and mixed control marks. These visual cues were paired with programmatic states rather than relying on color alone. | Keyboard and screen-reader users could navigate one predictable selection model, even when an item contained rich information. Internal content did not become a collection of separate focus targets or repetitive announcements. |
The edge case that changed the design
Single-select options initially relied on the selected-row treatment to indicate the current value. This depended too heavily on color. There were many systems using a checkmark at the end of the list item for single-select. However, adding a checkmark on the right created another problem: that region might already contain metadata, secondary actions, or a child indicator.
We thus introduced a reserved leading selection-indicator region. Unselected items kept the space empty, while the active option displayed a checkmark. This preserved content and trailing alignment while making the selected state identifiable without color alone.
05 / Guidance for international products
Turn global constraints
into product rules.
Internationalization
Design for various text lengths.
Longer translations exposed the limits of horizontal labels and fixed positioning. We moved labels above fields, allowed content to grow vertically, and separated actions from variable-length text.
The same structure remained readable across languages without creating locale-specific layouts.
Accessibility
Make state legible beyond color.
Focus and selection could not depend on orange alone. We paired color with a visible focus outline and explicit state marks: a leading check for single-select and checked or mixed controls for multi-select.
The states remained distinguishable when color was removed.
06 / The design system website
A shared front door
for design and development.
I contributed to the information architecture, page design, and guidance content of the Pebble website. We organized it at two levels: an overview that made the scope of the system easy to navigate, and detailed guidance that helped teams apply individual components and patterns.
At the overview level, the website connected design principles, methods, reusable resources, development guidance, and measurement. At the detail level, each page translated a resource into actionable guidance through anatomy, usage rules, examples, layout constraints, and links to implementation documentation.
EXAMPLE / COMPONENT GUIDANCECARD
WHENUse cards to group related information into a single, scannable unit—particularly when items need to be compared or arranged responsively.
HOWThe guidance defined component anatomy, content hierarchy, spacing, image behavior, usage examples, and rules for fixed and adaptive layouts.
CHECKConsider content length, responsive behavior, localization, image alternatives, and relevant accessibility requirements.
OWNERMaintained by the Pebble design-system team, with implementation links and contribution routes for design and engineering teams.
07 / Collaboration & adoption
From shared resources
to shipped products.
Pebble adoption grew through product delivery rather than a one-time handoff. As project owner, I coordinated design, front-end, and product teams to package reusable resources, apply them in Gattaran, measure adoption, and feed product needs back into the system.
PACKAGEBuild a practical starting point.
Basic components, Pro Components, page templates, development standards, and guidance gave teams reusable resources at different levels of complexity.
EMBEDApply the system in real delivery.
We introduced the system through the Gattaran homepage redesign and Gattaran CRM, using active product work to validate components, patterns, and documentation.
MEASURETrack scope, reach, and depth separately.
Within the Gattaran rollout, the basic component library was used in 15 projects and across 52 pages, representing 16.51% page coverage. Adoption reached 100% among newly initiated Gattaran projects; portfolio-wide adoption across all projects reached 50% within three months.
SUSTAINKeep the system connected to teams.
Designated system contacts and a user feedback group gave teams a route for questions, requests, and updates. Findings informed continued rollout in Gattaran and future co-creation of React components and best practices.
COLLABORATION MODEL
As project owner, I coordinated the roadmap and priorities across design, front-end, and product contributors. Real product delivery became the review mechanism: recurring needs were turned into shared resources, while implementation feedback informed subsequent iterations.
WHAT THE NUMBERS REVEALED
In the measured Gattaran rollout, 100% of newly initiated projects adopted the basic component library, while it appeared on 16.51% of pages. The gap showed that project-level adoption did not yet equal implementation depth—shaping the next rollout around deeper page coverage, richer reusable patterns, and ongoing team support.
08 / Outcomes & reflection
The system was measured
by what teams shipped.
50%
Portfolio-wide adoption in three months
Half of all projects across the three international product lines had adopted Pebble.
−10%
Average project duration
Average project duration decreased from the 2021 baseline of 65.78 person-days to 59.2 person-days.
| Evidence | What changed | Attribution / limit |
|---|
| Adoption / reach | Pebble reached 50% of all projects across Mobility, Food, and Finance within three months. | This is the portfolio-wide adoption rate. The separate 100% figure refers only to newly initiated Gattaran projects during the measured rollout—not the full project portfolio. |
| Team / delivery | Average project duration decreased by 10%, from 65.78 to 59.2 person-days. | Measured against the 2021 baseline. Reusable resources and clearer defaults may have reduced repeated design and implementation decisions; other delivery changes may also have contributed. |
Team confidence
| In an internal 1–5 benchmark where Ant Design / Element was anchored at 3, Pebble received a rating of 3.4 from designers and 3.3 from developers. | This was an early internal pulse, separate from measures of user outcomes. |
REFLECTION
I would keep the co-creation model and the distinction between project reach and page-level depth.
What I would change is to treat implementation, rollout, and measurement as part of the system from day one. I would develop the React components alongside the design resources earlier, assign clearer ownership for migration and maintenance, and define metrics for reach, depth, delivery efficiency, and interface quality before launch. I would also complement internal adoption data with direct evidence of consistency and user outcomes.
The project taught me that adoption is an early signal, not the finish line. A design system earns trust when it improves both what teams ship and how confidently they can maintain it.
Next / Complex product designRedesign of DIVE
Untangling complex business processes and translating them into clear, cohesive workflows.
↗