The Lojong Reversal: Why Tibetan Monks Practiced Wanting What They Dreaded
In 11th-century Tibet, Atisha Dipankara brought 59 mind-training slogans from India to Reting Monastery that would seem absurd to modern professionals: "Be grateful to everyone," including those who undermine you. "Drive all blames into one," meaning yourself. Most puzzling: "Regard all dharmas as dreams," then live as if your actions matter completely.
These weren't platitudes. Lojong was cognitive rewiring through practiced contradiction, developed specifically for householders and workers—not monks in caves. The slogan that reveals its utility for modern work is often mistranslated: "When the world is filled with evil, transform all mishaps into the path of bodhi." The Tibetan word "nyampa" doesn't mean generic evil—it means specifically the obstacles that block your intended path.
Here's what makes Lojong distinct from mindfulness or Stoic acceptance: you don't observe difficulties neutrally or reframe them positively. You actively practice desiring them.
The Practice of Obstacle Hunger
Geshe Chekawa, who systematized these slogans in the 12th century, instructed students to begin each work period by identifying what they hoped wouldn't happen. Not vague anxieties—specific, probable obstacles. The colleague who derails meetings. The client who demands unpredictable revisions. The technology that fails during presentations.
Then came the reversal: spend three breaths generating authentic curiosity about encountering precisely that obstacle today. Not "I accept this might happen" but "I am specifically interested in whether this happens."
This wasn't positive thinking. Students were told to examine how much of their energy was spent constructing elaborate obstacle-avoidance systems—which meetings to skip, which clients to evade, which technologies to over-prepare. Chekawa observed that this avoidance architecture consumed more resource than the obstacles themselves.
Why This Addresses Resource Prioritization Differently
Modern resource prioritization typically asks: "What matters most?" We rank initiatives, protect high-value time, eliminate low-leverage activities. The implicit assumption: optimal allocation means maximum obstacle avoidance.
Lojong suggests that obstacle avoidance itself is the resource leak. Every backup plan, every redundant system, every political maneuver to prevent difficulty—these don't just consume resources, they multiply the obstacle's power by confirming it as something that must be avoided.
The 16th-century commentary by Konchog Gyaltsen notes that Tibetan merchants who practiced Lojong specifically on customer disputes stopped maintaining extensive records to protect themselves from claims. Not recklessly—but they reallocated the energy from documentation systems to the actual relationships that made disputes rare. When disputes did arise, they were resolved faster because neither party was defensive; the merchant had already practiced wanting that exact conversation.
From Theory to Friction
This practice falls apart without specificity. "Wanting obstacles generally" becomes spiritual bypassing. The instruction is: name the obstacle you're avoiding tomorrow. The specific person, technology, or constraint.
Longchenpa's 14th-century refinement added: notice what you've already built to avoid this. Not to dismantle it necessarily, but to see its cost. The developer who maintains three redundant testing environments because deployment broke once. The manager who CC's everyone because one stakeholder felt uninformed. The consultant who over-scopes every proposal because a client once added requirements.
Ask: what resource would you recover if you practiced curiosity about the thing you're armoring against?
The Lojong approach isn't eliminating preparation—it's questioning whether your obstacle-avoidance architecture costs more than direct engagement with obstacles when they arrive.
Practice This Week
Tomorrow morning, before starting work, write one sentence: "Today I'm specifically interested in whether [exact obstacle] occurs."
Not "I'm prepared for" or "I accept that." Use "interested in whether."
Don't change your behavior. Just notice throughout the day: how much energy are you spending tracking whether this obstacle is approaching? What are you not doing because those sensors are running?
By Thursday, add one question: "What did I build this month primarily to avoid [this obstacle]?" A process, a meeting, a communication protocol, a technical system.
Calculate: if the obstacle happened once monthly and took two hours to handle directly, versus the continuous cost of the avoidance system, which consumes more?
This isn't about welcoming disasters. It's Chekawa's actual point: we often feed our obstacles more resources through avoidance than they could ever consume through occurrence.
These weren't platitudes. Lojong was cognitive rewiring through practiced contradiction, developed specifically for householders and workers—not monks in caves. The slogan that reveals its utility for modern work is often mistranslated: "When the world is filled with evil, transform all mishaps into the path of bodhi." The Tibetan word "nyampa" doesn't mean generic evil—it means specifically the obstacles that block your intended path.
Here's what makes Lojong distinct from mindfulness or Stoic acceptance: you don't observe difficulties neutrally or reframe them positively. You actively practice desiring them.
The Practice of Obstacle Hunger
Geshe Chekawa, who systematized these slogans in the 12th century, instructed students to begin each work period by identifying what they hoped wouldn't happen. Not vague anxieties—specific, probable obstacles. The colleague who derails meetings. The client who demands unpredictable revisions. The technology that fails during presentations.
Then came the reversal: spend three breaths generating authentic curiosity about encountering precisely that obstacle today. Not "I accept this might happen" but "I am specifically interested in whether this happens."
This wasn't positive thinking. Students were told to examine how much of their energy was spent constructing elaborate obstacle-avoidance systems—which meetings to skip, which clients to evade, which technologies to over-prepare. Chekawa observed that this avoidance architecture consumed more resource than the obstacles themselves.
Why This Addresses Resource Prioritization Differently
Modern resource prioritization typically asks: "What matters most?" We rank initiatives, protect high-value time, eliminate low-leverage activities. The implicit assumption: optimal allocation means maximum obstacle avoidance.
Lojong suggests that obstacle avoidance itself is the resource leak. Every backup plan, every redundant system, every political maneuver to prevent difficulty—these don't just consume resources, they multiply the obstacle's power by confirming it as something that must be avoided.
The 16th-century commentary by Konchog Gyaltsen notes that Tibetan merchants who practiced Lojong specifically on customer disputes stopped maintaining extensive records to protect themselves from claims. Not recklessly—but they reallocated the energy from documentation systems to the actual relationships that made disputes rare. When disputes did arise, they were resolved faster because neither party was defensive; the merchant had already practiced wanting that exact conversation.
From Theory to Friction
This practice falls apart without specificity. "Wanting obstacles generally" becomes spiritual bypassing. The instruction is: name the obstacle you're avoiding tomorrow. The specific person, technology, or constraint.
Longchenpa's 14th-century refinement added: notice what you've already built to avoid this. Not to dismantle it necessarily, but to see its cost. The developer who maintains three redundant testing environments because deployment broke once. The manager who CC's everyone because one stakeholder felt uninformed. The consultant who over-scopes every proposal because a client once added requirements.
Ask: what resource would you recover if you practiced curiosity about the thing you're armoring against?
The Lojong approach isn't eliminating preparation—it's questioning whether your obstacle-avoidance architecture costs more than direct engagement with obstacles when they arrive.
Practice This Week
Tomorrow morning, before starting work, write one sentence: "Today I'm specifically interested in whether [exact obstacle] occurs."
Not "I'm prepared for" or "I accept that." Use "interested in whether."
Don't change your behavior. Just notice throughout the day: how much energy are you spending tracking whether this obstacle is approaching? What are you not doing because those sensors are running?
By Thursday, add one question: "What did I build this month primarily to avoid [this obstacle]?" A process, a meeting, a communication protocol, a technical system.
Calculate: if the obstacle happened once monthly and took two hours to handle directly, versus the continuous cost of the avoidance system, which consumes more?
This isn't about welcoming disasters. It's Chekawa's actual point: we often feed our obstacles more resources through avoidance than they could ever consume through occurrence.