Concepts
The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types
Offer alternative times instead of justifying your focus…
When defending peak attention hours against meeting requests, offer alternative times outside your blocked window rather than explaining or justifying the block itself.
Above 0.85 capacity, counter-offer new requests…
When your commitment-to-capacity ratio exceeds 0.85, respond to new requests with explicit counter-offers stating either a later start date or a specific trade-off rather than accepting or declining without alternatives.
Signal capacity proactively with operational language…
Design capacity signals with neutral, operational framing (traffic light status, numerical availability) rather than emotional or complaint-based language, delivering them before requests arrive rather than as request-time justifications.
When overloaded, ask the requester
When utilization exceeds 85% and a high-stakes request arrives, respond with the trade-off question format: 'If I add this, which of my current commitments should I deprioritize?' directed to the requester with decision authority.
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.
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.
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.