For Whatfix's in-app guidance tools, should we emphasize creating more pre-built walkthroughs or invest in better customization options for clients?

Introduction

The trade-off we're examining today is whether Whatfix should focus on creating more pre-built walkthroughs or invest in better customization options for clients using their in-app guidance tools. This decision is crucial for Whatfix's product strategy and will significantly impact user experience, client satisfaction, and resource allocation. I'll analyze this trade-off by considering various factors including user needs, technical feasibility, business impact, and long-term product vision.

Step 1

Clarifying Questions (3 minutes)

• Based on Whatfix's current market position, I'm thinking this decision might be driven by changing client needs or competitive pressures. Could you share more about what's prompting this consideration now?

Why it matters: Helps understand the urgency and strategic context of the decision. Expected answer: Increasing client requests for customization or a competitor offering more flexible solutions. Impact on approach: Would influence whether we prioritize short-term client satisfaction or long-term platform scalability.

• Considering Whatfix's revenue model, I assume there's a balance between standardization for efficiency and customization for premium pricing. How does our current pricing structure align with these options?

Why it matters: Informs the potential revenue impact of each direction. Expected answer: Tiered pricing with basic pre-built and premium custom options. Impact on approach: Would help determine if we should focus on upselling through customization or expanding the user base with more pre-built options.

• Looking at user behavior, I'm curious about the adoption rates of pre-built walkthroughs versus custom ones. Do we have data on which type tends to drive more engagement?

Why it matters: Indicates which approach currently provides more value to end-users. Expected answer: Higher engagement with custom walkthroughs, but broader usage of pre-built ones. Impact on approach: Would guide whether to focus on improving the quality of pre-built walkthroughs or making customization more accessible.

• From a technical perspective, I'm wondering about the current limitations of our customization capabilities. What are the main technical challenges we face in expanding customization options?

Why it matters: Helps assess the feasibility and resource requirements for enhancing customization. Expected answer: Challenges in maintaining performance with highly customized walkthroughs or integrating with diverse client systems. Impact on approach: Would influence whether to invest in technical infrastructure for customization or focus on optimizing pre-built solutions.

• Regarding our product team's capacity, I'm curious about the current split of resources between creating pre-built content and supporting customization. How are we currently allocated?

Why it matters: Indicates the potential for reallocation or the need for additional resources. Expected answer: Majority of resources focused on pre-built content with a smaller team supporting customization. Impact on approach: Would help determine if we need to hire or train for new skills or if we can reallocate existing resources.