Skip to content
Back to articles

AI productivity strategy: the code behind stalled adoption

August 8, 2026 15 min read
Share
An orange survey marker stands in a vast prairie at sunrise, mapping the hidden terrain of the productivity code

You launched AI and trained people to use it. Adoption is stuck near the starting line, and the steering committee cannot name the real problem.

The AI works and people can use it. What holds adoption back is that using AI conflicts with how people get promoted in your organization. Until you redesign the invisible rules that govern daily work (what we call the productivity code), the dashboards will stay flat. This piece maps the conflict and shows how to surface the real code and rewrite it so adoption can move.

The Meeting Nobody Wants to Name.

Picture an AI steering committee session, late in the meeting and deep into the deck. Licenses are deployed and the dashboards are live.

Adoption is low and has not moved. The vendor swears the product works. IT confirms no technical blockers.

L&D reports completion rates above target. The CHRO says it is a people problem. The CFO wants to know when the ROI shows up.

And nobody in the room will say the thing everyone already knows: the technology is fine, and it is not moving because using it conflicts with how people get promoted here.

That conflict has a name. We call it the productivity code.

Every organization runs on an invisible set of rules that govern how work really gets done and what behavior the system rewards. It sits underneath the mission statement and the stated values.

It is the unspoken operating system that determines whose work gets seen and who gets ahead. And when you launch AI that conflicts with that code, adoption does not happen. People default to the behavior that made them successful under the old rules, even when leadership mandates the new ones.

The distance between what you announced and what changed is a code conflict. And until you map the real productivity code and redesign it around AI, the dashboards will stay flat.

What the Productivity Code Is.

The productivity code is the collection of unwritten rules that govern daily work: what tasks signal competence, what outputs prove value, how effort becomes visible to management, and which behaviors lead to advancement. It is undocumented and undiscussed, but it shapes every decision an employee makes about how to spend their time.

Take a professional services firm where the productivity code is simple: billable hours above all, and client face time as proof of seniority. The firm buys an AI assistant to automate research and first-draft document generation. The assistant works.

Adoption stalls anyway. The reason: using the assistant reduces billable hours and makes the work invisible to partners who value visible effort. The time it frees up is time the system has no way to recognize or reward. The productivity code says grind equals value.

The AI assistant and the code point in different directions, and people follow the code because that is what the firm rewards.

Picture the same conflict in clinical work. A healthcare organization deploys AI scheduling and triage support to give clinicians time back for patient care, while the real productivity code rewards documentation volume and committee participation.

Using the AI assistant creates time, but the system has no mechanism to recognize that time as valuable unless it goes into the old signal behaviors. Clinicians default to the documented grind, and the AI sits unused.

The productivity code evolved to solve real problems: how to measure contribution in ambiguous work, and how to allocate finite promotion opportunities. But it calcifies.

And when AI requires new behavior, the code does not update automatically. It has to be redesigned, deliberately and visibly, or people revert to what made them successful before.

Why Existing Productivity Codes Resist AI.

Many productivity codes evolved in an environment where effort and output were tightly coupled, where time spent was the best available proxy for value delivered, and where visibility required physical presence or documented activity. AI breaks all three assumptions.

AI decouples effort from output. Suppose a task that took half a day now takes moments. The code has no category for that. If your advancement depends on being seen working late, and the AI finishes the work by lunchtime, the rational move is not to use it.

AI makes expertise less visible. If the system generates the first draft or routes the decision, the human work shifts to judgment and oversight. But oversight is invisible.

Judgment does not leave a billable trail. The productivity code rewards visible grinding.

AI redistributes status. In many organizations, certain tasks signal seniority and others signal junior work. AI collapses that hierarchy.

When AI can do the analysis a senior analyst spent years learning to do, the old rule that mastering that analysis earns you the next role stops making sense. The senior analyst can learn to use AI. They resist because using it undermines the signal that justified their position.

Resistance here is rational behavior inside a system that has not updated its reward structure. People protect the productivity code because it protected them.

Ground Truth: Mapping the Code Before You Change It.

The usual approach to AI adoption is to announce AI launches with training and expect behavior to follow. That sequence assumes the productivity code will update itself. It does not.

The code is durable and invisible, enforced by small daily interactions: who gets invited to the meeting and who gets tapped for the next opportunity. Changing behavior without changing the code just creates shadow resistance: people comply in public and route around AI in private.

Ground truth before prescription means mapping the real productivity code first: the invisible rules that govern daily work, whatever the stated values and the official competency model say.

A first step is the AI Profit Ready Assessment: eight questions, and a read on where your team's AI use is and is not paying back. Mapping the code itself takes the questions below, asked of the people who live under it. The distance between the official answer and the real one is the productivity code.

Or take a financial services company where the official story is collaboration and client outcomes. The real code is individual deal ownership: protect your pipeline and never share a lead until the contract is signed. Leadership announces an AI assistant to surface cross-sell opportunities and share client insights across teams.

Adoption goes nowhere. Sharing a lead before it closes is giving away your bonus. The assistant requires exactly the behavior the code punishes, and no amount of training changes that arithmetic.

The comp plan was designed to drive aggressive individual accountability, and it is doing precisely that.

The assistant requires collaboration and the code rewards hoarding. Until the comp plan changes, behavior will not.

Ground truth makes the invisible code visible so you can redesign it deliberately.

The Questions That Surface the Real Code.

Mapping the productivity code requires asking questions the org chart does not answer:

  • What tasks do people protect, even when AI could do them faster?
  • What work makes someone visible to leadership, and what work is invisible no matter how well it is done?
  • What behavior got the last three people promoted, regardless of what the competency model says?
  • When someone has extra time, where do they put it to maximize their career outcome?
  • What does the organization say it values, and what does it measure and reward?

The distance between the answers is the code. And the code will not change just because you announced an AI launch.

People Before Process Before Platform: Redesigning the Code.

Once the productivity code is visible, the work is to redesign it so the new behavior becomes the path to success.

People before Process before Platform is the design sequence. Start with the people: what do they need to believe about their own value and career trajectory for the new behavior to make sense? Then redesign the process: the comp plan, the promotion criteria, the visibility mechanisms, the feedback loops.

Only then does the platform matter. The common mistake is to do it backward: ship the platform and assume people will follow. They do not, because the real code has not changed.

In the financial services example, the redesign starts with people. The executive team has to acknowledge that the current code rewards hoarding and that using the AI assistant requires a different definition of success. Individual performance gets redefined to include team revenue contribution alongside personal deals closed.

Cross-sell referrals become a formal input to bonus calculations. Collaboration gets tracked and made visible the way closings already are. Then the process updates behind it: pipeline reviews include shared opportunities, and managers are trained to recognize and reward referral behavior in real time.

Adoption moves only after the code has been redesigned. Sharing a lead has to be the thing that leads to advancement before anyone will share one.

In the healthcare example, the redesign starts with one change to the productivity code: clinical judgment time becomes a measured and rewarded category. Patient-facing time as a percentage of total shift hours becomes a metric, and it becomes visible in performance reviews. Using AI to automate scheduling and triage raises that percentage, and the rise counts as evidence of effective practice.

AI stops being a threat to documented grind and becomes a way to prove higher-order clinical contribution. Adoption follows.

Redesigning the code makes AI the rational path to the outcome people already want. When the code rewards the new behavior, resistance drops, because the system has changed.

Start With Identity.

People change behavior when the new behavior aligns with who they believe they are and who they want to become. The productivity code is also a definition of identity: what it means to be senior and what it means to be indispensable.

When AI requires new behavior, it requires a new identity. If your identity is built on being the person who can do the analysis faster than anyone else, and the AI now does it instantly, your identity is under threat. Telling you to use AI is telling you to become obsolete.

Starting with identity flips the sequence. Ask first: who do you need to be for this to make sense?

In the financial services example, the identity shift is from lone-wolf closer to multiplier and collaborator. In the healthcare example, it is from documentarian to clinical expert with leverage. Once the identity shift is clear and supported, the new behavior follows.

The outcome is the career progression people already wanted, now achieved through the new behavior, without the old grind.

If the productivity code defines identity around visible effort and individual heroics, that is who people will be, regardless of what AI you deploy. Redesign the code to reward judgment and collaboration, and identity shifts. Behavior follows identity.

The Messy Middle: Where the Old Code and the New One Collide.

Redesigning the productivity code does not happen in a single announcement. It happens in the messy middle, the months-long stretch where the old code and the new one are both active. Some people are rewarded for the new behavior while others still advance under the old rules, and everyone is watching to see which one wins.

The messy middle is where AI transformations stall. Leadership announces the new way. Middle management, whose own advancement depended on mastering the old code, defaults to rewarding what they know. Frontline employees see the conflict and choose the safer path: comply in public and route around AI in private while they wait to see which code controls their next promotion.

The messy middle is the transformation itself, and the work is designing through it.

Intelligent Resistance as Signal.

In the messy middle, resistance is data. When people resist AI, they are telling you where the old rules are still active and where the conflict between stated intent and real incentives is sharpest.

Treat intelligent resistance as signal. If a team is not using AI, the first question is what part of the existing code the AI is threatening. What behavior does it require that the current system does not reward?

What identity does it undermine, and what visibility does it erase?

Consider a sales team that resists a CRM-integrated AI assistant automating pipeline tracking and next-best-action recommendations. The stated reason is that the assistant is clunky. The underlying reason is different. The assistant makes each person's pipeline visible to leadership in real time, and that visibility erodes their negotiating leverage on quota and territory assignments.

The assistant works, and the resistance is rational, because the code says protect your information.

The fix is in the incentive structure. Leadership can commit to using pipeline data only for resource allocation and coaching, and not for punitive quota adjustments mid-quarter.

That commitment has to be public and enforced in the moments where the old code would have won. Trust takes time to rebuild, and adoption follows trust.

Resistance drops when the code changes to make using AI safe.

Intelligent resistance is the workforce telling you the truth. Listen to it.

Managing the Transition Without Breaking Trust.

The messy middle requires visible leadership commitment and ruthless consistency. People will not believe the new code is real until they see it enforced, repeatedly, in situations where the old code would have won. Promoting someone who used AI to deliver faster outcomes, even if their billable hours are lower, is what changes the code.

So is recognizing collaboration in a system that used to reward solo heroics, especially when quarterly pressure pulls toward the old signals.

Leadership has to model the new behavior, visibly and early. If the CEO says AI is strategic and then never mentions it again, the code has not changed. If the CFO says speed matters more than hours and then approves a promotion based on hours logged, the code has not changed. The workforce watches what gets rewarded.

The AI Profit Partnership gives a leader and their team the step-by-step structure to manage the messy middle without breaking trust. It starts with ground truth: research into how the team works today and where the leader's view and the team's do not match. Quick wins go in along the way, and it ends in a plan for the year ahead.

What Success Looks Like.

Success is the productivity code visibly changing so the new behavior becomes the default path to advancement, and resistance drops because AI aligns with how people now prove their value.

When the code changes, the shift shows up in specific observable patterns:

  • People start using AI because it makes them better at the work the new code rewards.
  • Middle managers stop defaulting to the old signals and start recognizing the new behaviors in real time, in performance reviews and promotion decisions.
  • High performers who resisted early become advocates, because the new code gives them a clearer path to the next role.
  • The distance between stated strategy and real daily behavior collapses, and the executive team stops needing to explain why adoption is flat.

The marker is whether the people the organization wants to keep are succeeding faster under the new code than they did under the old one. If they are, the code is real. If they are not, the change was announced and the system was never redesigned.

What should an AI productivity strategy measure?

Measure the work itself. Pick a few real outcomes, such as cycle time, error rate or throughput on a defined task. Baseline them before AI arrives and check them after. Treat the feeling of speed as a signal to investigate, because on its own it proves nothing about output.

Expect the answer to vary. In a 2025 randomized trial, METR found that experienced open-source developers working in their own repositories took 19% longer to finish tasks when they could use AI, while believing AI had sped them up by 20%. In February 2026, METR said developers were likely getting more speed from AI than in early 2025, and called its new data only very weak evidence of how big that change is. A number from someone else's study is no substitute for a baseline of your own.

Declaring victory because the room feels busier is the risk to watch. The free AI Profit Ready Assessment is a quick way to see where your team stands.

If you're launching AI across teams and want to know whether it's paying off, how we help starts with measuring the work.

What to Do Next.

If your AI adoption is stalled, look at the invisible productivity code that governs how work gets done and what behavior gets rewarded. Until you map that code and redesign it around AI, adoption will stay flat and resistance will stay high.

Start with ground truth. The AI Profit Ready Assessment gives you a first read on where your team's AI use is stuck, with the first move to make.

If you already know the code is the problem but need the structure to redesign it, the AI Profit Partnership is built for one leader and their team. It researches how the team works today and ends in a plan for the year ahead, with quick wins put in place along the way.

The productivity code will not change itself. The question is whether you are ready to redesign it.

Book a discovery call and we will walk through what you are seeing and where the resistance is coming from.

Take it with you

Download this as a PDF

A clean, branded version to read offline or share with your team.

Frequently Asked Questions

What is a productivity code?

A productivity code is the invisible set of unwritten rules that govern how work gets done in an organization: what tasks signal competence, what outputs prove value, how effort becomes visible to management, and which behaviors lead to advancement. It is distinct from stated values or official competency models and shapes every daily decision employees make about how to spend their time.

Why does adoption fail when AI conflicts with the productivity code?

Adoption fails when AI requires behavior that the existing productivity code does not reward or actively punishes. People default to the behavior that made them successful under the current system, even when leadership mandates AI, because the code defines how they prove value and advance their careers. Until the code is redesigned, resistance is rational self-protection.

How do you map the real productivity code in an organization?

Mapping the real productivity code requires asking what tasks people protect even when AI could do them faster, what work makes someone visible to leadership, what behavior got the last three people promoted regardless of official criteria, and where people put extra time to maximize career outcomes. The AI Profit Ready Assessment gives you a first read in about two minutes on where your team's AI use is stuck.

What does it mean to redesign the productivity code around AI?

Redesigning the productivity code means changing the actual reward structure, promotion criteria, visibility mechanisms, and feedback loops so that using AI becomes the rational path to advancement. This follows the People before Process before Platform sequence: start with what people need to believe about their value, then update compensation plans and performance metrics, and only then does the platform matter. The code must reward new behavior before adoption happens at scale.

What is the messy middle in AI transformation?

The messy middle is the months-long period where the old productivity code and the new one are both active. Some people are rewarded for new behavior while others still advance under old rules, and everyone is watching to see which code controls their next promotion. It is the transformation itself, and it requires visible leadership commitment and consistency to keep the new code in place until it becomes the default.

Why is resistance to AI treated as data?

Resistance is treated as data because it reveals where old rules are still active and where the conflict between stated intent and real incentives is sharpest. Intelligent resistance tells you what behavior AI requires that the current system does not reward, and what identity it undermines. Listening to resistance and redesigning the code around it is more effective than mandating compliance.

How long does it take to redesign a productivity code and see real adoption?

The timeline depends on the complexity of the organization and the distance between the current code and the new one. Visible shifts follow the changes people can see, in pay and promotion criteria and in how leaders behave. Measure success by whether high performers are succeeding faster under the new code than the old one, and whether resistance drops because AI now aligns with how people prove their value.

How does identity relate to the productivity code?

People change behavior when it aligns with who they believe they are and who they want to become. The productivity code defines identity around what it means to be senior or indispensable. Redesigning the code requires shifting identity first, from characteristics the old code rewarded to ones the new system supports, so new behavior follows naturally.

For your role

For COOs

AI for COOs: Where the Saved Hours Go

AI was meant to take work out of the process and the steps look the same. Why saved time gets absorbed, and how operations leaders turn it into return.

Share
Newsletter

With People

The people side of making AI pay.

  • One story from the news about AI at work, read through our book, The Elephant in the Algorithm.
  • A few links worth your time, and sometimes a podcast conversation.
Privacy Policy