You know the work you are supposed to be doing, and you are still building the thing around it instead of having the conversation that would tell you whether anyone wants it. The waiting sentence gives the delay away: I am waiting for ___ before I can ___ because ___. Jess ran that pattern in a Las Vegas hotel room, building a whole cohort before she pitched it, and nobody enrolled. This check runs your own version of that story through the sentence that exposes it, the test that names it, and the commitment check that breaks it.
Step 1: Build your waiting sentence
Stalling sounds like a sentence. Fill in your version of it, one thing at a time.
Or load one of Jess's examples from the episode:
I'm waiting for ___ before I can ___ because ___.
The because is the gate. Permission always hides behind a gate that sounds reasonable.
Step 2: Remove the gate. Run the test.
Take the gate out. If you decided to have the conversation anyway, could you? Answer honestly, not bravely.
Step 3: The commitment check
Name the conversation you have been avoiding. Then write what you would do if they said yes, specifically. Not the perfect version. The real version, with the commitments you already have.
One of three things happens when you have it: you realize you can commit, and that is data. You realize you cannot right now, and that is boundaries. Or they say no, and that is information. All three beat waiting in permission land forever.
Step 3: Say it out loud
This isn't the time. Name what you are protecting, and let the boundary stand without the guilt.
0 of 3 steps done.
It doesn't come from waiting, it comes from moving. You are the only one who can decide whether it is time to move or time to rest.
FAQ
What is permission seeking?
It looks like strategy. Jess calls it permission seeking: you use a requirement, a gate, or a prerequisite that needs to be true first to delay having a conversation or taking the next step you are already ready to take. It feels smart, protective, and intentional. What it actually does is keep you building things in isolation and wondering why they don't land when you put them out publicly. It keeps you from the feedback that tells you whether the thing you are building is the thing the market wants, and it keeps you waiting for internal certainty that only comes from external conversations. The cost is momentum and data, not time. It is the difference between guessing and knowing.
What is the 3-1-2 sequence, and what replaces it?
The 3-1-2 sequence is the default order: build the infrastructure first, put it out there, and hope the revenue validates it. Jess calls it the field of dreams play, and it fails because the build happens in isolation, with no feedback about whether the thing is what people actually want. The flip is 1-2-3: conversations and relationships first, validation second through an attraction event, a wait list, a pilot, or a down payment, and infrastructure third, built from real data about what people asked for. The difference is building something people want, instead of building something in hopes that they want it.
How do I tell stalling from a real season?
Remove the gate and ask whether you could have the conversation anyway. Could you pitch without the sales page? Could you validate demand without the perfect, fully fleshed-out infrastructure? If the answer is yes, but it would feel scary or premature, that is stalling. If the honest answer is that you cannot take on one thing more right now, that is a season. The two look identical from the inside and require completely different responses. Stalling requires movement through fear. Seasons require rest and protected boundaries. You can't do either one until you know which one is true.
What does a real gate look like?
A real gate looks like a season that is actually too full: the bandwidth is not there, and you are not supposed to be building the thing right now. Not every reason is a delay built out of fear. Jess's example starts last November, when her mom went to the ER and was diagnosed with stage two lymphoma, and the first half of the year that followed was appointments, chemo, and hospitalizations that included falls and sepsis. The honest sentence for a season is "I cannot take on one thing more right now," and the fix is protecting the boundary instead of feeling guilty about it.
What is the commitment check?
It is the exercise that breaks the permission cycle. Identify the conversation you have been avoiding, a pitch, a follow-up, a hey I'm thinking about this offer, would it be valuable to you. Then write down what you would do if they said yes, specifically. Not the perfect version with unlimited time and energy. The real version, with the commitments you already have. Jess's example: this cohort starts on Tuesday, September eighth, at 2 p.m. Central time and runs for eight weeks, with what happens each week named. One of three things happens when you have the conversation: you realize you can commit, and that is data. You realize you cannot right now, and that is boundaries. Or they say no, and that is information. All three beat waiting in permission land forever.
Why does building first feel like progress?
Because building is something you can control, and nobody has asked for anything yet, so there is no rejection to face. For people who think fast and move even faster, infrastructure feels like doing something instead of just talking about it. The problem shows up later: by the time the thing reaches real people, so much emotion and energy is invested in the wrong thing that pivots feel impossible. Jess's read is that the people moving faster than you are not braver, more confident, or less thoughtful. They got permission from other people. They had the conversation and did not set an internal standard first.
Go deeper
In Episode 28, Jess tells the Las Vegas story: the four-day conference, the hotel room, the 12-week framework built in eight to ten hours, the good reactions, and zero enrollments. She contrasts it with an earlier free experience, a tasting menu before the full meal, that gave her real-time feedback and commitments to the next step. The episode names the waiting sentence, the 3-1-2 sequence, the could-you test, and the commitment check, and it draws the line between stalling and a real season with the story of her mom's illness and the bandwidth constraints that came with it. The tool above runs the check for you. The episode tells you why the conversations come first.
Listen to Ep 28: You're Not Behind (You're Just Waiting for Permission)
"Permission only comes from other people, and you have to go ask."
Related
- Episode 32: The Advice Wasn't Wrong. (Your Conditions Were Different.) The could-you test is a conditions question. Episode 32 runs the fuller check: time, body, and environment, before you adopt what a room hands you.
- Episode 29: Rest Isn't Stillness (What High Capacity Brains Actually Need) The season side of the test. When rest is the move, and how to tell what actually restores you from what only looks like rest.
- Episode 10: Stop Thinking. Start. (The One Move That Closes the Gap) One conversation with one safe person, the unfinished version out loud. The language gets dialed in through the conversation, not before it.
Big Ideas Made Simple is a weekly podcast for entrepreneurs and fast thinkers building a business around who they are and how they operate. Hosted by Jess Webber. New episodes Mondays at bigideasmadesimple.captivate.fm.
Get the next one
Got your result? Get the next idea like it each week.
Three steps. About 20 minutes. Type everything on your mind, answer two questions about each one, and see what to keep, hand off, protect, and drop this week. You get the sheet right away, plus my weekly email afterwards.
