Nobody Changed Their Monday Morning

Corporate InnovationLayer 1Layer -1Internal Market ClarityProblem Classification

10 Mar

Why Funded Innovation Fails Without Internal Market Clarity

TLDR;-)
Most corporate innovation initiatives secure funding but skip internal go-to-market. They have a sponsor who says yes but no internal customer who will change their behaviour. Funding is not adoption. Until someone inside the organisation is willing to do something differently on Monday morning, the initiative is an expense, not an innovation.

Your pilot worked. Your sponsor renewed the budget. Your initiative is going to die.

Not because the technology failed. Not because the business case was weak. Not because someone cancelled the programme. It will die because you secured funding without securing adoption. You know who is paying for the initiative. You do not know who will use it.

This is the most commonly skipped layer in corporate innovation. Initiative teams jump from "problem is real and funded" to "let's run a pilot" without establishing who inside the organisation will actually adopt the output, what it will cost them to do so, and whether the value proposition survives translation into their vocabulary.

BCG's 2024 innovation survey puts a number on the pattern: 83% of companies rank innovation as a top-three priority. 3% are ready to act on those priorities. That gap is not a strategy problem or a technology problem. It is an adoption problem. Funded initiatives with no internal market.

In the Critical Path Layers framework, this is Layer 1: Internal Market Clarity. It sits between problem legitimacy (Layer 0) and organisational feasibility (Layer 2). For the full framework structure, see our article Critical Path Layers: A Dependency Map for Innovation. Everything in this article can be applied without the framework. But if you are running multiple initiatives, the dependency sequencing explains why this layer matters where it sits.

Funding is not adoption

A sponsor says: "This aligns with our strategic priorities. Here's the budget."

An internal customer says, or more often doesn't say: "This will make my Monday morning different. I'll reorganise my workflow around it."

The gap between those two statements is Layer 1. The sponsor absorbs the financial cost of the initiative. The internal customer absorbs every other cost.

This is why your initiative needs an internal go-to-market strategy. The phrase sounds strange. Why would an innovation inside your own company need a GTM strategy? Because the initiative has to reach people who have other things to do. Whose performance is measured on existing metrics. Who will bear the cost of adoption personally. They are not a captive audience. They are an internal market, and they behave like one.

Three elements determine whether that market exists.

Identifying the internal customer.
By name, by role. Not by function. "The operations team" is not an internal customer. Maria, the operations lead in Region North, who currently spends 14 hours per week on manual reconciliation, is an internal customer. If you cannot name three people who will change their behaviour when this initiative succeeds, you do not have internal market clarity. You have a hypothesis.
The demand signal.
Is there evidence these customers want this? Not that they would agree it's a good idea if asked. Internal customers will say yes to almost anything their boss's boss endorses. The question is whether they are experiencing pain the initiative addresses, and whether that pain exceeds the cost of adopting your solution. Agreement is not demand. Politeness is not pull.
Channel strategy.
How will the initiative reach its internal customers? Top-down mandate? Peer networks? Formal programme with training and support? The choice depends on the initiative's classification. Optimisation can often use top-down mandates because the change is bounded. Adjacency usually requires a combination because the change crosses functional lines. Transformation requires sustained multi-channel effort because the change asks people to see their roles differently. Choosing the wrong channel is as damaging as choosing the wrong product-market channel in a startup. It is the same problem, with the additional constraint that you cannot fire your internal customers.

The five adoption costs

Initiative teams underestimate adoption friction because they think of it as one thing: "resistance." It is not one thing. It is five different costs, each with a different driver.

Time cost.
How many hours will the internal customer need to invest in learning, adapting, and integrating the innovation? Not your estimate. Their estimate, which will be higher. Is this time available, or is it competing with existing commitments that already consume their week? An initiative that requires 10 hours of adoption work from someone who has zero slack in their calendar is not facing resistance. It is facing arithmetic.
Cognitive cost.
New tools. New processes. New terminology. New ways of thinking about work they have been doing competently for years. The cognitive load of adoption is often the binding constraint, especially for transformation initiatives. You are asking someone who is good at their job to become temporarily bad at their job. That is a real cost, and it is felt most acutely by the people who are best at the current way of working.
Political cost. This is the cost initiative teams almost never see, and it is frequently the one that kills adoption.

Does adopting this initiative align the internal customer with a faction, a leader, or a strategy that might not endure? Does it put them at odds with colleagues who haven't adopted? Does visible enthusiasm for the initiative mark them as "one of those innovation people" in a culture that rewards operational reliability?

Political cost is invisible to the initiative team because the initiative team is already politically committed. They cannot imagine why someone would hesitate to join them. The internal customer can. The internal customer is reading the room, tracking which senior leaders actually attend the steering committee meetings versus which ones send deputies, and calculating whether this initiative will still have sponsorship in 18 months.

The organisational immune response mechanisms I described in The Organisational Immune Response are, in part, the collective expression of high political cost. Procedural resistance and passive waiting are what political cost looks like at the systemic level.

4. Opportunity cost.
What will the internal customer not be doing while adopting this innovation? Every hour spent on the new thing is an hour not spent on the old thing. If the old thing is what their bonus is based on, the opportunity cost is not abstract. It is the difference between a 3 and a 5 on their next performance review.

This cost is particularly destructive because it is invisible to the sponsor. The sponsor sees the initiative as additive: we are giving the team a new capability. The internal customer sees it as substitutive: I now have to do this and everything else. When the initiative team presents the time requirement as "only two hours per week," the internal customer hears "two hours per week of work that will not appear in my performance review, taken from two hours per week of work that will."

5.Switching cost.
If the initiative fails or is discontinued, what is the cost of reverting? If the internal customer has reorganised their workflow, retrained their team, rebuilt their reporting around the innovation, and the initiative gets pulled after a leadership rotation, they are left exposed. This creates a legitimate reluctance to adopt anything that might not endure. It is not resistance. It is risk management.

The initiative team's response is usually: "But this initiative isn't going to fail." The internal customer has heard that before. From the last initiative, and the one before that.

The triangle dynamic

Internal market clarity involves a three-way dynamic. Each party has different motivations, different information, and different risk profiles. Understanding all three is not optional.

The initiative team wants the project to succeed. Motivated by career advancement, intrinsic interest, genuine belief. Their blind spot: overestimating the internal customer's willingness to change and underestimating political complexity. The initiative team lives inside the initiative. They forget that the internal customer lives outside it.

The executive sponsor wants to be associated with successful innovation. Motivated by strategic positioning, organisational legacy, competitive pressure. Their blind spot: underestimating the operational cost of adoption and overestimating the power of top-down mandates. A sponsor who says "just tell them to use it" has confused authority with adoption.

The internal customer wants to do their job effectively with minimal disruption. Motivated by performance metrics, career safety, workload management. Their blind spot: undervaluing long-term transformation benefits in favour of short-term stability. This is a rational response to incentive structures that reward quarterly delivery over multi-year capability building.

Layer 1 succeeds when the value proposition addresses all three perspectives. When it doesn't, the failure mode is diagnostic.
Value proposition works for the sponsor but not the customer: funding without adoption.
Value proposition works for the customer but not the sponsor: grassroots interest without structural support.
Value proposition works for the initiative team but neither the sponsor nor the customer: innovation theatre.

If you recognise your initiative in one of these three sentences, you have a Layer 1 problem. You may also have spent the last six months treating it as a Layer 2 or Layer 3 problem: building pilot plans, creating scaling playbooks, designing training programmes. All downstream work on an unresolved upstream dependency.

Two tests

The internal value proposition must pass two tests before it is ready for the internal market.

The translation test.
Can you state the value proposition in the internal customer's own vocabulary? Not in innovation-speak. Not in strategy-deck language. Not in the terminology the initiative team uses with each other. In the words the internal customer uses to describe their work, their frustrations, and their goals.

If the value proposition requires a glossary, it is not ready. If it relies on terms the internal customer has never used in a team meeting, it is not ready. If you can only articulate it using your language rather than theirs, you have not translated. You have presented.

The "compared to what" test.
Every internal customer has a current way of doing things. The value proposition must be better than the status quo on the dimensions the internal customer cares about. "Better" might mean faster, cheaper, more accurate, less risky, or more career-enhancing. But it must be better on criteria the customer recognises. Not criteria the initiative team thinks should matter.

This test kills more value propositions than any technical validation. The initiative team believes the new approach is obviously better. The internal customer compares it to their current workflow, which they have spent years optimising, and arrives at a different assessment. The initiative team is comparing the innovation to the problem. The internal customer is comparing the innovation to their solution, which already exists and already works, even if imperfectly.

Classification changes everything

How Layer 1 plays out depends entirely on how the initiative is classified. I've written about the classification problem in The AI Classification Problem. The short version: treating a transformation as an optimisation is the single most common root cause of corporate innovation failure. It affects every layer, and at Layer 1, it is decisive.

Optimisation. The internal customer is obvious: the process owner and their team. The value proposition is quantitative: time saved, errors reduced, cost avoided. Adoption cost is low because the workflow changes are bounded. The triangle dynamic is straightforward. Layer 1 is usually quick.

Adjacency. The internal customer may be in a different function than the initiative team. The value proposition needs to bridge vocabulary gaps between functions. Political cost enters because the initiative crosses territorial boundaries. The triangle dynamic involves inter-functional politics. Layer 1 requires deliberate cross-functional relationship work.

Transformation. The internal customer may not yet exist as a role. The value proposition may require the customer to see themselves differently: "You are not just a procurement manager; you are a strategic sourcing partner." Adoption cost is high across all five dimensions. The triangle dynamic involves multiple sponsors and conflicting customer groups. Layer 1 is the longest and most politically complex phase of the entire initiative.

The diagnostic insight: if your initiative is classified as transformation but you are treating Layer 1 as though it were optimisation, you are building on a false foundation. Assuming the customer is obvious, the value proposition is quantitative, the adoption cost is low. The classification sets the difficulty of every subsequent layer. Get it wrong here, and the error compounds.

Where you are

Four diagnostic questions. Answer them about your current initiative. Not in general. Specifically.

Can you name three internal customers, by name and role, who will change their behaviour if this initiative succeeds? Not sponsors. Not stakeholders who attend your steering committee. People who will do something differently on Monday morning.

Can you state the initiative's value proposition in the internal customer's vocabulary? Not in innovation-speak, not in strategy-deck language, but in the words they use to describe their work?

Have you estimated the five adoption costs, and is the estimate the internal customer's assessment, not yours?

Which triangle failure mode is your initiative closest to: funded but not adopted, grassroots but not supported, or believed by the team but not by either?

Layer 1 is where most corporate innovation quietly fails. Not with a rejected proposal or a cancelled budget, but with a funded initiative that nobody inside the organisation is willing to use.

What the answers tell you

The diagnostic questions above are not rhetorical. Each one points somewhere specific.

If you cannot name three internal customers by name and role, you do not have an adoption problem. You have a discovery problem. The work is not stakeholder engagement. The work is sitting inside the adopting function long enough to understand who actually does what, where the pain is, and whether the pain your initiative addresses is the pain they would prioritise. This is not a workshop exercise. It requires time in the operational environment — watching, asking, and listening for the language people use when their manager is not in the room.

If the value proposition fails the translation test, the issue is not messaging. It is proximity. You are too far from the internal customer to speak their language. The resolution is not to rewrite the deck. It is to build the relationship that would make the deck unnecessary. Find one internal customer who is willing to co-develop the value proposition in their vocabulary. If that person does not exist, your initiative does not yet have an internal market. It has an internal audience.

If the "compared to what" test reveals that your innovation loses to the status quo, do not argue. Understand what the status quo provides that you do not. Often it is predictability, social proof, or compatibility with existing performance metrics. The initiative may need to address the switching cost and opportunity cost before it can compete on capability. Sometimes the honest conclusion is that the internal customer's current solution is good enough, and the initiative's value lies elsewhere in the organisation. Redirecting is not failure. Persisting with the wrong internal customer is.

If you recognise a triangle failure mode, the mode itself is the instruction. Funded but not adopted means the sponsor relationship is working but the customer relationship is not: invest there. Grassroots but not supported means the customer relationship exists but the sponsor has not committed structural resources: make the business case in the sponsor's vocabulary, not the customer's. Believed by the team but neither sponsor nor customer: the initiative may be solving the wrong problem, or solving the right problem for an organisation that is not ready. This is the hardest diagnosis to accept. It sometimes means stopping.

Layer 1 resolution is not a single action. It is repeated, specific contact between the initiative and the people who would need to change their behaviour. The tests tell you whether that contact has happened. If it has not, no amount of downstream work — pilots, playbooks, scaling plans — will substitute for it.
Assess where you are and give our micro-diagnostic interactive tool a spin: https://resources.aieutics.com/permanence-diagnostic/

Alexandra Najdanovic is the founder of Aieutics, working with corporate innovation teams on strategic transformation and innovation sequencing.