Core concepts
Understand how goals, requests, and delivery work fit together.
FortyOne works best when each layer answers a different question. You do not need to use every layer on day one.
| Concept | The question it answers | Usually contains |
|---|---|---|
| Strategy | Where are we going? | An ultimate goal and strategic pillars |
| Objective | What outcome are we pursuing? | Owner, health, dates, and key results |
| Key result | How will we know it worked? | A measurable target and current progress |
| Roadmap | What are we likely to deliver, and when? | Priorities linked to objectives and work |
| Feedback | What needs attention from the team? | Requests, votes, comments, and status |
| Team | Who owns this part of the work? | Members, workflow, labels, and team settings |
| Work item | What needs to happen next? | Owner, status, priority, estimate, dates, and links |
| Sprint | What are we committing to now? | A time-boxed set of team work |
A simple workflow
- Capture a request, customer signal, field update, or internal need.
- Connect it to the objective, program, or roadmap priority it supports.
- Break the decision into owned work with clear estimates.
- Schedule focused work when timing matters.
- Use progress and delivery signals to update the roadmap and stakeholders.
The links are useful, but optional. A small team can begin with teams and work items, then add objectives, feedback, scheduling, and integrations as the need becomes real.