When RAYGUN Fails

(And How to Recover)

You will lose this. Everyone does. Here's how to get it back.

The fact that you're here troubleshooting means you're already experimenting. That's RAYGUN in action.

Which sounds like you?

👆 Select the option that best describes your situation, then click "Show My Recovery Path"

You're Too Depleted to Experiment

Why this happens

When your energy is at 0%, your brain can't access curiosity. Fascination requires minimum baseline energy. You're not failing at RAYGUN—you're trying to run it on empty battery.

What to do

  1. Recognize you're depleted (this is data, not failure)
  2. Choose: Rest (if possible) OR Grind on timer (if necessary)
  3. If resting: Sleep, walk, easy task, anything restorative
  4. If grinding: Set 25-min timer, grind through it, rest after
  5. Don't try RAYGUN until energy baseline restored

Example

"I need to file taxes (boring, necessary). I'm at 10% energy. Trying to make it fascinating fails. Instead: Set timer for 25 minutes, grind through what I can, accept it's grinding, stop when timer ends. Not everything is experimentable when depleted."
Read The Practice (Part 4)

The Loop Didn't Shift You

Why this happens

The Minimum Loop has 6 steps. If one step breaks, the shift won't happen. Let's debug which step failed.

Diagnostic questions

  1. Did you notice you were grinding? (Step 1: Notice)
    If NO: Practice meta-perception first
  2. Did you interrupt the pattern? (Step 2: Interrupt)
    If NO: Try somatic anchor (tap fingers 5x, embody shift)
  3. Did you identify actual constraint vs story? (Step 3: Check constraint)
    If NO: You might be solving wrong problem
  4. Did you feel curiosity about the puzzle? (Step 4: Reframe)
    If NO: Might be depletion (see Depletion path)
  5. Did you design smallest experiment? (Step 5: Experiment)
    If NO: Too big, scale down
  6. Did you observe what emerged? (Step 6: Update)
    If NO: Ran experiment but ignored results

What to do

Find which step broke, focus practice there. Don't try to run full loop until that step works.

Example

"I noticed grinding (step 1), interrupted (step 2), but couldn't identify constraint (step 3). Kept solving surface problem not root constraint. Fixed: Spent 5 minutes just identifying actual constraint before trying reframe."
Read the Minimum Loop

It Worked Once, Now It's Gone

Why this happens

You experienced the shift, then lost it. This is NORMAL. The skill takes practice to sustain. You're not broken—you're learning.

What to do

  1. Recognize this is skill-building, not one-time fix
  2. Set triggers for meta-awareness:
    • Every doorway you walk through
    • Every time you feel resistance
    • Every time you sit down
    • Every notification
  3. Practice catch-and-shift: Notice grinding → interrupt → reframe
  4. Start small: 1-2 catches per day (not constant)
  5. Build from there as skill strengthens

Integration strategies

  • Somatic anchor: Physical cue triggers experimenter state (tap fingers 5x)
  • Environmental cues: Post-it note: "Grinding or experimenting?"
  • Social cues: Tell someone, they remind you
  • Calendar reminders: 3x/day check-in initially
Read The Practice (Part 4)

You Get It, But Can't Do It

Why this happens

Intellectual understanding ≠ embodied practice. You know what RAYGUN is, but haven't felt the shift yet. You're trying to "succeed at RAYGUN" which is itself grinding.

What to do

  1. Stop trying to "do it right" (that's grinding about experimenting)
  2. Pick ONE small moment today
  3. Just notice: "Am I grinding or experimenting right now?"
  4. Don't try to shift, just observe
  5. Do this for 2-3 days (build meta-awareness first)
  6. THEN try the Minimum Loop on something small

Example

"I read the framework 3 times, understood it intellectually, but couldn't practice it. Realized: I was grinding to 'get RAYGUN right.' Fixed: Spent 3 days just noticing grind vs experiment states. Didn't try to shift. Just observed. After 3 days, shift started happening naturally."
Do the Guided Experiment

Notice what you just did?

You troubleshot a problem by:

  1. Identifying the actual constraint (which failure mode)
  2. Treating it as puzzle (which recovery path)
  3. Designing experiment (what to try next)

That's the Minimum Loop. You're already doing RAYGUN.