A developing framework for understanding the cognitive structure underneath work.

The Basic Idea

Cognitive Mode Theory proposes that work can be understood partly through the kind of cognitive transformation required to move it from its current state toward its desired state.

In plain language:

Something is true before the work.

Something needs to change.

Something different is true after the work.

For example:

Before: A decision has not been made.
After: A decision has been made.

That is different from:

Before: An artifact does not exist.
After: An artifact exists.

And both are different from:

Before: An artifact exists but does not yet meet the required standard.
After: The artifact has been improved until it does.

Those differences matter because they may require different forms of thinking.

CMT calls those recurring categories of cognitive work modes.

The research is currently investigating how reliably those modes can be defined, distinguished and identified across real-world work.

A Task is Not Necessarily a Cognitive Mode

This is one of the most important distinctions in the framework.

Take:

Grade papers.

At first glance, it looks like one task.

But “grading papers” may require someone to:

• understand the student's response
• evaluate it against criteria
• determine a grade
• produce feedback
• refine that feedback
• record or return the evaluation

Those are not obviously the same cognitive operation.

So CMT does not begin by asking:

“What mode is grading papers?”

Instead, the developing methodology asks:

What has to become true for the grading process to move forward?

Only after the underlying work has been represented clearly enough should a cognitive mode be considered.

This distinction is important because otherwise classification becomes little more than intuition:

“That sounds like Research.”
“That feels like Creation.”

The goal of the research is to develop a method that does not depend on someone's ability to guess correctly.

Work Also Has Prerequisites

Another part of the developing model concerns readiness.

A task can exist without actually being ready to perform.

Imagine:

Build the workshop deck.

The deadline may be approaching.

The task may be important.

But if the workshop content has not been determined yet, deck creation may not actually be ready.

The deck has a prerequisite.

That gives us a different way to represent a project.

Something within a project may be:

KNOWN

Information or resources already available.

MISSING INFO

Information or resources that are currently unknown or unavailable.

Missing does not automatically mean blocking.

READY

Work whose required inputs and prerequisites are currently available.

BLOCKED

Work that cannot proceed because something it requires has not yet become true.

COMPLETE

Work whose required change has occurred.

This produces a dependency structure rather than a flat list of tasks.

And that structure allows another useful question:

What is actually possible to move forward right now?

That may be different from asking what is most urgent.

What is a Dependency Structure?

A dependency structure represents the relationships between the different states and pieces of work inside a project.

For example:

Lesson direction established

↓

Presentation can be built

↓

Presentation can be finalized

↓

Workshop can be delivered

The important relationship is not simply that all four things belong to the same project.

It is that one may need to become true before another can proceed.

CMT currently uses this distinction to explore how complex work moves through a sequence (or sometimes a branching network) of prerequisites and handoffs.

A guiding rule in the developing methodology is:

Only distinguish pieces of work when the distinction changes what is ready, blocked, required next or unlocked downstream.

The goal is not to break every task into microscopic pieces.

It is to find the minimum useful structure needed to understand how the work moves.

The Same Information Can Play Different Roles

CMT also distinguishes between what something is and what function it is serving within the work.

The same article, note, example or piece of research might:

help someone determine the direction of a project,

support an already-determined direction,

or become a resource included in the final deliverable.

Its identity did not change.

Its dependency role did.

One current working principle is:

The role of an input is determined by where it enters the dependency structure and what it enables next.

This matters because conventional task systems often organize information according to its label or location.

CMT is increasingly interested in its function within the movement of work.

“Your Brain, The Business”

One metaphor I use to make this easier to understand is:

Your Brain, The Business.

Imagine that your cognitive system behaves less like one employee doing everything and more like an organization containing different specialized functions.

Research has a scope of work.

Decision-making has a scope.

Creation has a scope.

Refinement has a scope.

Different departments receive different inputs and produce different outputs.

And organizations have handoffs.

A research team usually would not hand a pile of raw information directly to a design team and simply say:

“Make something.”

There may need to be interpretation.

A decision.

A specification.

A clearer definition of what should be produced.

CMT explores whether cognitive work contains similar handoff conditions.

In that metaphor:

Modes are specialized functions.

Prerequisites are required inputs.

State changes are outputs.

Dependencies describe what must be available before work can move.

And eventually, technology may be able to function as a kind of routing system between those forms of work.

The metaphor is not the theory itself. It is simply an accessible way to visualize some of the relationships CMT is studying.

How the Research Currently Works

The methodology is still being developed and stress-tested.

The current research pipeline is approximately:

1. Work Episode Definition

First, establish the boundaries of the work being studied.

Who is doing the work?

What bounded piece of work are we examining?

What is already available?

What information is missing?

What condition would indicate that this work episode is complete?

2. Recursive Cognitive Decomposition | RCD

RCD works backward from an outcome by asking questions such as:

Immediately before this could become true, what would need to already be true?

The purpose is not to produce the longest possible task list.

It is to identify meaningful prerequisite relationships.

If an answer is only behavioral..

“I have to read the paper.”

The protocol may ask:

What does doing that make different from before?

If several distinct prerequisites are hidden inside one answer, they can be separated.

The process continues until the decomposition reaches information or resources that were already available at the start of the work episode.

3. Dependency Structure

The identified relationships can then be represented as a graph showing:

what is known,

what is missing,

what is ready,

what is blocked,

and what completion of one piece of work makes possible next.

This is currently becoming an important part of the research because it allows project structure to be studied separately from cognitive classification.

4. State Change Translation | SCT

Once an individual piece of work has been isolated, it can be represented as:

BEFORE

↓

CHANGE

↓

AFTER

One SCT representation should describe one meaningful transition.

This is the point where the project-level question

“What needs to happen?”

becomes the cognitive question

“What actually changes when this work is completed?”

5. Transition Adequacy Rubric | TAR

Before a transition is classified, the research asks whether it has been represented clearly enough to classify at all.

TAR currently examines questions such as:

Can we identify what changed?

Is the before-state clear?

Is the after-state clear?

Are those states meaningfully distinguishable?

Are we representing the relevant change rather than merely naming a behavior?

Is there enough information to apply the ontology without guessing?

If the answer is no, the transition returns for clarification.

It should not be forced into a cognitive category.

6. Ontology Classification

Only after a transition is adequately represented is it compared against the current CMT ontology.

The question becomes:

Which cognitive mode, if any, actually describes this transformation?

Possible results include:

Classified — one mode sufficiently fits.

Ambiguous — more than one mode legitimately fits.

Out-of-ontology — the transition is adequately represented, but none of the current modes explains it.

That last result matters.

The protocol is not supposed to protect CMT from failure.

If real work repeatedly produces a kind of cognitive transformation that the current ontology cannot represent, the ontology may need to change.

What CMT is Trying to Discover

The larger research questions include:

Can cognitive work be categorized reliably according to the transformations it produces?

Can independent raters identify those transformations consistently?

Are the current modes sufficiently distinct?

Is the current ontology complete?

Can prerequisite structure help explain why seemingly actionable work feels impossible to begin?

Do transitions between different cognitive demands create measurable friction?

Can matching work to current cognitive availability improve initiation, effort or completion?

Can technology perform some of the translation and routing work without increasing cognitive burden on the user?

Those questions are not answered yet.

They are what the research exists to investigate.

Where ModeSpace fits

ModeSpace is the developing software implementation associated with CMT.

The long-term goal is not to require users to learn this methodology.

A person should be able to say:

“I need to teach an AI workshop.”

The system should eventually be able to help determine:

what they already have,

what is still missing,

what needs to become true,

what depends on what,

what is currently ready,

what is blocked,

and what form of cognitive work may be required next.

The user should be able to describe their work in ordinary language.

The sophistication should live underneath the interface.

One of the central product principles emerging from the research is:

The user supplies context. The system carries the burden of translating that context into useful structure.

ModeSpace is currently under development and does not constitute validation of CMT.

What CMT is Not Claiming

Cognitive Mode Theory is currently an emerging research framework, not an established scientific theory.

At this stage, CMT should not be interpreted as:

a proven model of human cognition,

a diagnostic framework,

a treatment for ADHD or executive dysfunction,

a clinical or psychological intervention,

proof that cognitive modes predict productivity,

or evidence that ModeSpace improves cognitive performance.

The ontology, terminology, methodology and boundaries of the framework remain subject to revision.

Some ideas documented here will almost certainly change.

That is intentional.

Why Document the Research Publicly?

Because the uncertainty is part of the work.

A real-world task may expose a flaw in the methodology.

Two raters may disagree.

A transition may fit multiple modes.

A supposedly simple task may reveal a missing prerequisite.

An entire category of work may appear that the current ontology cannot explain.

Those moments matter.

This site exists to document not only what CMT currently proposes, but also:

what is being tested,

what fails,

what changes,

why it changes,

and what remains unresolved.

The goal is not to build a public argument that CMT must be correct.

The goal is to make the process of finding out visible, traceable and open to scrutiny.

Follow the work

If you're interested in CMT, there are several ways to continue from here.

Read the Research Notes

Follow individual questions, experiments, failures, revisions and observations as the framework develops.

See the Current Research Status

View the active research phase, current methodology, unresolved questions and what is being tested now.

Submit a Work Episode

Contribute an ordinary real-world example of work that can help stress-test the developing methodology.

Join Future Testing

Express interest in structured CMT research, ModeSpace pilots and future studies.

Collaborate

Researchers, educators, technologists, practitioners and institutions interested in the work can explore opportunities for methodology review, applied pilots, advisory support or research collaboration.