All active tasks and assignments captured in a single system where they are visible, attributable, and current. The right people know what is being worked on, by whom, at what pace, and whether it is producing results.
Most organizations have a work tracking system. The problem is that it reflects a fraction of the work actually happening. Some people log everything. Others log nothing. High-visibility work gets tracked. Background work, coordination work, and maintenance work disappears. The result is a system that looks like a complete picture but is actually a curated highlight reel. The Work Index is not a project management tool. It is the discipline of capturing all active work in one place where it is visible, attributed to one person, and current. When the index is functioning, leadership does not need to ask what is being worked on. The system tells them. For AI, the Work Index is the operational layer. An agent assigning tasks, assessing capacity, or evaluating progress is reading from this index.
The Work Index is a core dimension of the Awareness phase in the Ragsdale Framework for Autonomization, developed by Marc Ragsdale. Prospus implements it as part of structured AI transformation engagements. Kaamfu operationalizes it as a native layer inside the Autonomous Operating Environment, giving AI agents the operational layer they need to route, assign, and track work.
Work lives across multiple disconnected tools with no single environment reflecting what is actually happening. Shadow task lists, personal to-do systems, and informal assignments exist outside the primary system. Getting a clear picture of what any team is working on requires asking and waiting.
All active work is captured in a single system. Every task has an owner and a current status. Leadership can see the status of any initiative or contributor without initiating a reporting cycle. AI agents can assign work, assess capacity, and track progress without human intervention.
| Metric | Before | After |
|---|---|---|
| Visibility | Getting a clear picture of what any team is working on requires asking, waiting, and assembling manually. Leadership needs to know the status of a key deliverable before a client call. The project manager is not reachable. Nobody else knows where things stand. |
All active work is visible in a single system. Leadership can see the status of any initiative or contributor without asking. |
| Attribution | Work is assigned informally. When something does not get done, nobody is clearly accountable. A deliverable is missed. Three people thought someone else was responsible. The assignment was made in a Slack message that scrolled off. |
Every task has a single owner. Accountability is structural rather than social. |
| Completeness | The task system reflects formal project work. The work that fills people's days is invisible. A team appears to have capacity based on the project system. In reality they are carrying 30 hours per week of work that was never logged. |
All active work is captured, including coordination, maintenance, and background work that never makes it into formal project scopes. |
| AI Routing | AI agents have no view of active work and capacity. Assignments are made without knowledge of what people are already doing. | AI agents read from the Work Index to assess capacity, route new assignments, and flag overload before it becomes a problem. |
| Effort Alignment | The organization does not know where its capacity is going. Effort data is absent or too fragmented to be useful. An initiative that appears to be a top priority is receiving ten percent of the organization's actual effort. The other ninety percent is going to work that was never connected to a strategic priority. |
The Effort Index shows where organizational capacity is being applied. Decisions about priorities are informed by where effort is actually going. |
A score of 10 on the Work Index means this dimension is fully resolved and no longer a constraint on the phases that follow. Here is what that requires in practice.
Establish a single system of record for all active work. Not necessarily a new tool. A commitment that all work goes into the existing system, including the work that currently lives in personal lists and informal channels.
Define the minimum required fields for every task: owner, status, priority, and connection to a goal or initiative. Tasks without these fields are incomplete and get flagged.
Build the Priorities Registry. Active work is ranked by priority, not just listed. When priorities change, the registry reflects it before people start executing against the old priority.
Establish the Effort Index. Define how time and effort get captured without creating overhead that discourages use. The goal is an operational signal, not a surveillance system.
Make the index queryable. Inside Kaamfu for organizations on the platform, or as a standalone natural language interface for those that are not.
The system gets built but task entry is inconsistent. Some people log everything. Others log nothing. Partial visibility is worse than acknowledged invisibility because it creates a false sense of operational awareness. Completeness requires discipline from every person in the organization, which is a culture change, not a tool change.
The Autonomy Diagnostic scores the Work Index on a 0 to 10 scale. Each point reflects a specific observable state in your organization.
Work lives across multiple disconnected tools. No single view of what the organization is working on exists.
A primary task system exists but captures only formally scoped project work. Most active work is invisible.
The task system captures project work and some team-level tasks. Personal task lists and informal assignments remain outside it.
Most formal work is captured. Effort and priority data are absent. Ownership is inconsistent.
A Work Index exists with most active tasks captured. Ownership is defined but priority ranking is informal.
Active work is captured with clear ownership and priority. Effort data is tracked inconsistently.
All significant active work is captured in a single system with clear ownership, priority, and current status.
The Work Index is complete and current. Effort data is structured. Leadership can see the status of any initiative without asking.
The Work Index is queryable and referenced by AI agents for routing and capacity decisions.
All active work is captured, owned, prioritized, and tracked in a single queryable system. AI agents assign work, assess capacity, and track progress without human intervention.
No. Project management tools track scoped project work. The Work Index captures all active work, including the coordination, maintenance, and background tasks that fill people's days but never appear in a formal project scope. The discipline is what is different, not necessarily the tool.
The entry point is demonstrating that invisible work is the primary cause of capacity misunderstandings and accountability gaps. When the organization sees concretely that its capacity estimates are wrong because half the work is invisible, the case for complete logging makes itself.
The Goals Index captures what the organization is trying to achieve. The Work Index captures what is actually being done. They connect through cascade: work should trace back to a goal. When it does not, that disconnection is visible and addressable.
A structured record of the time and capacity being applied to active work. It is an operational signal that tells the organization where its capacity is going, not a surveillance tool. The difference is in how the data is used: operational visibility rather than individual performance monitoring.
AI agents that assign tasks, route work, or assess capacity are reading from the Work Index. Without it, every assignment is made without knowledge of what people are already doing. The Work Index is the operational layer that makes AI-assisted work management possible.
Access governance defines who can see what. Not all work is visible to all actors. The Work Index documents what exists and at what access level. Sensitive work can be captured without being surfaced to everyone who queries the system.
Not all work needs to be a formal task. The Work Index should capture work at the level of granularity that is useful for visibility and capacity decisions. The right granularity depends on the organization.
The Priorities Registry is updated to reflect current priorities before work continues on the old ones. When priorities change but the task system does not, people keep executing against the old priority because that is what the system tells them to do.
Operationally, the person responsible for work management owns the index. But enforcement requires leadership commitment. If leadership does not reference the Work Index for operational decisions, the organization will not maintain it.
A score of 7 or above means all significant active work is visible in a single system with clear ownership and current status. The Autonomy Diagnostic will tell you which dimensions need the most attention first.
The Autonomy Diagnostic scores every dimension of the Ragsdale Framework and tells you exactly where to focus first.
Take the Diagnostic