Day 12: Decide the thing you've been weighing.
That A-or-B decision sitting on your plate. Five questions, five minutes, decision made. Off your list.
Welcome to Day 12 of the challenge.
There’s a decision you’ve been carrying. A software tool you’re choosing between. A hire you’re weighing. A vendor. A venue. A format. Maybe an offer on the table you keep meaning to say yes or no to.
It’s been a week longer than it should have been.
Today we put it to bed.
A word before we start
Most “I’m weighing this” is not really weighing. It’s circling. The reason it’s been a week is not that the decision is hard. It’s that you haven’t been forced to be specific about your criteria yet.
The cure isn’t more thinking. It’s a sharper question.
Today Claude plays the role of the brilliant strategist who, instead of trying to recommend anything, makes you answer five questions you’ve been avoiding. Once you’ve answered them, the decision usually makes itself.
This is the version of AI as a thinking partner most people miss. It’s not “AI tells me what to do.” It’s “AI asks me what I should have asked myself.”
Step by step
Step 1. Pick the decision. Real one. Currently on your plate. Has been there longer than a week.
Don’t pick the biggest decision of the year. Pick one that’s mid-stakes and overdue. Software tool, hire, vendor, format, venue, offer to say yes or no to. The kind of thing that’s been sitting on the back of your brain.
Step 2. Open Cowork. New chat. Paste this brief:
I’m choosing between [Option A] and [Option B] for [purpose].
Context: [3-4 lines on what’s at stake, what’s making it sit, what I’ve already half-decided.]
Don’t recommend yet. Step one: ask me FIVE questions that would help you make a sharper recommendation. The kind a real strategist would ask, not the obvious ones I’ve already asked myself. One question at a time. Wait for my answer before moving to the next.
Hold the recommendation until after question five.
Step 3. Answer the five questions. One at a time. Don’t rush. The questions are the work.
A few will feel uncomfortable. That’s the signal you’re answering the right ones. Use Wispr Flow if you want to talk through your answers instead of typing them.
Step 4. After question five, paste this:
Now compare the two options against the criteria my answers implied. Score each on a 1-10 scale per criterion. Tell me which to pick. If it’s close, tell me what would tip it the other way.
Be direct. Don’t hedge.
Step 5. Read the recommendation.
You’ll either feel relief (the answer matches what you were already leaning toward, you just hadn’t said it out loud) or surprise (the answer is the opposite and you need to sit with it).
Both are useful. Don’t override the surprise on instinct. Sit with it for an hour. If at the end of the hour you still disagree, override. Tell Claude why. Save that note. The reasoning matters more than the choice.
Step 6. Save the decision.
Save this whole conversation as 2026-XX-XX-decision-[short name].md in my Cowork folder.
This becomes the receipt. Six months from now, when you’ve forgotten why you chose the way you did, the file remembers.
Step 6.5. Draft the message.
The decision is the inside work. The message is the outside work. Day 12 isn’t done until the outside work lands. Ask Claude:
Draft the message I’ll send to [the person waiting] explaining the decision and what happens next. Three to five lines. My voice. No hedging.
Read it. Edit if needed. Step 7. Send it.
Don’t end the day with the message drafted but un-sent. Email, Slack, text, whatever the channel. Close the loop today.
Step 8. Add to MEMORY.md.
Before you close, add one line to MEMORY.md (or jot it down to add tomorrow if you haven’t built MEMORY.md yet):
Decision pattern that works for me: five questions before recommendation, then the message drafted immediately.
Reinforces the pattern for next time.
A safety note
If the decision involves people (a hire, a redundancy, a contract you’re walking away from), Claude is excellent on the criteria and clumsy on the humanity. Use it for the criteria step. Don’t use the recommendation as your script when you go to talk to anyone.
Same for anything legal, medical or financial with real consequences. Claude is a clarifier of your thinking, not a substitute for advice from the relevant professional.
What you’ll notice
You’ll already know the answer after question three or four.
That’s normal. The questions surface what you’d been holding back from yourself. By the time Claude recommends, the recommendation is a formality.
The other thing you’ll notice: the relief of having decided is bigger than the decision deserved. That’s the open-loop tax you’d been paying. Every day the decision sat on the back of your brain, it was costing you energy you weren’t accounting for. The five-minute exercise reclaims it.
Run this once a month on whatever’s been sitting longest. Compound effect across a year is real.
Why this works
Decisions stall because the criteria aren’t named. Once the criteria are named, most decisions are obvious. A good strategist’s job is to surface the criteria, not to recommend.
Claude is good at this because it has no skin in the game and no relationship to protect. It just asks the question your inner circle has been too polite to ask.
The pattern is the same as the other days. Claude does the assembly (in this case: asking the right questions). You make the call. The call is faster because the assembly is done.
Key takeaway
Five questions before the recommendation. The decision you’ve been carrying, decided, in twelve minutes. The receipt saved for future-you.
This is what AI as a thinking partner actually means.
Where this is heading
You’ve used AI on real tasks all week. Tomorrow we set up the structure that holds everything you build with it. Three folders. Eight minutes. The foundation Week 2 closes with.
Tomorrow on Switched On
Day 13: Set up the folder that holds your AI brain.
Three empty folders. That’s the infrastructure. It looks like nothing today. By the end of next week it’ll hold the brain about you.
Nishma x
P.S. How did today land? Three buttons, thirty seconds → Tap one
I read every response. The data shapes the rest of the challenge.
Catching up? Days 0 to 11 are on the Switched On Substack archive HERE.
Got a friend or a colleague who this might be useful for? Send her to nishma.co/30daychallenge




