Energy over Time

Work is usually planned in hours, but hours do not tell us how much cognitive capacity is available inside them.

More hours do not guarantee more output. When time and capacity pull in different directions, capacity determines what work is possible. Seventy-five focused hours can produce more than a hundred and sixty depleted ones.

Why time-based assumptions fail

Most systems - calendars, project plans, workplace norms - are designed around one default brain: consistent attention, stable energy, predictable working hours.

That assumption does not fit many people. Cognitive capacity changes across a day, a week, and a life. For people with ADHD, depression, autism, anxiety, or chronic fatigue, that variability can be larger or less predictable, but it is not unique to any one diagnosis.

Software that ignores this leaves people to compensate manually: muting interruptions, simplifying the task, hiding overload, or pretending their capacity is steady. That extra work consumes capacity too.

The model: wh, ph, sd

The argument is specific, not vague. Three variables:

• Work hours (wh) - total hours present or clocked.
• Productive hours (ph) - the subset of those hours where focused output actually happens.
• Stuff done (sd) - measurable output: tasks shipped, docs written, decisions made.

The constraint is always:

ph ≤ wh

You cannot have more productive hours than work hours, but you can have fewer. Extending wh does not linearly increase ph, and ph is what produces sd. Adding hours to a depleted person adds time; it may not add useful output.

The practical conclusion is to plan work around the capacity available, not hours alone.

Energy as a first-class variable

If capacity is what matters, software should treat it as real state - not something the user silently absorbs. Kumbatio models cognitive energy on a five-level scale:

• 100 peak - full capacity. Complex work, dense interfaces, everything available.
• 75 active - engaged and capable. Normal operation.
• 50 steady - functional but conserving. Reduce noise, surface what matters.
• 25 low - limited capacity. Essentials only, maximum forgiveness.
• 0 rest - not working. The system should get out of the way entirely.

Energy here means cognitive capacity - not physical energy, not enthusiasm. It's self-reported: you tell the system what you can handle, and the system adapts complexity, notification load, and interaction patterns to match.

This is what energy-system implements as an SDK, and what every Kumbatio product builds on.

Beyond work

The same principle applies past the workday. Learning, socializing, and self-care all run on the same variable capacity. A system that respects energy at work but assumes infinite capacity everywhere else has missed the point.

Kumbatio products support self-management, workflow, and cognitive energy awareness. They are not medical diagnosis tools or treatment, and are not a replacement for professional mental health support.