How can Salsify balance the simplicity of its Digital Shelf Analytics dashboard for new users against the depth of insights demanded by experienced brand managers?

Introduction

Balancing simplicity and depth in Salsify's Digital Shelf Analytics dashboard presents a classic product trade-off. We need to create an intuitive experience for new users while providing the comprehensive insights that experienced brand managers require. I'll outline my approach to addressing this challenge, focusing on user segmentation, feature prioritization, and iterative design.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm assuming Salsify is seeing a mix of new and experienced users. Could you confirm if there's a specific ratio of new to experienced users we're dealing with?

Why it matters: Helps determine the weight we should give to each user group's needs. Expected answer: 60% new users, 40% experienced users. Impact on approach: A higher percentage of new users might prioritize simplicity initially.

• Business Context: Based on Salsify's business model, I'm thinking this dashboard is a core revenue driver. How critical is it to our overall revenue and retention strategy?

Why it matters: Helps prioritize this initiative against other business objectives. Expected answer: It's a key differentiator and directly impacts our main revenue stream. Impact on approach: High priority would justify more resources and a faster timeline.

• User Impact: I'm assuming experienced brand managers are our highest-value customers. Can you confirm if they're more likely to churn if their needs aren't met?

Why it matters: Influences how we balance simplicity vs. depth. Expected answer: Yes, experienced users have higher lifetime value and are more sensitive to product changes. Impact on approach: We might need to focus on progressive disclosure of advanced features.

• Technical: Given the complexity of e-commerce data, I'm wondering about our current data processing capabilities. Are there any technical limitations to providing real-time, in-depth analytics?

Why it matters: Affects the feasibility of certain advanced features. Expected answer: We have some limitations but are working on improving our data infrastructure. Impact on approach: Might need to phase in more complex features as our capabilities improve.

• Timeline: Considering the competitive landscape, how urgent is this redesign? Are we looking at a quick win or a longer-term overhaul?

Why it matters: Influences the scope and approach of our solution. Expected answer: We need some improvements in the next quarter, but have flexibility for a longer-term strategy. Impact on approach: Could suggest a phased approach, starting with high-impact, low-effort changes.