The Stride Framework
Stride is a delivery-centric framework designed to eliminate jargon and align teams around an outcome-focused model of work. Whether you're learning Stride for the first time or looking up specific concepts, this documentation has you covered.
Core Philosophy
Stride emerged from a simple frustration: most Agile frameworks prioritise process over progress. They introduce jargon, ceremonies, and overhead that obscure what actually matters—delivering value to users. Stride strips away the complexity to focus on what teams actually need.
Clarity over Complexity
Plain language everyone understands. No sprints, story points, or velocity—just work organised at four clear levels.
Outcomes over Outputs
Focus on user value, not feature counts. Every piece of work connects to something users will actually benefit from.
Visibility over Process
Progress should be obvious to everyone. When work completes, it rolls up naturally through the hierarchy.
Pragmatism over Perfection
Ship working solutions, iterate based on feedback. Perfect plans don't survive contact with reality anyway.
The Four-Level Hierarchy
Every piece of work in Stride fits into one of four levels. This structure ensures that business needs flow through functional design into technical implementation.
Release
Delivery target
Outcome
What user can achieve
User Action
User Action
Task
Task
Task
Task
Level 1: Releases
Delivery targets that contain the Outcomes to be delivered. Releases provide the strategic view of what's shipping and when.
Level 2: Outcomes
What the user can achieve using the system. Driven by user and business needs. Functional Designers take Outcomes and create User Actions.
Level 3: User Actions
The actual things the user does in the system to achieve Outcomes. Created by Functional Designers. Developers take User Actions and create Tasks.
Level 4: Tasks
Implementation work that Developers do to build User Actions into the system. When all Tasks complete, the User Action is complete.
The Flow of Work
Work flows downward through design and upward through completion.
Downward: Design Flow
Upward: Completion Flow
Getting Started
You don't need to plan everything upfront. Stride is designed to let you start simple and add structure as you need it.
Your First Stride Project
Create a Release
Define your next major milestone. This could be a quarterly goal, a product version, or simply “First Launch”.
Define 3-5 Outcomes
What user value will this release deliver? Write outcomes as user capabilities: “Users can...” Focus on what they'll achieve.
Break Down into User Actions
For each Outcome, list the specific things users will do in the system. These become the bridge to development.
Create Tasks and Start Working
Developers create Tasks for each User Action. Assign, track progress, and watch completion roll up naturally.
Quick Reference
Ready to start with Stride?
Dive deeper into the framework or start building with the Stride platform.