Contributing to the Pharos design system

pharos mantra text

Problem & Goals

  • What challenges did the absence of a dedicated team create?

  • What did you aim to solve or maintain (e.g., consistency, scalability, adoption)?

  • Any relevant KPIs or success indicators (if available).

Approach & Strategy

  • How you embedded system work into existing team sprints.

  • Methods used to prioritize design system tasks.

  • How you balanced cross-functional needs (e.g., design, engineering, product).

  • Communication and alignment strategies across teams.

Collaboration and Execution

  • Key tasks you completed: component maintenance, documentation, tokens, versioning, etc.

  • Examples of improvements, additions, or refactors.

  • Integration with dev workflows or design libraries (e.g., Storybook, Figma).

  • Screenshots, diagrams, or before/after comparisons.

Outcomes & Impact

  • Measurable improvements (e.g., component usage, reduced inconsistencies).

  • Adoption or contribution rates.

  • Time saved for teams, improved handoff quality, or other wins.

Challenges & Learnings

  • What was hard about doing this solo or ad hoc?

  • How did you handle prioritization without a clear backlog?

  • What would you do differently next time?

TLDR

  • Recap the value of this work.

  • Call out how it influenced broader design culture or product velocity.

  • Optional: what’s next for the system?

Next
Next

Expanding business reach with a new website