Using Pleasant Events Scheduling to enhance Calm Company Design

What each one is actually for

Pleasant Events Scheduling

Pleasant events scheduling comes out of Peter Lewinsohn's work on depression and asks you to do something narrow and concrete: pick an activity that used to give you some enjoyment, put it on the calendar at a specific day and time, and then show up and do it — not when you feel ready, not when the mood lifts, but at the time you wrote down. The reasoning is that low mood tends to strip away the desire to do the things that would actually help the mood, so if you wait for the desire to come back first, you can wait indefinitely. Doing the thing on schedule, even joylessly, is what breaks the loop, because completing it is itself the reward that starts rebuilding the appetite for more.

Calm Company Design

Calm company design, the philosophy Jason Fried and David Heinemeier Hansson built at Basecamp, treats most of what makes a workplace feel frantic — the instant-reply chat culture, the meeting called because writing a clear paragraph felt slower, the unspoken rule that looking busy signals commitment — as something the organization chose, on purpose or by default, rather than something the work itself required. The practice replaces those defaults with async ones: written updates instead of live status meetings, a day's grace to answer a message instead of minutes, and blocks of protected time that are treated as real commitments rather than the first thing that gets sacrificed when someone pings you.

What you get out of pairing them

What pleasant events scheduling gives a person in low mood is a way back into feeling better that doesn't require feeling better first — you can act your way there instead of waiting to be moved. What calm company design gives an organization is a version of the same trade at a different scale: instead of waiting for a quieter quarter that never comes, a team decides in advance which hours are protected and defends that decision the way you'd defend an appointment, rather than treating focus as whatever's left over once every interruption has had its turn. Put next to each other, the two show something a person managing their own energy inside a busy company runs into constantly: your personal plan to do something restorative tonight and your employer's plan to protect a focus block this afternoon are the same move, aimed at different clocks, and each one gets easier to hold onto once you can see the other one working the same way.

What Pleasant Events Scheduling rests on

• Small wins compound randomised trials
  Repeating a small consistent action accumulates over time into a result too large to produce in a single step.
• Behavioral activation precedes motivation randomised trials
  Taking action before motivation appears, rather than waiting for motivation to arise first, itself generates the motivation and improved mood that waiting would delay.

What Calm Company Design rests on

• Protected focus time improves deep work observational studies
  Structuring uninterrupted blocks of time protects the conditions required for high-quality cognitive work that fragmented attention otherwise prevents.
• Reducing artificial urgency lowers chronic stress observational studies
  Removing manufactured urgency cues like constant chat and unnecessary meetings and replacing them with async focused-work structures lowers chronic workplace stress.

Where they actually meet

Both practices treat a good intention as something that loses, reliably, to whatever feels most urgent in the moment it's meant to happen — so both take the decision away from the moment. A person in low mood doesn't decide at 6pm whether they feel like calling a friend; they decided on Sunday that Tuesday at 6pm is the call, and Tuesday's mood doesn't get a vote. A team using calm company design doesn't decide, meeting by meeting, whether this one is worth interrupting someone's focus block for; the block was already decided to be protected before this week's urgent-feeling request existed. Same move — pre-commit while calm, then let the pre-commitment overrule whatever the moment wants — aimed at a person's evening in one case and a team's Tuesday afternoon in the other.

The principle underneath both

A commitment made in advance, at a calm moment, and then defended against revision once the pressured moment arrives, survives that pressured moment far more reliably than a decision left open to be made fresh each time. The pressure itself — low mood telling you to skip the call, a colleague's ping telling you this is worth breaking focus for — is real in the moment it occurs. What both practices are betting on is that the calm-moment version of you, or of the team, made a better call than the pressured-moment version will, and the way to make that bet pay off is to remove the pressured moment's ability to re-litigate the decision.

What that makes the real goal

The objective isn't the walk or the phone call, and it isn't the two-hour meeting-free block either — those are just where each practice happens to apply the same move. The actual goal is protecting a decision made under good conditions from being overturned under bad ones, by converting an intention into something scheduled and specific enough that showing up doesn't require a fresh act of willpower each time. Once you see it that way, the objective is separable from either depression treatment or company culture — it's about what makes any pre-commitment survive contact with a moment that doesn't want to honor it.

Other practices that serve the same goal

Implementation intentions — the if-then planning technique of deciding in advance 'if it's 6pm Tuesday, then I call Sam' rather than deciding in the moment — pursue this identical objective and carry some of the strongest controlled-trial evidence in behavioral science for closing the gap between meaning to do something and doing it. Time-blocking more generally, treating calendar slots as commitments rather than suggestions, is the family both practices belong to, and Cal Newport's writing on deep work makes the organizational-scale case in almost the same language calm company design uses, though largely from observation and case study rather than controlled trials. Environmental design — physically removing the phone from the room, closing the chat app during a protected block — attacks the same problem from a different angle: instead of strengthening the pre-commitment, it weakens the moment's ability to interrupt it at all.

A tradition that already does this

The Rule of Saint Benedict, the sixth-century monastic schedule that assigned fixed hours to prayer, manual labor, reading, and rest, was doing organizational-scale pre-commitment centuries before either modern practice existed: the horarium decided in advance, once, what the day looked like, so that no single hour had to be renegotiated against whatever felt most pressing when it arrived. It's a genuine ancestor of the same structural idea calm company design applies to a modern team's calendar, even though the two have nothing else in common.

Using Pleasant Events Scheduling to enhance Calm Company Design

Most calm-company protected time gets defined by what it excludes — no meetings, no chat — which makes it easy to protect on principle and easy to quietly give away in practice, because an empty block has no specific reason to defend. Pleasant events scheduling's contribution is to make the block about something positively chosen rather than merely uninterrupted: instead of a generic 'focus time' slot anyone can talk themselves into sacrificing for one more quick call, assign it a specific piece of work the person actually finds satisfying to do — the part of the job they'd choose if nothing were urgent — the same way the clinical practice insists on a specific, chosen activity rather than a vague plan to 'do something nice.' The concrete move: when a team sets up protected blocks, have each person name, in writing, the one piece of their actual work they find most satisfying, and assign that specific work to the block by name, not just 'deep work' as a category. A block defending a named, wanted thing gets defended harder than a block defending an absence.

Using Calm Company Design to enhance Pleasant Events Scheduling

A pleasant events schedule built for someone whose day is otherwise governed by an urgent, always-on workplace is fighting the exact culture calm company design was built to dismantle — the six o'clock call gets 'just five more minutes' by a Slack message that arrived at 5:58, and the five minutes eats the whole slot. Calm company design's contribution is naming that interruption as a choice rather than a fact of life, and giving a concrete, borrowable practice for defending against it: an explicit personal async default, meaning notifications are checked at set times rather than as they arrive, applied to your own evening the same way a calm company applies it to a Tuesday afternoon. The concrete move: before the scheduled activity, set your own status to unavailable the way a calm-company employee would before a protected block, and treat a message that arrives during the pleasant-event slot as something for tomorrow's list, not a reason to renegotiate tonight.

The Tuesday call you almost let a notification eat

You scheduled a call with an old friend for 6pm on Tuesday, three days ago, back when Tuesday felt manageable. It's 5:55 now, and the week has gone the way weeks go — a colleague pinged you at 5:40 about something that reads as urgent but is really just impatient, and the honest, low-energy version of you wants to answer it, then maybe just reschedule the call, you've talked to Sam plenty this month. Instead you do the thing you decided in advance to do: you silence the notification the way you'd silence it for a real meeting, because the version of you who scheduled this on Sunday knew that 5:55pm-you would want an excuse, and built the appointment specifically so 5:55pm-you doesn't get a vote. Forty minutes into the call you notice you've laughed twice, genuinely, for the first time that day — not because you felt like calling at 5:55, but because you did it anyway, and the wanting showed up after, which is exactly what the Sunday version of you was counting on.

When this is worth reaching for

Someone rebuilding activity after a stretch of low mood also works inside a job where urgency is the whole culture, and the job is winning against the recovery plan more days than it's losing. The same structure helps a manager trying to make protected time actually stick, borrowing from clinical practice a model of why one specific chosen commitment survives the moment better than a vague protected slot does.

Where this does not apply

Pleasant events scheduling is a clinical response to low mood specifically, built on the finding that withdrawal from once-enjoyable activity both reflects and deepens depression; someone who isn't in low mood and simply wants a calmer, less interrupted workplace gets nothing from the clinical framing and should just look at calm company design on its own. And a person whose overwhelm is entirely coming from an organization's chaotic culture — nine meetings a day nobody consulted them about — cannot fix that by rearranging their own personal evening schedule; that's a structural problem one individual's pleasant-events plan has no power over, and the honest move there is to name it as an organizational issue, not a personal-scheduling one.

What the evidence does and does not support

Behavioral activation and pleasant events scheduling specifically have strong randomized-trial support as a treatment for depression, including at least one trial finding scheduled activity roughly equivalent to medication for severely depressed patients. The claim that protected, uninterrupted time improves deep cognitive work and that removing manufactured urgency lowers chronic stress both rest on observational workplace research rather than controlled experiments at company scale — consistent findings, but not causally isolated ones. Nobody has run a study applying clinical activity-scheduling logic to organizational calendar design, or the reverse; the resemblance described here — that both work by pre-committing under calm conditions to overrule a pressured moment later — is a structural argument, not a measured result, and should be read as a reason to try the specific moves above, not as proof they'll work.