The Law of the Uncomfortable

Here is a detailed explanation of The Law of the Uncomfortable, framed from the dual perspectives of an engineer and a CEO. This law is one of the most challenging yet essential principles in Steven Bartlett's The Diary of a CEO, as it directly confronts our natural aversion to difficulty.

The Law of the Uncomfortable: "If you are not uncomfortable, you are not growing."

1. Definition: What Is the Law of the Uncomfortable?

The Law of the Uncomfortable (Law 6 in the 33-law framework) states that growth and comfort cannot coexist. Every meaningful expansion of capability—whether technical, strategic, or personal—requires venturing into territory where you feel awkward, uncertain, and exposed.

Core Principle: Comfort is not a sign of success; it is a sign of stagnation. When you feel completely at ease, you are operating within your existing capabilities, not expanding them. Discomfort is not a signal that something is wrong; it is a signal that you are growing.

Bartlett argues that we have been conditioned to avoid discomfort. Our lizard brain (the amygdala) interprets unfamiliar situations as threats. But the path to mastery—whether mastering a programming language, leading a company, or building a public brand—runs directly through discomfort.

The insight: The discomfort you feel when facing a new challenge is not a reason to stop. It is evidence that you are exactly where you need to be.

2. The Psychology of Discomfort

Bartlett grounds this law in the neurobiology of learning and adaptation:

Concept Explanation

The Comfort Zone 

Where you operate with competence and ease. No learning occurs here.

The Learning Zone 

(Stretch Zone) Where tasks are challenging but achievable. Discomfort is present. Neuroplasticity is activated. Growth occurs here.

The Panic Zone 

Where challenges exceed current capability. Overwhelm and shutdown occur. Growth is not possible here.

The goal: Stay in the Learning Zone. Push into discomfort, but not so far that you tip into panic. The boundary between comfort and discomfort is where growth happens.

The Neurochemistry of Discomfort:

· When you encounter unfamiliar challenges, your brain releases cortisol and norepinephrine—stress chemicals.

· These chemicals heighten attention and create the conditions for new neural connections.

· If you persist, the brain rewires. What was once uncomfortable becomes familiar. The discomfort threshold moves.

Bartlett's observation: Most people interpret the stress of discomfort as a sign that they are "not ready" or "not cut out for this." In reality, it is a sign that the brain is doing exactly what it needs to do to adapt.

3. The Comfort Trap

Bartlett describes the Comfort Trap as one of the greatest dangers to long-term success:

Stage Description

1. Initial Growth You work hard, struggle, and expand your capabilities. Discomfort is constant.

2. Competence Achieved You master the skills. Tasks become easy. Discomfort fades.

3. Comfort Settles In You continue doing what you know. There is no challenge. You mistake comfort for success.

4. Stagnation While you rest in comfort, the world moves. Your skills become outdated. Competitors pass you.

5. Crisis External change forces you out of comfort. But now you are behind, and the discomfort is panic, not stretch.

The tragedy: People often work incredibly hard to achieve a level of comfort—and then stay there, mistaking it for arrival. But in a world of constant change, comfort is not a destination. It is a warning sign.

4. The Law of the Uncomfortable: Engineer's Perspective

For an engineer, discomfort is the gateway to technical growth, career advancement, and lasting relevance in a field that evolves relentlessly.

A. Technical Discomfort: Learning New Technologies

Comfort Behavior Uncomfortable Growth Behavior

Staying with the programming language you know Learning a new language with different paradigms (e.g., going from Python to Rust, or from imperative to functional programming)

Using familiar frameworks Building something from scratch to understand fundamentals

Copy-pasting solutions Debugging unfamiliar errors yourself

Avoiding mathematics or systems design Studying distributed systems, algorithms, or low-level architecture

Why It's Uncomfortable:

· You feel slow and incompetent again. Tasks that took minutes now take hours.

· You make beginner mistakes. Your code is ugly. You feel exposed.

· Your ego takes a hit. Colleagues who stayed in their comfort zone seem more productive.

The Growth:

· You build transferable knowledge—understanding concepts, not just syntax.

· You develop learning agility—the meta-skill of picking up new technologies quickly.

· You future-proof your career. When the industry shifts, you shift with it.

Example:

An engineer spent 10 years as a PHP expert. He was comfortable. He was the "go-to" person. But he noticed job postings shifting toward Node.js, Python, and cloud architectures. He decided to learn Node.js. For three months, he felt like a junior again. His pride hurt. His productivity dropped. But he persisted. A year later, his company needed to build a real-time service. He was the only senior engineer who could lead it. His discomfort had opened a door that would have been closed if he had stayed comfortable.

B. Career Discomfort: Taking on New Responsibilities

Comfort Behavior Uncomfortable Growth Behavior

Staying as an individual contributor Moving into tech lead, architect, or management roles

Avoiding public speaking Presenting at team meetings, conferences, or technical reviews

Staying in the same company Leaving for a role that stretches your capabilities

Avoiding ambiguity Taking ownership of ill-defined problems

Why It's Uncomfortable:

· You are no longer judged solely on code quality. You are judged on communication, leadership, and outcomes.

· You make decisions with incomplete information. You are accountable for things you do not fully control.

· You face criticism, disagreement, and the weight of other people's careers.

The Growth:

· You develop leverage—your impact scales through others, not just your own output.

· You build influence—the ability to align teams, secure resources, and drive direction.

· You become indispensable in ways that pure technical skill cannot achieve.

Example:

A senior engineer was deeply respected for her technical skills. She was comfortable. When asked to lead a critical project with three junior engineers, she hesitated. Leading meant less time coding. It meant unblocking others, managing stakeholders, and being accountable for outcomes she could not control. She took the role anyway. The first three months were brutal. She made mistakes. She felt incompetent. But she persisted. Two years later, she was a director of engineering, leading 40 people. Her technical skills were still there, but now she had multiplied her impact.

C. Relational Discomfort: Giving and Receiving Feedback

Comfort Behavior Uncomfortable Growth Behavior

Avoiding difficult conversations Giving direct, constructive feedback to peers or managers

Being defensive in code reviews Asking for feedback proactively and receiving it without defensiveness

Staying silent in meetings Speaking up, challenging assumptions, advocating for quality

Why It's Uncomfortable:

· Conflict is uncomfortable. You risk damaging relationships or being disliked.

· Receiving feedback triggers defensiveness. Your ego wants to explain why the feedback is wrong.

· Speaking up risks being wrong publicly, or being perceived as difficult.

The Growth:

· You build trust—people know you are honest and can handle honesty in return.

· You accelerate learning—feedback is the fastest way to see your blind spots.

· You develop influence—your voice carries weight because you use it thoughtfully.

Example:

An engineer consistently avoided code review conflicts. If someone suggested a change, he accepted it, even when he disagreed. He was comfortable. But his code quality suffered from design-by-committee. His growth stalled. He decided to change. He started explaining his reasoning calmly, asking clarifying questions, and standing firm when he believed his approach was correct. It was uncomfortable. Some conversations were tense. But his designs improved. His team respected him more, not less. He had learned that discomfort was not conflict—it was clarity.

D. Identity Discomfort: Redefining Yourself

Comfort Behavior Uncomfortable Growth Behavior

Identifying as "just an engineer" Expanding identity to include leader, mentor, communicator, or founder

Hiding behind technical complexity Making technical concepts accessible to non-technical stakeholders

Avoiding business context Understanding users, markets, and business strategy

Why It's Uncomfortable:

· You are no longer the expert in the room. You are learning from product managers, salespeople, and customers.

· You risk being seen as "not technical anymore" if you focus on leadership or business.

· Your sense of identity—"I am the person who solves hard technical problems"—is challenged.

The Growth:

· You become T-shaped—deep in engineering, broad in adjacent domains.

· You become strategic—able to align technical decisions with business outcomes.

· You become unstuck—your career is no longer limited by technical ceilings.

Example:

An engineer was known as the best backend developer in the company. His identity was tied to being the "deep technical expert." When he was asked to lead a cross-functional initiative involving product, design, and marketing, he resisted. That was not "his job." But he took it. He had to learn to speak the language of product managers. He had to understand user research. He had to present to executives. It was deeply uncomfortable. But after that project, he was no longer just a backend engineer. He was a technical leader who could bridge engineering and business. His career trajectory changed completely.

5. The Law of the Uncomfortable: CEO's Perspective

For a CEO, discomfort is not occasional; it is the permanent condition of leadership. The higher you rise, the more frequently you encounter situations with no clear path, no precedent, and no guarantee.

A. Strategic Discomfort: Making Decisions Without Certainty

Comfort Behavior Uncomfortable Growth Behavior

Waiting for perfect data Making decisions with incomplete information

Avoiding difficult trade-offs Choosing between two good options or two bad ones

Delegating hard decisions Owning the decisions that cannot be delegated

Why It's Uncomfortable:

· You cannot outsource uncertainty. The weight of decisions rests on you.

· You will be wrong sometimes. Publicly. With consequences for employees, customers, and investors.

· There is no playbook for the situation you are in. You are creating the path as you walk it.

The Growth:

· You develop judgment—the ability to make high-quality decisions with imperfect information.

· You build decisiveness—speed of decision-making becomes a competitive advantage.

· You earn trust—people follow leaders who make hard calls with clarity and accountability.

Example:

A CEO faced a decision: pivot the company to a new market or double down on the existing product. The data was ambiguous. The board was divided. The team was anxious. Staying comfortable meant delaying the decision, gathering more data, running more analyses. But delay was itself a decision—and a costly one. She made the call. She chose to pivot. It was uncomfortable. She lost some employees who disagreed. The first six months were chaotic. But the pivot ultimately saved the company. She learned that discomfort was not a sign to stop; it was a sign that she was doing the job of a CEO.

B. People Discomfort: Having Hard Conversations

Comfort Behavior Uncomfortable Growth Behavior

Avoiding performance conversations Giving direct feedback to underperforming leaders

Keeping misaligned team members Letting people go when they are not the right fit

Avoiding conflict Addressing misalignment, politics, or toxicity directly

Why It's Uncomfortable:

· You are affecting people's livelihoods and identities. The weight is heavy.

· You risk being disliked. You risk being wrong.

· Your own discomfort with conflict can lead to avoidance, which damages the entire organization.

The Growth:

· You build a healthy culture—clarity, accountability, and trust.

· You create psychological safety—when leaders model difficult conversations, others learn to do the same.

· You earn respect—people may not always like hard decisions, but they respect leaders who make them with integrity.

Example:

A CEO had a co-founder who was brilliant but toxic. The co-founder belittled engineers, dismissed feedback, and created a culture of fear. The CEO avoided the conversation for months, hoping it would resolve. The discomfort of conflict felt worse than the slow erosion of culture. But eventually, he realized the cost of avoidance: top engineers were leaving. He had the conversation. It was brutal. The co-founder left. The CEO lost a co-founder and a friend. But the company culture healed. He learned that avoiding discomfort was not protecting the relationship; it was destroying the company.

C. Scaling Discomfort: Letting Go of Control

Comfort Behavior Uncomfortable Growth Behavior

Making all decisions Delegating authority, accepting decisions you would not have made

Staying in the details Stepping back to strategy, trusting others to execute

Hiring people who think like you Hiring people who challenge you, who are better than you in their domains

Why It's Uncomfortable:

· You lose control. Decisions are made that you would not have made. Mistakes happen.

· Your identity shifts from "the person who knows everything" to "the person who enables others."

· You feel irrelevant. The company can operate without you—which is the goal.

The Growth:

· You build scalability—the organization can grow beyond your personal capacity.

· You develop leaders—people who can take on responsibility and grow.

· You become a true CEO—focusing on vision, culture, and strategy, not operations.

Example:

A founder-CEO was involved in every decision: every hire, every feature, every marketing campaign. The company grew to 50 people, and he was the bottleneck. He knew he needed to let go, but it was uncomfortable. He hired a COO. He delegated engineering to a VP. He stopped attending every product meeting. For months, he felt anxious. Decisions were made that he would not have made. Some were wrong. But the company grew to 200 people. He learned that his discomfort was the price of scale. If he had stayed comfortable, the company would have stayed small.

D. Visibility Discomfort: Public Leadership

Comfort Behavior Uncomfortable Growth Behavior

Staying behind the scenes Becoming the public face of the company

Communicating through polished statements Speaking authentically, vulnerably, and directly

Avoiding controversy Taking stands on issues that matter to your mission and values

Why It's Uncomfortable:

· Public visibility invites scrutiny, criticism, and personal attacks.

· Authenticity risks saying the wrong thing, alienating stakeholders, or creating controversy.

· Vulnerability—admitting mistakes, uncertainty, or struggles—feels like weakness.

The Growth:

· You build trust—with employees, customers, and the public. People trust leaders who are real.

· You create alignment—your communication reinforces the mission and culture.

· You become a magnet—talent and partners are drawn to leaders with clarity and courage.

Example:

A CEO had always avoided public speaking. She let her product lead talk to customers, her marketing lead talk to the press. She was comfortable behind the scenes. But the company was struggling with retention. Employees wanted to hear from her. Customers wanted to know the company had a leader. She started recording a weekly video update—unscripted, raw, honest. The first video was terrifying. She stumbled. She revealed uncertainty. But employees responded. They felt connected. Customers trusted her. She learned that discomfort in visibility was not exposure—it was connection.

6. The Growth Formula: Comfort + Risk = Stagnation

Bartlett offers a simple formula:

Formula Implication

Comfort + No Risk = Stagnation Staying where you are, doing what you know, avoiding discomfort. Growth stops.

Discomfort + Calculated Risk = Growth Stepping into uncertainty, stretching capabilities, embracing the awkwardness of learning.

Panic + Reckless Risk = Burnout Taking on challenges far beyond current capability without support.

The sweet spot: Discomfort with calculated risk. You should feel awkward, uncertain, and stretched—but not overwhelmed, unsupported, or hopeless.

7. How to Embrace Discomfort: A Framework

Step Engineer Application CEO Application

1. Identify Your Comfort Zone What technologies, tasks, or roles feel easy? What have you been avoiding? What decisions do you delegate? What conversations are you postponing? Where do you feel in control?

2. Define the Stretch Choose a specific skill, project, or responsibility that sits just outside current capability. Choose a decision, conversation, or strategic shift that you have been avoiding.

3. Accept the Inevitable Discomfort Acknowledge that you will feel slow, foolish, and uncertain. This is not failure; it is the feeling of learning. Acknowledge that you will feel exposed, anxious, and uncertain. This is not weakness; it is the feeling of leading.

4. Create Support Structures Pair with someone more experienced. Set up a learning project with safe failure modes. Find a peer CEO or coach. Create board alignment. Ensure you have support before stepping into exposure.

5. Reflect on Progress After each uncomfortable step, ask: What did I learn? What is easier now than three months ago? After each hard decision, ask: What did I learn about myself? What can I do now that I could not before?

6. Expand the Threshold As what was uncomfortable becomes comfortable, find the next edge. Growth is never finished. As you grow into new capabilities, the organization grows. Your discomfort threshold is the company's growth ceiling.

8. Why the Law of the Uncomfortable Matters in the Book's Structure

The Law of the Uncomfortable sits in Part 1: The Self, the foundational section on internal mastery. Its placement is critical:

· Part 1 is about building yourself before building your company or brand.

· The Law of the Uncomfortable teaches that self-mastery is not about reaching a state of permanent comfort. It is about developing the capacity to tolerate discomfort.

· This law enables all others. Without the ability to tolerate discomfort, you cannot:

  · Build reservoirs (requires discipline now for future security)

  · Fail intelligently (requires tolerating the discomfort of failure)

  · Learn by teaching (requires vulnerability)

  · Lead authentically (requires exposure)

Bartlett's deeper argument: Your capacity for discomfort is the ceiling of your growth. If you cannot tolerate the discomfort of learning, you will stop learning. If you cannot tolerate the discomfort of leadership, you will stop leading. If you cannot tolerate the discomfort of vulnerability, you will stop connecting.

9. Summary: The Law of the Uncomfortable

Element Summary

Definition Growth and comfort cannot coexist. Discomfort is not a sign of failure; it is a sign of expansion.

Core Principle If you are not uncomfortable, you are not growing.

Zones Comfort Zone (no growth) → Learning Zone (discomfort, growth) → Panic Zone (overwhelm, no growth)

Comfort Trap Achieving comfort, mistaking it for success, and stagnating while the world moves.

Engineer Applications Learning new technologies, taking leadership roles, giving/receiving feedback, expanding identity.

CEO Applications Making decisions with uncertainty, having hard conversations, letting go of control, embracing public visibility.

Growth Formula Discomfort + Calculated Risk = Growth. Comfort + No Risk = Stagnation.

Book Context Part 1 (The Self)—internal mastery means developing capacity to tolerate discomfort.

Quick Reference: Uncomfortable Growth Checklist

For Engineers For CEOs

What technology have you been avoiding learning? What decision have you been postponing?

What role or responsibility feels beyond you? What conversation have you been avoiding?

When did you last ask for feedback? Where are you still holding control you should delegate?

When did you last speak up with a dissenting view? When did you last communicate vulnerably?

What would you do if you were guaranteed not to fail? What would you decide if you were guaranteed to be supported?