Mutual Aid and Human-Centered Learning for Neurodivergent and Disabled People

Pattern 26 — Sustainable Pace

Home » The Pattern Language of Neurodivergent Life » Pattern Library » Pattern 26 — Sustainable Pace

Intent

Let people work and learn at the rate that actually produces their best work, and treat variation in rate as ordinary rather than as being behind.

The Pattern

This pattern is about rate, not rhythm. That distinction is what keeps it from collapsing into the two patterns beside it.

Recovery cycles are about oscillation — effort, then restoration. Energy debt is about balance — not borrowing from tomorrow. Sustainable pace is about the speed itself: how fast a person moves through work or learning when nothing is going wrong.

Our own developmental pace entry states the case in an educational register, and the argument generalises intact. Pace is the rate at which a person arrives — at a skill, a concept, a capacity — and it varies enormously between people, and within one person across different domains.

School treats it as a fixed background condition: children grouped by birth date, taught the same content at the same time, and marked on the distance between where they are and where the timetable says they should be. That distance gets recorded against the child.

“Behind” is information about the ruler, not about the learner.

Workplaces do the same thing with a different vocabulary. Slow, dragging, not keeping up, low throughput. Each is a measurement against a cadence somebody chose, presented as a property of the person.

And pace is not one number. A person can be fast at one thing and slow at another, quick to understand and slow to produce, or the reverse. A single speed rating averages across domains that have nothing to do with each other — which is Average User Fallacy applied to time.

The practical form is intermittent collaboration: deep solo stretches at whatever tempo the work and the person require, with periodic exchange. It lets a group coordinate without forcing everyone onto the cadence of its meetings.

Why It Matters

When one rate is assumed, people may:

be assessed on speed when the work was never about speed
produce worse results rushing than they would have produced slowly
be described as behind by a schedule they had no part in setting
hide how long something actually took
lose the depth that their slower rate was buying
conclude they are less capable than they are

The output was available. The tempo was not negotiable.

Forces

Coordination is easier when everyone moves at one speed.
Rate varies between people and within a person by domain.
Speed is easy to measure and quality is not.
A standard cadence advantages whoever set it.
Going faster than your rate degrades the work invisibly.
Deadlines are real, and some of them are genuinely fixed.

Problem

How do we coordinate work and learning without forcing everyone onto a single rate, and without treating a different rate as a deficiency?

Solution

Separate the deadline from the tempo. Most cadences are conventions rather than constraints, and the ones that are genuinely fixed are fewer than a calendar suggests.

Judge the work rather than the rate at which it arrived. Where a rate genuinely matters, say so and say why, rather than letting an unstated norm do the work.

Then let people run at their own speed in the stretches between synchronisation points — which is what intermittent collaboration is for, and what Collaboration Gradients and Asynchronous Access make possible.

What This Looks Like

In physical spaces

Let people finish at different times without it being remarked on.
Do not group by age or start date and then teach to one tempo.
Give the slow-and-deep worker somewhere to keep going.
Stop using completion order as a visible signal.
Never post the finishers and the unfinished side by side.

In digital spaces

Do not show how long someone took unless it matters.
Avoid timers on tasks where speed is not the skill.
Let people work ahead or behind a shared schedule.
Make the deadline explicit and the tempo open.
Do not rank contributors by throughput.

In social and organizational practice

Set fewer synchronisation points and hold the space between them open.
Ask what a realistic rate is before setting the schedule.
Distinguish a real deadline from a habitual cadence, out loud.
Let a person be fast at one thing and slow at another without comment.
Do not treat the quickest person’s rate as the standard.
Never describe someone as behind without naming the ruler.

Implementation Notes

Find the cadence in your environment and ask who set it.

Which of our deadlines are real, and which are conventions?
What rate are we assuming, and where did it come from?
Do we measure speed anywhere that quality is what matters?
Is anyone here fast at one thing and treated as slow overall?
What would this person produce at their own rate?
How would someone say they need longer, and what would it cost them?

A good test: if your schedule would still work with the same deadlines and no shared tempo between them, the tempo was never the requirement.

Signals of Misuse

This pattern is being violated when people hear:

“You’re behind.”
“Everyone else has finished.”
“We need to pick up the pace.”
“How long did that take you?”
“It shouldn’t take this long.”
“You’ll have to keep up.”

The last one states the requirement honestly, which at least makes it arguable.

Consequences

When this pattern is honored:

work is judged by what it is rather than by when it arrived
depth stops being sacrificed to tempo
variation in rate stops reading as variation in capability
people stop concealing how long things take
coordination happens at fewer, clearer points
the slow-and-deep contributor becomes possible to employ

When it is ignored, an organisation gets uniform speed and pays for it in quality it cannot see.

Anti-Patterns

Grouping by age or start date and teaching to one tempo
Habitual cadences treated as deadlines
Throughput as a performance measure
Completion order made visible
A single speed rating across unrelated domains
“Behind” used without naming the standard
Timers on work where speed is not the skill

Design Moves

Strategies for coordinating without imposing a tempo.

See recipes:

Related Environments

Environments that impose a tempo:

Related Experiences

Experiences produced by a tempo that does not fit:

Patterns Below

Patterns Above

Recovery cycles set the rhythm and energy debt sets the balance. Sustainable pace is the rate underneath both — the speed at which a person works when nothing has gone wrong.

Related Patterns

Related Principles

The Right to Learn Differently
Broken Systems, Not Broken People
Recovery Is Part of Participation
Everyone Can Contribute