IMPACT codes
- Income
- Maker
- Pipeline
- Automation
- Client
- Trigger
Entropy managed.
The ICE!… framework shapes outputs and outcomes.
ICE!… OS separates the form of work from its strategic value, then routes it through the correct execution surface. The point is not more tasks. The point is a cleaner operating state.
Classification
Five categories stop priority becoming theatre.
Task Impact describes how work should be treated strategically. It is separate from Task Type, which only describes the form of the item.
I
IMPACT
High-leverage work that drives revenue, assets, automation, client outcomes, irreversible progress or major strategic movement.
C
CORE
Governance, operational, relational and maintenance work that preserves system integrity and keeps execution stable.
E
ELSE
Necessary but non-strategic work. Minimise it, automate it, time-box it or allow it to decay where sensible.
!
Exclamation
Urgent, unexpected and reactionary work. Capture it, act where necessary, then review the root cause.
…
Shouldn't Exist
Work created by system weakness, repeated friction or avoidable failure. It is a signal for elimination.
Codes
The Task Impact system drives prioritisation.
The categories are not decorative labels. They decide what gets protected, what gets maintained, what gets reduced, what gets reviewed and what gets eliminated.
CORE codes
- Continuous Improvement
- Operational
- Relationship
- External governance and reallocation
ELSE codes
- Execution Support
- Logistical
- Sandbox
- Excess
Effort
Priority only matters when it meets capacity.
Execution Effort tells the system what kind of time, attention and routing a piece of work deserves.
Delegate5-15 minutes
Brief, hand off and define the expected result.
Agents5 minutes to allocate
Send work to an AI or agent workflow with source, output and done-state.
Quick Action5-15 minutes
Small, clear work that can be completed immediately.
Standard Action60 minutes
Routine work, meetings, updates or bounded execution.
Focus Block3-4 hours
Deep strategic or creative work requiring protected attention.
Day Task6-8 hours
Major outcome work that deserves the whole day.
Task type
Form is not importance.
A bid, reminder, question or trade alert can have different strategic weight depending on context. ICE!… keeps those dimensions separate.
Task
A standard actionable item with defined scope and completion criteria.
Bid / RFP
A formal proposal or request requiring structured response.
Contract change
A contractual modification requiring assessment, ownership and response.
Trade alert
A market or capital signal requiring qualification before action.
Question
An inquiry requiring research, clarification or decision before action proceeds.
Idea
An unstructured concept captured for future consideration or conversion.
Reminder
A time-based prompt to check, review or follow up.
Purchase
An item or service requiring sourcing, approval or transaction.
Journeys
The operating loop is deliberately simple.
The product spec proves four things: capture without friction, classify without flattery, route to the right mode, and review without leaving residue.
Capture
Turn raw inputs into structured records quickly enough that the system keeps being used.
Triage
Separate form, impact, effort, owner and next action before work enters the queue.
Execute
Move from classified work to output with the right amount of attention and effort.
Review
Correct drift, archive residue, kill weak tasks and improve the system itself.
GLACIER
The cockpit is where the logic becomes usable.
Every GLACIER surface follows the same contract: Queue, Scoreboard, Alert Strip and Route. No visible item should become a dead end.
Queue
What requires action.
Scoreboard
What is true right now.
Alert Strip
What is urgent, risky, slipping or dangerous.
Route
Where to act, update, decide or inspect further.
AI and agents
AI executes better when the system stays in control.
ICE!… gives Notion AI, Claude Cowork, Claude Code, Codex and future agents a shared operating record. The agent layer can execute without becoming the source of truth.
Native and external AI route through the same framework.
POE handles integrated Notion AI workflows. Claude Cowork, Claude Code, Codex and future agent systems can work from the same classification, effort and routing logic.
The framework is not a task list.
Not a hustle system. Not a method for cramming more into the day. Not a passive database. The system exists to make the right work visible, bounded and executable.