Scribe Help Center Opportunity: Validate Demand, Scope an MVP and Plan a Roadmap

You work on the product team at Scribe, whose product turns a workflow someone performs on screen into a step-by-step guide. New user research shows that some customers are using Scribe to build help centers. How would you assess building complete, end-to-end help center functionality? Walk through the research, the feature scope and the roadmap, given a team of four engineers and one product designer. ### Clarifying Questions - Does "help center" here mean a public site for a company's own customers, an internal knowledge base for employees, or both? - Roughly how many accounts are doing this, and are they mostly on paid team or enterprise plans or on free plans? - Is the team of four engineers and one designer dedicated to this effort, or shared with work on the core product? - Is there a company goal this should serve, such as winning larger accounts, raising revenue per account, or reducing churn? ### Part 1 — Validate the opportunity What would you want to learn before committing the team, how would you learn it, and what evidence would make you proceed or stop? ```hint Ask why they stretch the tool Customers bending a guide-making tool into a help center are pointing at a gap. Find out what they combine with Scribe today, and whether the gap is on Scribe's side or in the help center tools they already use. ``` #### What This Part Should Cover - Who builds help centers with Scribe, which audience those help centers serve, and how much of the customer base and revenue they represent - Usage data, customer interviews and sales or support signals, each answering a different question - The alternatives customers already use and where Scribe could credibly win - Proceed and stop criteria agreed before the research starts ### Part 2 — Scope the product If the evidence supports building, what does end-to-end mean for this product, and what goes into the first release versus later? ```hint Map the workaround List every step these customers complete outside Scribe to get from a set of guides to a working help center, then ask which steps cost them the most time or push them toward another tool. ``` #### What This Part Should Cover - The full help center workflow broken into capabilities - A prioritization method that weighs customer value against what five people can build - A clear first-release scope, with reasons for what is excluded - Which capabilities to build and which to deliver through integrations ### Part 3 — Plan the roadmap Lay out a roadmap for four engineers and one product designer. How would you sequence the work, and how would you decide at each stage whether to keep going? ```hint Plan around the designer One designer supports four engineers. Think about which work needs design before engineering can start, and which work engineers can do in parallel. ``` #### What This Part Should Cover - Phases defined by what each one must prove, not only by the features shipped - Sequencing that reflects the team's size, including the single designer - Metrics and a decision point for each phase - The effect on Scribe's existing product and roadmap ### What a Strong Answer Covers - Treating the build as an open decision, with a real option to integrate with existing tools or not build at all - Fit with Scribe's core strength in creating guides, and the risk of pulling focus from the core product - Consistent use of the team constraint from scoping through sequencing - Metrics that connect help center adoption to business results such as retention, expansion or new customers - Risks such as competing with established help center tools and the added burden of hosting public sites ### Follow-up Questions - The research shows most of these customers already pay for a help center tool and mainly want Scribe guides to appear inside it. How does your plan change? - Leadership asks for a launch much earlier than your roadmap allows. What do you cut, and what do you refuse to cut? - How would you package help center functionality: include it in existing plans, sell it as an add-on, or reserve it for a higher tier?