Rules
1,053 rules · page 15 of 22
Articulate your values before asking AI for values-related…
Before using AI for values-related decisions, articulate your values and hierarchy explicitly—then use AI to generate arguments from your stated values' perspective rather than accepting AI recommendations as substitute values.
Difficulty without depletion confirms values alignment…
When values-aligned work produces difficulty without depletion, interpret sustained difficulty as confirmation of alignment rather than signal to quit—genuine alignment enables voluntary acceptance of costs.
Strong resistance despite logical alignment signals…
When a decision activates strong emotional resistance despite logical alignment with stated values, use the resistance intensity as a signal to examine whether an unstated value or identity concern is operating below conscious awareness.
Three components of an effective boundary
State boundaries with three explicit components—the specific limit, the consequence of crossing it, and clear communication to the other person—rather than expressing vague preferences.
Override the fixing reflex for unfixable suffering…
When witnessing unfixable suffering, override the fixing reflex by repeatedly returning attention to the person's face, voice, and body language rather than your own internal planning, to maintain presence without absorption.
Calculate activity cost as disruption footprint
When calculating whether an activity is worth your energy, include not just its duration but its disruption footprint—the ramp-down before, the activity itself, and the ramp-up after—to account for attention residue costs.
Convert infinite information activities into finite ones…
Set time-bounded windows for information consumption (email twice daily, news once for 15 minutes) rather than open-ended consumption, converting infinite activities into finite ones with natural stopping points.
Pre-define information boundary overrides — real-time…
Define explicit override conditions for information boundaries in advance (on-call status, time-sensitive requests from key people) rather than negotiating exceptions in the moment when anxiety will generate spurious justifications.
Acknowledge, boundary, alternative — this three-part…
Frame relational boundaries using the three-part structure: acknowledge the request, state your boundary with the value it protects, and offer an alternative, rather than leading with rejection.
Boundaries are rules about YOUR behavior, not demands…
State relational boundaries as rules about your own behavior in response to others' actions ('I will leave the room if voices are raised') rather than as demands about others' behavior ('You are not allowed to yell'), preserving their sovereignty while protecting yours.
Set boundaries when the pattern emerges…
Communicate relational boundaries early when patterns emerge rather than accumulating resentment until delivering them as emotionally-charged ultimatums, because delayed boundaries appear as ambushes to the other person.
Enforce boundaries consistently — inconsistent…
When a stated boundary is violated, follow through with the pre-specified consequence consistently, as inconsistent enforcement teaches others that your boundaries are negotiable and undermines all future boundary-setting.
Write what your role includes AND excludes — default…
Define professional scope boundaries by writing what your role explicitly includes and excludes, then default to 'no' for requests falling outside that scope unless you consciously choose to make an exception.
Frame professional boundaries as quality commitments…
Frame professional boundaries as commitments to work quality rather than confessions of personal weakness ('To protect the architecture review, I'm limiting meetings to 15 hours per week' vs 'I have too many meetings'), because quality-based framing generates respect while capacity-based framing generates sympathy.
Surface trade-offs with forced-choice
When receiving requests that don't map to your top three priorities, use the forced-choice formula 'I can do X or Y this week—which matters more to you?' to surface tradeoffs rather than silently absorbing both demands.
Graduate your refusals
Match the strength of your 'no' (soft/firm/hard) to both the severity of the boundary violation and the history with that person, using soft no for first occurrences, firm for patterns, and hard for core integrity violations.
Use natural consequences, not punitive ones — 'if scope…
Pair boundary statements with natural consequences rather than punitive ones ('If scope expands, timeline extends' vs 'I will be angry'), allowing reality to operate rather than imposing penalties.
Escalate from behavior description to pattern-naming…
When someone repeatedly violates a clearly stated boundary, escalate from describing the behavior to naming the pattern ('I've mentioned several times that...') before consequences, as pattern-naming often produces adjustment where single-instance feedback did not.
Audit commitments as actively chosen vs. passively…
Conduct a resource audit by categorizing recent commitments as actively chosen versus passively absorbed, then calculate total hours consumed by passive absorption to make your boundary deficit visible before attempting to change it.
Resentment signals unacknowledged boundary violations…
Track resentment as a signal of unacknowledged boundary violations rather than a character flaw, because resentment specifically marks the accumulation of costs you absorbed without agreeing to bear them.
Rebuild boundary capacity through small wins first — after…
When learned helplessness has developed from repeated boundary failures, rebuild boundary-setting capacity through very small, low-stakes boundaries with high probability of enforcement before attempting major ones.
When the org rewards boundarylessness and punishes…
In organizations that systematically reward boundaryless output while punishing friction, recognize the selection pressure as structural rather than personal and design exit or protection strategies accordingly, because the system will not change before it depletes you.
Is post-boundary guilt moral feedback or compliance…
When guilt arrives after setting a boundary, apply a diagnostic question: 'Is this guilt moral feedback about genuine harm I caused, or is it the emotional residue of a compliance pattern I am outgrowing?' to distinguish between guilt carrying genuine moral information and guilt as conditioned response.
Situation-Impact-Request
Communicate boundaries using three-component structure: (1) non-judgmental description of situation, (2) impact on you using 'I' language, (3) specific behavioral request the other person can act on—rather than character judgments or vague wishes.
Use the broken record technique for boundary testing…
When a boundary you've stated clearly is being tested through persistent requests, use the broken record technique: calmly repeat your boundary statement in identical words without adding new arguments, justifications, or escalation—the repetition itself removes footholds for continued negotiation.
Pre-write responses to 3-5 predicted boundary tests…
When setting a new boundary, predict and document 3-5 specific ways people will test it (who will test, what form tests will take) and pre-write your planned responses before tests arrive, because anticipating tests converts surprise into expected system behavior you've already decided how to handle.
The first 3-5 days after a new boundary are non-negotiable…
During the first 3-5 days after setting a boundary, maintain absolute consistency without exceptions regardless of pressure, because this initial period is when extinction burst testing is most intense and any capitulation during this window trains others that sufficient escalation will produce the old response.
Log every boundary test
After each boundary test, log what happened (who tested, how, what you did, how it felt) in an external system to build a dataset revealing patterns invisible from inside—which relationships produce most testing, which test types are hardest for you to withstand, whether your consistency is actually consistent.
State both the exception AND the return date
When adjusting a boundary for legitimate contextual reasons (genuine emergency, changed circumstances), explicitly state both the adjustment and the return timeline: 'I'll help with this through Friday, and then the original boundary resumes'—to prevent temporary exceptions from becoming permanent erosion.
Upgrade commitment enforcement to Level 3+…
Structure commitments at enforcement Level 3 or higher (environmental modification, social contract, or structural impossibility) rather than Level 1-2 (intention or implementation intention alone) when the commitment is irreversible, high-stakes, or has failed three or more times on willpower.
Repair boundary violations within 24 hours
When a boundary violation occurs with another person, initiate repair within 24 hours using the three-step sequence: acknowledge the violation explicitly, reassert the boundary without softening, and address the practical or emotional cost the violation created.
First violation
After the first boundary violation by the same person, conduct repair with clearly stated consequences; after the second violation, enact the stated consequences rather than issuing new warnings, to distinguish boundary flexibility from boundary erosion.
Leaders
When you hold positional authority or high status within a group, prioritize modeling boundaries over communicating boundary policies, because your visible behavior establishes the actual permission structure more powerfully than stated rules.
Self-censorship in conversation signals a boundary deficit…
When you notice yourself censoring thoughts or managing another person's emotions during conversations, use that observation as a diagnostic signal that the relationship lacks sufficient boundaries to support honest exchange, then design one boundary that would enable you to speak more freely.
After commitment failure, diagnose within 48 hours
When a commitment fails, conduct the diagnostic protocol (identify failure trigger, locate decision point, match structural support to vulnerability type, install before next instance) within 48 hours rather than treating failure as evidence of insufficient willpower.
Calibrate commitment device strength to your failure…
Match the binding strength of commitment devices to the documented severity and frequency of past failures in that domain, using hard pre-commitments (physical impossibility or high cost) only for behaviors with long track records of in-the-moment failure.
Public commitments must be behavioral + verifiable…
Structure public commitments as behavioral specifications with verification mechanisms rather than identity declarations, because identity-based announcements produce premature satisfaction that reduces subsequent effort while behavioral commitments create accountability pressure.
Place commitment reminders where breakdowns happen…
Place written commitments in the physical or digital location where the breakdown typically occurs rather than in convenient filing locations, because visibility at the decision point creates structural friction that memory-based retrieval cannot provide.
Layer multiple commitment mechanisms for high-failure…
For recurring commitments with documented histories of failure, install multiple reinforcing commitment layers (pre-commitment + device + public accountability + implementation intention) rather than relying on any single mechanism, because commitment failures typically result from alignment of multiple weaknesses not single-point vulnerabilities.
Choose accountability partners for enforcement capacity…
Select accountability partners based on their demonstrated willingness to enforce rather than their social proximity, because enforcement capacity (asking hard questions, refusing rationalizations) determines accountability effectiveness while social closeness often reduces willingness to challenge.
For novel goals, generate multiple if-then plans covering…
When forming implementation intentions for novel or complex goals, generate multiple if-then plans covering different potential breakdown contexts rather than relying on a single anticipated trigger, because breakdown patterns in unfamiliar domains cannot be predicted accurately from first principles.
Check-in with evidence ('did/didn''t on these days')…
Format public commitment check-ins as evidence-based reports ('I did/didn't do X on these specific days') rather than narrative explanations ('I tried hard but...'), because evidence-based formats prevent rationalization at the reporting layer while narrative formats invite it.
A commitment contract needs five elements
Write commitment contracts with all five structural elements (behavior, schedule, completion criteria, duration, signature) and treat any commitment missing one or more elements as a preference rather than a binding commitment.
Maximum 1-3 active implementation intentions at a time…
Limit active implementation intentions to 1-3 simultaneously for novel behaviors, adding additional if-then plans only after existing ones have compiled into automatic execution, because cue-accessibility mechanisms have finite attentional capacity.
When your anchor behavior changes context, immediately…
When an anchor behavior's context changes (time, location, or sequence), immediately redesign dependent stacked commitments rather than expecting them to survive the anchor disruption.
One new stacked commitment per month maximum — overloading…
Stack only one new commitment per month onto existing anchors to prevent chain overload that converts working infrastructure into brittle sequences.
Commitment thresholds must be binary — 'done' or 'not…
Specify commitment thresholds as clear boundaries that separate 'done' from 'not done' without requiring interpretation, eliminating the space for rationalized partial compliance.
Budget commitments on two dimensions
Track both time cost (hours per week) and cognitive cost (mental bandwidth on 1-5 scale) for each active commitment when budgeting capacity.