The Backbeat Framework

v1.0

Component Hierarchy

Area
├── Goal — outcome-focused, time-bound
│   ├── Signal(s) — measures progress + drives action
│   └── Project(s) — defines the work
│       └── Milestone(s) — key checkpoints within a project
│
└── Practice — process-focused, ongoing
    ├── Signal(s) — measures consistency
    └── Project(s) — supports the practice (optional)
        └── Milestone(s)

Goals and Practices sit at the same level within an Area. Signals and Projects can attach to either.

Component Definitions

Area What deserves deliberate attention right now. Not everything that matters to you, just what you're actively choosing to focus on this season. Priorities shift. Review annually or quarterly.

Goal A specific, time-bound outcome describing a change. Should be STAR: Specific, Time-bound, Achievable, Relevant. Measurability lives in your Signals, not the goal itself.

Practice An ongoing discipline you maintain because something needs to stay, not change. No end date. Sometimes you elevate a regular habit to an explicit Practice for a season to build it up intentionally.

Signal A quantifiable indicator of direction. (You may know these as KPIs… same idea, less corporate baggage.) One to four per Goal or Practice. Must be a gauge, not a switch. If it can only tell you whether you arrived, it can't tell you whether you're on track. Favour counts, rates, and percentages over boolean yes/no.

Project The work required to reach a Goal or sustain a Practice. Projects define the how and are expected to shift. A Goal can outlive multiple Projects. Progress is tracked through Milestones.

Milestone A binary checkpoint within a Project: done or not done. Should represent roughly comparable effort so progress stays visible throughout, not just at the end.

For the story behind this framework: Next thing you know, I'm running my life like it's a Fortune 500 company →

Worked example: Backbeat Team Goal Example →

Wil Arndt