top of page

The Permission to Not Ask Permission: Steve Jobs' Insight

In the conference rooms of corporate world, a familiar scene plays out thousands of times each day. An employee identifies a problem, develops a solution, and then... waits. They wait for approval, for sign-offs, for someone higher up the chain to give them permission to make things better. Meanwhile, opportunities slip away, innovation stagnates, and the very people who understand the work best remain powerless to improve it.


Steve Jobs saw this bureaucratic dance for what it truly was: a massive waste of human potential. His philosophy on workplace empowerment, captured in his profound observation about quality approaches, challenged one of the most entrenched aspects of traditional business: the need to ask permission before taking action.


Steve Jobs
Steve Jobs, co-founder of Apple Photo: Norman Seeff
"Authority should be vested in the people doing the work to improve their own processes, to teach them how to measure them, to understand them, and to improve them." - Steve Jobs

This wasn't just another management theory from Silicon Valley's most famous perfectionist. It was a fundamental reimagining of how organizations could unlock the creative potential of every single employee by giving them something revolutionary: the permission to not ask permission.


Ready to unleash your curiosity and start innovating? Subscribe to our newsletter for weekly insights, inspiring stories, and practical tips to help you think bigger and achieve more!


The Traditional Hierarchy: A Castle Built on Control

To understand why Jobs' philosophy was so radical, we need to examine the traditional corporate structure that dominated the business world for decades. Picture a towering pyramid where decisions flow downward and requests for permission flow upward, creating bottlenecks at every level.


Across American industry, from IBM's mainframe divisions to Kodak's film laboratories, brilliant minds were trapped in systems that valued control over creativity, compliance over innovation. The unspoken rule was clear: if you want to change something, ask your boss. If your boss agrees, they'll ask their boss. And so the cycle continued, with each layer adding delay, diluting the original vision, and often killing the initiative entirely.


Consider the case of Toyota in the 1950s. Faced with resource constraints, Toyota’s engineers pioneered the Toyota Production System—a revolutionary approach emphasizing frontline worker input. By giving assembly-line workers the authority to halt production if they spotted a defect, Toyota drastically reduced waste and improved quality. This “jidoka” principle, or “automation with a human touch,” showcased the transformative power of distributed decision-making at scale.


The Cost of Permission Culture

The financial impact of permission-based cultures extends far beyond delayed projects and missed deadlines. When employees must seek approval for every improvement, organizations pay a hidden tax in the form of lost opportunities, reduced engagement, and brain drain.


Take the case of Xerox PARC in the 1970s, where researchers developed groundbreaking technologies including the graphical user interface, Ethernet networking, and laser printing. Despite having some of the world's brightest minds working on revolutionary innovations, Xerox's corporate structure prevented many of these breakthrough technologies from reaching the market quickly. The permission-seeking culture meant that brilliant engineers had to spend more time justifying their work to executives than actually innovating.


First GUI computer at XEROX parc
GUI was pioneered at the Xerox Palo Alto Research Center (aka. PARC) Photo: Xerox PARC

Consider another example of Kodak.

In 1975, a Kodak engineer named Steven Sasson invented the first digital camera prototype. It worked. It was revolutionary. But Kodak’s management didn’t approve of pushing it forward.

Why? Because it threatened their film business. Kodak had the future in its hands—and said no.


Steve Sasson, alongside first digital camera
Steven Sasson with the first digital camera (which was the size of a toaster) Photo: David Duprey/AP

Meanwhile, companies like Apple and 3M were building cultures where employees were encouraged to experiment without extensive approval processes. Steve Jobs had a pirate flag for Macintosh team. 3M's famous "15% time" policy allowed employees to spend a portion of their work hours on personal projects without seeking permission from management. This freedom led to innovations like Post-it Notes, which emerged from Art Fry's experimentation with adhesive technology.


The contrast couldn't be starker: organizations that empowered their people to act flourished, while those that demanded permission for every action struggled to keep pace with rapidly changing markets.


Steve Jobs and the Philosophy of Permission

When Jobs spoke about newer quality approaches, he wasn't just referring to manufacturing processes or Six Sigma methodologies. He was identifying a fundamental truth: the people closest to the work are often best positioned to improve it, but only if they have the authority to act on their insights.


When Steve Jobs returned to Apple in 1997 to rescue a floundering company, his vision extended beyond sleek designs and intuitive interfaces. Jobs championed a culture where teams had the autonomy to experiment, measure outcomes, and iterate rapidly—all without waiting for bureaucratic green lights.

“So I think a lot of the philosophy behind this quality stuff carries with it a flattening of the traditional hierarchical organization and a distribution of authority to the people who are best in the position to decide what should happen to improve these processes, the people doing the work themselves.” - Steve Jobs

This flattening manifested in Apple's organizational structure, where small teams were given significant autonomy to make decisions. Unlike traditional corporations where information and authority flowed strictly upward and downward, Apple created horizontal connections that allowed for rapid decision-making and implementation.


This approach birthed industry-defining products like the iMac, iPod, and ultimately the iPhone. By entrusting engineers and designers with decision-making power, Apple accelerated innovation and fostered a sense of ownership that permeated every product line.


When people have the authority to improve their work, they also own the outcomes of their decisions.


Real-World Success Stories

While Jobs championed distributed authority at Apple, other companies followed similar paths in their own ways.


Google’s 20% Rule

In its early years, Google implemented a rule that engineers could spend 20% of their time working on projects that weren’t part of their job description. No need to ask. No need to justify. That 20% time gave birth to Gmail, AdSense, and Google News.

Let that sink in.

Some of Google’s most profitable and widely used products didn’t come from top-down orders. They came from individuals who felt empowered to solve problems they cared about.


Adobe’s Transformation with “Kickbox”

Adobe’s “Kickbox” program offers a fascinating blueprint for distributed authority. Employees receive a red box containing ideation tools, a $1,000 prepaid card for prototyping expenses, and a step-by-step guide to develop and pitch concepts. Crucially, no manager approval is required to begin.

Result? Over 1,000 projects launched, several of which have been integrated into Adobe’s core offerings. The Kickbox initiative demonstrates how removing approval bottlenecks empowers employees to explore uncharted territory.


Adobe kickbox contents
Adobe’s Kickbox

Microsoft’s Agile Overhaul

Under CEO Satya Nadella, Microsoft abandoned rigid hierarchies in favor of Agile squads. Teams now own features end-to-end, from conception to deployment. This shift was instrumental in revitalizing products like Microsoft Teams, which saw explosive growth by responding swiftly to user feedback during the COVID-19 pandemic. By distributing decision-making, Microsoft regained the agility reminiscent of its early Windows days.


Spotify's Squad Model

At Spotify, the concept of “squad” teams—product, design, and engineering—illustrates the balance between autonomy and chaos. Each squad has autonomy over its product area but adheres to company-wide architectural guidelines. This structure preserves coherence while unleashing creativity and has enabled Spotify to rapidly expand into new markets, launch innovative features, and maintain its position as a leader in music streaming despite intense competition from tech giants like Apple and Amazon.


The Measurement Paradox: Freedom with Accountability

One of the most sophisticated aspects of Jobs' philosophy was his recognition that empowerment without measurement leads to chaos, while measurement without empowerment leads to paralysis. The solution lies in teaching people "how to measure them, to understand them, and to improve them."


Google's approach to this balance offers valuable insights. The company's OKR (Objectives and Key Results) system empowers teams to set ambitious goals and determine how to achieve them, while providing clear metrics for success. Teams aren't micromanaged on their methods, but they are held accountable for their results.


John Doerr, who introduced OKRs to Google, described the philosophy: "We don't tell people how to climb the mountain, but we make sure everyone knows which mountain we're climbing and how we'll know when we reach the summit."


This approach has enabled Google to maintain startup-like innovation despite employing over 100,000 people. Teams can pivot quickly, experiment boldly, and implement improvements without getting bogged down in approval processes, all while maintaining alignment with broader company objectives.


Practical Steps to Create a Culture of Permissionless Innovation

If you want to build a company or team where innovation thrives, start here:


  1. Push authority downward – Let those closest to the work make decisions about how it’s done.

  2. Reward initiative, Not Just Outcomes – Celebrate people who take action, even if the result isn’t perfect. When you reward only success, you inadvertently punish experimentation.

  3. Simplify approvals – Create guardrails, but reduce bottlenecks.

  4. Make quality everyone’s job – Don’t wait for a committee to spot flaws. Train everyone to fix them. Distributed authority demands rigorous learning loops.

  5. Protect time for exploration – Like Google’s 20% rule, give people time to follow their curiosity.


Overcoming Common Challenges

Resistance from Middle Management

Middle managers may feel their roles threatened as authority shifts downward. Address this by reframing their responsibilities:

  • Transition from gatekeepers to mentors.

  • Focus on coaching, removing obstacles, and nurturing talent.

  • Provide training on servant leadership and Agile methodologies.


Balancing Autonomy and Alignment

Too much autonomy can fracture organizational coherence. Regular cross-team syncs—such as Spotify’s “Guilds” and “Chapters”—facilitate knowledge sharing and standardization. Encourage voluntary communities of practice, where employees self-organize to maintain best practices.


Ensuring Accountability

Autonomy must be paired with accountability. Implement transparent tracking systems—dashboards, scorecards, and regular reviews—to ensure teams deliver against objectives. However, frame reviews as opportunities for support rather than punitive audits.


The Future of Work: Building on Jobs' Foundation

As we look toward the future of work, Jobs' insights about empowerment become even more relevant. In an era of remote work, rapid technological change, and increasing complexity, organizations that can't empower their people to act quickly and decisively will be left behind.


Jobs gave us a simple but powerful truth:

"People shouldn't have to ask management permission to do something that needs to be approved."

His message was clear: If you want people to do great work, give them the freedom to do it.


The most successful companies of the next decade will be those that can combine human creativity with technological capability, and this combination is only possible when people are empowered to experiment, improve, and innovate without bureaucratic barriers.


Conclusion: The Lasting Legacy of Empowerment

Steve Jobs' philosophy about giving people the permission to not ask permission represents more than a management technique—it's a fundamental recognition of human potential and dignity. When we trust people to improve their own work, we're acknowledging that they have valuable insights, good judgment, and the capability to make meaningful contributions.


From Toyota’s assembly lines to 3M's Post-it notes, history shows that permission to innovate without permission yields transformative results.


The permission to not ask permission isn't about eliminating structure or accountability. It's about creating organizations where structure serves empowerment, where accountability drives ownership, and where every person has the authority to make the work—and the world—a little bit better.


As Jobs understood, the ultimate quality improvement isn't in our processes or our products—it's in unleashing the full potential of the people who create them. And that potential can only be realized when we give people the most powerful permission of all: the permission to act on their best judgment without having to ask someone else first.


Ready to unleash your curiosity and start innovating? Subscribe to our newsletter for weekly insights, inspiring stories, and practical tips to help you think bigger and achieve more!


Watch Steve Jobs:

Comments


bottom of page