How can Poly balance the desire for sleek, minimalist design in its desk phones with the need for physical buttons preferred by some enterprise customers?

Introduction

The challenge at hand is balancing Poly's desire for sleek, minimalist design in desk phones with the need for physical buttons preferred by some enterprise customers. This scenario highlights a classic product trade-off between aesthetic appeal and functional familiarity. I'll analyze this situation through the lens of user experience, business impact, and technical feasibility to provide a strategic recommendation.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming Poly has a mix of consumer and enterprise customers. Could you clarify the revenue split between these segments and how it impacts our product strategy?

Why it matters: Helps prioritize design decisions based on revenue impact Expected answer: 70% enterprise, 30% consumer Impact on approach: Would focus on enterprise needs while balancing consumer appeal

• Business Context: Based on market trends, I'm thinking voice communication might be declining in some sectors. How does this product line align with Poly's long-term growth strategy?

Why it matters: Informs investment level and innovation approach Expected answer: Still core business, but shifting towards integrated communication solutions Impact on approach: Would consider modularity and integration capabilities in design

• User Impact: Considering the shift to remote work, I'm curious about changing user behaviors. How has the usage of desk phones evolved in our enterprise customer base over the past two years?

Why it matters: Helps identify key features and use cases to prioritize Expected answer: Decreased overall usage, but increased importance for specific roles Impact on approach: Would focus on power users and their specific needs

• Technical: Given the trend towards software-defined features, I'm wondering about our current technical architecture. How flexible is our current platform for adding software-based functionality to complement physical buttons?

Why it matters: Determines feasibility of hybrid solutions Expected answer: Moderately flexible, but requires significant investment Impact on approach: Would explore phased approach, balancing hardware and software solutions

• Resource: Considering the potential scope of this project, I'm thinking about team capacity. What resources do we have available for design, development, and user research in the next 6-12 months?

Why it matters: Helps scope the project realistically Expected answer: Limited resources due to other priorities Impact on approach: Would prioritize high-impact, low-resource solutions initially