Someone joins your program fired up. They sit down to record their first video, hit the button — and everything they planned to say vanishes. Not because they didn't understand the assignment. Because the gap between "I get this in theory" and "I can perform this on command" is exactly where most people quietly quit, and most creators never build anything to catch them there.1 Krisang names this precisely: at the effort stage of the journey he maps from Bharata Muni's five states of action, "you start recording a video, you click the button, and all of a sudden everything you planned goes blank."1
His prescription is specific and runs against a common instinct. "You can't tell people what to do and forget about it," he says. "You have to tell them what to do and then help them with everything that is stopping them from doing it."1 That second half is the actual job. It's not enough to hand someone an instruction — quit sugar, record daily, launch the product. The creator's real work, in his framing, is to enumerate every specific obstacle a person will hit while trying to follow that instruction, in advance, and have an answer already built before they need it.1 His own example: people going blank on camera is such a predictable failure point that his program has a named countermeasure ready for it — a technique he calls stream-and-shape, built specifically to stop someone from freezing when the record light comes on.1
The distinction matters. A creator who reacts to obstacles as they surface is running a help desk — responsive, but always one step behind, and every stuck student feels like a surprise. A creator who has already mapped the failure points is running something closer to a minefield-cleared path — the obstacle still exists, but it's been anticipated and defused before the person walking it even notices it was there.1 Krisang frames this as fundamental empathy work, not just tactics: "it doesn't matter how good your solution is if you don't have empathy for what they are going through."1 The prediction only works if it's built from genuinely imagining the specific mental script running in someone's head at each stage — what are they thinking, what question are they actually asking themselves — rather than assuming your own experience of the obstacle generalizes.
You're building a course or a content-creation program. Before you write a single lesson, sit down and walk through your own instructions as if you were a brand-new student with none of your accumulated fluency. At each step, ask: where, specifically, would I freeze? Not "might someone struggle here" in the abstract — name the literal moment. For a recording instruction, it's the blank mind at the record button. For a pitch instruction, it might be the sentence where you have to name your own price out loud for the first time.
For each frozen moment you find, build the countermeasure before you publish the lesson that creates the obstacle — a technique, a script, a reframe, something concrete a stuck person can reach for in that exact second. Ship the instruction and the countermeasure together, not the instruction alone with a promise of support if someone asks. Most people who freeze don't ask. They just quietly stop.
Krisang connects this directly to a completion-rate figure: where typical online courses see 2-3% completion, his programs run 90-100%.1 He attributes the gap specifically to this practice — never handing out information without also handing out the obstacle-clearing that makes the information usable in the moment it's needed, rather than assuming motivation alone will carry someone across a predictable gap.1 The claim is self-reported and unverified by outside data, but it's offered as the direct, causal payoff of the predict-in-advance discipline this page documents.
Evidence: This is Krisang's own stated teaching practice, illustrated with one named technique (stream-and-shape) and one self-reported completion-rate comparison.1 No independent verification of the completion-rate figures is available from this source.
Tensions: There's a real limit to how far obstacle-prediction can scale — the more diverse an audience, the more individual, unpredictable failure points exist that no amount of advance mapping will catch. Krisang's own material doesn't address what happens when a student hits an obstacle nobody anticipated; the framework as stated assumes the creator's own experience and small-group observation is enough to map the territory, which works better in small, closely-mentored cohorts than at true broadcast scale.
Open question: Is there a point of diminishing returns where obstacle-prediction becomes over-engineering — solving problems for people before they've had the productive struggle of discovering the problem themselves? Krisang's own five-stage model (documented on the sibling page) treats effort and struggle as necessary for the hero to "discover what they're capable of" — which sits in mild tension with removing every obstacle before the person meets it.
This page's obstacle-mapping practice sits directly inside the five-stage action journey Krisang teaches elsewhere in the same talk — see Five Karya-Avasthās for the full architecture this technique is embedded in. That page documents the stages audiences pass through; this page documents the specific creator discipline — enumerate and pre-solve obstacles — that applies most directly at the Prayatna (effort) stage, the second of the five. Read as a pair rather than duplicated: the sibling page is the map, this page is one specific tool for surviving the roughest terrain on it.
Business — Solar Entry-Point Onboarding. This business-domain page documents a structurally identical design instinct from the operator side: a newcomer facing a large, potentially overwhelming framework needs a deliberately sequenced, simplified entry point, or the overwhelm itself becomes the failure point that stops them before they start. Krisang's obstacle-prediction practice and Solar Entry-Point Onboarding are solving adjacent problems at different points in the same journey — the business page addresses the very first friction point (an overwhelming amount of material), while Krisang's practice addresses obstacles distributed throughout the middle of the journey (the effort stage, specifically). Neither page alone covers the full arc: the business page's onboarding thinking doesn't extend past the first-step problem, while Krisang's practice doesn't say much about how to design the entry itself, only how to survive what comes after entry is granted. What the pairing actually buys the reader: a complete journey design needs both disciplines running simultaneously — a simplified, staged front door (Solar Entry-Point Onboarding's contribution) feeding into a continuously obstacle-mapped middle (Krisang's contribution) — and a program that nails one without the other will lose people either at the threshold or partway through, depending on which discipline is missing.
Behavioral-Mechanics — Objection-Handling Five-Step Formula. This behavioral-mechanics page documents a sales-context version of the same anticipate-before-it-surfaces logic — a structured method for handling objections a prospect raises before or during a close. The surface-level parallel is obvious (both are about not being caught flat-footed by resistance), but the deeper, more useful distinction is in when the anticipation happens. The objection-handling formula is largely reactive-but-rehearsed: it prepares the seller to respond well once an objection is voiced. Krisang's practice is further upstream — it tries to prevent the obstacle from ever fully forming into a voiced objection at all, by building the solution into the instruction itself before the student even reaches the friction point. Neither page alone gives the complete toolkit: a creator who only has Krisang's upstream prediction will still occasionally be blindsided by an objection nobody anticipated and needs the reactive formula as a backstop; a seller who only has the reactive formula is accepting more lost prospects than necessary, because some resistance could have been designed away entirely before the conversation started. Line the two up and a sharper claim appears: obstacle-handling exists on a spectrum from fully-reactive to fully-preventive, and the two pages mark opposite ends of a single continuum that most real practice should occupy somewhere in the middle of.
Sharpest implication: If completion and conversion really do track how thoroughly a creator has pre-mapped obstacles rather than how good the core content is, then most content-quality debates in the creator economy are arguing about the wrong variable — the differentiator isn't the idea, it's the density of anticipated friction-points solved in advance.
Generative questions: