Cognitive Throughput Guide

What the user is actually trying to do

A cognitive-throughput calculator is useful when someone feels mentally busy but operationally stuck. The user may be a developer trying to finish one hard ticket, a manager moving between meetings, a student reading too much without retaining much, or a founder deciding which input stream deserves attention. They are not asking, "How smart am I?" They are asking, "Where did today's mental capacity go?"

That distinction matters. The Kefiw logic tools should not present themselves as clinical measures, medical screening, or productivity morality. They are simplified operating models. They turn messy workday conditions into numbers that are easy to reason about: how much signal survived the noise, how many contexts are active, how many decisions have been spent, and how much focus quality remains in the current block.

The research backdrop supports the direction, not every coefficient. Task switching has measurable performance costs; Rubinstein, Meyer, and Evans described executive-control stages involved in switching tasks. Sophie Leroy's work on attention residue explains why unfinished prior tasks can keep pulling mental resources after a switch. Decision-fatigue research is more debated than early popular accounts suggested, but reviews still describe choice overload and self-regulation costs as useful practical concepts. Treat these tools as planning heuristics, not lab-grade instruments.

References worth reading: Rubinstein et al. on task switching, Leroy on attention residue, and this open-access decision fatigue conceptual analysis.

The four meters in the cluster

Signal-to-Noise starts with information intake. Its practical question is: of everything you consumed, how much became usable output? A high-noise day can feel productive because it involved reading, watching, replying, and checking. The output test is harsher. Did it produce a decision, a written summary, a shipped change, a saved reference, or a clear next action?

Task Switching Tax asks how many active contexts are competing. The tool uses a simple rule: each added context consumes part of the remaining capacity. That is not a clinical law. It is a deliberately blunt model that makes hidden overhead visible. If the estimate looks ugly, the answer is usually not "try harder." It is "batch, close, defer, or serialize."

Decision Fatigue treats choices as withdrawals. Trivial choices are cheap, moderate choices cost more, and heavy choices cost much more. The value is not the exact battery percentage. The value is seeing that a day with hundreds of tiny preference calls can leave poor conditions for a genuinely important decision.

Focus Horizon models focus quality as decay over minutes. It helps choose a stop point before quality falls apart. A clean 45-minute block that ends with a saved note can beat a two-hour block that ends with rereading the same paragraph.

Formula, inputs, and assumptions

Each calculator uses a simplified closed-form model. Signal-to-Noise compares useful outputs against information inputs. Task Switching Tax applies a context-overhead curve to available work time. Decision Fatigue weights choice counts by severity. Focus Horizon uses a decay curve over minutes to estimate when quality drops below a useful threshold.

The inputs are intentionally plain: hours, projects, decisions, interruption counts, useful outputs, and planned focus minutes. The assumptions are intentionally visible. These tools do not know sleep, medication, illness, neurodiversity, stress, or workplace politics. They also do not know whether one decision was emotionally loaded or routine. When the model conflicts with lived reality, trust reality and use the mismatch to improve your inputs.

Rounding should be read as direction, not precision. A 64 percent focus estimate is not meaningfully different from 67 percent. A 20 percent switching loss is different from a 60 percent switching loss. Use bands and trends.

Worked example

Suppose a user starts with eight possible work hours. They have five active project contexts, three meetings, forty low-stakes messages, seven moderate decisions, and two heavy decisions. They also consumed two hours of articles, Slack threads, and docs, but only produced one shipped item and one clear decision.

The first pass through the cluster would be: Signal-to-Noise shows low conversion from input to output. Task Switching Tax shows the five-context day is expensive. Decision Fatigue warns that the two heavy decisions should not be made after the message storm. Focus Horizon suggests scheduling one protected 50-minute block for the hard task, not pretending the scattered afternoon is still deep-work time.

The actual intervention is simple: pick one project for the next block, write a parking-lot note for the other four, batch messages after the block, and move any irreversible decision to the morning. The tool did not do the work. It made the bottleneck visible enough to change the day.

When not to rely on the tools

Do not use these calculators to label yourself, diagnose attention disorders, prove someone is lazy, or make employment decisions. Do not use them as a substitute for medical or mental-health care. If attention changes are sudden, severe, or impairing daily life, that belongs with a qualified clinician.

Also avoid overfitting. A workday is not a physics experiment. The best use is repeated lightweight logging: run the tools for several representative days, compare estimates with what actually happened, then adjust your routine. The goal is a better operating rhythm, not a perfect score.