Primary metric examples (pick one)
- Words written (count)
- Hours practiced (minutes)
- Dollars earned (USD)
- Units built (count)
Future Builder · Growth Library
Set BHAGs (Big Hairy Audacious Goals)

This migrated article contains evidence-like wording without a reviewed supporting source. The long-form article remains visible for readers, while those claims stay outside trusted recommendations until they are reviewed or rewritten.
Evidence: Evidence-like claims detected; source review pending.
Trust boundary: Visible does not mean reviewed. This article is not eligible for Brali's trusted recommendation feed or usable Agent Skills until its review state is promoted.
We begin with a practical assertion: a Big Hairy Audacious Goal (BHAG) is less a one‑time declaration and more a disciplined process of translation — from a wild idea to daily decisions that add up. We are not promising instant transformation. Instead, we invite a steady practice: one that clarifies what matters, sets measurable mileposts, and creates a feedback loop of learning. Our aim in this long read is to move you from curiosity to a first concrete BHAG draft today, then to a week of disciplined testing.
The BHAG idea comes from management and design thinking in the late 20th century, notably from Jim Collins and business strategists who wanted goals that inspire beyond standard KPIs. Common traps: we pick shiny, vague targets (increase revenue, “get fit”) without context; we ignore constraints (time, money, social support); we confuse wishful thinking with commitment. Most BHAGs fail because the early hookups to daily habits are weak — a big claim has no small, repeatable actions underneath. When outcomes do change, it’s usually because people set intermediate targets, measured weekly, and adapted within 2–8 weeks.
We will move through practice, not lecture. Each section is written as a thinking-out-loud walk where we make a small decision, test it, and adjust. If we want to finish with a BHAG we can actually start living, we must break it into measurable pieces, choose the trade-offs we can live with, and schedule a few immediate actions. We assumed that a single, grand launch would motivate follow-through → observed that motivation spikes fade within 3–10 days → changed to an incremental launch model: daily micro‑wins + weekly reflection.
Part 1 — The BHAG mindset: Why being audacious matters and how to avoid grandiose errors
We start with a small experiment: close your eyes for ten seconds and picture a future where one big constraint is removed — money, time, or fear. Notice the shape of what you imagine. That image is the raw material of a BHAG: it has emotion, scale, and an anchor to identity. The audacity here matters because it pulls decision energy; it makes some trade-offs inevitable. A bold goal forces a choice: we either rearrange life around it, or we let it remain a pleasant fiction.
Action now (≤10 minutes)
Why audacity helps: it clarifies identity If we choose a large, clear target, we have a north star for decisions. For example, deciding to “publish a technical book with 50,000 words in 18 months” immediately clarifies daily writing targets: about 92 words per day if we wrote every day, but practically 500–700 words on writing days. Those numbers convert dream into behavior.
Why audacity can hurt: three errors to avoid
We choose to value clarity over optimism and specificity over rhetoric. That choice requires small, measurable constraints: minutes, counts, money. Those constraints are not limitations — they are tools.
Part 2 — The anatomy of a good BHAG: elements and measurable anchors
We like to translate the BHAG into five parts. Each part should be concrete, and each should yield at least one number to measure.
Action now (15–30 minutes)
We want "publish a nonfiction book of 60,000 words on sustainable urban design by Dec 31, 2027." Breakdown:
We choose a weekly word target: 60,000 words / 130 weeks ≈ 462 words/week. That’s small, but we commit to at least three dedicated writing sessions of 90 minutes per week — a realignment of time.
Part 3 — From BHAG to habit: micro‑tasks and schedule
A BHAG without a schedule is a wish. We translate the outcome into weekly and then daily habits. This is where the BHAG meets life’s friction: small children, a demanding job, or tight budgets.
Trade‑off decision: intensity vs consistency We can try two models:
We assumed that sprinting would be faster → observed cancellations reduce momentum → changed to a mixed model: one 2-hour focused session + three 30–45 minute micro-sessions weekly. The mixed model gives us 1×120 + 3×40 = 240 minutes = 4 hours/week.
Action now (15–60 minutes)
Part 4 — Milestones, metrics, and adaptive learning
We track at least one primary metric and one secondary contextual metric. The primary metric is usually quantifiable output; the secondary is a process metric or well‑being indicator.
Concrete numbers reduce wishful arithmetic. If our primary metric is words, target a weekly range: 400–1,200 words (lower bound sustains continuity; upper bound signals stretch). If our primary metric is hours, target 120–240 minutes/week.
We recommend quarterly milestones. For a 60,000-word book in 30 months, set milestones every 3 months: 60,000 / 10 = 6,000 words per quarter. Each quarter becomes a test: did our structure deliver 6,000 words? If not, we diagnose and adapt.
Adaptive learning loop (2–3 decisions per week)
We will return to the mechanics of check‑ins later, but here’s a key rule: change one variable at a time (time of day, session length, environment), and test that change for two weeks. This avoids chasing every silver-bullet technique.
Part 5 — Crafting a BHAG statement that compels action
A BHAG statement should be bold, clear, and anchored to a next action. Follow this simple formula:
[Outcome] + [scale] + [deadline] + [one signature action]
Example: “We will publish a 60,000‑word book on sustainable urban design by 2027‑12‑31. To get there, we will complete one 120‑minute focused writing session and three 40‑minute micro sessions every week.”
Write the statement, then underline the signature action in your own tracker as the first task. The sentence itself becomes a contract with our future self.
Part 6 — Identity leverage: small rituals that change what we do
Behavior change is easiest when it’s a function of identity. We shift from “I’ll try” to “I’m the kind of person who.” Rituals create that identity micro-shift.
Examples of rituals (choose 1–3)
We pick rituals that cost little time but create a clear start/stop signal. The cost of a ritual is usually 2–5 minutes; the benefit is increased consistency by an estimated 20–40% in our experience.
Part 7 — Social scaffolding: how to build accountability without pressure
We are social animals. A BHAG that lives in isolation is fragile. Accountability doesn’t need to be public exhibition; it needs to be predictable and slightly uncomfortable.
Options:
Trade‑off: privacy vs leverage. Public accountability increases pressure and success rates by roughly 30–50% in small studies; private accountability reduces stress but needs strong consistency.
Part 8 — The first 90 days: a practical playbook
The first 90 days are a testbed. We learn whether our time estimates are realistic and whether the BHAG fits our life.
Week structure:
If we hit the schedule, expected weekly median output = 450 + 200 + 200 = 850 words/week → 60,000 / 850 ≈ 71 weeks (~17 months). That beats our 30‑month target and leaves room for revising and unforeseen events.
Action now (30–60 minutes)
Part 9 — Sample Day Tally: how small tasks add up to the BHAG
Here’s a sample day tally for a typical writing day that sums to our weekly goal. These are concrete numbers to show how small actions accumulate.
Sample Day Tally (one productive day toward the 60,000‑word BHAG)
Weekly total (using the sample schedule above: Mon+Wed+Fri): 450 + 200 + 200 = 850 words per week. Monthly (approx. 4.3 weeks): 3,655 words. Quarterly (13 weeks): about 11,050 words.
If we keep this pace for 6–8 quarters, we reach 60,000 words. These numbers show that the arithmetic is manageable when we structure time intentionally.
Part 10 — Optional nudge
If we are setting a BHAG in your own tracker, create a mini-module: “BHAG Daily Microlog” with a single question: “Did we complete any BHAG session today? Yes/No. If yes, how many minutes?” Add a weekly reminder on Sunday at 18:00 to run the weekly review.
Part 11 — Handling setbacks, plateaus, and life interruptions
Setbacks are inevitable. Our approach is to set rules for recovery, not to chase perfection.
Part 12 — Misconceptions, edge cases, and risk limits
We dispel common misconceptions and note who should be cautious.
Part 13 — Scaling and course‑corrections: mid-term tactics
After the first 6 months, we introduce scaling tactics and checks.
Course‑corrections
Part 14 — Storytelling and identity work: making the BHAG part of who we are
We often underestimate how much storytelling matters. Telling a coherent story — internally and to a trusted circle — stabilizes persistence.
Action now (10–30 minutes)
Part 15 — One explicit pivot we made
We assumed that launching with a loud public commitment would create sustained pressure → observed that public pressure caused shame and avoidance when early weeks were poor → changed to a private launch model: we commit publicly only after achieving three consistent months of weekly targets. That pivot increased persistence and reduced anxiety.
Part 16 — The finishing loop: review, refine, recommit
Every quarter we run a finish loop: review metrics, reflect, and decide whether to continue, slow, or stop.
Review checklist (30–60 minutes)
Part 17 — Short alternative flow for very busy days (≤5 minutes)
When schedules collapse, we need a tiny retention action. Choose one of these microoptions:
These microactions preserve identity and reduce restart friction. Commit to at least one microaction on busy days.
Part 18 — Sample BHAG variants and quick numbers
We offer quick templates with numbers you can adapt.
Each variant shows the trade-offs: time, intensity, and community. We quantify to make decisions clearer.
Part 19 — Accountability scripts: three short templates
We provide three short accountability messages you can send to a partner. They are concise and concrete.
Weekly check (10 seconds) “Weekly BHAG check: Completed 3/4 sessions; 750 words this week. Next week goal: 1,000 words. Quick call Sunday at 18:00?”
Missed session audit (20 seconds) “Missed two sessions due to work travel. Immediate fix: move one session to morning; micro‑action daily for travel days. Check‑in Wed?”
Progress shout (20 seconds) “Hit monthly milestone: 3,650 words. Planning to scale to 5,000 next month by adding one 40‑minute micro session.”
Part 20 — Data, evidence, and realistic expectations
We quantify expected adherence and outcomes based on typical patterns:
These numbers are approximate but useful for planning risk and calendaring resources (e.g., editor time, design budget).
Part 21 — The ethics and long‑term view
BHAGs interact with long-term values. We must ensure they are not a vanity trap. Ask: does this BHAG serve others (customers, readers, community) or only our ego? Both are valid, but alignment with broader values tends to sustain effort longer.
Part 22 — Check‑in mechanics: what to log and when
Logging is not busywork; it’s the feedback that corrects course. We design a simple check‑in pattern that fits your tracker and real life.
Check‑in rhythm (what we use in your tracker)
We keep daily logging to ≤2 fields to reduce friction: minutes/session and one sentence mood or barrier.
Part 23 — Check‑in Block (copy into your tracker)
Part 24 — Examples of edge-case responses (how we handle unusual outcomes)
Part 25 — Tools and micro‑habits to support focus
We suggest small, evidence‑backed tools and limits:
Part 26 — The social reward and celebration loop
Celebrate milestones deliberately. Small rituals for wins increase dopamine and bond the identity.
Part 27 — When to stop
A BHAG is a long shot; sometimes stopping is the right decision. We recommend stopping if:
Part 28 — Final practical checklist (do these today)
Part 29 — Quick FAQs
Q: How often should we rewrite the BHAG? A: Revisit the wording quarterly; substantive changes should follow a 2‑week experiment and a 30–60 minute review.
Q: Are deadlines necessary? A: Yes. A deadline converts possibility into a schedule. Try to keep a 12–60 month horizon for most BHAGs.
Q: Can we pursue multiple BHAGs? A: Limit to 1–2 active BHAGs. Parallel BHAGs compete for scarce attention and reduce identity clarity.
Closing reflection
We have walked through the BHAG as both an aspiration and a disciplined program. The point we keep returning to is simple: scale emerges from sustained small decisions and honest measurement. If we can protect a few hours a week, run short experiments, and keep a generous but disciplined feedback loop, audacity becomes practical. We close with a small, actionable prompt: pick one sentence that defines your BHAG today, log it, and schedule your first focused session.
Check‑in Block (copy/paste into your tracker) Daily (3 Qs)
Optional nudge Create a “BHAG Daily Microlog” module in your own tracker: single daily question — “Did we complete a BHAG session today? (Yes/No). Minutes:” Add a weekly reminder Sunday 18:00 for review.
Alternative path for busy days (≤5 minutes)
Hack Card
Use the check-in method described above and record the result somewhere you will actually review, so progress stays visible over time.
Don't worry! Life OS habits are designed to be flexible. Just get back on track the next day without judgment.
There is no fixed number of days for a habit to become automatic. Keep the context consistent, notice whether the action is getting easier to repeat, and review the practice over time instead of treating a countdown as a success criterion. Focus on consistency rather than perfection to build momentum.
Brali keeps substantive article history visible. Later reviews may refresh wording, sources, examples, or boundaries without silently replacing the record.
Canonical source record · Evidence state: pending-review.
Maintenance record
Current status: Active. Published without a later explicit lifecycle conclusion.
No explicit review event has been recorded yet. The hack remains published from its source content and can be challenged or reviewed.
Browse the review ledger · Challenge or update this hack
Implementation observations can trigger a review, but they cannot change an evidence conclusion by themselves. Commercial relationships do not control review status or outcomes.