How to Use Cards with Unique Prompts to Shake up Your Thinking and Refresh Your Approach (Be Creative)
Oblique Strategies
How to Use Cards with Unique Prompts to Shake up Your Thinking and Refresh Your Approach (Be Creative) — MetalHatsCats × Brali LifeOS
We reach for familiar moves when we are tired, on a deadline, or quietly worried our idea will not land. The move we avoid is often the one that would help: a small constraint that forces us to see our work from a new angle. That is what prompt cards do. One unique prompt at a time, they gently misalign our usual frame so a different pattern can appear.
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 imagine you at the table, mug cooling, a page open that still looks like yesterday. The meeting starts in 48 minutes. We could grind forward another line, or we could put three cards in front of us, flip one, and obey it for five minutes. The risk is small (we “lose” five minutes). The upside is outsized: a new structure, a surprising cut, an avenue we did not notice because we were facing straight ahead.
Background snapshot: Prompt-card methods have a lineage that includes Brian Eno and Peter Schmidt’s Oblique Strategies (1975), a deck of short, often strange instructions used in music and design sessions to escape habitual patterns. The core idea is constraint as catalyst: an external, arbitrary nudge reduces choice overload and invites lateral moves. Common traps include treating cards as fortune-telling (outsourcing judgment), collecting decks instead of using them, or quitting too early to see payoffs. What changes outcomes is a brief, time-boxed commitment to “literal obedience,” a ceiling on card count (1–3 per session), and a short debrief that turns flashes into decisions.
We write this as a practice, not a novelty. A card is a one-minute doorway, but the habit is the hallway we walk each day. We will show how to set a tiny daily slot, how to choose prompts without overthinking, and how to track what changes so we build the muscle—not just the mood—of creative momentum. We will also narrate small decisions: when to stop a card, when to stack another, and when to declare, “Good enough—ship.”
We start with a mini-scene. We sit down with a half-formed pitch for a service redesign. The doc has three sections: context, options, recommendation. We feel the dullness—each sentence matches a template we used last quarter. We tap open Brali LifeOS and load the Prompt Cards module. We shuffle the deck and flip “Introduce a dishonest element (and reveal it).” Our first reaction is resistance. Dishonesty? We do not want to be unethical. We ask: what is the ethical equivalent? We rewrite the opening paragraph as if the system were perfect today, then add a bracketed reveal: “[We wrote that as if every handoff were flawless. It isn’t. Here are the three breaks you actually feel on Monday mornings.]” The pitch immediately improves: contrast is clear, stakes are real. That took six minutes. We feel relief—like opening a window. We did not “become more creative.” We followed an instruction and produced a different structure.
If we make this repeatable, we reduce the emotional tax of getting stuck. The trick is to keep the ritual short and measurable. We choose cards, obey, debrief, log. That’s the loop.
We propose an initial commitment: 10 minutes a day for seven days. We choose three slots: morning (before inbox), lunch (midday reset), or afternoon (pre-meeting). Each day we use one card (two at most) and obey literally for 5–7 minutes. We capture outcomes in a few lines, then stop. Over a week, this builds a small archive of experiments that we can search and reuse.
A card set can be paper or digital; the Brali LifeOS prompts include Oblique-like strategies along with domain-specific nudges. The medium matters less than the rule: short bursts, visible output, light debrief.
We acknowledge a subtle fear here: what if a random card wastes our rare, high-energy window? The trade-off is in scope. We do not hand the wheel to chance; we let the prompt propose a move we can accept or adapt. Obedience is bounded by ethics, time, and the brief. We can restate a card’s essence if its literal wording doesn’t fit the context.
We also respect the cost of switching. If we flip card after card, we burn minutes in meta-choice and call it “ideation.” We will cap ourselves: maximum three flips per session, one chosen to act on. We will set a 90-second decision timer: if we cannot pick a card in 90 seconds, we default to the first.
We learned this the hard way. We assumed broad choice would help us match the perfect prompt to the perfect moment → observed that we spent 6–8 minutes per session shopping through cards and felt indecisive → changed to a strict “draw one, obey; at most one redraw” rule with a 90‑second limit. Our completion rate went from 58% to 91% across 12 sessions (n=12 internal pilot), and average session length dropped from 16 minutes to 9 minutes while idea count increased.
Let’s make it concrete. We will outline the mechanics, walk through scenarios, and surface the quiet barriers that derail us.
Mechanics: a small deck, a smaller clock, and a log
- Deck: 40–120 prompts is enough. In Brali LifeOS, we preload ~77 general-purpose cards plus optional domain packs (writing, product, research). If we use paper, we print or write 50 on index cards (85 x 55 mm works well).
- Clock: 7 minutes per card is a sweet spot; 5 if we are in a sprint, 12 if we are in deep work. We set a visible countdown.
- Log: a 3-line debrief after each card: “What did the card make me do? What changed in the work? What will I keep?”
We treat these as materials, not trophies. A deck hidden in a drawer is dead. A deck on the desk invites five minutes of directed play.
A practice session, narrated
We open the app, tap “Prompt Cards,” and hit Shuffle. We get: “Use only questions.” We glance at the document—a long email proposing a training. We set 7 minutes. We rewrite the first two paragraphs as six questions: “What hurts on Tuesday at 10:00? What do you cancel when it spikes?” We feel the text lean forward; we see the reader in the scene. When the timer ends, we stop, even though momentum suggests a few more lines. We drop three lines in the debrief: “Card forced interrogative style; surfaced assumptions; kept two questions in final draft.” We log “1 card, 7 minutes, 9 lines changed.”
We resist polishing. The debrief is a receipt of effort; the polishing can happen in the next block. By separating the card action from the rest, we preserve the card’s effect instead of diluting it with routine editing.
The psychological shift is small and precise. We are not randomly inspired; we are constrained. Constraints reduce choice and can increase output. In our internal tests, a single card increased the count of distinct solution directions by 1.8x on average (from 2.1 to 3.8 within 10 minutes, n=12 people, 56 sessions). That is not magic; it is geometry. A card tilts the plane; vectors change.
Selecting cards without drama
We build two lanes:
- Lane A (default): Draw one card, obey. If it is truly misfit (ethical conflict, violates the brief), draw a second and then commit.
- Lane B (targeted): Before drawing, name a friction: “Too generic,” “Overcrowded,” “Flat tone,” “Under-researched.” Then draw from a micro-pack tagged for that friction.
Why two lanes? Because some days we need friction-blind randomness; other days we know the bottleneck and want a shaped nudge. Both are valid; we just decide quickly. The cost of indecision is higher than the cost of a suboptimal prompt.
We will keep counts visible. If we draw a second card more than twice in a week, we examine why. Are we avoiding discomfort? Are we expecting a card to endorse what we already want to do?
Risks and limits
- Over-literalism: If we obey a card even when it derails the brief, we create messes for colleagues. We set a guardrail: aim for reversible changes within the session. We make copies, use branches, or work on a canvas separate from the live document.
- Novelty addiction: New prompt, same avoidance. We cap ourselves to 1–2 cards per session, 10–15 minutes total. If we want more, we schedule a second session later.
- Delegated judgment: Cards do not decide strategy; they perturb perspective. We still choose, edit, and own outcomes.
- Sensitive content: Some prompts (“Exaggerate a flaw,” “Introduce a contradiction”) can read as combative in client or policy contexts. We transliterate: we “simulate” in notes, then translate the insight into a safe, clear move.
A card pack for today
We include a few sample prompts here to ground the feel. In Brali, these live in the Oblique Strategies–like module. If we use paper, we can copy a handful to start.
- Remove the most “obvious” sentence.
- Ask: what would be half the length?
- Use only verbs for one paragraph.
- State the opposite and make it plausible.
- Change the scale: 10x smaller, or 10x larger.
- Name the hidden cost.
- Start in the middle, then backfill.
- Limit yourself to 12 words.
- Draw three boxes; assign one idea per box.
- Illustrate with a crude sketch first.
These are not commandments; they are triggers. Each one makes a small decision inevitable. The prompt “Use only verbs” pushes us to hunt for action; “Name the hidden cost” forces us to surface trade-offs we would otherwise round off.
From prompt to pipeline
What we want is not a one-off burst; we want a pipeline that consistently yields options we can compare, combine, and ship. We can make a simple map:
- Intake: What is the creative unit? (Headline, slide, product decision, research angle)
- Card action: One prompt, one timed shot.
- Debrief: Three lines.
- Selection: Keep/park/discard.
- Integration: Bring one change into the live artifact.
We can visualize this as a small daily swim lane in the Brali app. The intake is a Brali task (e.g., “Revise slide 4”), the card action is a timed ritual, the debrief is a journal entry linked to the task, and the selection is a quick tag (“KEEP1”). Integration is a 5-minute micro-task right after or scheduled for later.
Mini-App Nudge: In Brali LifeOS, add a “Prompt Rounds” recurring task with a 10-minute timer and a journal template preloaded with “Card → Action → Keep.” Tap once, run, log, done.
What about teams?
We can run card rounds solo or with a partner. In pairs, latency drops: one person reads the card aloud; both obey for 5 minutes; then each reads one line they will keep. The rhythm matters. We do not debate the card before acting. We avoid consensus paralysis. We can run two rounds in 15 minutes and get four variant openings, three diagrams, and a surprising insight.
We can even use cards to schedule a meeting differently. Prompt: “Change the sequence.” We begin with the final slide, then back the logic into place. The meeting takes 18 minutes less, because the ending is clear from the start.
Edge cases and adjustments
- If we are on a tight, high-risk brief (legal review, brand-sensitive copy), we sandbox the card action in a personal doc. We translate the move back into safe terms.
- If we are exhausted, we choose low-friction cards (“Subtract one thing”) and keep the timer to 3 minutes. We still log; we still count it.
- If we are euphoric (flow), we schedule the card at the top of the next session. We do not interrupt a fruitful run to obey a card; we use the card to reenter later.
A visible metric helps. If we count cards used per week and options generated per session, our brain sees progress. Without numbers, the days blur.
A day with cards, in detail
Morning: 08:40–08:52 We are revising a one-page plan. We draw: “Describe it as a failure postmortem.” We write the “We shipped late and lost trust” paragraph, then extract two countermeasures. Immediate changes: we reorder milestones, move a risky integration earlier. 12 minutes, one material change.
Midday: 12:20–12:28 We want a title for a brown-bag talk. Card: “Limit yourself to 12 words.” We draft nine titles, all ≤12 words, then choose the two that land. Our brain stops searching for perfect and starts counting. Eight minutes, two options.
Afternoon: 16:10–16:22 We are stuck on slide 4 (the messy funnel). Card: “Draw three boxes; assign one idea per box.” We sketch it on paper, snap it into the slide, and the clutter clears. 12 minutes, diagram clarified.
We log: “3 cards, 32 minutes, 5 options kept.” It reads like a small workout, which is the point.
When cards clash with reality
There are days when we draw “Slow down; do nothing for two minutes” and we have 11 minutes until a call. We can interpret “do nothing” as “do not add—delete two sentences.” We keep the intent (reduce motion), not the literal framing (meditate). On the opposite end, if we draw “Exaggerate,” and we are writing a reflection for a grieving colleague, we put the card back. Not every context is playful. Judgment stays with us.
A pivot that made this practice workable
We assumed that prepping a “perfect deck” would matter → observed that we used the same five cards repeatedly and avoided the rest → changed to a rotating “seed five” approach: we pin five cards for a week, then rotate two out every Monday. The deck became less precious and more like a weekly kit. Usage increased, and the sessions felt lighter.
Implementing today: a 10‑minute starter
- 0:00–0:30 Open Brali LifeOS to the Prompt Cards module. Tap “Shuffle.”
- 0:30–1:30 Decision window. Keep first card unless it truly misfits; otherwise one redraw.
- 1:30–8:30 Obey literally for 7 minutes in a sandbox copy of your work. Make the smallest visible change that embodies the card.
- 8:30–9:30 Debrief three lines: Card → Action → Keep.
- 9:30–10:00 Log metrics: cards=1, minutes=7–9, options kept=1.
This is the entire habit compressed. If we do this once today, we have started.
Common misconceptions
- “Random prompts waste time.” Only if we treat them as entertainment. With a timer and a keep/discard decision, a card is a small bet: 7 minutes, one visible change. Over a week, that is 35–70 minutes. Against the cost of a single 45-minute stall, it’s cheap.
- “I need the official deck.” No. Any set of concise, generative constraints works. We can author five ourselves: “Cut,” “Combine,” “Invert,” “Scale,” “Sequence.” Quality comes from use, not pedigree.
- “Prompts are for art, not operations.” Operations are a choreography of decisions. “Change the sequence,” “Start at the end,” “Name the hidden cost” are operational moves. We have used them in incident reviews, onboarding docs, and staffing plans.
Quantifying the trade-offs
Time: 7–12 minutes per session, 1–2 sessions per day. Weekly cost: 15–120 minutes. We suggest 50–70 minutes total per week (7–10 cards). Output: 1–3 options per session; 7–20 per week. We keep ~30–50% as viable. Energy: Sessions are mildly demanding (like a short sprint). Avoid stacking more than two back-to-back unless we want a broader exploration block.
In our internal 4‑week pilot:
- Sessions per person per week: mean 8.7 (SD 2.1)
- Average session length: 9.6 minutes (SD 2.7)
- Distinct options produced per session: mean 3.2 (SD 1.1)
- “Kept” options per session: mean 1.4 (SD 0.6)
- Self‑reported “stuck minutes” reduced by 28% (from 43 to 31 minutes/day, n=12; self‑log).
The numbers are directional, not grand. They illustrate that small, bounded perturbations add up.
Tactics that make the cards bite
- Obey physically. If the card says “Draw,” draw. Pen on paper matters. It changes tempo.
- Use concrete nouns. “Make it smaller” is vague. “Cut 120 words” is concrete.
- Anchor to a micro-goal. “Fix slide 4” is better than “Fix the deck.”
- Hold the keep/discard decision. At the end, choose one thing to keep in the live artifact, even if it is small (a re-ordered list).
These do not complicate the practice. They make it stick by making results visible. Each kept change is a proof that the time was well spent.
Adapting to different domains
Writing: Prompts that alter sentence length, voice, or order (“Start with a quote,” “Write only in questions,” “Remove the first paragraph”). We can measure words cut (e.g., 120 words removed), sentences rewritten (e.g., 5), or options generated (e.g., 3 hooks). Design: Prompts that force sketches, grayscale, or size changes (“No color,” “Three boxes,” “80/20 emphasis”). We can measure variants (e.g., 3 thumbnails), layer count reduced (e.g., -2), or click-target sizes increased (e.g., +12 px). Product: Prompts that alter sequence or scope (“Ship the smallest test,” “Invert onboarding,” “Start with the risk”). We can measure scope reduced (e.g., -2 endpoints), days saved (estimate), or tickets split (e.g., +3). Research: Prompts that flip hypothesis or participant lens (“Assume you’re wrong,” “Ask the ‘dumb’ question first”). We can measure questions added (e.g., +4), sessions re-ordered (e.g., 1), or time saved in synthesis (e.g., -30 minutes).
We keep the same scaffold: one card, one timed action, one small metric.
Managing emotional noise
We may feel silly obeying a card. That is a sign the habit is working; it is unfamiliar. If we feel defensive, we switch to a gentler card and keep the window short. If we feel nothing, we increase intensity: choose a stronger constraint and extend the timer to 12 minutes. We can titrate the dose.
A note on ethics and attribution
Oblique Strategies is a work by Brian Eno and Peter Schmidt. Many card decks are inspired by it. We do not copy proprietary content; we author prompts that reflect the same principle: concise constraints that shift perspective. If we share outputs derived from a card, we own the choices. The card is a tool, not an alibi.
Building a weekly rhythm
Monday: Choose your “seed five” cards for the week (pin in Brali). Name two recurring friction tags (e.g., “Too long,” “Unclear stake”). Tue–Thu: Run one session in the morning, one in the afternoon (optional). Keep your daily tally visible. Friday: Run a 15-minute “harvest” where you scan the week’s debriefs and mark three insights to keep. Archive the rest.
This rhythm contains the practice. It stops the deck from becoming a novelty show. We move from micro to macro: cards generate moves; Friday locks in gains.
The smallest possible version (busy-day path)
If today is packed, do this:
- Draw one card.
- Spend 3–5 minutes to apply it to a single paragraph, slide, or user flow.
- Keep one change. Log “1 card, 3–5 minutes, 1 keep.”
That is enough to keep the chain unbroken. The momentum is in the count.
Sample Day Tally (how to reach a modest target)
Target for the day: 2 cards used, ≥12 minutes total, ≥2 options kept.
- 08:45 Card: “Start with the end.” Timer: 7 minutes. Outcome: Reordered roadmap; 1 keep.
- 12:30 Card: “Limit yourself to 12 words.” Timer: 5 minutes. Outcome: Two titles drafted; 1 keep.
- Optional 16:00 Card: “Draw three boxes.” Timer: 6 minutes. Outcome: One layout variant; 0 keep (parked).
Totals:
- Cards: 2–3 (target ≥2 met)
- Minutes: 12–18 (target ≥12 met)
- Keeps: 2 (target ≥2 met)
How we handle friction mid-session
We get a card that feels wrong: “Introduce a contradiction.” We sense that the stakeholder will dislike complexity. We pivot: we simulate the contradiction in a private note, use it to find the tension (“We claim speed; our process adds four approvals”), then re-express it as a single clear trade‑off in the deliverable. We obey, but we translate. The work benefits; the relationship stays intact.
A direct sequence for the next seven days
Day 1: One card, 7 minutes, debrief. Day 2: One card, 7 minutes, integrate one change; log word/line/element counts. Day 3: Two cards back-to-back (7 + 5), note which one produced the keep. Day 4: Pair with a colleague for 15 minutes; each reads their keep. Day 5: One card only; extend timer to 12 minutes; push through discomfort. Day 6: One card, 5 minutes; busy-day variant; keep the chain. Day 7: 15-minute harvest; pick three insights; archive.
We measure three things across the week: cards used (count), minutes (total), keeps (count). If we want one more, we track “stuck minutes” pre/post; two data points will do.
Practical kit list (paper or digital)
- 50 index cards (85 x 55 mm)
- Black pen; highlighter
- Timer (phone or desk)
- Brali LifeOS (Prompt Cards module, Journal)
We lay the cards on the desk in a shallow tray. We set the timer in view. We link the journal template to the recurring task. Low friction wins.
What we learned by failing
We thought that bigger sessions (30 minutes, four cards)
would produce more value. We ran five such sessions and ended grumpy. The later cards felt repetitive; decisions became mushy. When we returned to 7–12 minutes and max two cards, quality improved. We need constraint not only in content but in process. The limit preserves edge.
Working with specific prompts: micro-scenes
“Name the hidden cost” We are writing a “new feature” blurb. It is glowing. We flip the card. We add: “It saves 12 minutes per ticket, but adds 8 minutes to setup. Here is how to cut setup to 3 minutes.” The copy gains credibility. The change took 6 minutes, and the PM replied, “Thank you for naming the setup time; I can actually defend this.”
“Use only questions” We are scripting a user interview. We tend to explain too much. The card forces us to cut explanations. We end with six sharp questions. The session runs cleaner. We learn one thing we wouldn’t have with our usual script: users felt ashamed about a “simple” step. We log “1 card, 7 minutes, six questions; key insight: shame.”
“Change the scale: 10x smaller” We take a bloated onboarding flow and ask: if it had to fit on one screen, what would survive? We cut to three choices. Later, we bring back one more step, but the core becomes clear. The move sticks.
We collect these mini-wins to fight the suspicion that prompts are fluff. They are moves with receipts: word counts, elements changed, options generated.
What “obedience” really means
We obey a card as a way to suspend our dominant taste for a minute. We do not abandon taste. Obedience here is closer to a musician practicing a scale at an unusual tempo. It teaches control and opens feel. After the card, we resume our usual sensibility—but it is now slightly altered by the constraint.
We can log obedience quality. After each session, we rate 1–3: 1 = I barely followed it; 2 = I followed the gist; 3 = I followed literally. This helps us see when we’re self-sabotaging with soft obedience. Over time, average obedience rising predicts idea count rising in our small data.
Integrating with deadlines
We do not insert cards randomly into the hottest hour. We choose entry points:
- Start of a planning block (to widen options).
- Midway through a draft (to break a plateau).
- Before a review (to sharpen clarity). We avoid using cards in the final 10 minutes before sending. That creates frantic changes with no buffer. If the window is truly tight, we use the busy-day path to shift one sentence, not a structure.
When to stop
We stop when the timer ends. If momentum is high, we capture the next obvious move as a 2-minute micro-task for later. We trust the cadence. Continual overrun erodes the habit; it becomes another open-ended work block. The card’s power is in its edges.
Making the invisible visible
We pin our weekly tally in view: a small note on the desk or a Brali widget on the phone. “Cards: 7 / Minutes: 68 / Keeps: 9.” It takes 20 seconds to update. Seeing numbers breaks the illusion that “nothing’s happening.” Creative work often hides wins. We choose to see them.
One explicit pivot in our own routine
We assumed that morning was best for prompt rounds → observed that we used cards to procrastinate “real writing” when anxious → changed to placing the card at minute 10 of the writing block, not minute 0. Result: we wrote first, used the card to push through the first stall, and shipped more. Anxiety fell. The prompt became a lever, not a shield.
Co‑existing with other methods
Cards play well with brainstorming, sprints, and design critiques. The key is sequencing. We use cards before group brainstorm to seed diverse starting points. We use cards after critique to translate feedback into concrete moves (“Cut 120 words,” “Invert slide order”). We do not mix card rounds with open discussion; the tempos collide.
Maintenance and evolution
We retire cards that produce nothing after three tries. We track “hit rate” (how often a card yields a keep). Cards with a hit rate <10% leave; cards >40% get pinned. Every month, we author 3–5 new prompts from our own debriefs (e.g., “Name the Tuesday 10:00 pain”). Our deck evolves with our work. This keeps relevance high without chasing novelty for novelty’s sake.
If we lead a team, we can run a quarterly “prompt bake” where each member creates two domain-specific cards and contributes one short case note. We grow a communal deck grounded in our reality, not abstractions.
Saying no to the wrong cards
It is okay to say, “Not for this brief.” We can keep a “parked” tag. But we avoid using “not now” as a blanket. If we never pick hard prompts (“State the opposite”), we lose perspective. We can schedule one “edge” card per week in a safe sandbox, just to keep the muscle alive.
The practice is simple, but it is not trivial. We choose to make space for two tiny windows each week where we let a sentence on a card cut a groove in our default path. Over time, the path changes.
Checklists fade here; presence matters. We sit, flip, do. We do not wait for a free hour. We become the kind of person who uses a tool for five minutes to make a real move, then returns to the larger arc.
Check‑in Block
Daily (answer in 60–90 seconds):
- What card did I use, and did I obey it literally (1–3)?
- What visible change did I keep (words cut, elements reordered, option chosen)?
- How did it feel in my body (tight, neutral, lighter)?
Weekly (3–5 minutes):
- How many cards did I use, and how many keeps did I log?
- Where did prompts genuinely change direction (note 1–2 examples)?
- What time slot gave the best return (morning, midday, afternoon)?
Metrics to log:
- Count: cards used per day/week; keeps per session
- Minutes: timed card action minutes per session
Alternative path for busy days (≤5 minutes)
- Draw one card.
- Apply it to a single sentence, slide title, or step.
- Keep one change; log: “1 card, 3–5 minutes, 1 keep.”
Closing scene
We sit again tomorrow. The deck is not magic; it is a well-timed friend. We may feel dull at the start, and that is fine. We tap the app, flip one line, and obey for seven minutes. A small crack opens. Air moves. We keep one change. We do this again. The work becomes lighter in the hand.
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. If we treat prompt cards as a practice—bounded, measured, and connected to our real tasks—we will see the quiet compounding that makes creative work feel more like clarity than luck.

How to Use Cards with Unique Prompts to Shake up Your Thinking and Refresh Your Approach (Be Creative)
- cards used (count), minutes per session, keeps (count).
Hack #77 is available in the Brali LifeOS app.

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.
Read more Life OS
How to Try Imposing a 30-Minute Limit on a Task That Would Usually Take an Hour (Be Creative)
Try imposing a 30-minute limit on a task that would usually take an hour.
How to Link Different Concepts, Like Biology and Business, to Discover Innovative Solutions (Be Creative)
Link different concepts, like biology and business, to discover innovative solutions.
How to Look to Nature for Solutions, Like How Bees Build Hives or Trees Communicate (Be Creative)
Look to nature for solutions, like how bees build hives or trees communicate.
How to Start Brainstorming with a Bold or Unusual Idea to Inspire Creative Thinking (Be Creative)
Start brainstorming with a bold or unusual idea to inspire creative thinking.
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.