Core Concepts

Joyous is built around four core concepts that work together to turn ambitious goals into completed work. Understanding how they fit together will help you get the most out of the platform from day one.

Outcomes

An outcome is a goal you want to achieve — not a task to complete, but a result to deliver. Every outcome has a goal that describes what success looks like, optional success signals that define measurable criteria, and directives that provide guidance and constraints for the work.

Think of an outcome as "Launch the mobile app by September" or "Reduce customer onboarding time to under 3 minutes." Outcomes keep your team focused on why the work matters, not just what needs to get done.

Outcomes can also be nested — a parent outcome like "Ship Q3 product roadmap" can contain child outcomes like "Launch mobile app" and "Revamp onboarding flow," giving you a natural hierarchy for tracking progress at multiple levels.

Work Cards

A work card is the atomic unit of work in Joyous. Each card represents a single task or deliverable and belongs to an outcome. Cards have a goal field describing what needs to happen, and can include rich document content, assignees, effort estimates, and constraints.

Every work card moves through a status lifecycle:

• Backlog — identified but not yet planned
• Committed — planned and ready to work on
• Blocked — waiting on a dependency or decision
• Done — completed
• Archived — no longer relevant

Cards connect upward to outcomes, giving you a clear line of sight from individual tasks to organizational goals. You can create cards manually, inline within an outcome, or let the AI agent generate them for you.

Teams

Teams are how you organize people in Joyous. Each team groups members who collaborate on shared outcomes — like "Engineering," "Marketing," or "Product." Teams own outcomes, and their members are the people who do the work.

Every team member has a profile with skills across four levels — Mastered, Capable, Developing, and Growth Interest — along with capacity settings for hours per week and current allocation percentage. This helps you understand who's available and what they're strongest at when planning work.

Teams appear in the sidebar for quick navigation, and you can scope views to show only a specific team's outcomes and cards.

Sprints

A sprint is a time-boxed execution cycle with a start date, end date, and a set of committed work cards. Sprints move through three phases:

• Planning — select and commit cards from your backlog
• Active — the sprint is underway and the team is executing
• Closed — the sprint is complete, providing a snapshot of what was accomplished

Sprints give your work a rhythm. Instead of an open-ended backlog, you commit to a focused set of cards for a defined period — typically one or two weeks — and track how much gets done.

How it all fits together

The hierarchy flows naturally:

Teams → own Outcomes → contain Work Cards → are executed in Sprints

A team like "Product Engineering" creates an outcome like "Launch v2.0 by Q3." That outcome gets decomposed into work cards like "Build new dashboard," "Migrate user data," and "Write API documentation." Those cards are committed to a two-week sprint, and the team tracks progress as cards move from Committed to Done.

This structure means every piece of work traces back to a goal, every goal belongs to a team, and every sprint drives measurable progress. No orphaned tasks. No goals without accountability.

Next Steps

• Your First Outcome — A hands-on tutorial walking through the full workflow
• Outcomes — Deep dive into creating and managing outcomes
• Work Cards — Learn about the full work card lifecycle
• Sprints — Set up time-boxed execution cycles
• Teams & Members — Organize your people into teams