Emerging Work Identification

Emerging Work Identification is the practice of recognizing, during daily coordination, newly discovered necessary work that was not part of the original plan but has become apparent through the course of active execution, ensuring that such work is explicitly noticed and named rather than either silently absorbed without visibility or overlooked entirely until it causes disruption later. It differs from unplanned work handling in that it focuses specifically on the moment of recognition itself, within the daily rhythm of coordination, rather than the subsequent decision about how to formally respond to that work once identified.

Why Emerging Work Requires Deliberate Recognition

Discovery During Execution Is a Normal, Expected Occurrence

As contributors work through planned items, they frequently uncover additional necessary work—a related defect, a missing prerequisite, a previously unnoticed edge case—that genuinely needs attention but was not part of the original scope.

Unnoticed Emerging Work Creates Hidden Scope

If newly discovered necessary work is not explicitly identified and communicated, it can be quietly absorbed into ongoing effort without ever being acknowledged, silently expanding the actual scope of work beyond what was originally planned or visible to the team.

Early Recognition Enables Better Decisions

Identifying emerging work as soon as it becomes apparent, rather than only recognizing it once it has already consumed significant effort, gives the team the opportunity to make a deliberate, informed decision about how to handle it.

Common Sources of Emerging Work

Discoveries Within Planned Items

While implementing an already-planned item, a contributor may discover a related issue or missing piece that itself represents new, previously unrecognized work.

Side Effects of Completed Work

Newly completed work sometimes reveals unintended consequences elsewhere in the system, surfacing additional work needed to address them.

Clarified Understanding of Existing Requirements

As execution proceeds and understanding deepens, what was originally thought to be within an existing item's scope may turn out to be more accurately understood as separate, additional work.

Environmental or System Changes

Changes in the underlying technical environment or external systems, noticed during the course of daily work, can surface new necessary work unrelated to any single planned item.

How Daily Coordination Supports Identification

Providing a Regular Opportunity for Discovery to Surface

The daily coordination session offers a consistent, expected moment where newly discovered work can be raised, rather than requiring contributors to interrupt their focus immediately upon discovery or risk the discovery going unmentioned.

Encouraging Explicit Naming Rather Than Silent Absorption

A team norm that treats mentioning newly discovered work as expected and valuable, rather than an unwelcome complication, supports honest, timely identification.

Distinguishing Genuine New Work From Scope Already Understood

During identification, the team clarifies whether the discovered item genuinely represents new work or was already implicitly understood to be part of an existing item's scope, avoiding unnecessary duplication or confusion.

What Happens After Identification

Handing Off to Formal Handling

Once emerging work is identified, it is typically routed through the team's established process for unplanned work handling, such as triage against urgency criteria or deferral to the standard backlog.

Recording for Transparency

Even emerging work that will not be immediately actioned is recorded, preserving visibility into the true, evolving scope of what the team has actually encountered rather than only what was originally planned.

Informing Future Estimation

Patterns in the type and volume of emerging work discovered can inform future planning, helping the team account more realistically for the typical amount of discovery that occurs during execution of similar work.

Measuring Emerging Work Patterns

Emerging Work Rate

Tracking this rate over time provides useful context for future planning, indicating how much discovery-driven scope typically emerges during execution of comparable work.

Common Failure Modes

Silently Absorbing Discovered Work Without Naming It

Continuing to address newly discovered necessary work without ever explicitly identifying it hides the true scope of effort being expended and prevents deliberate decision-making about how to handle it.

Delaying Identification Until Significant Effort Has Been Invested

Waiting to mention emerging work until it has already substantially affected progress misses the opportunity for earlier, more informed handling decisions.

Treating All Emerging Work as Automatically Urgent

Assuming that anything newly discovered must be addressed immediately, rather than properly triaged alongside other priorities, can disrupt planned work unnecessarily for emerging items that could reasonably wait.

Failing to Distinguish Genuine New Scope From Existing Scope

Misidentifying something as newly emerging work when it was actually already implicitly part of an existing item's understood scope can create confusion and inflate the apparent volume of unplanned discovery.