Touch For Fun Prompt Deck
How do we keep the right five questions front-of-mind when decisions must be made fast?
Most Important Problem
Under pressure, teams default to habits and urgency cues; without a shared prompt deck, good intentions fail to stay in working memory at decision time.
Role in the Loop
This page is the fast loop operating layer:
- Think fast
- Decide fast
- Keep principles in RAM
- Capture drift signals immediately
Use this with the Business Plan and refresh it weekly from deeper strategic learning.
Five Question Entry (Front of Mind)
Use these before sessions, decisions, launches, or conflict moments:
- What good are we protecting right now?
- What is the real problem in this moment, not the loudest symptom?
- What is the next smallest safe move?
- What signal will tell us this move is helping?
- What should be captured so the system improves tomorrow?
RAM Stack
| Layer | Function | Touch For Fun Use |
|---|---|---|
| Prompt Deck | Decision prompts | Five-question entry for fast framing |
| Mantra | Identity + state cue | "Safety, play, presence, progress" |
| Working Memory | Temporary priorities | Top 3 active bets for this week |
| Micro-Protocol | Execution cue | Pre-session, in-session, post-session checks |
Mantra
Safety, play, presence, progress. Think slow so you can act fast.
- Safety: consent and trust first
- Play: keep experimentation alive
- Presence: attend to people and signal
- Progress: learn and improve every cycle
Working Memory Board (Weekly)
Keep only three active items:
- Primary problem this week
- Most important decision this week
- One protocol to improve this week
If more than three items appear, demote the rest to Business Plan.
Fast Decision Protocol
PAUSE -> ASK 5 -> PICK NEXT SAFE MOVE -> RUN -> LOG SIGNAL
| Step | Prompt | Output |
|---|---|---|
| Pause | What state are we in right now? | Calm, shared frame |
| Ask 5 | Run five-question entry | Problem clarity |
| Pick Move | What is smallest safe move? | Immediate action |
| Run | Who does what by when? | Executed decision |
| Log | What happened and why? | Learning artifact |
Drift Signals
Stop and reset if any are true:
- More debate than observation
- More activity than measurable progress
- Safety checks skipped due to urgency
- Decisions made without naming trade-offs
- Repeated issues with no protocol update
Update Rule (Slow -> Fast)
Refresh this prompt deck from the Business Plan when:
- A weekly review identifies repeated drift
- A pilot result invalidates a core assumption
- A new constraint changes priorities
- A better protocol proves itself in practice
Escalate to Slow Planning
When fast-loop signals persist, jump to the relevant planning depth:
| Fast-Loop Trigger | Slow-Loop Destination |
|---|---|
| Repeated ambiguity on what matters | Tight Five Planning Frame |
| Decision quality is inconsistent | Decision Framework to Execution Procedures |
| Pilot design is unclear | 6. Execution & Unit Economics |
| Risks are recurring | 9. Governance & Risk |
| Team asks "what now?" | Three Phases and Plan-to-Deck Update Protocol |