Business execution and project results
The project is falling short.
You’re the one explaining why.
Another status meeting. Different explanations from each team. You still need to decide what happens next.
The project still matters, but the expected result has not arrived. You may have discussed it more than once without a clear explanation or a decision about what to change. The Stalled Priority Snapshot gives that one result a focused investigation and a recommended next step.
$1,500 USD fixed · 90-minute session · Up to three participants
Stalled Priority Snapshot
Investigate one result that still matters.
Bring one delayed decision, incomplete rollout, or launch whose expected benefits have not arrived. ES uses the session and the records you bring to reconstruct what happened, examine possible explanations, and recommend one next step.
What you receive
A written readout within 24 hours, with a map of the work as far as the evidence supports, a plain-English assessment, and one recommended next step. A 15-minute walkthrough helps you review it.
Where the evidence supports them, the readout includes an extra-labor estimate and a proposed 14-day test. Missing evidence becomes a specific question to investigate.
The work path may not be the problem.
The investigation may point to resources, priorities, the business case, or an outside dependency. A supported finding that the work path is not the cause is a useful outcome, with the reason explained.
When the cause is still unclear, the readout says that. The recommendation may be to gather evidence or make a management decision before changing the workflow.
What could change this conclusion?
Every readout names the assumptions behind any cost estimate, any unresolved question that could change the recommendation, and whether resolving it needs more evidence, a management decision, or both.
Follow-up after the agreed test or evidence review is included. There is no commitment to a further engagement.
What it looks like when the result falls short
These patterns often appear when leaders ask why projects fail. Each one is evidence of a problem, but it is not yet proof of a cause.
The team starts the day in meetings and does the real work after hours.
Every new priority stayed active. Nothing came off.
The team that delivered last quarter is gridlocked this quarter. Same people. Same skills.
The rollout works at headquarters. The branches are still waiting.
The work itself took four hours. Approval took nineteen days.
A completed deliverable is back for a third review because the criteria arrived late.
The new process launched on time. People still use the old spreadsheet.
The AI pilot added review and exception work. The old process still runs beside it.
The intake got automated. The request reaches the same reviewer's queue a day sooner and waits there just as long.
Urgent work keeps shipping. The strategic initiative that defined the plan is still on the slide.
These symptoms do not establish one cause. Operational bottlenecks can sit in resources, approvals, dependencies, or cross-functional handoffs. Workflow bottlenecks often show up as waiting and rework, while slow decision-making can point to unclear authority or an overloaded decision route. Emergent Skills examines these explanations against what happened on the work path and the conditions around it.
Stalled, partly delivered, or launched but underused? See the three situations →
From strategy to the work path
The priority crosses departments. So can the delay.
Select a role to see its execution commitment, where work can stall, and the possible business consequence.
An illustrative map of eleven roles. Responsibilities and reporting lines vary; these groups are not a chain of approvals. The examples show conditions to investigate, not findings about a particular company.
CEO
Execution commitment
Chooses the strategic priority, commits resources and resolves conflicts between business goals.
Where work can stall
A new priority is announced while all the existing commitments remain active.
Possible business consequence
Teams can spend effort across too many commitments while the expected strategic benefit arrives late.
Chief strategy officer
Execution commitment
Connects the strategic choice to assumptions, business plans and intended results.
Where work can stall
The plan names an outcome without resolving the decisions and dependencies needed to deliver it.
Possible business consequence
Investment can continue while the expected customer or financial benefit remains untested.
CFO
Execution commitment
Tests the economics and connects funding, review authority and benefit ownership.
Where work can stall
Margin criteria arrive after work has been prepared, or Finance review capacity is missing from the schedule.
Possible business consequence
Repeated analysis adds labor; a delayed pricing change can postpone expected margin benefits.
COO
Execution commitment
Coordinates operating commitments, capacity and quality across functions.
Where work can stall
Each function has a workable local plan, but their handoffs or shared resources do not line up.
Possible business consequence
Customer delivery can slip while teams spend extra time coordinating or restarting work.
Chief of staff
Execution commitment
Follows executive decisions through and coordinates selected priorities across reporting lines.
Where work can stall
An initiative has a named owner but lacks commitments from the people whose work it needs.
Possible business consequence
Status meetings and escalation consume time while the unresolved decision continues to hold up delivery.
CHRO
Execution commitment
Connects workforce plans, skills, incentives and development with the chosen priorities.
Where work can stall
Staffing or training arrives after the work needs to begin, or incentives pull teams toward competing targets.
Possible business consequence
Delivery may require added support or rework. Any turnover effect needs separate evidence.
CIO / CTO
Execution commitment
Connects technology commitments, integration work and reliability with the business plan; mandates vary.
Where work can stall
Several initiatives need the same engineer, platform change or technical review at the same time.
Possible business consequence
A launch can wait while other teams repeat checks or rebuild work around changing technical assumptions.
Transformation office / EPMO
Execution commitment
Tracks portfolio dependencies, decisions and intended benefits, where this function exists.
Where work can stall
A milestone is marked complete while adoption, a downstream dependency or benefit ownership remains unresolved.
Possible business consequence
Project spending can finish before the business receives the result it funded.
Department / business-unit heads
Execution commitment
Turn the priority into delivery commitments and agree what their functions need from one another.
Where work can stall
Product, Finance and Sales use different assumptions, acceptance criteria or dates.
Possible business consequence
Work can return for revision, consuming more labor and delaying the customer offer.
Middle managers
Execution commitment
Sequence work, coach people and resolve day-to-day conflicts and exceptions.
Where work can stall
Reviews and decisions collect around one manager, or the same people receive competing assignments.
Possible business consequence
People spend time chasing decisions and rebuilding context while the deliverable waits.
Professionals
Execution commitment
Build, sell, implement and support the offer, and surface evidence from the work and customers.
Where work can stall
Inputs, access or acceptance criteria arrive late; capability and quality may also need attention.
Possible business consequence
Repeated work costs time. Incorrect quotes, configuration or delivery can also require customer corrections.
Illustrative example
One pricing change. Four connected functions.
Leadership chooses a pricing change intended to improve margin. The offer still has to become something customers can buy and the company can deliver.
-
01 Product
Defines the offer, scope and proposed price for Finance to evaluate.
-
02 Finance
Checks margin assumptions and agrees pricing conditions Sales can use.
-
03 Sales
Turns the approved offer into quotes and terms implementation teams can fulfill.
-
04 Implementation
Configures billing and delivery, then feeds errors and customer issues back.
Where it can loop: If margin criteria change after Sales prepares its quote templates, those templates may need another pass. If billing setup depends on the approved terms, it waits too.
What to count: Extra analysis, revisions and retesting. Report elapsed waiting separately, and estimate any delayed margin benefit only from a supported business case.
A simplified example, not a client case. Reviews can run in parallel; authority, controls and dependencies determine the actual path.
Project and work-management systems such as Workfront, ServiceNow, Jira, Asana, Smartsheet, and Planview show owners, status, deadlines, dependencies, workload, and blockers. Those records do not by themselves establish why a queue moved more slowly than the plan assumed or why completed work returned for review. Business process mapping documents the route. Emergent Skills traces what happened on that route and tests the operating explanation.
Before the route. We check the intended outcome, the priority leadership has chosen, the skills and resources available, and any external dependency setting the pace. If one needs attention first, we explain why. That alone does not rule out a work-path contribution. Previous success is useful evidence; a new result may require investigation of both capability and the work path.
What the delay costs
The delay is visible. Its full cost may not be.
Four hours of work followed by nineteen days waiting for approval can carry several costs. People may spend extra time chasing a decision, repeating a review or rebuilding context. A customer delivery, a billing milestone or the expected benefit of a launch may also move later. Count the extra labor separately from elapsed waiting and any financial effect the evidence supports. The five Capacity Taxes below organize those questions. Turnover and missed opportunities require additional evidence and stay outside the labor estimate.
01 Extra coordination
Meeting Tax · Traceable extra labor.
A delivery team spends the day in coordination meetings and finishes the deliverable after hours. Identify the extra meetings, follow-up and repeated explanations associated with the stalled result. Count that time once; do not assume every meeting or interrupted hour was wasted.
02 Rework and corrections
Decision Density Tax · Traceable extra labor.
A proposal returns because pricing criteria arrived after the review. People revise the numbers, repeat the checks and explain the change to the client. Those additional hours are a cost to investigate. Check whether the return reflects late criteria, necessary review or a quality problem.
03 Approval delays
Manager Load Tax · Waiting and extra labor reported separately.
Finished Monday, reviewed Thursday: the work waits, and both people may need to rebuild context. Record the waiting separately from time spent chasing or restarting. In the illustrative Northline sample, about 60 percent of elapsed time was waiting. That figure describes an invented case, not a client result.
04 Turnover exposure
Recovery Debt Tax · Requires additional evidence.
Repeated delivery pushes, persistent after-hours work and resignations deserve investigation. A Snapshot can flag the concern. Establishing whether work conditions contributed to a departure, and estimating replacement or ramp-up costs, requires evidence beyond one session.
05 Missed opportunities
Forfeited Upside Tax · Assumption-based exposure.
A pricing change or customer opportunity stays in a queue while its expected value remains unrealized. Estimate that exposure only from a documented business case or pipeline, with the assumptions shown. The invented Northline sample models roughly $7.5M of exposure. It is illustrative, not a measured client loss, and is excluded from the extra-labor estimate.
One traced result shows what happened on that occasion. Similar work may encounter the same condition, but that needs checking. Where the evidence supports a change, a 14-day experiment tests whether it helps relevant work move with less waiting or rework, while preserving required controls and quality.
How the number holds up
The Snapshot reports supported extra-labor estimates with the arithmetic and key assumptions beside the figure. The readout also names any unknown that could change the recommendation. Elapsed waiting stays in days, on its own line. The Tax categories overlap, so their figures are not added together. Turnover and opportunity exposure stay outside the labor estimate. The illustrative sample read shows the format and the calculation.
Common questions about business execution and stalled work
What if the work path is not the problem?
When the evidence supports that conclusion, the readout explains why. We first check whether the intended outcome still makes sense, whether leadership still chooses it as a priority, whether the required skills, information, authority and funding are available, and whether an external dependency controls the pace.
A problem in one of those areas can make a resource or leadership decision the next step. It does not, by itself, rule out a work-path contribution. If the evidence is insufficient, we say the cause remains unclear and name the evidence or decision needed next.
Is this a burnout, engagement, or L&D program?
The Snapshot investigates one project result. Broader ES work can also examine whether work demands are affecting how people use their skills. That is a separate question requiring its own evidence. A delay or low adoption alone does not establish burnout, disengagement, or a skills gap.
Could my team do this with AI?
Yes. Your team can use AI to help organize records, draft a map and examine possible explanations. The question is whether the investigation will get done and what evidence can support the decision.
With the Snapshot, ES leads a focused working session, checks explanations against the available records, and produces a written recommendation with its assumptions and limits. The Snapshot page sets out the scope and what to bring.
Bring one priority that still matters.
A stalled project, a partly delivered rollout, or a launch that has not produced the expected result. Start with a focused investigation and a recommendation about what to do next.