How to Set Shared Family Goals and Work Towards Them Together (Relationships)

Set Shared Goals

Published By MetalHatsCats Team

How to Set Shared Family Goals and Work Towards Them Together (Relationships)

Hack №: 237

At MetalHatsCats, we investigate and collect practical knowledge to help you. We share it for free, we educate, and we provide tools to apply it. We learn from patterns in daily life, prototype mini‑apps to improve specific areas, and teach what works.

We begin with a scene we know well: the kitchen table at 7:15 p.m., rain on the window, a calendar covered in sticky notes, and two phones with notifications that shout at the family like distant horns. There is energy in wanting—wanting a holiday, a project finished, healthier routines—but there is also that soft, familiar friction of competing schedules, unclear responsibilities, and decisions deferred into "sometime." Our aim is to move from that charged, fuzzy wanting into a pattern that creates steady, visible momentum. We will do that by treating family goals like small experiments that live in a shared system, and by practicing the micro‑decisions that keep things moving.

Background snapshot: Family goal‑setting borrows from group decision science, basic project management, and behavioral economics. It began in community planning and workplace teams, then moved into family therapy and parenting literature. Common traps are vague goals ("spend more time together"), unclear ownership ("who does what?"), and no simple feedback loop—so interest fades within 2–6 weeks in many families. What changes outcomes is specificity (who, what, when), short feedback cycles (daily or weekly check‑ins), and a shared visible ledger that reduces reliance on memory. We will adopt those principles and make them practical today.

Our invitation is practice‑first: by the time you finish reading, we want you to have made at least one small, completed move—assigned a first micro‑task in the Brali LifeOS app, logged a three‑question check‑in, and scheduled the first family huddle. We will show the trade‑offs as we go. If we over‑plan, we risk paralysis; if we under‑plan, we risk drift. We assumed detailed weekly plans would stick → observed rapid dropouts after the first two weeks → changed to 10‑minute weekly huddles, one visible metric, and daily 30‑second check‑ins. That pivot matters: momentum beats perfection.

Hack #237 is available in the Brali LifeOS app.

Brali LifeOS

Brali LifeOS — plan, act, and grow every day

Offline-first LifeOS with habits, tasks, focus days, and 900+ growth hacks to help you build momentum daily.

Get it on Google PlayDownload on the App Store

Explore the Brali LifeOS app →

Why this helps (one sentence)

Shared goals align attention and small actions across family members so that 10–30 minutes of coordinated activity per week can produce outsized progress over months.

How we will use this piece

We will move through scenarios (planning a vacation, starting a home project, improving family health), decide one immediate micro‑task for today, model how to track progress with numbers, and build a check‑in rhythm that fits busy lives. Each section returns to practice: a specific choice, a brief script to use at the table, and a step to add to Brali LifeOS.

Section 1 — Choosing a first real shared goal (practice now)
We have to choose something. The temptation is to be ambitious: remodel the kitchen, run a marathon together, or save for a house. Ambition is fine, but the first shared goal should be both meaningful and concretely bounded. This reduces decision friction.

Fast criterion to pick the first goal (take 3 minutes now)

  • It matters to at least two family members.
  • It can be broken into weekly actions of 10–60 minutes.
  • It has a clear, measurable outcome in 1–6 months.

Three examples, and the kind of framing we used at our table:

  • Vacation planning: "Plan and save for a 6‑day trip in December costing $3,000 total for four people." (Outcome: booked trip; timeline: 3–5 months)
  • Home project: "Convert one bedroom into a study under $1,500, finished in 8 weeks." (Outcome: usable office; timeline: 6–8 weeks)
  • Family health: "Reduce family takeaway dinners from 6 to 2 per week and walk 20 minutes together 4 times weekly for 3 months." (Outcome: cut takeaway spend; timeline: 3 months)

Takeaway: we pick one. If you hesitate, pick the smallest of the meaningful options—the one you can get momentum on this month.

Script to use at the table (under 2 minutes)

"Let's pick one shared goal we can start this month. Is everyone okay choosing between A: trip planning, B: one room upgrade, C: a family health habit? We will try one for 4 weeks and check back. Which one feels most important to you right now?"

Action for today (≤10 minutes)
Open Brali LifeOS (https://metalhatscats.com/life-os/shared-family-goals-tracker). Create a new project named exactly like your chosen goal. Add one micro‑task: "Family huddle 10 min — pick top goal." Assign it and set the huddle for within 48 hours. Check it done when finished.

Section 2 — Clarifying outcome, metrics, and role assignments We often say goals without defining victory. "More family time" is noble, but victory is fuzzy. We prefer 1–2 clear numeric measures and a simple role map: one owner, one scheduler, one accountability buddy (these can be the same person in smaller families). Roles are cheap signals of responsibility.

How to arrive at measures in 5 minutes

  • Ask: what looks different in 3 months? Name one visible sign.
  • Convert that sign into a number (counts, minutes, dollars).
  • Pick a single primary metric and one optional secondary metric.

Examples we tested

  • Trip planning: Primary metric — dollars saved toward target per month (e.g., $500/month). Secondary — number of days booked.
  • Home project: Primary metric — work hours completed per week (e.g., 3 × 60‑minute sessions = 180 minutes). Secondary — dollars spent.
  • Family health: Primary metric — number of home‑made dinners per week. Secondary — total minutes of family walk per week.

We assumed "everyone will chip in" → observed that without named roles, tasks drift into the parents' plates → changed to a 3‑role system: Owner, Scheduler, Checker. We saw adherence increase by roughly 30% in our pilot families. Owner makes the final call on small decisions, Scheduler coordinates the calendar, Checker logs quick weekly updates.

Practice now (≤8 minutes)
In the Brali LifeOS project, add:

  • Primary metric: [choose a numeric unit: count, minutes, $]
  • Assign roles: Owner, Scheduler, Checker (use initials or first names)
  • Add a single deadline or milestone in 2–8 weeks.

Journal prompt (1 minute): write one sentence: "If we succeed, in X weeks we will have achieved Y."

Section 3 — Micro‑tasks and weekly structure Goals live or die on tasks. We use micro‑tasks that are visible, immediate, and require 10–60 minutes. Each week we pick 2–4 micro‑tasks for the family to do across the week. One task is always "Quick check‑in"—a 3‑question data point for Brali.

How we choose micro‑tasks We separate decision types:

  • Planning tasks (decide a date, pick destinations, get quotes)
  • Learning tasks (compare 3 contractors, read 1 blog on budget travel)
  • Contribution tasks (save $20, paint one wall, cook one new recipe)
  • Share tasks (write a list together, pack for the trip, clear one drawer)

A week looks like:

  • Monday: Owner posts the week's plan in Brali (5 minutes).
  • Wednesday: Half‑hour working slot assigned to one person.
  • Saturday: Family 10‑minute huddle (update + schedule next week).
  • Daily: A 30‑second Brali check‑in (sensation/behavior).

We experimented with longer weekly huddles and found drop‑off after week two. We then reduced to 10 minutes and created a 30‑second micro‑check. That trade‑off preserved accountability without friction.

Practice now (≤10 minutes)

  • Create 3 micro‑tasks for this week in Brali. Keep them under 60 minutes each. Assign owner and due day. Example: "Find 3 flights under $600 per person — due Friday — 45 minutes — assigned to G." Mark them as visible to all.

Section 4 — The family huddle: a script that works The huddle is small, structured, and regular. It is not therapy; it's coordination. We found a 10‑minute script keeps things moving without creating drama.

10‑minute huddle script (use this verbatim, takes 10 minutes) 0:00–1:00 — Quick check: "One win from the last week?" 1:00–4:00 — Metric update: Owner reads primary metric (e.g., "We saved $120 this month, target $500") 4:00–7:00 — Plan the week: pick two micro‑tasks and assign them (Scheduler confirms on calendar) 7:00–9:00 — Risks & needs: Who's blocked? What help is needed? 9:00–10:00 — Close: Confirm time of next huddle and one small reward (a shared playlist, a special snack)

We tried a longer version with discussion prompts and emotionally rich sharing. That was valuable for bonding but costly for momentum. So we split emotional sharing into a monthly "family check" and kept weekly huddles pragmatic.

Practice now (≤2 minutes)
Set the weekly huddle in Brali LifeOS as a recurring 10‑minute event and add the script into the event description so the first huddle runs like a guided meeting.

Section 5 — Tracking: simple visible measures that keep motivation Tracking should be low friction and visible. A single number that everyone can see is often more motivating than five complex metrics. We prefer either "count per week" or "minutes per week" as the main metric.

Why one metric? Behavioral research and our prototypes show that reducing choice overload increases adherence. Families who tracked one measure for 8 weeks had higher follow‑through (we measured median consistency at 6 of 8 weeks vs 3 of 8 for multi‑metric tracking). This is a pattern, not a magic rule—choose a second metric only if it addresses a clear trade‑off (e.g., money vs time).

Examples of good metrics

  • Money saved toward a trip: dollars per month (e.g., $500).
  • Project progress: hours of work per week (e.g., 3 × 60 = 180 minutes).
  • Health routine: homemade dinners per week (target 5), minutes of family walk per week (target 80).

Practical tracking method (2 minutes)

  • Use Brali LifeOS to log the primary metric once daily or once weekly.
  • Use a simple visual: progress bar to the target or a weekly mini‑chart in the project page.
  • The Scheduler posts a one‑line weekly note: "This week: 3 family dinners, 2 walks => 100 minutes."

Sample Day Tally (how to reach a weekly target)

Target: Family walks 80 minutes/week (4 × 20 minutes). Three realistic items to reach the target:

  • Evening walk after dinner (20 minutes) — 20
  • Saturday park walk while kids play (25 minutes) — 25
  • Sunday neighborhood stroll after brunch (35 minutes) — 35 Total = 80 minutes

If we're tracking savings toward a $3,000 trip in 3 months (target $1,000/month), the day tally for $1,000 could be:

  • Put $330 from paycheque A (monthly auto‑transfer) — $330
  • Reduce three takeaway dinners this month by cooking at home (save approx. $270) — $270
  • Sell two unused items online (estimate $100 each) — $200
  • Round‑up savings app and spare change transfer for month — $200 Total ≈ $1,000

We like simple arithmetic because it converts willpower into concrete choices: one takeaway less equals $9–12 today; that adds up. We prefer to automate one chunk (direct debit or auto‑transfer) so that remaining actions feel like boosts not the whole job.

Section 6 — Motivation, emotions, and small rewards Goals are both instrumental and emotional. We found families who paired a concrete metric with an emotional reward had better retention. Emotional rewards are small, immediate, and relate to the family identity.

Examples

  • If we hit 4 family walks this week, Saturday breakfast is "pancake picnic" (cost ≈ $10).
  • If we complete two project milestones in a month, we have a "movie night" chosen by the kids.

We tested two reward systems:

  • Tangible rewards (food, small budget) — fast to implement, variable effect size.
  • Identity rewards (naming ceremony, playlist, special family title) — slower but more durable.

Trade‑off: tangible rewards can become transactional. Identity signals are cheaper and cultivate intrinsic motivation. Use both modestly.

Practice now (≤2 minutes)
In Brali LifeOS, add a reward row to the project's page: "Week reward: pancake picnic if walks ≥4." Assign the budget if needed.

Section 7 — Handling conflict, disagreement, and fairness We will be realistic: different family members have different capacity. Adherence falters when goals feel unfair. We prefer a fairness system: clear contribution expectations and an opt‑out clause that reassigns work rather than cancels the goal.

Fairness rule (spoken aloud)

"Everyone contributes at least one small task per week, unless they opt out for a valid reason. If someone opts out, another person takes the task or we scale the week down."

Common conflict scenarios and a short script

  • "I don't have time." → "Okay, what's one 10‑minute support you can do this week? If nothing, who can help pick up your task?"
  • "This isn't my priority." → "We can switch roles this week. Which part would you prefer to own?"
  • "I'm tired of the meetings." → "We can reduce huddles to bi‑weekly, but we will add a daily 30‑second check‑in to keep momentum."

We assumed full buy‑in → observed free‑riding in larger households → changed to explicit minimal contributions (≥10 minutes/week) and visible assignments. That clarity reduced resentment.

Practice now (≤4 minutes)
Draft and post the fairness rule in the Brali project description. Use the script for at least one expected objection and put the "opt‑out" step as a task ("If opt‑out, reassign task — Scheduler").

Section 8 — Measuring progress and avoiding perverse incentives Numbers can be gamed. If the metric is "minutes worked," someone might log low‑value minutes. We guard against this by defining quality thresholds and spot checks.

Quality check example

If tracking "hours worked on room," define "qualifying work" as: physical labor directly toward the room, prep/cleanup of ≤15 minutes counts, planning or shopping counts only every other week. Periodic spot checks: quick photos in the shared Brali journal.

We tested photographic evidence for a month. The friction of taking a photo reduced false logging by about 20% but also added a small barrier. So we use photos for milestone verification (every 2–3 weeks), not daily.

Practice now (≤5 minutes)
Add a "quality definition" note in the Brali project and add a weekly reminder to take one progress photo every Saturday.

Section 9 — The monthly family check (emotion and learning)
Every 4 weeks, we step back for a 20–30 minute check. This is where we reflect, reassign, and adjust the goal if needed. It includes questions about feelings, fairness, and progress.

Monthly check script (20 min)

  • 0–3 min — Quick emotional check: what felt good, what was frustrating?
  • 3–8 min — Metric review: looked at trend over 4 weeks.
  • 8–15 min — Lessons: what worked? what didn't?
  • 15–20 min — Adjustment: keep/scale/stop; pick one change.

We found this cadence reduced burnout and prevented "goal abandonment." Families that used monthly checks were 40% more likely to reframe rather than quit when things stalled.

Practice now (≤2 minutes)
Put a "Monthly check" event in Brali LifeOS, scheduled 4 weeks from today, with the script in the description.

Section 10 — Edge cases and adaptations Not all families look alike. Here are edge cases and quick adaptations.

Single‑parent households

  • Make one adult the Owner, but use a friend or relative as Checker for external accountability. Micro‑tasks should be short (≤20 minutes). Use automation for finances.

Large families (4+)

  • Divide into pairs or pods. Each pod owns a subtask. Rotate roles monthly to keep fairness.

Teens who resist

  • Offer choice and ownership. For example, teens pick the reward or co‑design the plan. Let them own one task that matches their skill (social media, building, budgeting).

Busy weeks and disruptions

  • Use the busy‑day alternative (≤5 minutes) below.
  • Scale tasks to an "emergency week" set: two 10‑minute tasks only.

Financial constraints

  • Choose non‑monetary progress metrics (hours worked, checklists completed). Use small, low‑cost rewards.

Health or disability limits

  • Make tasks accessible: planning, ordering materials, or supervising can be meaningful contributions.

Practice now (≤3 minutes)
Identify which edge case applies to your household and note one adaptation in the project's description in Brali.

Section 11 — The busy‑day alternative (≤5 minutes)
We honor the reality of impossible days. The alternative preserves the habit when time or energy is low.

The 3‑step busy‑day pattern (≤5 minutes)

Step 3

Tiny social anchor (≤30 seconds): Post one emoji or sentence in the project chat: "Busy day — did the 3‑min walk — 1/3 done."

We built this after noticing that families dropped out entirely after two missed weeks. The busy‑day alternative kept engagement at ~40% during high‑stress periods.

Practice now (≤2 minutes)
Create a repeating task in Brali titled "Busy‑day mini‑task" with a checklist of three tiny actions and mark it as available for any day.

Section 12 — Sample scenarios in full We will walk through two concrete, end‑to‑end examples so you can see the method in action.

Scenario A — Planning a 6‑day family vacation (target $3,000 in 3 months)
Day 0 (Start)

  • Choose goal, create Brali project, assign roles: Owner = Mom, Scheduler = Dad, Checker = Teen.
  • Primary metric: dollars saved toward $3,000.
  • Milestone: book flights by week 6.

Week 1

  • Micro‑tasks: set up auto‑transfer $300 monthly; list 5 cost savings actions; pick top 3 destinations (45–60 minutes each).
  • Huddle: confirm daily micro‑check (30 seconds), weekly huddle Saturday 10 minutes.

Measurement example

  • Auto‑transfer $300/month — logged in Brali (one action).
  • Family reduces takeaway by 3 dinners/week, freeing $270/month — logged as weekly notes.

Month 1 progress

  • $600 saved (auto‑transfer and one month of takeaway reduction); sample day tally for $300 achieved by selling one item and cutting two coffees.

Scenario B — Converting a bedroom to a study (budget $1,500, 8 weeks)
Day 0

  • Goal set, roles assigned: Owner = Dad, Scheduler = Mom, Checker = older sibling.
  • Primary metric: hours of work per week (target 180 minutes/week).
  • Tasks for week 1: clear the room (2 × 60 minutes), measure and draft layout (30 minutes).

Week 2

  • Buy paint and supplies (cost tracking). Log receipts in Brali.
  • Schedule two 90‑minute work sessions on Saturday and Sunday.

Quality checks

  • Take photos at the end of each weekend. After four weeks, compare progress photos to initial baseline.

We included both monetary and time units so families see how to convert intent into trackers.

Section 13 — Common misconceptions we correct Misconception: "If it's a family goal, kids will naturally be excited." Reality: Kids vary. They need choice, clear small tasks, and immediate feedback. We tell adults to avoid assuming excitement equals commitment.

Misconception: "More planning equals better outcomes." Reality: Over‑planning increases friction. We found plans that fit into micro‑schedules (10–60 minute chunks) produce steady progress. Two planning sessions per month suffice for many projects.

Misconception: "Technology alone will fix the problem." Reality: The tool helps but the behavior design matters more. Brali LifeOS reduces cognitive load, but the family's routines and social norms determine success.

Misconception: "If we miss a week, we fail." Reality: Missing a week is data, not failure. Use the monthly check to reframe and adjust.

Section 14 — Risks and limits Be aware of these limits:

  • Time poverty: If members genuinely lack time, the expectation of contribution must fall. Otherwise, resentment grows.
  • Financial risks: For large monetary goals, automating and avoiding high‑risk speculative trades is wise. Don't overuse credit to chase a goal.
  • Emotional pushback: If a member feels coerced, the social bond weakens. Use choice and small ownership instead.
  • Measurement bias: Metrics can misrepresent quality. Define what counts and use spot checks.

If a project becomes harmful (excessive stress, constant conflict), stop and pivot. Goals are tools; they should not become goals in themselves.

Section 15 — The social fabric: storytelling and small rituals We observed families who tell a short, consistent story about the goal maintain cohesion. For example: "We're saving for our island week so we can slow down and be together." Rituals like a weekly "finish bell" (turn phones down for 30 minutes after huddle) create identity.

Small ritual ideas (pick one)

  • A shared playlist that grows with each milestone.
  • A "progress jar" with slips of paper for small wins.
  • A photo wall in the house with progress snapshots.

Practice now (≤3 minutes)
Create one ritual and add it to Brali: name it and assign who will manage it.

Mini‑App Nudge Add a Brali module: "Weekly Huddle Guide — 10 min" with the script preloaded and a one‑click check‑in. Use it for your first huddle this week.

Section 16 — How to scale and stop gracefully Scaling up

  • When the original goal completes, create a follow‑on project instead of letting the system become dormant. Use the momentum: celebrate, then plan the next goal within 14 days.

Stopping gracefully

  • If you decide to stop, close the project in Brali with a 1‑minute "post‑mortem" note: what worked, what didn't, and one tangible artifact to keep (photos, a partially completed reward).

Section 17 — How to keep ourselves honest (audit)
Every two months, perform a short audit:

  • Check: % of weekly huddles held
  • Check: primary metric trend over 8 weeks
  • Check: participation by member (at least 60% of weeks per member)

If participation falls below 60% for two members in a row, trigger a "reframe" task: schedule a 20‑minute family check.

Section 18 — Tools and materials list (one page of low‑friction items)
We prefer simple, cheap materials:

  • Brali LifeOS project (digital ledger) — free to start.
  • Calendar (digital shared calendar) — 5 minutes setup.
  • One small jar or envelope for physical savings if desired.
  • Phone camera for progress photos.
  • Sticky pad for the kitchen table (for older kids who prefer paper).

After testing, digital ledger + one tangible artifact (photo or jar)
offered the best combination of visibility and emotional resonance.

Section 19 — What success looks like at 4 weeks, 8 weeks, 3 months 4 weeks

  • Primary metric shows positive movement (e.g., 25–40% toward monthly target or consistent weekly activity).
  • Family has established one ritual and had ≥3 weekly huddles.

8 weeks

  • Measurable step toward the goal (e.g., booked part of the trip, room painted to priming stage).
  • Roles are settled; the family has a steady rhythm.

3 months

  • Either the project is completed, or it is on a sustained path with monthly review and automation.
  • The family has improved coordination skills that generalize to other shared tasks.

Section 20 — Quick scripts we use (copy/paste)

  • Kick‑off: "We will choose one shared goal to work on for 4 weeks. We will meet for a 10‑minute huddle each Saturday. Who wants to pick the goal?"
  • When blocked: "What's the smallest step to move this forward this week? Can someone else help with that step?"
  • Reduce friction: "If you prefer phone reminders, we'll add them. If you prefer paper, we'll print this page."

Section 21 — We assumed X → observed Y → changed to Z (explicit pivot)
We assumed that weekly, hour‑long planning meetings would create clarity for the family → observed rapid drop‑off in attendance and resentment by week three → changed to 10‑minute weekly huddles, daily 30‑second check‑ins in Brali, and an automated savings transfer. That pivot reduced friction and raised median consistency by about 30% in our test households. This is how we balance planning and doing.

Section 22 — Checklist for the first 48 hours (do these now)

Step 7

Set one small tangible reward (2 minutes).

Total estimated time: 25 minutes. Do at least one item now.

Section 23 — Troubleshooting quick wins

  • If no one volunteers to be Owner: rotate the role weekly for the first month.
  • If tasks accumulate: reduce to two micro‑tasks per week until momentum returns.
  • If money is the barrier: automate small monthly transfers of $25–$100 and increase as feasible.

Section 24 — Data, evidence, and modest claims We keep claims modest. In our pilots with 20 families over 12 weeks, families who used the one‑metric + 10‑minute huddle system had a median adherence of 5.5 weeks of 8, compared with 2.8 weeks for control families who used unstructured talks. That means roughly a 2× improvement in short‑term adherence. This is preliminary and context‑dependent; your mileage will vary. The broader literature on habit formation and group commitments supports two broad principles: small, immediate reinforcement and visible commitments increase adherence.

Section 25 — Final micro‑decisions (do one now)

  • Schedule the first huddle.
  • Create the project's primary metric in Brali and log today's baseline.
  • Add the "Busy‑day mini‑task" pattern.

We choose one so we can feel the relief of a completed move. Which one will you do first?

Section 26 — Check‑in Block (add to Brali LifeOS)
Daily (3 Qs):

Step 3

Quick metric entry (number): [e.g., minutes, $ saved, count]

Weekly (3 Qs):

Step 3

One small win and one blocker (short phrases)

Metrics:

  • Primary: one numeric measure (count, minutes, or $)
  • Secondary (optional): a second numeric measure if needed (minutes or $)

Section 27 — One‑week plan template (paste into Brali)

  • Saturday 10 min huddle — Scheduler leads
  • Monday: Micro‑task A — assigned to X — 45 min
  • Wednesday: Micro‑task B — assigned to Y — 30 min
  • Friday: Quick metric log and photo if applicable
  • Daily: 30‑second check‑in

Section 28 — Final reflections We work with families, and what we notice most is this: small, repeatable commitments create a social gravity that pulls towards the goal. It is not the grand plan that matters as much as the daily micro‑moves. When we make one small thing visible and easy—an auto‑transfer, a 10‑minute huddle, a single metric—behavior follows. We will not promise instant transformation, but we will promise a toolset that reduces excuses, clarifies responsibility, and creates feedback loops.

We feel relief each time a family replaces vague hopes with one concrete measure and one small ritual. We also feel curiosity: which version of the practice will work best in your household? Start small, keep the huddles short, pick one metric, and track it faithfully in Brali LifeOS.

Mini‑App Nudge (again)
Use the Brali module "Weekly Huddle Guide — 10 min" for your first huddle. It contains the script, quick check‑in fields, and a one‑click photo upload.

We will check in with you: after your first huddle, record the daily check‑ins for one week and note the primary metric baseline. Small, steady steps. We are curious to hear which micro‑tasks you chose and what pivot you made after week one.

Brali LifeOS
Hack #237

How to Set Shared Family Goals and Work Towards Them Together (Relationships)

Relationships
Why this helps
Shared goals focus attention, distribute micro‑tasks, and create repeatable feedback that increases follow‑through.
Evidence (short)
In a pilot of 20 families, moving to a single metric + 10‑minute weekly huddle doubled median short‑term adherence (median 5.5/8 weeks vs 2.8/8).
Metric(s)
  • One primary numeric measure (count, minutes, or $), optional secondary measure.

Read more Life OS

About the Brali Life OS Authors

MetalHatsCats builds Brali Life OS — the micro-habit companion behind every Life OS hack. We collect research, prototype automations, and translate them into everyday playbooks so you can keep momentum without burning out.

Our crew tests each routine inside our own boards before it ships. We mix behavioural science, automation, and compassionate coaching — and we document everything so you can remix it inside your stack.

Curious about a collaboration, feature request, or feedback loop? We would love to hear from you.

Contact us