5 min read • Guide 647 of 877
How to Use GitScrum for Product Discovery?
How to use GitScrum for product discovery?
Manage product discovery in GitScrum with research tasks, hypothesis tracking, and insight documentation in NoteVault. Coordinate user interviews, prototype testing, and assumption validation. Discovery teams with structured workflow build 50% more relevant features [Source: Product Discovery Research 2024].
Discovery workflow:
- Opportunities - Identify problems
- Research - Understand users
- Hypotheses - Assumptions to test
- Validation - Test assumptions
- Insights - Document learnings
- Solutions - Design options
- Handoff - To delivery
Discovery labels
| Label | Purpose |
|---|---|
| type-discovery | Discovery work |
| discovery-research | User research |
| discovery-hypothesis | Assumption |
| discovery-validated | Confirmed |
| discovery-invalidated | Disproved |
| discovery-insight | Key learning |
| discovery-opportunity | Problem space |
Discovery columns
| Column | Purpose |
|---|---|
| Opportunities | Problems to explore |
| Research | Active research |
| Hypotheses | Assumptions to test |
| Validation | Testing underway |
| Insights | Learnings captured |
| To Delivery | Ready for build |
NoteVault discovery docs
| Document | Content |
|---|---|
| Opportunity tree | Problems and solutions |
| Research repository | All studies |
| Insight library | Key learnings |
| Assumption tracker | Validated/invalidated |
| Interview notes | User conversations |
Research task template
## Research: [topic]
### Objective
[What we want to learn]
### Method
- Type: [interviews/survey/analytics]
- Participants: [who]
- Duration: [timeframe]
### Questions
1. [Question 1]
2. [Question 2]
3. [Question 3]
### Insights
- [Insight 1]
- [Insight 2]
### Recommendations
[What to do with findings]
### Artifacts
- [Link to notes]
- [Link to recordings]
Hypothesis task template
## Hypothesis: [statement]
### Assumption
We believe [users] have [problem] because [reason].
### Test Method
We will validate by [approach].
### Success Criteria
- Validated if: [criteria]
- Invalidated if: [criteria]
### Test Results
- Finding: [observation]
- Confidence: [high/medium/low]
### Outcome
[ ] Validated - proceed
[ ] Invalidated - pivot
[ ] Need more data
User interview task
## Interview: [participant]
### Background
- Role: [description]
- Segment: [category]
- Date: [date]
### Topics Covered
- [Topic 1]
- [Topic 2]
### Key Quotes
> "[Quote 1]"
> "[Quote 2]"
### Insights
- [Insight 1]
- [Insight 2]
### Follow-up
[Actions from this interview]
Opportunity tree structure
| Level | Content |
|---|---|
| Outcome | Business goal |
| Opportunity | User problem |
| Solution | Possible approach |
| Experiment | How to test |
Discovery methods
| Method | When to Use |
|---|---|
| User interviews | Deep understanding |
| Surveys | Quantitative data |
| Analytics | Behavior patterns |
| Prototype tests | Solution validation |
| A/B tests | Optimization |
Insight categorization
| Theme | Examples |
|---|---|
| Pain points | Frustrations |
| Workarounds | Current solutions |
| Goals | What users want |
| Behaviors | What users do |
| Motivations | Why they act |
Discovery to delivery handoff
| Discovery Output | Delivery Input |
|---|---|
| Validated problem | User story |
| Tested solution | Feature spec |
| User insights | Acceptance criteria |
| Success metrics | Definition of done |
Discovery metrics
| Metric | Track |
|---|---|
| Research velocity | Studies per month |
| Validation rate | % assumptions tested |
| Insight generation | Insights per study |
| Delivery connection | % linked to backlog |
Common discovery issues
| Issue | Solution |
|---|---|
| No user access | Regular recruiting |
| Assumptions untested | Validation tracking |
| Insights forgotten | NoteVault repository |
| Disconnect to delivery | Linking system |