Caitlin Kalinowski has sat at the highest tables in tech, leading hardware teams at Apple, Meta, and OpenAI. She’s seen the titans up close: Steve Jobs, Mark Zuckerberg, and Sam Altman. For ambitious founders, her unique vantage point offers a rare look into the core operating principles that define these leaders, and more importantly, how their distinct approaches can refine your own leadership playbook.

Key Takeaways

  • Sam Altman instills an almost unsettling focus on scale, pushing teams to ask, “Why not 100x or 10,000x?” and reject incremental thinking.
  • Steve Jobs cultivated a culture where the bar for technical talent and product excellence was “not wavering,” demanding exceptionally high quality from every team member.
  • Mark Zuckerberg built Meta for rapid growth through radical decentralization, empowering decision-making at the lowest possible level to maintain speed.
  • Zuckerberg’s deep technical understanding allowed him to grok 20-page engineering reports, comprehend complex trade-offs, and contribute directly to technical discussions, even as CEO of a massive company.

Sam Altman: Why Not 100x More?

Most founders think about growing their companies by 10% or doubling revenue. Maybe 5x if they’re feeling bold. But if you want to understand the mindset of a true exponential builder, look at Sam Altman. Kalinowski observed that Altman’s default setting is a relentless push for orders of magnitude beyond current thinking. “Sam is really good at saying, 'Why not more? Why not 100x or 10,000x? You're thinking too small,'” she explained.

This isn't just about ambition; it’s a strategic reframing. When you ask “Why not 10,000x?” you stop optimizing your existing product or process and start imagining entirely new paradigms. You’re forced to abandon linear improvements for breakthrough solutions. It’s a challenge to the very definition of the problem you’re solving, compelling you to uncover non-obvious paths to massive impact.

Steve Jobs: The Unwavering Bar

At Apple, the standard for technical talent and product quality wasn’t a suggestion; it was an absolute. Kalinowski recounts, “For Steve, the bar he held for the company for technical talent and for excellence was not wavering. It was up here and you were either going to meet it or you weren't.” Jobs didn't just preach excellence; he enforced it through an uncompromising hiring process and a culture that rewarded meticulous craftsmanship. This meant a constant culling of what wasn't working and an intense focus on what was. Quality wasn't a feature; it was the foundation.

This unwavering standard permeated every team, pushing engineers, designers, and product managers to deliver their best work, not just good work. It created an environment where cutting corners was unthinkable, and meeting high expectations was the only path forward. For Jobs, attracting top talent and demanding exceptional output were two sides of the same coin.

Mark Zuckerberg: Speed Through Deep Decentralization and Technical Fluency

Mark Zuckerberg's genius, according to Kalinowski, lay in his ability to run a hyper-growth company with striking efficiency. “Mark Zuckerberg, I think that he I have to say he ran a company very, very well,” she stated. His method? Decentralized decision-making. “Decisions were made at the lowest level possible in the company to maintain speed.” This wasn't just a management philosophy; it was an operational imperative, empowering individual teams to move fast without getting bogged down by layers of approvals.

Crucially, this decentralization didn't mean a lack of oversight or technical depth from the top. Kalinowski highlighted Zuckerberg's ability to dive into the weeds: “having him and Andrew Bosworth, the CTO, involved in the technical decisions, able to read, you know, reports that were maybe 20 pages long, grock the trade-offs, understand them, and be able to contribute to the technical discussion.” This blend of distributed authority and deep technical insight allowed Meta to scale rapidly while making informed, high-quality technical bets.

What to Do With This

This week, pick one product or feature your team is building and apply Altman’s “Why not 100x?” challenge. Force yourself and your team to brainstorm ideas that would achieve an order of magnitude more impact or reach, even if they sound impossible. Then, review a key technical decision made by a team member. Did they possess Zuckerberg’s depth to fully grok the trade-offs? If not, spend time with them to raise their technical fluency on that specific project.