My System Has Signals
Big idea: A feeling is a signal, not a command. A body clue is information.
This is the same telemetry idea from Week 1, packed into a tool you can use in the moment.
Your body sends little messages all day. Noticing one early — "my shoulders just went tight" — gives you a head start on choosing what to do.
Why it matters
A signal you never notice tends to drive the action for you: you snap, freeze, or shut down before you realize what happened. A signal you do notice opens a small gap between the feeling and the next move. Every other tool in this kit lives in that gap.
Read your dashboard
Your body usually sends the clue before you have words for the feeling:
- tight or raised shoulders
- a fast or pounding heartbeat
- a warm or red face
- a stomach that feels fluttery, tight, or weird
- wanting to yell
- wanting to hide or disappear
- trouble focusing or sitting still
- clenched hands or jaw
None of these are "bad." Each is your system reporting that something matters.
Mini activity: Signal Detective
- Pick an everyday moment, real or made up: losing a game, waiting a long time, getting corrected, being left out.
- Ask: "If my body had a clue about this, where would I feel it?"
- Name the signal: "My chest is fast. That's a signal."
- Say the motto: "A signal gives me information. It does not have to choose my action."
Discussion questions
- Where in your body do you usually notice a feeling first?
- Can a signal be real but its meaning still be unclear?
- Why does noticing a signal before acting help?
Try it this week
Once a day, catch one body clue and silently name it: "That's a signal."
- Low-stakes noticing week — curiosity, not disclosure.
- Narrate your own signals to model it ("my jaw's tight — that's a signal I'm rushing").
- Offer location options ("some people feel it in their stomach — where do you?") rather than telling a child what they feel.
- Made-up examples always count. Never require personal sharing.