Tasks & Stories is where you convert insights and research into actionable development work with user stories and task management, ensuring your development efforts are grounded in validated user needs and research findings.
What are Tasks & Stories?
Tasks & Stories encompasses the development planning and execution tracking features:
Tasks: Individual pieces of work that need to be completed, from development tasks to research activities and project management items.
User Stories: Tasks written from the user's perspective that connect development work to specific Insights, ensuring features solve real user problems.
This feature helps you bridge the gap between research insights and actual development work, maintaining traceability from user needs through to delivered features.
How to Access Tasks & Stories
Navigate to Tasks & Stories from the main sidebar by clicking Tasks & Stories.
Tasks Section
Task Structure and States
Task Data Structure
Each task contains:
Title & Description: Clear description of what needs to be done
Task State: Current status (Backlog, Ready, In Progress, Completed)
External Integration: Links to development tools like Jira, Linear, or GitHub
Task States
Backlog: Tasks that haven't been triaged or planned yet
Ready: Tasks that are planned and ready to be worked on
In Progress: Tasks currently being worked on
Completed: Completed tasks
Creating Tasks & Stories
Creating Development Tasks and User Stories
Create Development Tasks
Plan and track development work
Option 1: Click Create Task and write a title and description
Option 2: Click Create User Story in an Insight card to use a Spell
User Story Best Practices
A user story is a task written from the user's perspective that connects development work to specific Insights, ensuring features solve real user problems.
Reference Personas: Use specific personas rather than generic "user"
Link to Assumptions: Connect stories to validated beliefs about user needs
Define Success: Include measurable acceptance criteria
Example User Story Structure:
Story: As Maria (busy marketing manager persona), I want to quickly analyze campaign performance so that I can make data-driven optimization decisions during my limited review time.
Research Link: Based on Interview findings about time constraints and Data & Insights about decision-making patterns
Acceptance Criteria: Performance dashboard loads in under 2 seconds, key metrics visible without scrolling, one-click drill-down to details
Tasks & Stories in the Product Management Process
Research-to-Development Pipeline
Tasks & Stories complete the research-to-development cycle:
Market Research: Identify market opportunities and user segments
Break large features into smaller tasks that deliver incremental user value.
6. Review and Refine
Regularly review completed tasks to learn what worked and improve future planning.
7. Collaborate with Context
Share the research context behind tasks so the whole team understands the "why."
Tasks & Stories Success
The most effective development planning combines systematic user research with agile development practices. Use research insights to guide what to build, and user stories to ensure development work delivers real user value.
Integration with Other Platform Features
Validation Activities
Data & Insights: Use research findings to justify and prioritize development work
Interviews: Reference user conversations when writing user stories and acceptance criteria
Workflow Examples
Research-Driven Feature Development
Identify Need: Review Data & Insights to find validated user problems
Select Persona: Choose specific user segment this feature will serve
Write User Story: Create story linking feature to persona needs and research
Define Acceptance: Set criteria based on user success metrics from research
Estimate & Prioritize: Use research confidence and user impact to set priority
Develop & Test: Build feature and validate with target Persona
Problem-Solution Validation Cycle
Problem Discovery: Conduct Interviews to identify user problems
Document Assumptions: Write beliefs about solution approaches
Create Validation Tasks: Plan tasks to test solution concepts with users
Build & Test: Develop minimal solutions and gather user feedback
Generate Data & Insights: Process feedback into actionable learnings
Iterate Tasks: Refine tasks based on validation results
Scale Solution: Expand successful solutions into full features
Sprint Planning with Research Context
Review Research: Start planning with latest Data & Insights and user feedback
Assess Assumptions: Identify which beliefs need testing through development
Select User Stories: Choose stories that serve validated Persona needs
Plan Validation: Include tasks for testing assumptions during development
Execute Sprint: Build features while gathering user feedback
Review & Learn: Use sprint results to update research and plan next iteration
Tasks Section
Tasks Board