Goals That Actually Finish (SMART, Without the Acronym)

Most goals fail at the moment they are written, not the moment they are attempted. "Improve the guest experience" cannot fail - and that is exactly what is wrong with it. Nothing that cannot fail can finish.

The old cure is the SMART acronym. The acronym is forgettable; the five questions underneath it are not:

The five questions

1. What exactly? One sentence describing the world when this is done. Not "work on the rancho" but "the rancho hosts its first paid event". If the sentence will not come, the goal is not ready - which is useful to know now.
2. How will we know? Point at something visible: a signed document, an open gate, money received, a family moved in. If knowing requires asking how everyone feels, you have a hope, not a goal.
3. Who owns it? One name. Owners can change; "everyone" cannot be asked how it is going.
4. Can we really? Honest dates and an honest budget envelope. Ambition is welcome - dishonesty about capacity is how teams burn out politely.
5. By when? A target date, even a rough one. Dates draw the goal onto the Roadmap where drift is visible early, while it is still cheap to fix.

How the hub holds this

A goal is a Project record: its "done means" sentence in the description, its owner as Lead, its dates on the Roadmap, its budget envelope set once. The concrete steps are Tasks underneath - each physical, each owned. From there the system keeps score: quotes and payments roll up into the budget line, blocked steps surface themselves, and the weekly status email reports position from the records with no compiling.

Ask Sera to pressure-test any goal: "is this goal specific enough?" - she will run the five questions with you, kindly.

The regenerative footnote

Goal discipline is usually sold as a productivity trick. Here it is a care practice: honest dates protect people's rest, one-name ownership protects people from vague accountability, and a visible "done means" protects the team from projects that quietly never end. The portfolio view across sectors shows whether the community's energy is feeding all of its life, or only the loudest part.

Key points

A goal needs: a specific outcome (one sentence of what done means), a way to know it happened (visible in the world, not in a feeling), one accountable owner, honest reach (resources and dates you actually believe), and a deadline that draws it on the Roadmap. Vague goals hide in verbs like "improve", "explore", "support" - the fix is asking "what would we point at to prove it happened?". Goals live as Projects; the concrete steps live as Tasks under them. The system keeps score automatically: dates draw the timeline, quotes and payments fill the budget line, and the weekly email reports position without anyone compiling it.