Apr 13, 2024 · 35m · saastr
Todd McKinnon CEO of Okta: Top 10 Learnings Building a High Performance Organization (Updated)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this SaaStr interview, Okta co-founder and CEO Todd McKinnon discusses the contrarian bets, architectural choices, and transparent leadership philosophies that propelled Okta into a category-defining cybersecurity leader.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Jason holds 31.7% of the talking time here. How this is scored →
Jason as informed peer 5.7 Guest teaching 3.5 Guest disagreement 1.2 Jason pushing back 1.7
speaking balance: gold is Jason, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 19:15 Visceral reaction to niche label
McKinnon expresses sharp lingering irritation about early skeptics and investors who dismissed cloud identity as too small of a market.
Hardest push from Jason ▶ 5:53 Challenging B2C vs SaaS uptime standardsLemkin pushes back on McKinnon's refactoring comparison, arguing that unlike consumer platforms where brief outages go unnoticed, Okta's enterprise front door cannot tolerate any downtime.
Biggest teaching moment ▶ 16:56 Correcting developer expansion assumptionsMcKinnon corrects Lemkin's assumption that developer traction is an easy front-end API fix, explaining that sophisticated developers quickly evaluate the deep underlying architecture.
Jason holds their own ▶ 25:06 Incumbent weakness and multi-cloud dynamicsLemkin articulates why single-ecosystem incumbents like Microsoft and Salesforce structurally fail against dedicated multi-cloud solutions.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Jason as informed peer | Guest teaching | Guest disagreement | Jason pushing back | Why |
|---|---|---|---|---|---|---|
| Architecture, Uptime, and Technical Debt | 6 | 4 | 1 | 2 | Lemkin draws on his own SaaS experience regarding technical debt, architectural refactoring, and uptime requirements. McKinnon reframes the trade-off by noting that early-stage companies often over-engineer architecture instead of prioritizing market momentum. | |
| Go-to-Market Strategy and Building the Integration Ecosystem | 6 | 4 | 1 | 2 | Lemkin digs into enterprise direct sales mechanics and unscalable integration work. McKinnon educates on customer-driven integration strategies, explaining why Okta hand-built connections rather than relying on standard protocols. | |
| Navigating Strategic Bets: Mobile Expansion and Developer Identity | 5 | 4 | 1 | 2 | Lemkin asks whether expanding to developers was just a matter of assigning a small dedicated team. McKinnon politely clarifies that developer adoption requires core architectural redesign rather than superficial surface-level APIs. | |
| Creating the Category and Overcoming Skepticism | 5 | 3 | 2 | 1 | Lemkin highlights the paradox of customers understanding a problem while early investors and candidates dismissed it. McKinnon recalls the frustration of early skepticism and explains how holding the category definition created a powerful defensible moat. | |
| Responding to Competition and Incumbents | 7 | 3 | 1 | 2 | Lemkin demonstrates deep SaaS familiarity by pointing out how incumbent bundling often generates downstream leads for best-of-breed tools. McKinnon details how Microsoft and Salesforce product limitations validated Okta's neutral multi-cloud positioning. | |
| Culture of Transparency: Addressing Gartner Magic Quadrant | 5 | 3 | 1 | 1 | Lemkin explores McKinnon's decision to publicly address Okta's minor dip in the Gartner Magic Quadrant. McKinnon shares his leadership philosophy on radical transparency with employees and customers rather than spin. |
Statements from this episode (16)
Okta was founded on two bets: independent scale and ubiquitous cloud
“The bet for us was that there's really two parts of it, kind of. One was that it would be a big enough problem in the future to build a large independent company because previous generation, a lot of the vendors were near sure they got picked up by bigger comp…”
Okta halted feature development for eight months to engineer zero-downtime upgrades
“I remember we spent seven or eight months just engineering the fact that we didn't have to take it down for maintenance. And before I came from Salesforce and we had to take the service down for four hours every three months for maintenance to upgrade it. And …”
Early-stage startups over-invest in refactoring before securing market traction
“I think a lot of early companies do too much refactoring and too much perfecting of the architecture. Being successful in the marketplace and getting momentum with customers can make up for a lot of sense. And give you a lot of time and effort and flexibility …”
Todd McKinnon personally sold Okta's first 50 to 100 enterprise customers
“The first 50 customers, the first hundred customers, I probably at some level personally sold a lot of them, right?”
Okta's first enterprise customer only integrated Salesforce and Google
“I remember the first customer we had was, there were two apps. There was Salesforce and Google.”
Startups must land one major bet; perfection across all is unnecessary
“If you don't get one A plus, if you don't get one big bet, you're probably gonna struggle. So that could be comforting because you'll have to get one right. Or it could be stressful because you're not sure. And then beyond that, I think you can, you do have, y…”
Okta should have focused on its developer identity product much sooner
“Getting our product that was getting our product a plus to work perfectly for the developer was something if I had to do the last 10 years over and I would have done much sooner.”
Winning developer adoption requires core architectural integrity, not just APIs
“It's much deeper than just having APIs or just having a good website. It's cause you think about developers is they're smart. Once they get past the website and the API, they realize the core of the architecture, how it's built.”
Enduring early skepticism allows startups to eventually set the industry agenda
“The learning for me was that if you stick with your vision and you power through that, it's It feels really bad in the moment, but it's good because once it flips and once you prove that it is big enough, you by de facto own the category, right? You're the per…”
Retreating to established software categories destroys the advantages of category creation
“The ironic thing is that when you're going through the tough parts of that process, the natural reaction is to try to, if that's a word, undifferentiate yourself by shifting into something else that someone else owns. Oh, we're really like, yeah, exactly. We'r…”
Okta's business has shifted to roughly 25% customer identity
“And this was when the company was a hundred percent employee identity. Now it's about 25% customer identity.”
Amazon's broad but shallow services ultimately drive customers to specialized alternatives
“Amazon tends to, they're doing a lot of things, but nothing super deep. They're successful a lot with the services that are broad and don't have to be super deep. But the ones they have that are more, not as deep, they tend to get customers excited about them,…”
Incumbents like Salesforce prioritize their own products over helping startup partners
“It turns out that like a lot of companies, Salesforce is more into selling their own product than your product. So it did end up being a, it did not end up being that helpful to have that relationship, but like a lot of things, you gotta do it on your own and …”
Okta's position dropped slightly in Gartner's Magic Quadrant as competitors caught up
“And last year we were like way up in the leader position. And this year we came down a little bit and the other competitors got, got around us and caught us a little bit in the quadrant and it was, everyone's bummed out when that happens.”
Founders should not fear discussing negative news because buyers already know
“If it's a relevant question and if it's a relevant issue, the people that it matters to are gonna know about it. Like for us, the people that look at the magic quadrant have already looked at it. They're not gonna go look at it and see our position went down a…”