Topic · Legacy collection

Future Builder

Turn a future goal into assumptions, controllable next moves, and review points you can actually revisit.

Three people choosing one action, pausing to try it, and recording an observation

New ontology

This stable legacy collection now maps to the topic Goals.

Library

50

Total entries in this Growth Zone.

Trusted feed

9

1 reviewed · 8 practical.

Review queue

41

41 pending · 0 restricted.

Life Area: Focus & Execution.

Topics: Goals (50)

Research gaps: none from the current 24-topic baseline are mapped to this zone.

Machine-readable zone record →

Start with trusted protocols

These entries currently meet Brali's reviewed/practical retrieval bar. “Trusted” is a publication state, not a promise that every protocol has equal scientific support.

  • Ask Why Until a Goal Becomes ClearerWrite one goal or problem, ask why it matters, and continue asking why while each answer adds something useful. Stop when the answers become repetitive, speculative, or split into different causes. Then choose one next step or one assumption to check.practical
  • Choose Up to Three Priority Outcomes for the DayReview today's deadlines, dependencies, and available capacity; choose up to three outcomes that most deserve progress; define what done means for each; reserve appropriate time where possible; place other tasks in a visible backlog; and re-plan explicitly when genuinely urgent work changes the day.practical
  • Goal Journal ReviewAfter a meaningful work session or at a regular review point, write four short lines: what I intended, what happened, what helped or blocked me, and what I will change next.practical
  • Run a Weekly Review That Produces One Clear ChangeReview the active goals and commitments, note what moved and what did not, identify the main constraint or changed assumption, decide what should continue, stop, shrink, delegate, or move, and schedule the first concrete action created by the review.practical
  • Use 80/20 as a Prioritization HypothesisDefine one outcome, list the inputs that could influence it, rank a small number by expected impact and cost, choose one to check, and compare the observed result with your initial ranking. Revise the ranking when the data disagrees.practical
  • Use a Short Pause Before an Ordinary DecisionName the decision in one sentence. Take a few comfortable breaths or use a quiet pause; seven is only a memorable optional count. Ask what is known, what is missing, and whether the choice is reversible. Then act, gather one specific piece of information, or set a deliberate time to revisit it.practical
  • Use a Stretch-Goal Sprint to Expose What Must ChangeWrite one desired outcome and the constraints around it. List the levers you can actually change, choose one reversible experiment, define what you will observe, run the smallest useful version, and review whether the result changes your plan.practical
  • Use WOOP to Turn a Wish Into an If-Then PlanChoose one meaningful and reasonably feasible wish. Describe the outcome you want, identify an internal obstacle that could derail you, then write: If I notice this obstacle, then I will take this specific action. Try the plan in real life and revise it if the cue or response is not useful.reviewed
  • Work in Focused 25-Minute Intervals (pomodoros) Followed by a 5-Minute BreakPick one concrete outcome, work on it for one 25-minute focus block, take a short break, and then decide whether another block is useful. Treat 25 minutes as a starting setting, not a scientifically optimal duration.practical

50 library entries

Full archive below. Evidence states differ; use the trusted list above for normal retrieval and recommendation.