How a Company Can Regain Its Competitive Edge

How a Company Can Recover Its Edge Without Reenacting Its Past

A company regains its edge when it can repeatedly create a differentiated result under current conditions.

The work begins by identifying the capability behind its earlier success. It continues by restoring the information, expertise, authority, experimentation, and economics that let that capability operate now.

This is different from reviving an old campaign, rehiring a familiar leader, recreating a founding ritual, or telling employees to act like the company is small again. Those moves may create energy. They do not prove the operating system changed.

The finish state is observable. Customers choose the new work without permanent subsidy. Field evidence reaches the people who can act. Specialists retain ownership of consequential tradeoffs. Experiments become better decisions. The company can explain what it stopped, what it rebuilt, and why the resulting economics are credible.

Why returning to the roots often fails

Founding stories compress a capability into an artifact. Nike has the waffle iron. A software company has the first weekend prototype. A retailer has the original store. A services firm has the founder who knew every customer.

The artifact is memorable because it makes the past visible. It is also dangerous because copying it can feel like recovering the edge.

Bill Bowerman's waffle experiment mattered inside a larger loop. He coached runners, observed performance problems, altered materials and construction, put prototypes into real use, and carried the results into another iteration. The waffle iron did not create the capability. It happened to sit inside it.

James March's research on organizational learning explains another part of the problem. Organizations improve the exploitation of known work faster than the exploration of uncertain possibilities. The short-run efficiency can crowd out the search that long-run adaptation needs. A later empirical study of 87,911 European firms also found value in balancing technological exploration and exploitation, while showing that the useful balance depends on risk.

Recovery therefore has to protect the current business and reopen learning. It cannot choose memory over reality.

flowchart TD
    A["Historical success"] --> B["Extract the underlying capability"]
    B --> C["Test it against today's customer and market"]
    C --> D["Restore evidence, expertise, and authority"]
    D --> E["Run bounded modern experiments"]
    E --> F["Measure behavior and economics"]
    F --> G{"Differentiated value repeats?"}
    G -->|No| C
    G -->|Yes| H["The edge is becoming operational again"]

Recovery is a learning loop, not a reenactment.

1. Describe the edge as a capability

Start with a sentence that contains an action, a subject, and evidence.

"We were innovative" is too broad. "Our running specialists repeatedly translated athlete problems into tested footwear changes faster than the category" is more useful. It names who held the knowledge, what they did, who benefited, and how the advantage became observable.

The sentence should survive the removal of founder language. If the only explanation is charisma, hunger, culture, or caring more, keep digging.

Look for repeated choices across several products, customers, or years. An isolated success may be luck. A capability leaves a pattern in hiring, decision rights, investment, product behavior, partner relationships, and customer response.

At this stage, collect contradictory evidence. If the company remembers itself as technically superior, find the products that were not. If it remembers exceptional service, find the customers who left. Recovery gets weaker when history is required to flatter the organization.

2. Separate the principle from its old conditions

Write two columns. The first contains the principle that created value. The second contains the conditions that happened to surround it.

Early Nike's principle included athlete proximity, technical experimentation, specialist judgment, and rapid feedback. The surrounding conditions included a small team, severe cash pressure, founder control, supplier dependence, and limited process.

The principle may deserve recovery. The old conditions may be impossible, irresponsible, or undesirable at current scale.

This distinction protects the organization from copying chaos. A public company should not recreate the financing insecurity of a startup. A regulated product should not remove safety review to imitate the speed of an early prototype. A global employer should not rely on personal loyalty in place of governance.

The question is how the principle changes form when responsibilities change.

3. Find where the capability broke

Map the path from evidence to decision.

Begin with a real customer or operational signal. Follow it into research, prioritization, design, approval, production, distribution, and post-launch review. At each handoff, record what is summarized, delayed, relabeled, or lost.

A company may still employ excellent specialists while routing their evidence through a portfolio process that removes the detail. It may conduct extensive research while giving no one authority to change the roadmap. It may launch experiments while rewarding only predictable quarterly delivery. It may listen to direct customers while losing the retailer who sees customers compare alternatives.

David Teece's dynamic-capabilities framework offers a useful lens. Adaptation requires the ability to sense an opportunity or threat, seize it through a commitment of resources, and transform the organization or asset base when necessary. A company can fail at any one of those points.

Do not diagnose the break from a leadership workshop alone. Trace actual decisions.

4. Restore a live source of truth

An edge cannot return through retrospective analysis only. The company needs current evidence.

Choose users and conditions that can disprove the recovery thesis. A technical product should reach people with the relevant task, not friendly employees. A channel change should be tested where customers compare competitors. A service promise should be measured through exceptions, not just average completion.

Preserve the raw observation beside the summary. This is especially important when evidence travels across several layers. A sentence such as "customers prefer convenience" may hide a fit problem, a staff recommendation, an unavailable size, or a return policy.

Nike's current distribution reset illustrates the difference. Fiscal 2026 wholesale growth and Direct decline show a changing channel mix. They do not, on their own, prove that product edge returned. The useful evidence would connect customer choice, product performance, partner behavior, inventory health, repeat use, and economics.

5. Rebuild ownership around the tradeoff

Cross-functional work needs a named person who can resolve the consequential tradeoff.

That person does not have to make every decision. They must know when evidence is material, which specialist to involve, what can be changed, and what requires escalation. If everyone participates but no one owns the decision, coordination can dilute expertise.

The organization also needs a durable map of who knows what. Research on transactive memory systems describes effective team knowledge through specialization, credibility, and coordination. The point is not to create silos. It is to keep differentiated expertise available and trusted while the work moves across functions.

Define the review that protects technical memory. Define where channel evidence enters. Define what happens when commercial pressure conflicts with product evidence. Define who owns the result after launch.

6. Run a bounded expression of the old capability

The first recovery project should be meaningful enough to test the edge and bounded enough to learn before the whole company depends on it.

State the user problem, differentiated hypothesis, specialist owner, operating constraint, evidence threshold, economic threshold, failure condition, and next decision date. If any of those is missing, the project can remain inspiring without becoming informative.

Nike's Project Amplify is a useful example of an announced direction, not a completed recovery. Nike says the powered-footwear system combines a motor, drive belt, rechargeable cuff battery, and carbon-plated shoe to assist running and walking. It also says the project remains early in testing and is being developed with Dephy for a wider launch in coming years.

The public announcement shows ambition. The recovery evidence will come from performance readiness, user experience, safety, durability, price, adoption, repeat use, manufacturing, support, and contribution.

Do not ask one project to carry the entire identity claim. Ask it to produce evidence the next decision can use.

7. Measure behavior and economics together

Turnaround language changes faster than the system.

Watch which projects receive protected time, who attends user sessions, how quickly a failed assumption changes a plan, whether specialists can stop a weak decision, how partners experience the relationship, and what the company is willing to discontinue.

Then connect those behaviors to economics. Track customer choice, repeat use, price realization, returns, inventory, support, contribution, and the cost of maintaining the capability. A differentiated product that cannot be delivered or supported sustainably has not restored a durable edge.

Avoid one grand recovery score. Use a small set of measures that can disagree. Strong launch attention with weak repeat use should remain visible. Improved wholesale shipments with poor sell-through should remain visible. Faster experiments with no decisions should remain visible.

The disagreement tells leaders where the system is still theatrical.

Common recovery mistakes

What good recovery looks like

A recovered edge does not look exactly like the past. It feels recognizable because the company is again unusually good at a valuable activity.

The modern system may use different people, tools, channels, controls, and economics. It may move more deliberately in high-risk areas. It may distribute expertise across teams that did not exist at the founding.

The continuity is functional.

The company senses a problem others miss. It routes that evidence without stripping away its meaning. A trusted specialist and accountable owner can act. A bounded experiment produces information. The result changes investment. Customers choose the work for the reason the company intended. The economics allow the loop to continue.

That is an edge.

History helps because it reveals a capability the company once coordinated. Recovery happens only when the capability earns a new life in the market that exists now.

Continue the series

The E114 episode story applies this distinction to Nike's early product loop and current strategy. The specialist-team Field Note focuses on preserving technical memory during reorganization. Episode 115 extends the idea by separating visible output from reproducible capability, and Episode 119 shows why real-use conditions belong inside validation.

Sources and disclosure

The exploration and exploitation boundary comes from James March's 1991 paper and a 2025 open-access study of 87,911 European firms. The sensing, seizing, and transformation lens comes from David Teece's 2007 dynamic-capabilities paper. The Nike case uses the company's fiscal 2026 Form 10-K, full-year results, and Project Amplify announcement.

This is an operating framework, not a claim that Nike proves a universal turnaround formula. Dalton Anderson's preserved E114 transcript supplies the case interpretation. AI assisted with research organization and drafting; the framework, source limits, and final editorial decisions remain Dalton's.