Poko manifesto · 12 October 2026

Slack is not waste

Why spare cognitive capacity is an operating asset

The proposition

Most organisations understand why they need cash reserves. They understand why a bridge needs engineering tolerances and why a network needs spare capacity to survive a surge. Yet they routinely plan human work as though every available minute of attention should be allocated.

A team with a completely filled calendar can look efficient. It may actually be a team that can no longer respond intelligently when reality changes.

Slack is the reserve capacity that allows a human system to absorb variation, detect error, learn, recover and act when something unexpected matters.

This is not an argument for doing less for its own sake. It is an argument for treating responsiveness and adaptability as part of performance—not as a luxury left over after the schedule has been filled.

1. Why attention changes the economics of capacity

Human work is not a uniform conveyor belt. Different tasks demand different forms of attention, memory, inhibition, judgement, coordination and recovery. Two identical half-hour blocks are not interchangeable if one requires a high-stakes decision after six meetings and the other is routine admin in a quiet room.

Herbert Simon's work on bounded rationality established a central constraint: decisions are made by limited information processors, not all-knowing optimisers. Research on working memory and executive control gives that general insight psychological substance. Organisational attention theory extends it: firms do not act on everything that exists; they act on what their processes and people notice, interpret and elevate.

Now consider what happens when new demands arrive while those systems are fully loaded. They do not simply add onto a neutral blank space. They displace, fragment or delay attention already committed elsewhere. Interruptions create reload costs. Decisions are postponed or simplified. Early warnings are missed. Work is handed to whoever still appears able to carry it.

Overload can therefore create a second-order burden: more checking, rework, coordination, escalation and recovery are needed just to keep the original work moving.

2. The three functions of slack

Shock absorption. Demand changes, people become unavailable and systems fail. Uncommitted capacity prevents every disturbance from becoming a crisis.

Quality of judgement. Good decisions require time to compare, challenge and update. When the entire system is in response mode, the easiest available default can displace the better considered choice.

Learning and adaptation. Maintenance, reflection, improvement and experimentation are often the first activities dropped in overload. Yet they create the very capability needed to reduce future problems.

Slack is therefore not necessarily idle capacity. It is sometimes the option to think before committing.

3. Slack exists at several levels

At the individual level, slack might be a buffer between demanding tasks, an external memory system or a recovery period that prevents one hard day from impairing the next.

At the team level, it might mean fewer simultaneous priorities, named backup roles, time for handoffs and a process for surfacing overload before mistakes multiply.

At the organisational level, it might mean protected investment capacity, simpler reporting, clear decision rights, less decision churn and room to respond to strategic opportunity.

At the institutional level, it might mean public services that do not require citizens to master a miniature bureaucracy merely to receive ordinary support—and frontline systems with enough capacity to detect and correct mistakes.

A crucial fairness question sits across all four: who actually holds the slack, and who has to absorb the overflow? An executive's protected diary may be maintained by an assistant's constant interruption. A firm's 'lean' operation may depend on unpaid family effort, contractors or frontline staff working around the rules. Slack is not distributed fairly merely because aggregate utilisation looks acceptable.

4. The hidden failure of optimisation

A system can be locally efficient and globally brittle. Removing every apparent inefficiency often removes the resources used to recover from unusual events or correct mistaken assumptions.

The paradox is that spare capacity can look wasteful right until it becomes the most valuable resource in the organisation.

This does not mean there is one scientifically established ideal utilisation percentage for all cognitive work. Queueing models can predict sharp delays near saturation under specified assumptions, but human tasks, stochastic demand, organisational networks and recovery do not reduce to a universal '80% rule'. The right level and kind of slack must be tested for the context.

Nor should slack become an excuse for poor operational discipline. Some spare capacity is badly allocated. Some buffers hide delays and unclear accountability. The strategic question is which reserve enables better outcomes, in what conditions, at what cost.

5. Turning the thesis into a design method

A practical cognitive-slack audit starts with six questions:

  1. What must this system do reliably? Define the actual outcomes, not just hours or utilisation.
  2. Where do demands arrive and accumulate? Identify interruptions, dependencies, decisions, variation and rework.
  3. Who pays the invisible cognitive cost? Map remembering, anticipating, checking, switching, translating and recovering.
  4. What is the current failure mode? Look for delayed decisions, repeated errors, uncontrolled handoffs, churn or cognitive fatigue.
  5. What reserve, rule or redesign might help? Protect capacity, simplify work, externalise memory, improve handoffs or reduce avoidable switching.
  6. What evidence would change our mind? Compare outcomes and costs before and after; watch for displaced burden rather than declaring victory from one attractive metric.

This is where Poko Neurostrategy becomes operational. The method asks for an objective, a constraint, a cognitive budget, an explicit trade-off, the lever to change, an operating rule, a likely failure mode and an adaptation trigger.

6. What this means for Poko products

Weekly Reset: reserve time and attention for the week that is actually coming, not the imaginary week in which nothing unexpected happens.

Personal software: preserve a person's task state and next action, reduce unnecessary re-deciding and help them restart after disruption.

Practitioner workflows: evaluate whether a support plan improves function without creating a larger system-maintenance burden.

Enterprise software: reveal decision bottlenecks, handoff churn and repeated attention demands—not as an employee scoring system but as potential work-design problems.

Smart workplaces and furniture: examine whether environments can reduce unnecessary sensory burden, enable transitions and create usable recovery or concentration opportunities.

Wearables and neurotechnology: test whether sensed information adds a decision-relevant benefit beyond simpler, less intrusive methods. If it does not, do not collect it.

7. The research test

A serious research programme cannot simply declare 'slack creates resilience' and find agreeable anecdotes.

The propositions should face rival explanations and measured comparisons. For example:

The answers may narrow the theory. That is the point.

8. What this means for Poko

The possibility behind Poko is that cognitive capacity and its allocation could become visible operating variables in products, workplaces and organisational decisions.

A company that helps a customer create reliable outcomes with less unnecessary attention cost may create commercial value through fewer failures, better time use, improved retention or higher quality decisions. Those outcomes require evidence; they cannot be assumed simply because the theory is appealing.

As digital systems become more capable of creating demand for human attention, the ability to manage the conditions under which people think may become a larger commercial category.

Poko's bet is not that the world needs another optimisation dashboard. It is that the next generation of productive systems will know when not to consume the human capacity they depend on.

Selected intellectual foundations

This memo synthesises established ideas with Poko's own proposed framing. These sources support relevant components; they do not validate Poko's complete model.