Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Pajamas Design System
Pajamas Design System
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 276
    • Issues 276
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 14
    • Merge Requests 14
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • gitlab-services
  • Pajamas Design SystemPajamas Design System
  • Issues
  • #733

Closed
Open
Opened Oct 16, 2020 by Jeremy Elder@jelderglMaintainer

UX Foundations > Pajamas OKR exploration

During a recent conference, Design Systems & DesignOps, one of the self-work times was dedicated to thinking through what OKRs could look like for your design system. We were given about 40 minutes total to complete a list and then discuss in a small group. These were a few that came to mind, and I found it very helpful to think through objectives specific to the system itself.

Feel free to add your own, and perhaps we can have further exploration on a few of these. All of the below ramp up to a larger objective of making the product more beautiful, performant and accessible for users, while providing clear foundational answers to common questions so that designers can focus on designing and not on rehashing what should be “boring” decisions. A reoccurring phrase from the workshop was “align the easy thing to do with the right thing to do,” which I think aligns with our goal of building foundational things for the team to build on.

Edited Oct 16, 2020 by Jeremy Elder
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab-services/design.gitlab.com#733