It’s 1971. You’ve spent seven years building a business that finally works. Seventy percent market share. The category is yours. Then you find out, indirectly, that your only supplier is interviewing your replacement.
Not a rumor. Not a misunderstanding. They are actively shopping for someone to take your place.
That’s where Phil Knight was. His company, Blue Ribbon Sports, didn’t own a factory. It didn’t own a patent. It didn’t own a brand anyone would recognize. What it owned was a distribution agreement with a Japanese manufacturer, and that agreement had just become optional, from the other side.
Here’s the decision in front of him: defend the relationship that’s feeding you today or start building the thing that might keep you alive tomorrow, knowing that if your current partner finds out, they can cut you off immediately.
What do you do when the only platform you have is also the thing that could suffocate your future?
The Company Before the Swoosh
If you know Knight today, you know how the story ends. Nike: global sportswear giant, billions in brand value, the swoosh on every continent.
But in 1971, there was no Nike. There was a fragile outfit called Blue Ribbon Sports, importing running shoes from Japan, run out of a scrappy operation of true believers that included Knight and his former college track coach, Bill Bowerman. No factories. No brand recognition. No backup supplier. And a contract that tied them to Onitsuka, the very company now looking for a US distributor to replace them.
That’s the only reason this decision matters. Knight wasn’t choosing between two mature options. He was choosing between protecting a relationship where he had no leverage, or creating leverage out of nothing.
At stake: the entire business he’d spent seven years building. The livelihood of his small team. His partnership with Bowerman, who had lent his credibility and his name to the whole operation. If Blue Ribbon lost Onitsuka, it didn’t lose a client. It lost its only product.
The Constraints That Made This Hard
Four things made Knight’s position genuinely difficult.
First, no confirmed alternative supplier. Knight had theories and contacts in Japan, but nothing signed; nothing he could switch to on a Monday morning.
Second, no brand identity of his own. Runners knew Tiger (Onitsuka’s shoes). They didn’t know Blue Ribbon, the company that had brought those shoes to the US. The perceived value sat with the Japanese logo on the side of the shoe, not with the distributor who got it onto American feet.
Third, no manufacturing capability. No factories, no production lines, no in-house design engine that could spin up a new footwear line on demand.
Fourth, a non-compete with Onitsuka. On paper, if Knight moved first and started building an alternative brand while still under contract, he would be in breach: legally vulnerable, financially exposed.
If Knight acted preemptively (sourcing shoes from another manufacturer, building his own identity while still under contract) he risked the exact outcome he feared: Onitsuka discovering the parallel effort and cutting Blue Ribbon off before the new brand was ready. But if he waited, and Onitsuka calmly chose another distributor, he’d wake up one morning with nothing to sell and no time to build.
This is the trap a lot of operators live inside without ever naming it. Act early, and you might blow up the only thing keeping you alive. Wait, and you might get cut off with no alternative, at the worst possible moment.
Three Choices
Knight had three real options in front of him.
Option A: play defense. Go back to Onitsuka, act surprised, and try to renegotiate a new long-term exclusive. Sweeten the deal, improve terms, sell them on loyalty and history. This is the move almost anyone would suggest. Protect the relationship. We built this together, let’s lock in the next decade. On paper it looks reasonable, mature, risk-aware.
Option B: wait and hope. Assume performance wins. Keep executing, keep growing the US market for Tiger shoes, and trust that Onitsuka would see reason and stay with Blue Ribbon. Don’t rock the boat. No legal risk, no side deals, just faith that being a good partner is enough.
Option C: keep operating Blue Ribbon as if nothing had changed, while secretly building a new brand in parallel. Find a trading company in Japan that would finance and arrange manufacturing outside Onitsuka’s ecosystem. Design a new logo. Create a new name. Stand up a completely separate identity underneath the surface, so when Onitsuka pulled the plug, Blue Ribbon wouldn’t be staring into the abyss. They would already have Nike.
Notice Option C was not “wait until the contract ends, then start.” It was build the alternative before you have permission, while you still technically belong to someone else.
That’s what turns this from an origin story into a decision worth studying. Knight wasn’t choosing between safe and risky. He was choosing between two different kinds of risk: legal and relational risk now, or existential, business-ending risk later. It’s the same move Andy Grove made at Intel over a decade later, deciding to become the outsider who’d eventually force his way into Intel’s memory-chip business before the market did it for him. We broke that decision down in Identity Is a Strategic Liability, and the mechanism is identical: act from the position you’re afraid of losing, before someone else acts on it for you.
What Knight Actually Did
He found a partner: a Japanese trading company with the reach and capital to help him source manufacturing outside Onitsuka’s ecosystem. With that company’s help, he began secretly developing a new line of shoes.
He commissioned a logo from a design student, Carolyn Davidson, for $35. He named the new brand Nike. All of this while Blue Ribbon was still, officially, Onitsuka’s exclusive US distributor. Shoes were still shipping under Tiger branding. Invoices were still being paid. Onitsuka believed the relationship was intact.
Blue Ribbon was two companies at once: the one Onitsuka could see, and the one Knight knew he would need the moment Onitsuka decided it could get a better deal elsewhere.
Eventually, Onitsuka discovered what was happening. Legal action followed. The relationship ended. But because Knight had already done the pre-work, committed to the path, and built enough of an alternative, Nike wasn’t a theory when the break came. It was ready. When Onitsuka terminated the relationship, Knight didn’t start from zero. He flipped a switch.
Is that reckless? Maybe. Clean? Absolutely not. But look at the logic underneath it. If one party already holds all the leverage, the only way to rebalance the relationship is to create an option they don’t control. Knight understood that trying to repair the relationship would only keep him inside a dependency he could never escape. Building Nike wasn’t just a backup plan. It was a leverage play.
Onitsuka sued. Nike fought. The courts ultimately sided with Blue Ribbon. The legal exposure Knight had taken on, the technical breach, the parallel development, didn’t sink him. It became a chapter in the story of a company that suddenly had its own name, its own logo, its own designs. From there, Nike grew. The company went public in 1980. What began as a defensive hedge, a brand built out of the fear of losing everything, became the dominant sportswear company on the planet. A $35 piece of student work became one of the most valuable symbols on earth.
The thing that created that value wasn’t a clean launch plan. It was a decision made from the most uncomfortable position possible: dependent on a single supplier, legally constrained, and already out of leverage.
Knight’s answer to that constraint wasn’t “protect what I have.” It was “use what I have to build something they can’t take away.”
Three Principles Worth Building Into Your Operating System
Build the alternative before you need it
Knight’s best moment to build Nike was not after Onitsuka formally cut him off. By then it would have been too late. The worst possible moment to plan a transition is when your current platform has already disappeared, because that’s when you have the least time, the least leverage, and the most panic in the system.
So he did the opposite. While Blue Ribbon still held the US running market for Tiger shoes, while cash was still coming in, while the relationship still technically existed, he started building the replacement.
This principle is brutal in its simplicity. If there’s a single point of dependency that could kill you in ninety days, the time to build your alternative is now, while that dependency is still feeding you. You don’t wait for your only client to leave before you diversify. You don’t wait for the platform to change its algorithm before you build your own list. You don’t wait for the internal sponsor of your project to retire before you build broader support. The move is the same: use the stability you have to build the option that will keep you standing when that relationship ends.
Yes, it will look disloyal, paranoid, or premature on a spreadsheet. But the spreadsheet never includes the cost of being trapped. This is the same discipline behind protecting a long-cycle bet from short-cycle pressure; we go deeper on why that trade-off is so hard to see in real time in The Short Cycle Trap.
Single-source dependency is an existential risk, not a performance problem
Blue Ribbon hadn’t done anything wrong in the ordinary sense. It had grown the Tiger brand in the US and held seventy percent of the market. Onitsuka’s interest in other distributors didn’t show up because Knight underperformed. It showed up because dependency cuts both ways: if one party controls the product and the other is replaceable, the power was never symmetric to begin with.
Knight’s real vulnerability wasn’t that he might lose a contract. It was that he’d allowed his entire business to exist in a position where one external decision could zero him out.
It doesn’t matter how strong a relationship looks today. If your business, your career, or your project rests on one supplier, one client, one platform, or one internal sponsor, that’s existential risk. The danger compounds because it usually feels fine right up until it doesn’t. The revenue is predictable, the relationship is warm, the feedback is good. Which is exactly why most operators don’t move until the renewal notice arrives, or the strategy memo lands, or the sponsor calls to say they’re leaving the company. By then, you’re reacting. Knight refused to treat the dependency itself as anything other than the risk it was.
The forced-transition window is also your maximum creative window
Nike didn’t come from comfort. It came from the feeling of a door about to close. Knight didn’t sit down in a calm, diversified market and decide to add a second brand to his portfolio. He moved when the clock started ticking, and that pressure produced urgency. Urgency, aimed correctly, becomes creativity.
He didn’t have the luxury of overoptimizing. He couldn’t spend three years workshopping the perfect name or the perfect logo. He had to move, and the constraint forced clarity: what’s the smallest set of decisions we need to make to stand on our own if we’re cut off? A name. A logo. A manufacturing path. A product good enough to sell. Not perfect branding. Not a perfect org chart. Just enough to live.
The lesson isn’t “wait for a crisis so you can become creative.” It’s this: when you can feel a dependency starting to tilt, that window is your best chance at a real, noncosmetic change, because you’re finally willing to do things that would have felt too extreme when everything looked safe. The question is whether you use that window on purpose, or let it use you.
The Contrarian Read
From the outside, Knight’s move looks reckless. He was technically in breach of his agreement. He risked lawsuits. Most reasonable operators, especially inside larger organizations, would have gone straight for the adult playbook: call the partner, renegotiate, protect the relationship, preserve the status quo.
But look at the power dynamics. Onitsuka already held the leverage. They owned the product. They could choose another distributor whenever they wanted, and they were already looking. What exactly was Knight going to negotiate from that position? A slightly longer fuse on the same bomb?
He understood something uncomfortable: when the other side already holds all the cards, preserving the relationship doesn’t restore your power. It just keeps you dependent longer. The only real counter-move was to build something they didn’t own.
That’s the contrarian move here. Not burning bridges for sport. Not ignoring contracts. It’s reading the power dynamics clearly enough to see when the relationship you’re trying to save is the exact thing preventing you from ever being independent.
Where This Shows Up in Your Own Decisions
You may not be running a shoe company. You might be inside a large organization, leading a program, running a team, or building something on nights and weekends. The pattern is identical. Start by auditing your single points of failure.
Where are you one decision away from a cliff? Maybe it’s one client that makes up sixty percent of revenue. One executive sponsor whose backing is the only thing keeping your project funded. One channel, one platform, one referral source that drives nearly all of your inbound. One supplier who controls a critical component or capability.
Pick one, and ask a brutal question: if this ended in ninety days, no renewal, no warning, no replacement, what would I actually do? What would you actually have to build, scramble, or cobble together to stay alive? That answer, messy as it is, is your Nike. (If your honest answer is that you’d freeze rather than move, that’s a separate problem worth its own diagnosis; see Indecision Will Kill You.)
Then the move is simple, but not easy. Start building that answer now, while the relationship still looks fine. If it’s a client dependency, start deliberately cultivating smaller accounts or a second key client, even though it makes next quarter’s numbers harder. If it’s an internal sponsor, build a coalition of stakeholders who understand the value of your work, even though it costs you more meetings and less focus. If it’s a platform, start building an owned channel, even though the returns look tiny next to your main source of traffic.
You’ll feel disloyal doing it. You’ll feel like you’re hedging against your own success. You’ll be tempted to wait one more year, one more cycle, until this next phase is stable. That’s exactly how manageable dependencies turn into existential ones.
Knight didn’t wait for permission. He used the window while he still had something to stand on, to build the thing that would keep him standing when the platform disappeared. You don’t need Nike’s scale to apply this. You need the willingness to build your next move while the current one still looks safe, because by the time you’re forced to jump, it’s already too late to have started building the bridge.
Where in your life are you still hoping the incumbent chooses you, instead of quietly building the thing they can never take away?
Stay unstoppable.
If you’re working through a pivotal decision of your own, The Edge Forums is where founders, executives, and operators sharpen the decisions most at risk of defining them. Apply or ask a question here.
Unstoppable is a decision intelligence podcast for leaders who refuse to settle. Hosted by Jana. New episodes weekly.
Key Takeaways
Knight’s core move was not choosing between safety and risk; it was choosing which kind of risk to carry: relational and legal risk now, or existential business-ending risk later.
Single-source dependency (one client, one supplier, one platform, one sponsor) is an existential risk even when the relationship feels healthy, because dependency is asymmetric by nature: whoever is more replaceable holds less power, regardless of performance.
The best time to build an alternative is while the current dependency is still feeding you, not after it disappears; by the time you’re cut off, you have the least time, the least leverage, and the most panic in the system.
Of the three real options Knight faced (renegotiate, wait and hope, or quietly build the alternative in parallel), only the third rebalanced the power dynamic, because it created an option the other side didn’t control.
A forced-transition window, the moment you can feel a dependency starting to tilt, is also your maximum creative window, because constraint forces clarity on the smallest set of moves that actually matter.
FAQ
What is single-source dependency in a business context?
Single-source dependency is a situation where a business, career, or project relies on one supplier, one client, one platform, or one internal sponsor for its survival. It’s dangerous not because the relationship is unhealthy (Blue Ribbon Sports held 70 percent of the US market for Onitsuka’s Tiger shoes and was performing well) but because power in that relationship is inherently asymmetric: whichever party is easier to replace holds less leverage, regardless of how the relationship currently feels.
Why did Phil Knight secretly build Nike while still under contract to Onitsuka?
In 1971, Knight’s company, Blue Ribbon Sports, learned that its only supplier, the Japanese manufacturer Onitsuka, was quietly interviewing other potential US distributors. Rather than wait for Onitsuka to formally end the relationship, Knight began developing a new brand, sourcing manufacturing through a separate Japanese trading company, commissioning a new logo, and creating the Nike name, all while Blue Ribbon continued operating as Onitsuka’s official US distributor. When Onitsuka eventually discovered the parallel operation and the relationship ended in litigation, Knight already had a functioning alternative instead of starting from zero.
How much did Nike pay for the swoosh logo?
Nike paid graphic design student Carolyn Davidson $35 in 1971 to design the swoosh logo, which later became one of the most recognizable brand marks in the world. Nike went public in 1980.
What are the three principles from the Nike origin story that apply to any business or career?
First, build the alternative before you need it, while the current dependency is still stable, not after it’s gone. Second, treat single-source dependency as an existential risk rather than a performance issue, since it doesn’t matter how well the relationship is going if one external decision can eliminate you. Third, recognize that a forced-transition window (the moment you feel a dependency starting to tilt) is also your maximum creative window, because constraint forces you toward the smallest set of decisions that actually matter.
How do I identify my own single point of failure?
Ask a direct question about each major dependency in your work: if this ended in ninety days with no renewal, no warning, and no replacement, what would I actually have to build or scramble to survive? Common single points of failure include one client responsible for the majority of revenue, one executive sponsor whose support funds a project, one platform or channel driving most inbound opportunities, and one supplier controlling a critical capability. Whichever dependency produces the most uncomfortable answer to that question is the one worth building an alternative for first.
