Heed & Deem
Framework Guide v1.0Licensed under CC BY-SA 4.0
Definition
Heed & Deem is a personal focus framework for the individual knowledge worker. Every day: heed - deliberately choose what matters today. Every day: deem - reflect on what it was worth. Together, they make it verifiable where your most important working time actually went.
1. The Method
Heed & Deem is built on two movements that together describe a complete working day.
Heed is the first movement: deliberately choosing what matters today. Which few things deserve your Focus Time today? What stays out - consciously? This decision happens once a day, before the day begins.
Deem is the second movement: reflecting on what it was worth. What did this task produce? What do the patterns show over weeks? This review happens at the close of each task and accumulates into an honest picture of your own work over time.
Both movements are complete and inseparable. Heeding without deming is planning without review. Deming without heeding is reflection without deliberate choice. Only together do they form the method.
The method is the framework. What the following sections describe is the execution of these two movements: the rules, core elements, and metrics that define how you heed and deem.
2. The Values
Two principles carry the framework. Without them, the method does not work.
Selection over completeness. What stays out deliberately is as much a decision as what comes in. Heed & Deem is not an archive. It does not capture everything that could be done. It selects what matters today.
Self-reflection. Deem means evaluating your own work yourself. No external judgment, no comparison against a norm, no score. The Architect looks back honestly. The metrics describe what was. They do not evaluate the person.
3. The Role: Architect
In the Heed & Deem framework, the knowledge worker acts as the Architect. They build the bridge from the world of team methods to their own practice. They take what carries over from agile team work to the individual: deliberate selection, honest review, a measurement layer. They leave out what serves no individual: no meetings, no coordination ceremonies, no duplicate data entry.
The Architect heeds every day. And deems every day. Both together make the complete method.
4. The Foundation: Selection over Completeness
The Daily Selection is a selection, not an archive.
The goal is never to capture all tasks or projects. The goal is to choose the few meaningful things for the day and deliberately leave the rest out.
What belongs in the Daily Selection: project work, change initiatives, research, drafting, documentation, strategic topics, and meaningful external requests that need to be handled alongside regular work.
What does not belong in the Daily Selection: routine work. Tickets, emails, calls, routine meetings. The everyday work the role exists to handle does not go into the Daily Selection.
4.1 The Calendar Test
The operating criterion:
Whatever you would block time for in your calendar belongs in the Daily Selection.
Nobody blocks time for "answering emails." But "draft concept for department X" or "research on topic Y" - those you block. The Calendar Test replaces every complicated priority definition with an intuition every knowledge worker already has.
The most common misuse: when routine work drifts into the Daily Selection, Heed & Deem collapses back into exactly the endless list it was designed to replace. The Daily Selection becomes a backlog, the cap breaks, and the metrics become dishonest. When in doubt, apply the strict reading: would you actually reserve a calendar block for this? If not, it stays out.
4.2 Focus Time and Routine Work
The Calendar Test produces the fundamental distinction of the entire system.
Focus Time is the meaningful, deliberately chosen work in the Daily Selection.
Routine work is tickets, emails, calls, routine meetings. It does not go in the Daily Selection.
An empty Daily Selection is not a failure. When routine work consumes an entire day, the Daily Selection goes untouched. That is not a shortcoming - it is a signal that routine work dominated the day.
Heed & Deem metrics evaluate only the quality of Focus Time, not the entire day. Perfect focus quality across two hours of Focus Time in a ten-hour routine work day means something very different from the same quality across eight hours. To assess the full day, you need to know how much Focus Time there was relative to routine work.
4.3 Working Alongside Team Boards
Heed & Deem operates as a personal sub-system beneath classical team frameworks like Scrum or PMBOK. It does not replace them. They solve multi-person coordination. Heed & Deem solves a self-leadership and accountability problem for a single person.
For this to work, a strict separation applies:
The team board determines the WHAT. A Jira ticket, a sprint backlog entry, or a milestone deliverable is an authorized work item. At the Intake Check, Heed & Deem does not filter whether a valid project ticket should be executed. If it passes the Calendar Test, it belongs in the Daily Selection.
The Daily Selection determines the HOW. The Jira ticket is broken down into day-sized, outcome-oriented tasks for the Daily Selection.
If a pure routine work item appears as a ticket, it fails the Calendar Test and remains routine work.
The metrics are not a tool for refusing committed team work. They provide the evidence to make your actual capacity a more grounded input into future planning.
The upward boundary: Heed & Deem plans the day. The Architect brings the broader weekly or project direction. That direction is deliberately outside the scope of Heed & Deem.
5. Framework Structure: Core, Modules, Optional Elements
Heed & Deem is a unified method with clearly defined boundaries. There are three levels.
Level 1: The Core - mandatory for everyone. Without these six elements, it is not Heed & Deem:
- 1Selection over completeness (Calendar Test, Section 4)
- 2The Daily Selection as a linear day plan, only one position active (Section 6.1)
- 3Tasks with a single outcome, completable today (Section 6.2)
- 4The Intake Check as the entry gate (Section 6.4)
- 5The four tagging axes and the metrics they produce (Sections 7 and 8)
- 6The distinction between Focus Time and routine work (Section 4.2)
Level 2: Context Modules - mandatory or irrelevant depending on work context. These are not optional extras. For certain work contexts they are methodologically necessary; for others they are superfluous: the Routine Work Review (Section 8) and the Category (Section 7).
Level 3: Optional Elements. The dormancy rule as a hygiene convention (Section 6.5).
The Parsimony Principle
To keep the Core minimal, two fixed rules apply.
The four tagging axes are closed. There is no fifth mandatory axis - ever. Any additional analysis must either be derivable from the four axes or be an optional label. This protects the three-second tagging from creeping overhead.
Admission criterion for the Core: something may only be Core if it applies to every work context and Heed & Deem does not function without it. Everything context-dependent is, by definition, a Context Module.
The Two Context Dimensions
The Context Modules are governed by two independent dimensions.
Dimension 1: Schedule Autonomy. How freely can the person shape their own working day?
With high Schedule Autonomy (little routine work, self-determined rhythm), the Routine Work Review is optional. With low Schedule Autonomy (management, support, coordinating roles), the Routine Work Review is methodologically necessary. Without it, the actual degree of external direction remains invisible and the External Share cannot be read honestly.
Dimension 2: Context Plurality. Does the person work for one context or several?
With a single context, Category is optional. With multiple contexts (freelancers, consultants, project leads with parallel initiatives), Category is methodologically necessary. Without it, the attribution that per-context impact tracking requires is missing.
| Schedule Autonomy | Context Plurality | Active Context Modules |
|---|---|---|
| High | Single context | None (Core is sufficient) |
| High | Multiple contexts | Category |
| Low | Single context | Routine Work Review |
| Low | Multiple contexts | Routine Work Review and Category |
Two Benefits on Different Timelines
Heed & Deem delivers its value on two levels that unfold at different speeds.
From day one, the structure provides relief: selection over completeness, the tight cap, the single active position, routine work staying out. That relief is felt on the first day, without any metrics at all.
Over time, the measurement layer provides insight. The four tagging axes and the metrics only deliver their full value after several weeks, once enough history exists to reveal patterns. Tagging starts as a three-second reflex when completing a task. Its value grows with the length of your own history.
The entry point lives in the structure, not the measurement.
6. The Core Elements
6.1 The Daily Selection
The Daily Selection replaces the endless backlog with a strictly bounded day plan.
The default is four tasks per day, in a range of three to five, as a ceiling, not a target. On many days there are fewer. The ceiling is a well-supported heuristic within the range of what working memory reliably holds - research into working memory shows an individual capacity of three to five units, with four as a robust midpoint. Those who want to work more tightly can lower it. It does not go above five. What makes the method work is not the specific number, but the hard ceiling that forces selection.
Only one position is active at any given time. No parallel work. Positions are worked from top to bottom.
Whatever is not finished on a given day is re-selected the next day. It does not carry over automatically. Every day begins with a fresh, deliberate selection.
The Selection Session takes place once daily, either the evening before or in the morning. The evening before has a structural advantage: the selection is made before the next day's pressure begins, not under it. There is no automatic carry-over - every selection is a new, deliberate decision.
6.2 Tasks: One Outcome per Task
Each position holds one task. The scoping rule is not a time estimate - it is an outcome question.
A task is correctly scoped when it produces exactly one concrete, nameable outcome. One thing you can point to after completing it and say: "That's done."
"Build feature X" does not produce a single outcome and must be broken down. "Implement login form" produces one.
The second question: completable today? A nameable outcome alone is not enough. "Refactor auth service" has a clear outcome but is too large for one day and must be broken down ("Module A," "Module B," "tests"). This is a yes/no boundary, not an hours estimate.
Research, analysis, and conceptual work can almost always be broken into steps that each leave a distinct outcome. If a thinking step genuinely cannot be scoped into a deliverable outcome, the captured insight itself is the outcome. "Didn't hold up under review" is a valid close.
6.3 Multi-Day Work
A large piece of work spanning multiple days is not a project with sub-structure. It is a chain of individually scoped tasks, only the next of which exists in the Daily Selection at any given time. The initiative lives in the Architect's head and in the chain of completed tasks - not as a hierarchy.
6.4 The Intake Check
A task enters the Daily Selection only after passing the Intake Check. Entry is a three-step process:
- 1Calendar Test: Does this even belong in the Daily Selection? Would I block time for it? Routine work is filtered out here.
- 2Outcome Check: Does it produce exactly one nameable outcome? If not: break it down.
- 3Day Check: Can it be completed today? If not: break it into a chain of day-sized tasks.
Entry logic: Calendar Test, then Outcome Check, then Day Check, then the first open position.
6.5 Parked
When an active task cannot be completed today - for any reason - it moves to Parked. It leaves the Daily Selection immediately and frees up the position. The next task moves up.
Parked is not a backlog. It only holds tasks that have already passed the Intake Check and then stalled.
At the daily Selection Session, Parked is reviewed: what is still objectively blocked stays. What is done or no longer relevant is discarded.
A task that has been Parked for more than seven days without movement should be reviewed: reactivate or drop it. This is not a deadline at which anything happens automatically, but a prompt for a closer look.
6.6 Emergency Injection
When a significant externally driven task arises mid-day, it may displace the active position. The current task is interrupted and moved back. The new task is placed at the first position and worked immediately.
Emergency Injection is reserved for significant externally driven tasks. An incoming email does not justify an injection.
7. Tagging: Four Dimensions, Three Seconds
After completing each task, a tag is applied across four independent dimensions. Each measures something different. None overlaps with another.
| Axis | Question | Values |
|---|---|---|
| Impact | How much strategic impact? | High / Low |
| Type of Work | What kind of work was this? | Focused Work / Coordination |
| Effort | How much energy did it take? | Effortless / Draining |
| Origin | Self-directed or externally driven? | Self-directed / Externally driven |
Two values per axis, four axes. Tagging remains a three-second action at task completion.
All four axes are tagged at close, not at creation. The axes are diagnostic: they describe the work in retrospect and do not drive selection decisions in advance. A task can have low impact and still need to get done today. Impact is not priority.
Optional: Category. Alongside the four axes, a task may carry a Category label indicating its context: a client, a project, a topic. It serves only retrospective analysis. Category is a filter label, not a planning container. If you work in one context, leave it out. If you run several in parallel, it provides the attribution that per-context impact tracking requires.
8. The Metrics
All metrics refer to the deliberately chosen Focus Time in the Daily Selection, not the entire working day. Heed & Deem measures how well the Focus Time was used.
These numbers are mirrors, not targets. The moment a metric becomes a quota, you optimize the number instead of the work. The Impact Share is easy to improve by simply not taking on low-impact tasks or by inflating tags at close. The number goes up, self-knowledge goes down. The metrics are therefore read together, retrospectively, as observations.
Reliability builds over several weeks. With few tasks per period, percentage values are volatile.
Share of high-impact tasks in total Focus Time. Reference point: around 40 percent. Not a target to hit - a threshold below which a sustained reading warrants a closer look.
Not a target. A threshold for reflection.Share of externally driven tasks in Focus Time. The denominator is explicitly Focus Time, not the whole day. Reference point: around 20 percent. Also not a target - a threshold for reflection.
The External Share answers the question that matters most when making the case upward: how much of my meaningful, blocked time was driven from outside?
Never read in isolation. Always alongside the Focus Time / routine work ratio.Share of Focus Time spent in concentrated, uninterrupted work (Focused Work) as opposed to coordinating work. It answers: am I actually getting to deep, concentrated work, or is the day fragmenting into back-to-back coordination?
Derived Views
These are not standalone concepts. They are patterns that follow directly from the four axes.
What the Metrics Do Not Measure
Impact Share, External Share, and Focused Work Share evaluate Focus Time only. They say nothing about how large Focus Time was relative to the full day. This is critical for honest interpretation, especially in externally driven roles.
Routine Work Review
For roles whose day is heavily shaped by routine work, there is an advanced practice: roughly estimating the routine work share at the end of the day and tracking it over time. This produces the ratio of Focus Time to routine work. "70 percent of my week went to routine work - only 30 percent was left for strategic work" is often the most powerful argument available when making a case upward.
This practice is optional and context-dependent. Roles with high Schedule Autonomy do not need it. Externally driven roles gain their most important piece of evidence from it.
9. Heed & Deem in Practice
A complete working day, from evening to evening.
Review Parked. What is still waiting, what has become irrelevant? Fresh deliberate selection for tomorrow. Not carrying over the remains of today. Four tasks, each scoped to one outcome. Selection is made before the next day begins.
Task 1 is already known. Communication channels are closed. No decision overhead at the start of the day.
Full concentration on Task 1. Incoming emails and tickets run as routine work. They do not enter the Daily Selection.
Task 1 is done. Close and tag: High Impact, Focused Work, Effortless, Self-directed. Three seconds.
A critical system failure occurs. Externally driven, but significant. Injection. The active task is interrupted and moved back. The crisis takes the first position. At close: Low Impact, Focused Work, Draining, Externally driven. That produces Externally driven and draining.
Task 3 needs an approval. The contact is unreachable. The task moves to Parked. The position opens. The next task moves up.
Rough estimate of how much of the day went to routine work. Not as self-criticism - as an honest picture. Then the fresh selection for tomorrow: what comes back into the Daily Selection, what stays Parked, what gets dropped? End of day.