Obstacle Function Review¶
Method — instantiates Self-Handicapping Disruption
Examines what the obstacle protects, what it costs, whether it is real or modifiable, and what support or boundary would make effort safer.
Obstacle Function Review treats a barrier — a delay, an overcommitment, a vague "I'm blocked" — as a functional signal rather than a moral defect, and takes it apart before anyone changes their behavior. The single idea that makes it this mechanism: it asks what the obstacle is doing — which painful interpretation of failure it shields, what it costs, whether it is a real constraint or a modifiable protective ambiguity, and what support or boundary would let effort feel safe. It is a diagnosis run upstream of effort, not a way of responding to finished work, and it lives or dies on refusing to moralize while still telling the difference between a real barrier and a self-protective one.
Example¶
A product lead keeps volunteering for firefighting and side projects in exactly the weeks before each major launch, then arrives underprepared. His manager runs an obstacle function review instead of a reprimand. What does the busyness protect? A weak launch can be blamed on overload rather than on his judgment. Is the overload real? Partly — two genuine incidents landed on him; partly self-assigned. What is the protective story? "I'd have nailed it if I hadn't been slammed." What support or boundary would make focused effort safe? A protected two-week runway before launch and an explicit no-new-projects rule during it. The review ends by splitting the barrier: the real slice becomes a staffing problem to solve directly, and the protective slice gets a boundary — without ever calling him an excuse-maker.
How it works¶
- Name the function. Ask what identity or worth the obstacle shields, stated as a hypothesis, not an accusation.
- Run the reality test first. Separate genuine workload, access, safety, or fairness constraints from modifiable protective ambiguity; when in doubt, treat it as real.
- Surface the protective story. Draw out the sentence the obstacle keeps available ("the conditions made it impossible") so it can be examined rather than acted on silently.
- Prescribe support or boundary. Specify the concrete resource or limit that would make trying feel safe.
Tuning parameters¶
- Probe depth — how hard to press on the protective story vs. respect privacy; deeper surfaces more, but can tip into interrogation.
- Real-constraint threshold — how much evidence before labeling a barrier real; set high in structurally unequal settings to avoid mislabeling.
- Who runs it — self-review vs. a trusted third party; a third party sees blind spots but raises the threat.
- Remedy bias — support-first vs. boundary-first; support enables, boundaries protect, and most cases need some of each.
When it helps, and when it misleads¶
Its strength is that it catches the archetype's worst failure mode before it happens: mislabeling a structural barrier — a resourcing gap, a discriminatory condition — as self-handicapping.[n1] Its own failure mode is the mirror image: the review can slide into an accusation ("so you're just making excuses"), which intensifies the very pattern it means to disrupt, or it can over-attribute a genuine constraint to "protection." The classic misuse is running it to someone as a disciplinary tool rather than with them as a diagnosis. The guarding discipline is that the reality test comes first and the stance stays functional, not moral — the obstacle is asked what it accomplishes, never whether it is shameful.
How it implements the components¶
protective_obstacle— its object of study: it reads the barrier as a functional signal to be understood, not punished.real_constraint_check— the reality test that separates genuine barriers from modifiable protective ambiguity is its central safeguard.protective_story_probe— it surfaces the self-protective narrative the obstacle keeps alive so the narrative can be examined.support_requirement— it ends by naming the concrete support or boundary that would make effort safe.
It stops at diagnosis; it does not shape how feedback lands on the work — keeping the person separate from the result via identity_performance_separation and revision_path is the job of its method-twin process_focused_feedback.
Related¶
- Instantiates: Self-Handicapping Disruption — supplies the upstream diagnosis that distinguishes real constraints from protective obstacles.
- Sibling mechanisms: process_focused_feedback · safe_accountability_check_in · low_stakes_draft · private_commitment_window · effort_tracking_rubric · failure_debrief_without_global_label · low_stakes_rehearsal
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Obstacle Function Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it examines what the obstacle protects, what it costs, whether it is real or modifiable, and what support or boundary would make effort safer.
Independent corroboration: The frozen evidence defines Obstacle Function Review as 'Examines what the obstacle protects, what it costs, whether it is real or modifiable, and what support or boundary would make effort safer', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Psychology
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Behavior analysis and clinical psychology developed functional assessment that asks what a behavior or obstacle accomplishes and what contingencies maintain it before attempting removal.
Related originating lineages:
- Education & Pedagogy — Coaching and learner-support practice contributes converting the diagnosis into support, boundary, and next-effort design.
Review resolution: Both independent reviews agree on primary origin psychology; reconciliation resolves alternate_origin_disagreement. Formative alternate lineages retained: education_pedagogy. The broader reach of later applications is kept separate as domain_reach=multi_domain; origin_mode=single_lineage describes the historical relationship among lineages. Confidence is conservatively reconciled to high, and encyclopedia_synthesis=true preserves the reviewers' boundary judgment.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] In behavior analysis, a functional analysis asks what a behavior accomplishes for the actor — what maintains it — rather than whether it is good or bad. Reading a protective obstacle by its function, not its morality, is the same move, and it is what keeps the review from becoming a verdict. ↩