What Creators and Innovators Can Learn from What Every BODY Is Saying
Leo watched through the one-way glass of a borrowed conference room as a tester clicked through his app's new onboarding flow. She said "this makes sense" twice, moving her mouse steadily. But her shoulders had crept up near her ears, and she kept tapping one finger against the desk between clicks, a habit she hadn't shown during the easier screens before. Leo's instinct was to trust her words and mark the flow a success. His product lead, watching beside him, asked her to think out loud on the next screen instead. She admitted she'd guessed at two buttons and gotten lucky. The tapping had been telling the truth the whole time.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
What users say versus what they show
People giving feedback on something you made are managing your feelings, not just describing their experience, so their words often run more polite than their comfort actually is. Watching for tension, hesitation, or stillness underneath a kind comment tells you where the real friction lives.
A creator hears "I love it" from a tester who fumbled through the interface and ships the version exactly as tested, missing the actual point of confusion.
When someone praises your work while showing visible tension, ask them to walk you through their experience step by step instead of accepting the compliment.
Learning a tester's normal before the demo
A tester who fidgets, avoids eye contact, or sits very still might just be their normal self, not reacting to your work at all, and this varies widely across individuals and neurodivergent presentations. A few minutes of casual conversation before the real session starts gives you a baseline to compare against once the actual task begins.
A creator assumes a naturally reserved tester is struggling with the product, when that stillness is simply how this person always looks while concentrating.
Open every test or critique session with two minutes of unrelated small talk, purely to see how this person behaves before anything is on the line.
Catching the moment interest drops
The signal worth tracking is the change: someone who was leaning in and engaged suddenly sits back, crosses their arms, or checks their phone. That's your cue to pause and ask, not proof the whole idea has failed.
A creator sees a reviewer's energy dip during one section and scraps the entire concept, when a direct question would have isolated one fixable detail.
When you notice interest drop mid-demo, pause and ask specifically what just happened, rather than pushing through the rest of the pitch on momentum alone.
Managing your own reactions to critique
The people giving you feedback are watching your face just as closely as you're watching theirs, deciding in real time how honest they can afford to be. A visible wince, crossed arms, or tight jaw when someone raises a concern teaches them to soften future feedback instead of giving it straight. Staying aware of your own reactions during critique, and keeping your posture open even when it stings, keeps the useful, honest feedback coming instead of drying up.
Reading your audience's reactions and managing your own defensiveness compete hardest right after hard feedback lands. Watch the room too closely and you might miss your own visible flinch giving away exactly how much the comment stung. Focus only on your composure and you miss the room's actual reaction while you're busy managing your face. The practical fix is a short built-in pause after any pointed comment, long enough to steady yourself before responding.
Name one thing, honestly
Think of the last time praise for your work didn't quite match the body language delivering it: what did you do with that mismatch?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
When you notice interest drop mid-demo, pause and ask specifically what just happened, rather than pushing through the rest of the pitch on momentum alone.