How can InVision enhance its prototyping tools to better support responsive design workflows?

Introduction

InVision's prototyping tools are crucial for designers creating responsive designs, but there's room for improvement in supporting these workflows. I'll analyze the current state, identify key pain points, and propose strategic enhancements to better serve our users and strengthen InVision's market position.

Step 1

Clarifying Questions (5 mins)

• Looking at InVision's product suite, I'm seeing a potential gap in seamless responsive design workflows. Could you share more about how our users typically approach responsive design tasks using our current tools?

Why it matters: Helps identify specific areas where our tools may fall short. Expected answer: Users often create multiple artboards for different screen sizes and struggle with consistency. Impact on approach: Would focus on streamlining the multi-device design process.

• Considering the evolving design landscape, I'm curious about our user base composition. What's the breakdown between individual designers, small teams, and enterprise clients using our prototyping tools?

Why it matters: Determines which user segments to prioritize in our improvements. Expected answer: Growing enterprise segment, but still a significant individual user base. Impact on approach: Would balance advanced features for teams with intuitive tools for individuals.

• Given the competitive nature of design tools, I'm wondering about our current market position. How do we currently stack up against competitors like Figma or Adobe XD in terms of responsive design capabilities?

Why it matters: Helps identify our unique selling points and areas for differentiation. Expected answer: Strong in collaboration, but lagging in some responsive design features. Impact on approach: Would focus on leveraging our collaboration strengths while closing feature gaps.

• Thinking about our product roadmap, I'm curious about our data on user engagement with responsive design features. What metrics are we currently tracking, and have we seen any significant trends?

Why it matters: Guides us in setting measurable goals for improvements. Expected answer: Tracking feature usage, but seeing lower engagement with responsive tools. Impact on approach: Would prioritize improving discoverability and usability of responsive features.