Skip to content

Latest commit

 

History

History
98 lines (85 loc) · 3.3 KB

VISION.md

File metadata and controls

98 lines (85 loc) · 3.3 KB
Raw

Lyne Design System — Vision

What Lyne is and why we need it

The Lyne Design System is a holistic approach towards a consistent, maintainable, cross-company design language for all SBB digital products/services for a better common understanding between stakeholders, designers and developers.

What Lyne consists of

The Lyne Design System is based on an intuitive, unique — the Single Source of Truth — referential resource, including shared and well-documented guidelines, processes and vocabulary, design decisions (so-called Design Tokens), as well as centralized, vendor and framework-agnostic basic building blocks (Lyne Components).

What Lyne does

The Lyne Design System not only enables an optimized collaboration and integration workflow between the Lyne team and consumers of Lyne Design System but also accelerates the creation and development process (time to market) in a sustainable, maintainable, and long-term committed fashion.

Lyne's advantages and the resulting (→) chances

  • One language/terminology →
    • Better understanding
    • Clearer communication
    • Cross-company design language
    • Reducing the knowledge gap
    • Iterating faster
  • Single Source of Truth (SSoT) →
    • Central knowledge collection
    • Easy onboarding
    • Empowerment
    • Reducing the knowledge gap
  • Efficient & optimized collaboration →
    • Team member happiness (PO, UX, DevOps, Frontend, Backend)
    • Developer Experience of (component) consumers
    • Clear feedback/Review mechanisms
    • Iterating faster
  • Makes things easier →
    • Team member happiness (PO, UX, DevOps, Frontend, Backend)
  • Consolidation →
    • Optimized patterns
    • Optimized code
  • Consistency →
    • Consistent design within the SBB → One SBB
    • User Experience
    • Design cohesiveness
  • Modular/flexible →
    • Maintainability
  • Reusable →
    • Faster implementation of projects (time to market)
    • Cross-platform usage and re-usability
  • Technology/tool agnostic →
    • Exchangeable
    • Allows growth
    • No vendor lock-in
    • Faster implementation of projects (time to market)
  • Well tested →
    • Better QA
  • Accessible →
    • Built-in accessibility on module level
  • Measurable →
    • Data-driven decisions
  • Long-term focus →
    • Sustainability
    • Commitment

Potential which could be unlocked thanks to Lyne

  • Better understanding
  • Clearer communication
  • Cross-company design language
  • Iterating faster
  • Central knowledge collection
  • Easy on-boarding
  • Empowerment
  • Reducing the knowledge gap
  • Team member happiness (PO, UX, DevOps, Frontend, Backend)
  • Developer Experience (DX) of (component) consumers
  • Optimized patterns/code through consolidation
  • Cross-platform usage and re-usability
  • Clear feedback/review mechanisms
  • Consistent design throughout the SBB → One SBB
  • Maintainability
  • Faster implementation of projects (time to market)
  • Allows growth
  • No vendor lock in
  • Better QA
  • Built-in a11y on component level for everybody
  • Data-driven decisions
  • Sustainability
  • Commitment

Risks

General risks of a Design System that we always need to face and be aware of:

  • Single Point of Failure (SPoF)
  • Fear of harming the designers' creativity
  • Governance difficulties
    • Design System rejection/denial
    • Missing adoption
  • Documentation — if not well enough documented
  • Funding difficulties