How might InVision refine its Design System Manager to streamline the process of creating and maintaining design libraries?

Introduction

InVision's Design System Manager is a crucial tool for design teams, but there's room for improvement in streamlining the creation and maintenance of design libraries. I'll analyze the current state, identify key pain points, and propose strategic solutions to enhance this product.

Step 1

Clarifying Questions (5 mins)

• Looking at the product context, I'm thinking about the primary use cases for the Design System Manager. Could you help me understand the most common workflows and user types interacting with this tool?

Why it matters: Determines which aspects of the tool to prioritize for improvement Expected answer: Primarily used by design teams for creating and managing design systems, with collaboration features for developers Impact on approach: Would focus on enhancing designer-developer collaboration and streamlining design system creation

• Considering user behavior, I'm curious about cross-platform usage patterns. How do users typically interact with the Design System Manager across different devices or platforms?

Why it matters: Influences decisions on feature parity and synchronization across platforms Expected answer: Mainly desktop-based usage, with some mobile access for viewing and minor edits Impact on approach: Would prioritize desktop experience while ensuring critical mobile functionality

• Regarding pain points and market position, where does InVision's Design System Manager stand in comparison to competitors like Figma's design system features?

Why it matters: Helps identify unique selling points and areas for differentiation Expected answer: Strong in collaboration but facing increased competition from integrated design tools Impact on approach: Would focus on enhancing unique collaborative features and integration capabilities

• Considering the product lifecycle, what stage is the Design System Manager currently in, and what key metrics are driving this improvement initiative?

Why it matters: Determines if we optimize for growth, retention, or feature expansion Expected answer: Mature product with a focus on user retention and feature enhancement Impact on approach: Would prioritize user satisfaction and advanced functionality over basic feature expansion