You're here because something isn't adding up. Your team is working hard. Meetings are full. Reports are flowing. People are putting in the hours. But when you look at the numbers that actually matter, revenue targets, strategic milestones, the initiatives that were supposed to move the company forward, they're not landing.
And it's not because your people aren't trying.
You've probably told yourself this is a performance issue. Maybe you need better talent. Maybe you need tighter KPIs. Maybe you just need everyone to "execute better."
Here's what's actually happening: the work itself is broken.
Not the people doing it. Not their effort. Not their intentions. The structure underneath it all, the way work gets assigned, owned, prioritised, and connected to your strategy, that's where it falls apart.
After scaling a company to a $2 billion NASDAQ listing, I've seen this pattern from the inside. The CEO sees output. Activity. Busyness. But underneath, the organisation is bleeding time, money, and momentum on work that was never set up to succeed.
I call it non-productive work. And it comes in eight specific forms.
The first four are Vague Work, where the outcome, scope, or ownership is unclear. This is the work that exists because nobody asked whether it should. The orphaned initiatives. The duplicated efforts. The projects resourced at 100% on paper but 40% in reality. The hero who saves the day while the system quietly collapses behind them.
The next four are Fragile Work, where the path, value, or impact is unclear. This is the work that keeps moving even though the team knows it's headed nowhere. The decisions that never get made. The mandates handed down with no room to push back. The tickets closed without context. The deliverables that hit spec but miss the point entirely.
Right now, your organisation is almost certainly carrying three or four of these. Maybe more. And nobody is naming them.
That's the real problem. Not effort. Not talent. Not commitment. It's that these patterns are invisible inside your current reporting, your dashboards, your standups. You can't see them, so you can't fix them. And your accountability structures break down, not because people are avoiding responsibility, but because the work was never structured in a way that made accountability possible in the first place.
The good news: once you can see them, you can eliminate them.
That's what the eight forms below will show you, the specific ways productive-looking work silently consumes your capacity, your capital, and your strategic momentum. Read through them. You'll recognise your organisation in at least three.
The required outcome, scope, and/or team are unclear.
Orphaned work exists because the strategy said one thing and the organisation did another. Sometimes the work isn't needed at all. Sometimes it's over-engineered for the purpose. Sometimes it's the opposite: critical work that should exist to support the strategy but has no team to deliver it because nobody defined it.
This happens for two reasons. First, teams default to doing what they already know rather than what the new strategy demands. Second, when strategy cascades through functional silos, some functions do their part while others quietly prioritise their own backlog. The result is the same: even the work that is aligned to strategy becomes orphaned because critical connecting pieces are missing.
Marcus, VP of Engineering at a mid-size industrial software company, noticed his most senior team — eight engineers billing at $180/hour — had been heads-down for three months rewriting the integration layer of a legacy product. The work was technically excellent. But when Marcus cross-referenced it against the product roadmap during a quarterly review, he discovered the entire product was scheduled for end-of-life in fourteen months.
The rewrite was never needed. A short-term component buy would have bridged the gap at a fraction of the cost. Nobody had asked whether the work connected to the strategy because nobody had made that connection explicit. Direct cost: roughly $520,000 in loaded engineering time. Opportunity cost: those eight engineers could have been building the integration layer for the new platform — the one that was now six months behind schedule because it was under-resourced.
Adrienne, CEO of a fast-growing logistics tech company, secured board approval for an aggressive push into cold-chain pharmaceutical delivery. She cascaded the strategy through her functional leaders and felt confident everyone was aligned.
Six months later, the picture was fractured. The commercial team had won three pilot contracts. Product had designed a temperature-monitoring module. Operations had mapped new warehouse configurations. But technology had never built the real-time compliance API that connected all three workstreams. Their VP had quietly prioritised a different project he considered more important.
Every individual function had delivered work. But the strategic initiative was orphaned because the connecting piece didn't exist. Three pilot customers received apology calls. Two of them went to a competitor.
Duplicate work is the tax you pay for growing faster than your coordination structures can keep up. When companies scale, communication retracts into silos. Leaders cascade objectives down their functional chains without visibility into what other functions are doing with the same objective. The result is two or more teams unknowingly replicating effort.
Functionally organised companies are especially prone to this. Without strong cross-functional governance, the same problem gets solved multiple times by different people who never talk to each other.
At a Series C fintech company with 300 employees, the Marketing department spent $55,000 licensing and implementing a third-party customer analytics tool to track user engagement across their product funnel. They had it running within six weeks.
Three floors up, the Product team — with no knowledge of Marketing's project — spent the same six weeks building a custom analytics dashboard from scratch. Two engineers and a data scientist invested roughly 720 combined hours building what they considered essential infrastructure for product-led growth. Their dashboard tracked the exact same metrics.
Neither team discovered the overlap until a board meeting, when the CEO asked why two slides showed the same user engagement data from different sources. With slightly different numbers. The direct financial waste was roughly $160,000 in combined tool costs and engineering time.
Chen, COO of a healthcare technology firm, was reviewing the annual budget when he noticed two separate line items for "customer onboarding redesign": one from Customer Success, one from Professional Services. Both had been running for four months.
When he pulled the teams together, he found they had each independently interviewed the same customers, mapped the same pain points, and designed competing onboarding workflows. Eight months of combined effort had produced one deliverable that could have been completed in four. And it would have been better, because both teams' insights would have been combined from day one.
This is the most insidious form of structural failure. Choked Work occurs when your best people are spread too thin across too many competing priorities.
The root cause is a blind spot around business-as-usual (BAU). While it is straightforward to measure the load on a direct production worker, standard systems completely fail to capture the invisible operational drag on expert knowledge workers. They are constantly pulled between vendor calls, urgent approvals, team management, and six different Slack channels.
The resulting math is brutal: leadership allocates 100% of an expert's time to a new strategic initiative, completely ignoring the 40–60% of their week already consumed by operational tasks. The strategic work doesn't fail because of a lack of talent. It fails because the capacity never existed.
Priya, a mid-level Director at a consumer goods company, was handpicked by the CEO to lead a high-visibility supply chain transformation — the single most important initiative on the company's strategic roadmap. She had the expertise and the drive.
But nobody restructured Priya's existing responsibilities. She was still expected to handle her daily quota of operational approvals (roughly 15 per day), still the escalation point for vendor disputes, still managing a team of twelve including one underperformer on a performance improvement plan.
Of her 45 available hours per week, 32 were already committed to recurring operational obligations. She had 13 hours per week for the company's most important strategic initiative. The transformation stalled within two months — not because Priya lacked talent, but because her structural capacity was mathematically over-allocated from day one.
Raj, CTO of a rapidly scaling SaaS company, committed his platform engineering team to three concurrent strategic initiatives: a cloud migration, a new API marketplace, and a security compliance overhaul mandated by their largest enterprise client.
Each initiative looked feasible on its own. But Raj hadn't accounted for the operational load his team was already carrying: production incident response (averaging 10 hours per week per senior engineer), code reviews for four product teams, and participation in six cross-functional steering committees.
Within three months, all three initiatives were behind schedule. His best engineers were context-switching so frequently that their effective output dropped by an estimated 40%. The security compliance initiative eventually missed its contractual deadline, triggering a penalty clause worth $400,000.
Hero work is the most dangerous form of structural disorder because it feels like victory. When your best people see a problem, they dive in and fix it. They work weekends. They pull all-nighters. They save the launch. Everyone applauds.
But the structural damage is enormous. The team that was supposed to deliver the work gets disempowered. They didn't learn to solve the problem themselves. The hero's own responsibilities get neglected. And the organisation learns exactly the wrong lesson: that the system works, when in reality it was held together by the willpower of a single individual who cannot sustain the effort.
Hero culture scales until it breaks, and when it breaks, it breaks catastrophically. Usually when the hero burns out or leaves.
Lena, CTO of a mid-stage SaaS company, was two weeks from a major product launch when the backend integration broke. The team responsible — three mid-level engineers — had been struggling with the architecture for days.
Lena rolled up her sleeves and dove into the code. She worked 14-hour days for ten straight days, personally rewrote the integration layer, and hit the launch deadline. The board was thrilled. The team celebrated.
But three things happened that nobody celebrated. Her engineers learned nothing and concluded they weren't trusted. Her executive work was completely neglected for two weeks. And the company learned that "Lena will fix it" was a viable execution strategy.
Within twelve months, she handed in her resignation. The company lost its CTO — not because of a competitor offer, but because the structure had turned her into a load-bearing wall instead of an architect.
David, founder and CEO of a 200-person professional services firm, had a pattern. Every time a major client relationship hit trouble, David personally stepped in. It worked every time. But his direct reports gradually stopped developing their own client management instincts. Why would they? David always swooped in before real consequences landed.
When David was hospitalised for three weeks with a cardiac episode — directly linked to chronic overwork — three client relationships simultaneously went into freefall. None of his managing directors had the experience, confidence, or relationships to stabilise them. Two clients churned. Combined annual contract value lost: $2.4 million.
The path, value, and/or impact are unclear.
You cannot delegate a task without delegating the authority to execute it. When leadership assigns outcomes but leaves decision-making power unsaid, the vacuum gets filled in one of two destructive ways.
In the first, nobody decides. Authority is unclear, so every decision becomes a committee exercise, an escalation chain, or an indefinite delay. In the second, the wrong person decides. A well-intentioned manager, under pressure and lacking clear boundaries, makes a call that belongs to someone else — someone with context they don't have.
A cross-functional tiger team at a B2B software company was assembled to redesign the pricing model — a strategically critical initiative expected to add $8 million in annual revenue. They had a clear mandate from the CEO: "Fix our pricing." What they didn't have was authority.
The team met every week for four months. They built pricing models. They ran conjoint analysis. They produced three detailed recommendation documents. But nothing shipped, because every meeting ended the same way: a well-reasoned recommendation, followed by a debate about who had the power to approve it.
After four months, the team was disbanded. No pricing changes were made. The $8 million revenue opportunity sat untouched, and twelve senior people had spent roughly 400 hours in meetings that produced nothing.
Greg, CTO of a logistics software company, was three weeks from a contractual delivery deadline with a $150,000 late delivery penalty on the line. He reviewed the remaining scope and made what he considered a logical call: cut the integrated communications module from the release.
The release shipped on time. The penalty was avoided. But the communications module was a contractual requirement, not a nice-to-have. Retrofitting it into the already-shipped platform cost $280,000 in rework — nearly double the penalty Greg had been trying to avoid.
Had Greg consulted the VP of Sales, he would have learned the client had privately indicated flexibility on the deadline but considered the comms module non-negotiable. The information existed in the organisation. Greg simply didn't know he needed it, because nobody had defined where his decision authority stopped and cross-functional consultation began.
Defeatist work is the quiet killer. It occurs when the people responsible for execution believe — often with good reason — that the outcome is impossible given the constraints they've been handed. They don't revolt. They don't refuse. They simply go through the motions, knowing it will fail.
This isn't a cultural problem with "negative people." It's a structural problem with farming dissent. When leadership hands down an ambitious mandate without creating space for the team to push back on feasibility, the team checks out mentally.
The most insidious part: the initiative doesn't die quickly. It dies slowly, cynically, over months. Consuming resources the entire time.
The C-Suite at a precision manufacturing company mandated a 30% reduction in production costs within a single quarter. The mandate came with a non-negotiable constraint: no changes to product scope, quality standards, or supplier agreements.
The engineering team knew immediately that it couldn't be done. But leadership hadn't asked them. The mandate was presented as a directive, not a discussion.
The initiative died a slow, cynical death over five months. It consumed roughly 2,000 hours of engineering time, produced no meaningful cost reduction, and left a residue of distrust between the engineering team and the executive suite that persisted for years.
Sophie, VP of Engineering, was given a hard deadline: ship a major platform feature in eight weeks. Her team estimated twelve weeks minimum. Sophie raised the concern once. She was told the date was immovable because of a marketing commitment. She didn't raise it again.
Her team knew the timeline was impossible. Their standups became performative. Senior engineers stopped volunteering for stretch tasks. Two junior developers began quietly interviewing at other companies.
The feature shipped two weeks late with critical stability bugs causing a 40% increase in crash rates. The post-mortem blamed "engineering quality," but the root cause was that no one had structured a dissent process to force an honest trade-off discussion before the team checked out.
Apathetic work is the scourge of the modern knowledge organisation. It happens when people do the task on the ticket with no understanding of why it matters. They follow the standard operating procedure. They meet the spec. They close the ticket. And they leave enormous value on the table because they had no context to do anything more.
This is counterintuitive: the more you lean and optimise your knowledge work with SOPs and workflow systems, the more likely apathy becomes, especially in the face of uncertainty. You've turned experts into assembly-line ticket takers.
A backend developer named James received a Jira ticket: "Build API endpoint for customer usage analytics. See attached spec." James was good at his job. He followed the spec precisely, wrote clean code, passed the tests, and shipped the endpoint in four days.
What James didn't know, because nobody told him, was that the customer requesting this capability was the company's second-largest account, and the data they needed would inform a $3 million contract renewal decision.
Had James known the context, he would have flagged something: a similar analytics endpoint already existed in the codebase, built eighteen months ago. It would likely have satisfied this customer as is, or at most required a few hours of minor adaptation. The company spent four unnecessary days building an inferior solution because no one connected a $30/hour task to a $3 million relationship.
A compliance team at a financial services firm was tasked with documenting internal controls for an upcoming regulatory audit. They were given a 140-item checklist and told to work through it systematically.
They did. Mechanically. No one raised systemic patterns. No one flagged that seven controls were fundamentally redundant. No one suggested that two controls were dangerously outdated.
The audit passed. Six months later, a regulatory investigation uncovered the outdated controls. The resulting remediation cost $2.8 million and consumed the compliance team for five months — fixing problems they had collectively walked past because their SOP never asked them to think. Only to document.
Disconnected work occurs when the work being delivered and the value expected by stakeholders drift apart during execution, and nobody notices until it's too late. In stable environments, this drift is manageable. In volatile, uncertain, or rapidly changing markets, it's inevitable unless you build dynamic feedback structures.
This is a leadership problem, not a team problem. Managing stakeholder expectations while simultaneously navigating uncertainty, realigning teams around moving targets, and maintaining delivery momentum requires an unusually high combination of strategic thinking and emotional intelligence. Most delivery leaders don't have frameworks to help them do this.
An enterprise software team — 14 engineers, two designers, and a product manager — spent eight months building a robust, on-premise security solution for a major client. Every feature met spec. Every test passed. The documentation was immaculate.
Four months into development, the client's board shifted their entire IT strategy to cloud-first. The client's CISO mentioned this in passing during a quarterly check-in, but the information never reached the delivery team. The product manager logged it as "FYI, client exploring cloud options" and continued execution against the original brief.
When the team delivered, the client's response was polite but devastating: "This is excellent work. We can't use it. We moved to the cloud." Eight months. Fourteen engineers. Roughly $2.2 million in delivery cost. A product that was technically perfect and strategically worthless.
Mei, Product Director at a B2B analytics company, launched a six-month initiative to build an advanced predictive forecasting module — the single most requested feature in their annual customer survey. Halfway through development, a well-funded competitor launched a near-identical feature at a lower price point.
Three of Mei's largest customers told their account managers they were evaluating the competitor. The account managers logged the feedback in the CRM. The information sat there for six weeks. Nobody escalated it to Mei because there was no structured mechanism to connect real-time market intelligence back to product execution decisions.
The feature launched to modest adoption. Two of the three customers had already switched, taking $1.6 million in annual recurring revenue with them. The failure was entirely structural: no framework existed to keep execution connected to rapidly shifting stakeholder value.
Every one of these eight disorders shares a root cause: the structure of work failed to adapt to the strategy, the environment, or both. They aren't talent problems. They aren't motivation problems.
Our 5-step Outcome-Focused Productivity Road Map begins with demonstrating immediate productivity gains, achieved by changing how the C-Suite structures the delivery of your strategy.
Book a 15-Minute Discovery →