← Back to Protocols

Dimension Reduction Protocol

When perfectionism blocks action, compress an overwhelming project into 3–5 candidate tasks and choose a single first physical action.

What problem this protocol targets

Many neurodivergent people experience a specific pattern: the more important or meaningful a project is, the more it expands into an impossible, multidimensional "perfect version" in the mind. Starting becomes unsafe; any small step feels both inadequate and irreversible.

In practice this shows up as: staring at the same sentence for 20+ minutes, rewriting the same paragraph, or "circling" a task in your notes system without taking any concrete action.

The core idea

Dimension Reduction treats overwhelming projects as a dimensionality problem, not a willpower problem. Instead of trying to "motivate" the person, the protocol reduces the project into a small, finite set of candidate moves and then selects a single first physical action that is cheap, reversible, and observable.

The protocol is implemented as a sequence of prompts and decision points that can be run in Obsidian, a custom tool, or even on paper. In all cases, it generates structured data in the shared schema.

Step-by-step flow (research version)

  1. Name the friction.
    Briefly describe the project and the stuck moment.
    Output: a friction_record with title, intensity, tags and context.
  2. Surface the "perfect version".
    Write down how the project would look if perfectionism were in full control (length, scope, standards, audience).
    Output: qualitative description linked to the friction record.
  3. Define a "good enough" version.
    Describe the smallest version that would still be genuinely useful and kind to your future self.
    Output: contrast between perfect vs. good-enough, stored in a c_note.
  4. List 3–5 candidate moves.
    Generate a small list of possible moves that can be done in 20–30 minutes, at the current energy level.
    Output: 3–5 candidate task_entity objects.
  5. Select one first physical action.
    For the chosen task, define the very first physical movement (open which file, type what, prepare which object).
    Output: a single selected task marked with is_first_action = true.
  6. Act, then log state change.
    Perform the first action, then rate energy, focus and mood before/after.
    Output: metric_entity entries linked to both the task and the original friction record.

Data hooks and schema

The research implementation of this protocol is wired into the shared schema used across the Inner Kingdom System and the Friction WishPool.

Entity Role in this protocol
friction_record Captures the initial stuckness (intensity, tags, context).
task_entity Stores candidate moves and the chosen first action.
metric_entity Tracks before/after energy, focus, mood.
c_note Holds narrative descriptions and reflections.
On duoremifa.com / friction-log.com, Dimension Reduction appears as concrete tools such as "极简启动 · 5分钟规则" and other launch aids. These are user-facing manifestations of the same underlying protocol: a short, guided sequence that turns "I should work" into "do this one small, specific thing next", while generating reusable friction data where users consent.

Research status

  • Core protocol tested informally with ND co‑creators through 1:1 work and Friction Lab tools.
  • Being integrated into the Inner Kingdom System as a standard response to perfectionism‑type friction.
  • Planned next step: small-N longitudinal study comparing weeks "with" and "without" the protocol in everyday work.
  • Over the next 1–2 years, I plan to formalise this as a small‑N longitudinal study comparing weeks "with" and "without" the protocol in everyday work and writing.