Six Hours

A young woman I know once waited six hours for a friend's reply to a text. By the third hour, she had built an entire story: she'd said the wrong thing at dinner, the friendship was cooling, something was wrong. By the sixth hour, the reply came — a dead phone, a long meeting, nothing more.

I have done this myself, with a letter once, in a different decade, with the same ending: hours spent on a story that had nothing to do with reality.

The feeling each time is a particular kind of ache — not quite anger, not quite sadness, but a sense of being wronged by someone who, it turns out, did nothing wrong at all. Normally that ache just fades once the explanation arrives, filed away as "oh, that's all it was," and forgotten.

What it actually reveals is a gap in a specific skill: the ability to notice when we've quietly swapped an observation for an interpretation. Left unexamined, this gap doesn't stay small — it shapes how we read every silence afterward, until we are arguing more with our own assumptions than with the people in our lives. 

Aaron Beck, one of the founders of cognitive therapy, built much of his life's work around exactly this distinction — the event is rarely the problem; the uninspected meaning we assign to it usually is.

The tool worth practicing: two columns, even mentally. One for what actually happened — only what could be filmed by a camera. One for what I am telling myself it means — which is always a guess, however confident it feels.

She never knew her six hours stayed with me. But the gap she lived that day is one most of us carry — mistaking our own story for someone else's intention.

If this resonates: Aaron Beck's original work on cognitive distortions (a quick search for "Beck cognitive triad" gets you the core idea) — or, more readable, David Burns' Feeling Good, which translates Beck's work for a general audience.

The Room You Leave Behind

Why your expressive style matters more than you think

Walk into any family gathering and you can feel it before anyone speaks. One person enters and the room exhales — shoulders drop, voices soften. Another enters and the room tightens, almost imperceptibly, as if bracing. Neither of them said a word. Both of them changed the room.

This is the part of expressiveness we rarely talk about: it was never just self-expression. It was always also a transmission.

Every style has a reason

We each carry a baseline — some of us cool and even-keeled, some warm and easily moved, some quietly intense, some openly boisterous. None of these is a character flaw waiting to be corrected. Each was built by temperament, and then shaped further by what was safe, rewarded, or punished in the home we grew up in. The child who learned that big feelings drew big trouble becomes the adult who keeps an even face. The child who learned that loud joy was met with loud joy becomes the adult who fills a room. Your style has a history. So does everyone else's.

But it doesn't stay contained

Here is the part that matters for living alongside others: whatever your style, it travels. Psychologists call this emotional contagion — the well-documented tendency for one person's emotional state to nudge the state of whoever is near them, often beneath conscious notice. A tense parent makes a tense household before a single word of tension is spoken. A genuinely relaxed presence can lower the temperature of an entire room without trying. We are, in this very specific sense, porous to each other.

This is not a reason to perform a feeling you don't have. It is a reason to notice that your inner weather has outdoor effects.

The difference between softening and faking

This is where it gets delicate, and where I want to be precise, because the instinct to protect people we love from our worry is a generous one — and it deserves better than being lumped in with dishonesty.

There is a real difference between two things that can look similar from the outside:

Modulation — choosing which true layer to lead with. A parent who is worried but keeps their voice steady for a frightened child is not lying. They are choosing, deliberately, to offer calm because calm is what is needed and calm is also, genuinely, available to them — even if it sits alongside worry underneath. This is sometimes called a display rule, and every healthy relationship runs on a quiet, mutual understanding of when to use one.

Fakery — manufacturing the opposite of what you feel, repeatedly, to manage someone else's reaction long-term. This is different in kind, not just degree. Used occasionally, it's a kindness. Used as a habit, it erodes two things at once: the other person's ability to read you accurately, and your own clarity about what you actually feel.

The test that tends to hold up: am I softening something true, or replacing it with something false? The first is generosity. The second, repeated, becomes a debt that eventually comes due — usually as distance, sometimes as resentment, occasionally as the other person sensing the gap and trusting you less for it, even if they can't say why.

A question worth carrying

You don't owe the people around you full intensity at all times. Restraint, in the right moment, is its own form of care. But you do owe them honesty about the shape of what you're carrying — even when the honest shape is "I'm not ready to say more right now," which is itself a true and complete sentence.

A useful daily question, then, is not how should I perform today but: what am I putting into the room, and is it true enough to stand behind?

Answer that honestly, and the room you leave behind will take care of itself.

---

Part of an ongoing series on self-mastery for the next generation.

The Four Words

At the airport last week, I watched a young man stare at his phone for a long minute, his shoulders dropping slightly with each re-read. I didn't know what the message said. But I recognized the posture — I have worn it myself, decades apart, over a telegram once, and later, an email.

It took me back to a young executive I once mentored, who'd received a two-line note from his boss and had spent the whole evening rehearsing apologies for a meeting that turned out to be about something else entirely.

The feeling in both cases was the same — a quiet flicker of dread. And in both cases, it would normally just pass. A few uneasy hours, a resolved misunderstanding, and the moment is forgotten — filed away as "anxiety," nothing more.

What's missed is what the dread reveals: not a problem with the message, but a skill gap — the ability to separate fact from inference under uncertainty. Left unexamined, that gap doesn't go away. It just resurfaces, slightly bigger, the next time a message, a silence, or a delay shows up. Daniel Kahneman would call this the unchecked rule of System 1 — fast, emotional, and confident, with System 2 never invited to the table.

The tool worth naming here is simple: before reacting to anything that spikes a feeling, ask one question — what do I actually know, versus what am I predicting? It takes ten seconds and it is the entire difference between a reaction and a response.

That young man at the airport may never know I noticed him. But he reminded me that this particular gap — mistaking prediction for fact — is something most of us carry, unexamined, for years.

If this resonates: Daniel Kahneman's Thinking, Fast and Slow is the foundational text on System 1/System 2 thinking — worth the first three chapters alone if the whole book feels long.

Next: what happens when the story we tell about someone else's silence turns out to be entirely our own invention.

The Pace of the Present: On Looking Ahead Without Losing Step

There is a particular kind of mistake that only thoughtful people make. It doesn't come from carelessness — it comes from caring too far ahead. You see the market before the product exists. You see the brand before the prototype works. You see the legal architecture before the database schema is settled. And in your eagerness to protect the future, you accidentally destabilize the present.

I was helping a younger one develop an AI Agent based on his idea of using AI. He had already done some work and was sharing with me what he had in mind. He even had thought of monetising the product. That was inspiring for me and when I started probing and suggesting he asked me not to share what he mentioned with anyone else. He stopped short of asking me to sign an NDA with non-compete clause.

We progressed step by step paraphrasing prompts starting from problem statement to hypothesis to framework to process to product design to engineering documentation, at which point he started with coding.

I have limitation in that area so I started thinking of market and go-to-market and social media and LinkedIn and web site and brand and brand identity and costs and pricing and legal aspects of registration and policies and agreements, while he was working on UI and UX and backend and database and Flutter and Python and prototype and what not.

I do not remember at which point I digressed into engineering side and suggested a few things based on my forward looking advance preparation aspects and that put him in a bind. When his AI Coder asked him counter questions, I knew I had only looked ahead without looking back.

That was the lesson. I have learnt that while it is good and necessary to prepare for future it is equally necessary to keep an eye on how are we progressing. I looked for support to my learning and found that this exact failure mode has a long intellectual history. Here is what some of the sharper minds on management, strategy, and systems have said about it.

Drucker: Effectiveness Before Efficiency

Peter Drucker drew a famous distinction between efficiency — doing things right — and effectiveness — doing the right things. His related discipline, "feedback analysis," asked managers to compare what they expected to happen against what actually happened, as a recurring habit, not a one-time audit. The implication for builders is blunt: forward planning is only as good as your willingness to check it against the unfolding reality. A brilliant go-to-market plan built atop an engineering stage that hasn't yet stabilized is efficient thinking applied to the wrong moment — right answer, wrong horizon.

Covey: Quadrant II, Not Quadrant Confusion

Stephen Covey's habit "begin with the end in mind" is often quoted in isolation, but he paired it deliberately with "put first things first." His time-management matrix separates the important from the urgent, and Covey's real warning was about Quadrant III and IV traps — but the subtler trap, the one builders fall into, is letting important-but-not-yet-urgent work (branding, legal structure, pricing) crowd out attention from important-and-urgent work (a teammate stuck on a database decision right now). Vision has its proper seat. It is not meant to occupy the driver's chair at every stage.

Mintzberg: Strategy Is Crafted, Not Just Planned

Henry Mintzberg's critique of the "planning school" of strategy is almost tailor-made for this situation. He argued that strategy is less like an architect's blueprint and more like a potter's craft — shaped by hands in contact with the clay, responsive to what the material is doing in real time. Deliberate strategy (the plan) and emergent strategy (what reality teaches you as you go) have to interleave. A relative offering forward-looking advice without staying in contact with the day's actual clay is planning without crafting — and Mintzberg would say that's not strategy at all, just paperwork.

Andy Grove: Task-Relevant Maturity and Tight Monitoring

Andy Grove, in High Output Management, introduced the idea of "task-relevant maturity" — the level of guidance a person needs depends entirely on how mature they are at that specific task, not their seniority or potential. A brilliant strategist can have low task-relevant maturity in, say, Flutter architecture, and that should change how much directive input they offer there. Grove was equally insistent on tight feedback loops and monitoring actual production indicators rather than intentions — his version of "trust, but verify the dashboard, not the dream."

Lean Startup: Validated Learning Over Imagined Scale

Eric Ries's entire framework — Build, Measure, Learn — exists precisely to prevent what happened here. The Minimum Viable Product isn't a smaller version of the grand vision; it's a deliberate refusal to build ahead of validated learning. Pricing models, brand identity, and go-to-market machinery built before the product has even reached its first working prototype are, in Lean Startup language, "premature scaling" — one of the most common start-up killers, because resources and attention get spent solving problems the market hasn't confirmed exist yet.

Systems Thinking: Today's Problems Are Yesterday's Solutions

Peter Senge and Donella Meadows both worked from the same root insight: a system is not a pile of parts to be separately optimized, but a web of feedback loops. Senge's recurring line of warning — that today's problems often trace back to yesterday's well-intentioned solutions — applies directly here. A forward-looking engineering suggestion, dropped into a system not yet ready to absorb it, doesn't just sit there neutrally; it ripples forward and becomes tomorrow's confusion. Meadows would add: the leverage point was never "give better advice" — it was "watch the feedback loop you're embedded in before you intervene."

The Three Horizons Model: Holding Multiple Time Frames Without Collapsing Them

The Three Horizons framework (Baghai, Coley, and White, popularized through McKinsey) separates Horizon 1 (the present, needing operational excellence), Horizon 2 (emerging opportunities), and Horizon 3 (future bets, still speculative). Its real discipline isn't having all three in mind — it's not letting Horizon 3 thinking leak uninvited into Horizon 1 execution. They're meant to run in parallel, governed separately, not poured into each other. Go-to-market and brand thinking was legitimate Horizon 2/3 work. The mistake was letting it cross the membrane into Horizon 1's engineering decisions before that horizon was stable.

Stewart Brand: Pace Layering

One more lens, less management theory and more systems design — Stewart Brand's idea of "pace layering," from his work on how buildings and civilizations change. Different layers of any system move at different speeds: fashion changes fast, infrastructure changes slow, foundations barely change at all — and a well-functioning system depends on the fast layers learning from and being protected by the slow ones, not the reverse. Brand identity, pricing, and market strategy are fast-moving layers. Database architecture and core engineering logic are slow-moving foundations. Advice flowing from a fast layer into a slow one, out of sequence, is precisely the kind of mismatch pace-layering theory predicts will cause friction.

The Common Thread

Every one of these thinkers, working in different decades and different vocabularies, converges on the same instruction: vision needs a feedback tether. Forward thinking isn't the error — unanchored forward thinking is. The skill isn't choosing between looking ahead and staying present; it's learning to do both at once, with the present always holding the leash.

The lesson — prepare for the future, but keep an eye on how we're actually progressing — is, in plainer language, the discipline every one of these frameworks is reaching for from a different angle. I didn't need their vocabulary to arrive at their conclusion. That itself says something about how reliable the lesson is.

Growth Does Not Find You. You Have to Go Looking for It

In fifty years of working with people and organisations, I have watched two kinds of professionals. Those who became who they were capable of becoming. And those who became whoever their circumstances made them. The difference was rarely talent.

I want to tell you something that took me most of my professional life to see clearly — and that I now believe is one of the most important things a young professional can understand early.

Most people do not grow. They accumulate.

They accumulate years of experience. They accumulate job titles. They accumulate responsibilities, connections, and the quiet confidence that comes from knowing how to navigate a particular environment. And they mistake this accumulation for growth.

It is a completely understandable mistake. From the inside, accumulation feels like becoming. The calendar moves, the pay rises, the business cards change. Something is happening. Something must be happening.

But accumulation and growth are not the same thing. And the difference between them — over a career, over a life — is vast.

What Accumulation Looks Like

Let me describe someone you may recognise.

They are good at their work. They have been doing it long enough to be trusted with more of it. They know the landscape of their industry, can read a room, can navigate office politics with the practised ease of someone who has survived several cycles of them. They have opinions, formed through experience, and those opinions are usually right.

But ask them what they want — truly want — from the next decade of their professional life, and they will pause in a way that goes beyond thinking. It is the pause of someone who realises, perhaps for the first time, that they have not asked themselves that question in years. Perhaps ever.

Ask them about their values — what they stand for, what they would not compromise — and they will give you the right answer. The answer that sounds right. But if you sit with it long enough, and they do too, a second pause arrives. The pause of recognition. The answer was fluent but not felt.

Ask them about their growth edges — the places where they are not yet who they want to be — and something interesting happens. They will tell you what they are working on professionally. The skill they are developing, the certification they are pursuing, the area where their manager gave them feedback last year. These are real. They are not nothing.

But they are not the growth edges I am asking about. I am asking about the interior landscape — the patterns of thinking, the tendencies of character, the beliefs about what they are capable of that were formed long before their current role — and that shape everything they do within it

Most people have never mapped that landscape. Not because they are incurious or uncommitted — but because no one ever asked them to, and they never thought to ask themselves.

The Illusion That Circumstances Will Do It For You

Here is the comfortable assumption I want to gently disturb.

Most professionals — and I was among them for longer than I like to admit — believe that growth is something that happens to you if you show up consistently and work hard. That time and experience, combined with effort, will produce the person you are capable of becoming.

It will not. Not by themselves.

Time produces people who are very experienced at being who they already were. Only intentional self-examination — the deliberate practice of turning inward, assessing honestly, and choosing differently — produces growth.

I have watched this play out hundreds of times across organisations I worked with over four decades. Talented people, given every opportunity, who plateaued not because they stopped working — but because they stopped examining. Who arrived at fifty having been thirty for twenty years, just with a more comfortable chair.

And I have watched others — sometimes less obviously talented, sometimes starting from less — who made a different choice. Not always consciously at first. But at some point, often triggered by a disruption or a dissatisfaction they could no longer ignore, they turned the lens inward. They began to ask: who am I, actually? What do I want, actually? What is preventing me from becoming who I am capable of being?

Those questions — asked seriously, pursued honestly, revisited regularly — are the beginning of genuine professional growth. Everything else is accumulation.

Why This Is Harder Than It Sounds

I want to be honest about something. The examination I am describing is not comfortable work.

It requires a willingness to see yourself as you are — not as you perform yourself to be for colleagues, for family, for the internal audience of your own self-regard. That kind of honest self-perception is genuinely difficult. We are all, to some degree, invested in our own narrative. We have a version of ourselves that we have been carrying for years, and questioning it can feel threatening even when it is liberating.

It also requires time and structure that the pace of modern professional life actively discourages. When you are always in motion — always producing, always responding, always managing — the interior landscape goes unvisited. Busyness is, among other things, a very effective way of never having to examine yourself.

And it requires a guide. Not necessarily a human mentor — though those are invaluable when you can find one. But some kind of structured, consistent, honest accompaniment that keeps you asking the right questions even when comfort or distraction would rather you did not.

Without that accompaniment, most people do not sustain the examination long enough for it to produce real change. They have a good conversation, read a good book, attend a workshop, feel genuinely moved — and then the busyness returns and the interior landscape goes unvisited again for another year.

A Different Kind of Professional Life

I am writing this because I have spent fifty years watching what happens when people do the examination and what happens when they do not. And the differences — in fulfilment, in impact, in the quality of the relationships they build and the work they produce — are not small. 

People who grow deliberately are more interesting. They are more flexible — because they know who they are well enough to adapt without losing themselves. They are more resilient — because their sense of self does not depend on any particular title, role, or external validation. They are more useful to the people around them — because they have developed the capacity for genuine self-awareness, which is the root of empathy, good judgment, and authentic leadership.

They also, in my experience, enjoy their work more. Not because their circumstances are necessarily better — but because they are living a professional life that is actually theirs, shaped by genuine values and genuine choices, rather than a life that happened to them while they were looking elsewhere.

You were not born to be a product of your circumstances. You were born to be the author of your becoming. That authorship requires something of you. It requires that you begin.

The question I want to leave you with — not as a rhetorical flourish but as a genuine invitation — is this:

When did you last deliberately examine who you are becoming? Not who you are at work, not what you are achieving — but who you are becoming as a person, as a professional, as someone who will look back at this decade and either recognise themselves or wonder where they went?

If the answer is 'not recently' — or 'not ever, in those terms' — then I hope this is the beginning of that examination.

It will be worth it. I have never met anyone who sincerely regretted beginning.

About the Author

Atul Mankad is a senior HR professional and organisational development consultant with over five decades of experience working with organisations and individuals across India and internationally. He writes about growth, leadership, and the wisdom traditions that have shaped his understanding of human potential.