high-stakes-spontaneous-speaking
The goal of effective speaking is to move from a conscious, overthinking state into a subconscious flow state. By focusing on root behaviors—intensity, presence, and recovery—you can project confidence even when you feel internal turbulence.
Core Mindset: The Professional "Stay in Character"
Internal nervousness is invisible to your audience unless you "leak" it.
- Do not break character: Avoid apologizing for a "bad" answer, laughing nervously after a mistake, or saying "I hope that made sense."
- Stay in it: Even if you feel you are rambling or failing, maintain a confident posture and tone. Your audience will perceive you as confident by default unless you tell them otherwise.
- Think Up: When gathering your thoughts, look up and to the right rather than down at the floor or your lap. Looking up makes you appear thoughtful and confident; looking down makes you appear uncertain or distracted.
The Accordion Method for Presentation Prep
Instead of writing a script (which leads to "robotic" delivery and memory failures), build your talk through speaking to internalize the content.
- The Three-Minute Dump: Speak your entire talk for 3 minutes. Do not stop for mistakes. Focus on getting the core ideas out.
- The Two-Minute Shave: Give the same talk in 2 minutes. This forces you to cut the "noise" and keep only the most important points.
- The 30-Second Essence: Give the talk in 30 seconds. This identifies your "Arrow"—the one single thing you want the audience to remember.
- The Expansion (Back to 3 Minutes): Now, give the talk for 3 minutes again. Having found the essence, you will feel you have a "football field" of space to add back only the most impactful stories or data points.
Spontaneous Performance Tactics
Land the Plane (End Strong)
Most speakers taper off at the end because they regain self-consciousness. Anticipate this "finish line" effect and use a Summary Prompt to force a strong finish:
- "To wrap up..."
- "My point here is..."
- "The one thing to remember is..."
The Bow and Arrow
Every communication should have one "Arrow" (the core message).
- The Arrow: A single sentence the audience should remember.
- The Bow: The tension/weight that makes the arrow fly. This is your supporting data, a vivid anecdote, or a personal story.
- Application: For every slide or meeting contribution, ask: "What is my Arrow here?" If you can't name it, don't speak yet.
Conviction Prompts
If you struggle with "Executive Presence," force your brain into a state of conviction by starting sentences with high-stakes phrases. Your brain will naturally fill in the gap with more authoritative content.
- "In fact..."
- "I genuinely believe that..."
- "It astonishes me when..."
Examples
Example 1: Navigating a "Stump" Question in a Meeting
- Context: A stakeholder asks a difficult question about a project delay you weren't fully prepared to answer.
- Input: "Why is the API integration two weeks behind schedule?"
- Application:
- Think Up: Look up to the right for 2 seconds to gather the "Arrow."
- Stay in Character: Do not say "Sorry, I wasn't expecting that."
- Conviction Prompt: Start with "The core reality is..."
- Output: (Looking up thoughtfully) "The core reality is that we prioritized security audits over raw speed. While it's two weeks behind, it prevents a major vulnerability. To wrap up: we are on track for a secure launch by Friday."
Example 2: Preparing an All-Hands Segment
- Context: You have 5 minutes to present the new product roadmap.
- Application:
- Run the Accordion Method. Discover that the 30-second version is: "We are moving from a features-first to a platform-first company."
- Identify the Bow: A story about a customer who couldn't use a specific feature because the platform was too rigid.
- During the talk, use the Arrow as your slide title.
- Output: A talk that feels conversational and "internalized" rather than read from notes.
Common Pitfalls
- The "Safety" Trap: Being monotonous to avoid mistakes. Correction: Allow your energy to fluctuate; use higher intensity for important points and lower intensity for reflections.
- The Script Crutch: Memorizing words instead of ideas. Correction: If you forget a word in a script, you crash. If you internalize a "pillar," you can always find your way back.
- Leaking Insecurity: Explicitly stating that you are nervous or that your answer was poor. Correction: Trust that the audience cannot see your internal state; if you don't mention the "turbulence," they won't notice it.
More from samarv/shanon
agentic-workflow-automation
Transition from static LLM chats to autonomous agents that execute multi-step tasks. Use this when you need to automate cross-platform reports (e.g., Snowflake to Google Docs), build self-service tools for non-technical teams, or create "anticipatory" engineering workflows that draft PRs based on Slack discussions.
62b2b-value-negotiation
A framework for defending price and extracting maximum value in B2B sales. Use this skill when a prospect asks for a discount, when transitioning a POC to a commercial deal, or when presenting high-ticket pricing to budget-conscious stakeholders.
18niche-market-opportunity-mapping
A framework for identifying high-margin, low-competition business ideas ("fishing holes") by leveraging personal unfair advantages and avoiding overcrowded markets. Use this when vetting a new startup idea, choosing a niche for a service business, or seeking to pivot an existing product into a more profitable segment.
16b2b-saas-workflow-strategy
A framework to evaluate the market potential and strategic direction of B2B products based on workflow frequency and organizational breadth. Use it when validating a new startup idea, evaluating a product's "ceiling," or planning a pivot to increase market share.
14agentic-engineering-workflow
Transition from a hands-on "bricklayer" to a high-level "architect" by managing a fleet of autonomous AI agents. Use this when you need to scale engineering output with a small team, handle repetitive migrations/bug fixes, or onboard engineers to complex legacy codebases.
10b2b-category-creation-strategy
A framework for determining when to create a new software category versus winning an existing one, and the tactical steps to define and validate that category. Use this when your product is too disruptive for current labels, when existing categories have negative associations, or when you need to expand your TAM.
9