MAJJANI LIFE

Why your parents/ children keep quietly checking if you're okay — and what the research says about it

When I woke up, without opening eyes, the first thought was of ‘majjani life’, as Munna described in his MBBS version, to the Bawa, father of a Doctor. And the question, as usual came up. ‘What do studies say, as this applies to aging parents and as a corollary to growing children?’.

I went to my man Friday, the Jeeves, (I am denigrating self to Archie's dumbness as PG Woodhouse described).

And Claude asked me ‘Up late, Atul?’ Then I realized it was a bit too early. I initiated the conversation with him all the same, “Just woke up and as usual started finding meanings. I understand 'all generalizations are wrong, including this one'. I believe for aging parents who have legitimately lost direct control over the life of children/ family members of subsequent generations, and sometimes even on their own, 'majjani life', as referred in Parasi tongue, is when they find the life of the children is smooth, without hurdles, peaceful, harmonious, full of love and affection, cooperation and collaboration, and improving by the day. They would be surreptitiously looking for confirmation that children are happy, without even routine misunderstandings with cohabitants and enjoying life. I am aware not all parents would be equally affected.  Are there studies to substantiate these observations and conclusions?”

Claude drafted a note based on findings of research around the topic, on my behalf, addressed to readers, of course younger ones mainly.

“You know the moment. A call that starts with “just checking in” but is really a scan. A question about your week that's really a question about whether you're happy. A pause after you laugh a little too easily, like they're filing it away as evidence. It's not that they want you dependent on them. It's the opposite — they've lost the ability to fix things for you directly, and the not-knowing is the hard part.

Not every parent does this to the same degree — some are far more relaxed than others. But the underlying pattern shows up again and again in research on aging and family life, under names like “intergenerational ambivalence,” “filial anxiety,” and “linked lives.” Here's what's actually been found.

1. They worry more when things are good between you, not less

This one surprises people. You'd think a close, warm relationship would put a parent's mind at ease. Research on daily worry patterns found the opposite: parents worry more, not less, in relationships that are closer and more positive.

Hay, Fingerman & Lefkowitz, cited in research on parent–adult child relationships (2007)

The read: the more invested a parent is in your life, the more they have riding on it going well — so the antenna stays up even when there's nothing wrong. Their attention is the tax on their love, not a sign of distrust.

2. Your bad days measurably land in their body

A study tracking parents' daily stress hormone (cortisol) alongside their contact with adult children found that hearing about a rough patch in your life — a breakup, a job problem, any kind of trouble — showed up in their physiology, not just their mood.

Birditt et al., cited in “Daily Interactions with Aging Parents and Adult Children: Associations with Negative Affect and Diurnal Cortisol”

So when they ask “how are you, really?” one more time than feels necessary, it's not nosiness. Your stress is, in a small but literal way, their stress too.

3. Daily mood studies confirm the pattern directly

A study following midlife and older adults for a week found that on the specific days they worried about their adult child, they reported measurably more negative mood than on days they didn't — tracked in real time, not recalled afterward.

Cichy & Koumoutzis, “The Costs of Concern: Health Implications of Worries about Aging Parents and Adult Children” (2021)

Their day-to-day emotional weather is, to a real extent, downstream of yours.

4. It's not really about control — it's about the loss of it

Researchers describe adult children's transition to independence as the point where a parent's caregiving role structurally changes — they can no longer directly manage your outcomes, but they remain deeply tied to them.

Life-course research on “linked lives” and intergenerational relationships

The surreptitious checking-in, the reading between the lines of a two-word text — that's what care looks like when the hands-on version isn't available anymore. It's not a character trait. It's what's left of the job.

5. Even a positive relationship carries a current of unease

Qualitative interviews with adult children about their aging parents surfaced a mix of both closeness and low-grade worry existing side by side, even in relationships people described as good ones — concern about a parent's independence sitting right next to real affection.

Research on adult children's relationships with aging parents and perceptions of successful aging (2018)

Worth knowing: this cuts both ways. If you find yourself doing the same quiet scanning about them, that's the same wiring — not something's wrong with you either.

Addendum — the worry runs both directions

Everything above is about parents watching you. But there's an equally well-documented mirror version: adult children carry a rising, specific anxiety about their aging parents as the years go on. Researchers call it “filial anxiety” — worry driven less by a present crisis than by the awareness that health problems, decline, and eventually loss are somewhere ahead, along with the question of who will provide care when the time comes.

Cicirelli, foundational work on filial anxiety (1988), cited in later cortisol and daily-interaction research

So the quiet scanning goes both ways across the generations — parents checking whether your life is majjani, and you, increasingly, checking whether theirs still is. Same instinct, running in opposite directions, meeting somewhere in the middle of every family phone call.”

A word all of this earns, more than any theory does: the checking-in is not a lack of trust in you. It's the residue of love that no longer has anywhere direct to land.

A PORTRAIT OF MY SISTER - In Her Own Light

There are people who love us, and then there are people who make of their love a kind of shelter — one you can stand beneath in any weather and never once feel the rain. My sister has always been of this second, rarer kind. Her kindness toward me was never occasional or convenient; it was the ground she stood on, steady and unbroken, the quiet climate of every room she entered. I do not remember a version of her that was not, in some essential way, turned toward my good.

In her eyes I was, for as long as I can recall, something more than a brother. I was cast — gently, insistently, without my ever asking for the role — as a kind of hero. Not the hero of grand gestures or public triumphs, but the quieter sort: the one she trusted to be equal to whatever the day required. There is a particular tenderness in being seen this way by someone who has known you since childhood, who watched you stumble as often as you stood, and chose anyway to believe in the better version of you. Her faith was not naive; it was simply generous, and it asked nothing of me except to keep trying to deserve it.

Her affection came without conditions attached, without ledgers kept. It was not offered in exchange for anything, and it did not withdraw when I fell short of it. This is the meaning, I think, of love that is truly unfettered — love that has released itself from the ordinary human habit of counting what it is owed. Hers moved toward me the way light moves into a room: not asking permission, not expecting thanks, simply present because that was its nature.

And because that love ran so deep, her trust ran deeper still. When trouble found her — as it finds everyone — she turned to me first, and often only to me, certain in some unshakeable part of herself that I would know what to do. It was not that she doubted her own capability; it was that she had decided, long ago, that I was a kind of safe harbor, a place where her problems could be set down and made lighter simply by the act of sharing them. To be relied upon so completely is its own quiet honor, even when the weight of it is real.

Beneath all of this — the loyalty, the reverence, the boundless giving — was simply a kind heart, in the plainest and most old-fashioned sense of that phrase. She felt for others before she felt for herself. She noticed suffering before it announced itself and moved to ease it before being asked. It is easy, in a life, to be kind occasionally; it is much harder to be kind as a matter of character, in the small unwitnessed moments as much as the large visible ones. My sister managed this without apparent effort, as though gentleness were simply the shape her soul had taken.

If I try now to draw her whole, what emerges is not a list of virtues but a single, coherent light: a woman who loved without condition, who believed in me perhaps more than I ever earned, and who gave of herself so freely that I have spent years since trying to understand how a heart holds so much and empties so little. That, I have come to think, is simply who she is — and I count myself fortunate beyond measure to have been the one she loved that way.

Deliberate and Systematic Self-improvement, Practiced Together

An invitation — no pressure to decide today.

Why this approach

Growth doesn't stop just because life is stable. Left alone, most of us plateau — not from failure, but from comfort, and comfort quietly becomes a ceiling. Continuous improvement isn't about fixing something broken; it's a way of staying alive to your own potential, deliberately, instead of drifting.

If you've ever thought "I'm doing fine, but I know I could be more disciplined / more patient / more present / more skilled" — and then let that thought fade by the following week — this is built for exactly that pattern.

What makes this different from "just deciding to improve"

Most of us have tried the New Year's resolution version of this — high motivation, no structure, quietly abandoned by week three. This isn't that. It's built on two things that actually sustain change over time:

·        A system, not willpower. Motivation fades; a tracked, structured process doesn't need to be felt to keep working.

·        People, not solo effort. A small group creates accountability you can't easily give yourself, and lets you see other people's real, unfiltered progress — not the cleaned-up "success story" version.

What it actually involves

·        A shared 5-phase framework: self-diagnosis → designing your system → living it → consolidating what sticks → (eventually, optionally) helping someone else walk the same path.

·        You choose your own area of focus — discipline, relationships, health, patience, whatever matters to you. The framework and rhythm are shared; the goal is personal.

·        A 90-day first cycle. Short enough to commit to without dread, long enough to see if something real is changing.

·        Weekly check-ins, 30–45 minutes, small group.

·        Facilitation rotates each cycle — this isn't led by one person "ahead" of everyone else. Everyone's a participant.

A few honest things, upfront

·        Regression is expected. Backsliding isn't failure here — it's normal and part of the process. No one's tracking a perfect streak.

·        This takes real commitment, not a lot of willpower. Showing up weekly matters more than being impressive in any given week.

·        You don't need experience with self-development frameworks, journaling, or anything like that. You need honesty about where you are and a willingness to be seen mid-process, not just at the end.

If you're on the fence

That's completely fair — this is a real commitment, not a casual chat group. You're welcome to join the kickoff session as an observer first, hear how the group is thinking about it, and decide after that whether to commit to the 90-day cycle. No obligation either way.

Next step

Show your willingness to give yourself a chance to ‘continuously improve’ and join groups, in comments. We will create groups of individuals who know each other, want to help each other and make life more fulfilled, and get together to kickoff joint effort.

Two Hours: Twice

A young man I know spent two hours one evening lost in a side project — building something, fully absorbed, looking up startled when his phone buzzed because he'd forgotten it existed. The next evening, he spent two hours scrolling, and looked up just as startled — but this time, faintly worse than before he'd started. Same duration. Opposite aftertaste. He mentioned it to me almost as an aside, not realizing it was the more interesting part of his story.

I've lived both kinds of two hours myself, just with different tools — absorption in a piece of writing once, hollow distraction in idle television another time.

The feeling afterward is the tell: one kind of immersion leaves something behind; the other leaves only the time gone. Most people don't separate the two — both get filed simply as "I spent two hours on X."

What's missed is a real gap: not knowing how to recognize, on purpose, which conditions produce the first kind of two hours rather than the second. Left unexamined, the more depleting kind quietly becomes the default, because it requires no setup and gives an easy, low-grade hit regardless. 

Mihaly Csikszentmihalyi spent much of his research career on exactly this distinction popularized in his foundational text, Flow: The Psychology of Optimal Experience.  Optimal experience, is the scientific term for what we colloquially call being "in the zone" or achieving flow. 

Flow depends on clear goals, a fitting challenge, and real feedback as you go; its absence is what scrolling reliably offers instead.

Optimal experiences are the primary engine behind personal growth. When you choose to invest your limited psychic energy (attention) into a challenging task, you actively train your brain to be more orderly and resilient. Every time you emerge from an optimal experience, you become a more complex individual with increased skills, higher self-esteem, and a greater capacity for joy.

The tool worth trying: once a day, name in advance one block of time meant for something with a goal, a slight challenge, and a way to tell if you're getting better at it. Not the whole day — one block.

The young man I mentioned, may not have noticed the asymmetry himself yet. But the two hours that left something behind are the ones worth protecting.

If this resonates: Mihaly Csikszentmihalyi's Flow: The Psychology of Optimal Experience is the original, full account — dense in places, but the early chapters on the conditions for flow are very practical.

Length and Strength of Our Relations

❧

A note for the younger ones

❧

WHY I FEEL I CAN SAY THIS WITH SOME CERTAINTY

What I am about to share is not borrowed opinion or something I read once and found appealing. It comes from having lived long enough to watch relationships play out across decades — my own, and those of many others who have walked this road. We have seen relations begin, deepen, strain, break, mend, and in some cases quietly fade. When one lives long enough, patterns become visible that are invisible to someone in the middle of their twenties or thirties or for some even in their forties. That is the only authority I claim here — not expertise, but time served, and eyes kept open through it.

RELATIONS ARE GIVEN OR CHOSEN — BUT BOTH ARE MEANT TO BE KEPT

Some relations come to us by birth — parents, siblings, cousins. Others we choose — friends, spouses, the family we build around ourselves. The two are different in origin, but I would not want you to conclude that either can simply be let go. My own softer, and I believe truer, view is this: the strength of a relation may rise and fall over the years, but desire to maintain the same till last must not weaken.

With relations by birth, some distance or friction is only human. Not everyone in a family sees the world the same way, and not every bond will feel equally warm at every stage of life. That weakness can be understood — even expected — but it should never be promoted. We should not tell ourselves a story that makes it easier to walk away from a brother, a parent, a cousin. Blood did not ask our permission, and I don't believe we should ask its permission to end it either. Where warmth has faded, the door should still be left open.

With relations by choice, the standard I would hold everyone to is higher still. A friend, a spouse, a chosen family member entered our life because we let them in — nobody forced that door open. Precisely because it was our choosing, I believe it deserves to be maintained at almost any cost. It is easier to justify walking away from something we didn't choose than from something we did. So hold the relations we chose most carefully of all.

In both cases, the work is not a one-time declaration of love or loyalty; it is small, repeated acts of nurturing, nourishing, strengthening, and maintaining — the way a garden is tended, not once, but again and again, season after season. A relationship left alone does not stay the same. It does not merely pause — it quietly erodes, even if it never technically ends. This is true of a marriage, a friendship, and of the bond between a parent and a grown child, or between cousins who once shared a childhood and now share only a WhatsApp group.

WHAT EXPERIENCE TEACHES — AND WHAT RESEARCH CONFIRMS

Over the years, I — and I suspect most of us who have lived long — have been on every side of this. We have caused strain we didn't intend. We have absorbed strain we didn't deserve. We have faced situations that could have broken a relationship and somehow didn't; others where a small thing, left unattended, grew into a permanent distance. We have both damaged and repaired. We have both been forgiven and had to forgive.

It turns out this lived experience lines up closely with what relationship researchers have found. The psychologist John Gottman spent decades studying couples — watching how they argued, not just whether they argued — and could predict with striking accuracy which relationships would last and which would not. He found four behaviors that corrode a relationship over time if left unchecked: harsh criticism of the person rather than the issue, contempt (mockery, eye-rolling, superiority), defensiveness, and stonewalling — simply shutting down and withdrawing. He also found that the relationships that lasted weren't the ones without conflict — they were the ones where positive moments (affection, appreciation, humor, small kindnesses) outnumbered the negative ones by a wide margin, and where relatives kept a store of fondness and admiration they could draw on when times were hard.

What made the difference between people who fell into those corrosive patterns and people who didn't? Emotional intelligence — the capacity to notice what we are feeling, notice what the other person is feeling, and choose our response rather than simply react. This is the thread that connects a lifetime of family experience to serious research: the relationships that lasted were not the ones between people who never got hurt or never made mistakes. They were the ones between people who stayed emotionally aware enough to catch themselves, repair quickly, and keep choosing the relationship even in its harder seasons.

KNOWING OUR OWN PATTERN — AND STAYING WATCHFUL OF OTHERS'

There is another piece of this that took me years to understand, and that comes from what is called attachment theory. It suggests that very early in life — long before we have any memory of it — each of us develops a kind of template for how to be close to another person. Broadly, people tend to fall into one of a few patterns: some grow up secure, comfortable with both closeness and independence; some become anxious, craving closeness and fearing it will be taken away; some become avoidant, valuing independence to the point of keeping others at arm's length; and some become a mix of both — wanting closeness while distrusting it.

I share this not so we can diagnose ourself or anyone else, but so we stay watchful — of our own patterns, and of the patterns in people we love. If we notice we tend to pull away when someone gets close, or panic when someone goes quiet on us, that is worth knowing about our self — not as a flaw, but as a starting pattern we were handed, which we are free to work with and soften over time. The same goes for watching the people around us with compassion rather than judgment: a parent who struggles to say “I love you” may not lack love, only the template for expressing it easily. A sibling who withdraws during conflict may not be indifferent, only overwhelmed.

This is where emotional intelligence becomes the tool that lets us work with whatever pattern we were given rather than be ruled by it. Awareness of our own pattern, and gentleness toward others', is what allows old wounds to be mended and new closeness to be built — no matter what template either of us started with.

HOW TO ACTUALLY BUILD EMOTIONAL INTELLIGENCE — BECAUSE IT CAN BE BUILT

Here is the most hopeful part of everything I have shared: none of this is fixed. The research on this is consistent — emotional intelligence is trainable at any age, not just something you either have or don't. It grows the way a muscle does — through repetition, not through reading about it once. A few ways that genuinely help:

❧    Reflect after emotional moments, not just during them. A few minutes of honest review — what did I feel, what did they feel, what did I actually do — builds self-awareness faster than trying to be aware in the heat of the moment.

❧    Practice receptive listening. Let the other person finish. Reflect back what you heard before responding. This single habit resolves more conflict than any clever argument.

❧    Watch and learn from others' emotional stories — in books, in conversation, in family history like this one. Empathy grows by witnessing, not just by instruction.

❧    Rehearse the hard conversations, even in your head, before you have them. Real practice, even imagined, builds the skill.

❧    Keep at it over months, not days. A weekend of good intentions rarely changes a pattern. Small, repeated practice does.

I want you to understand what is at stake in this, beyond any single relationship. A life well-tended in its relations is, in my experience, a fulfilled life — regardless of what else it contains. Wealth, achievement, and recognition fade in importance as the years go on; the people who stayed close to us, and the people we stayed close to, do not. If there is one skill I would want you to carry from this note, it is this: notice your feelings, notice theirs, and let that noticing guide what you do next. Everything else in a relationship — its length, its strength, its capacity to survive hard seasons — tends to follow from that one habit, practiced patiently, for a lifetime.

❧

The Comment I Skipped Past

A young colleague once showed me a piece of feedback she'd received — specific, useful, slightly uncomfortable to read. She'd skimmed it once, said "noted," and moved on to the next task within a minute. I asked her, gently, what she planned to do with it. She didn't have an answer. I have done the same — skimmed past a sharp comment because the praise three lines above it felt nicer to sit with.

The feeling, in both cases, is a small flinch — barely noticeable, gone in seconds, filed away as "feedback received."

What the flinch reveals is a quiet avoidance: a preference for feedback that is comfortable over feedback that is useful. Left unexamined, this gap doesn't just slow skill-building — it trains a person to seek comfort and call it confirmation, while the actual gap in their skill stays exactly where it was.

The tool worth naming comes from Anders Ericsson's research on deliberate practice: feedback only builds skill when it is specific and immediate — not "good job," but "this exact thing, this exact moment." The practice is to ask for that kind of feedback on purpose, once a week, on one piece of work, and to sit with it for longer than the minute it takes to feel the flinch.

My colleague, I later learned, went back and reread that comment properly. I don't know if it changed anything yet. But I suspect rereading it was the actual beginning.

If this resonates: Anders Ericsson's Peak lays out the deliberate practice research in accessible terms — the chapters on feedback specifically are worth the read.

Developmental Openness: The Meta-Competency Behind Continuous Improvement

"Nobody improves by defending what they already know."

Consulting is a profession built on learning. Every assignment, every client interaction, every proposal, every presentation, and every difficult conversation presents an opportunity to learn something new. Yet learning does not occur simply because experiences accumulate. It occurs only when we are willing to examine our assumptions, accept feedback, challenge our own thinking, and consciously adapt.

This capability may be called Developmental Openness—the willingness and ability to seek, receive, evaluate, and act upon ideas, observations, feedback, evidence, and experiences that can improve one's effectiveness, even when they challenge existing beliefs or habits.

Unlike technical expertise or domain knowledge, Developmental Openness is a meta-competency. It enables the development of every other competency.

Why it matters in consulting

Professional service firms do not manufacture products; they create value through knowledge, judgment, collaboration, and client relationships. Consequently, the quality of consulting depends not only on what consultants know today, but on how effectively they continue learning everyday.

Consultants who remain developmentally open are more likely to:

• learn faster from assignments;
• improve client relationships;
• collaborate effectively across teams;
• innovate and solve complex problems;
• adapt to changing client expectations;
• become trusted advisors rather than merely subject matter experts.

Organizations that cultivate this capability develop stronger institutional knowledge and improve continuously.

What research consistently tells us

Research from organizational psychology and management has produced remarkably consistent findings.

·        People generally believe they are more receptive to feedback than others perceive them to be.

·        As responsibility and authority increase, candid feedback often decreases—not because leaders no longer need it, but because fewer people are willing to provide it.

·        High-performing organizations are distinguished not by the absence of mistakes but by their ability to learn from them quickly.

·        Teams perform better when members feel psychologically safe to question assumptions, express concerns, and respectfully disagree.

·        Learning-oriented individuals consistently outperform those whose primary concern is protecting their image or appearing competent.

These findings have been replicated across industries, including consulting, engineering, healthcare, technology, and other knowledge-intensive organizations.

Our blind spots

Ironically, consultants are especially susceptible to several developmental blind spots.

·        Experience becomes certainty. Years of successful practice can unconsciously reduce curiosity.

·        Expert identity. Being recognised as an expert may make it uncomfortable to acknowledge gaps or seek help.

·        Defending instead of discovering. Feedback is sometimes interpreted as criticism rather than an opportunity to improve.

·        Time pressure. Delivery deadlines leave little time for reflection and learning.

·        Confirmation bias. We naturally notice information that supports our existing views while overlooking contradictory evidence.

·        Hierarchical silence. Junior colleagues may hesitate to challenge senior professionals, depriving the organization of valuable perspectives.

These are human tendencies, not individual weaknesses. Awareness is the first step toward overcoming them.

Continuous improvement requires more than good intentions

Most organizations genuinely encourage learning. However, there is a significant difference between expressing support for development and creating conditions that make development inevitable.

Wishful thinking sounds like:

• "Please be open to feedback."
• "Learning is everyone's responsibility."
• "Keep improving."

A developmental ecosystem asks:

• How is meaningful feedback obtained?
• How frequently do people reflect on their work?
• Are mistakes analysed without blame?
• Do managers coach or merely evaluate?
• Are improvements documented and shared?
• Is experimentation encouraged?
• Is learning recognised and rewarded?

Without such systems, continuous improvement remains an aspiration rather than an organisational capability.

Building a developmental ecosystem

An effective consulting organization deliberately creates mechanisms that make learning part of everyday work.

These include:

• regular developmental conversations;
• structured peer reviews;
• client feedback beyond project closure;
• after-action reviews following important assignments;
• mentoring and reverse mentoring;
• reflective learning journals;
• communities of practice;
• knowledge sharing sessions;
• coaching by managers;
• individual development plans linked to observed behaviours.

Development then becomes part of the way work is performed—not an activity separate from work.

A personal commitment

Each of us can ask ourselves:

• When was the last time I actively sought critical feedback?
• What belief have I changed during the past year?
• Whose perspectives do I routinely ignore?
• What recurring feedback have I not acted upon?
• How often do I help others learn from my own mistakes?

Our answers may reveal more about our future potential than our current expertise.

Closing thought

Knowledge creates competence.

Experience creates wisdom only when accompanied by reflection.

Feedback creates improvement only when accompanied by openness.

Developmental Openness is therefore not simply another competency. It is the foundation upon which all continuous improvement, professional excellence, and consulting effectiveness are built.

In consulting, the most valuable professionals are not those who know everything. They are those who never stop learning.

Equation is simple:

Continuous Improvement = Developmental Openness × Deliberate Practice × Reflection × Feedback × Application

As Developmental Openness tends to zero, Improvement stops.

Every Role Asks Something Different of Us

Imagine meeting the same person in four different situations.

In one, they are comforting a worried child.

In another, they are leading an important meeting.

Later, they are caring for an elderly parent.

Finally, they are helping neighbours during a community emergency.

Would you expect exactly the same behaviour in every situation?

Probably not.

The person is the same, but the role is different. And every role asks something different of them.

We All Wear Many Hats

Life is like a stage on which each of us performs many roles.

Some roles come to us by birth. Others come through choice, education, work, relationships or experience.

At different times in our lives, we may be:

• a child
• a student
• a friend
• a spouse
• a parent
• a grandparent
• a colleague
• a professional
• a manager
• a leader
• a mentor
• a citizen.

Each of these roles carries responsibilities.

And every responsibility quietly asks,

"Are you ready?"

Success Means Different Things in Different Roles

Think for a moment.

What makes someone a good parent?

·        Patience.

·        Love.

·        Listening.

·        Guidance.

Now think about a good project manager.

·        Planning.

·        Decision making.

·        Communication.

·        Organisation.

Now think about a trusted friend.

·        Empathy.

·        Honesty.

·        Reliability.

·        Presence.

Notice something interesting.

The definition of success changes with the role.

No single quality is enough for every situation.

Instead, every role calls upon a different combination of competencies.

Competencies Are Not Random

Sometimes at work people believe competencies are simply long lists created by HR departments or management experts.

While at home, in family, community ‘competencies’ are hardly talked about. Individuals are evaluated in terms of success as defined by others.

In reality, competencies arise from life itself. Whenever life gives us a new responsibility, it quietly asks us to grow.

When we become students, we learn how to study.

When we begin working, we learn how to contribute.

When we supervise others, we learn how to guide.

When we become parents, we learn patience in new ways.

When we become leaders, we learn to think beyond ourselves.

Life itself is the greatest teacher.

Competencies simply describe the capabilities that life asks us to develop along the journey.

Growth Is Not About Becoming Someone Else

Many people worry that self-development means changing who they are.

It does not.

The purpose of development is not to replace your personality.

It is to strengthen your ability to fulfil the responsibilities that matter to you.

A thoughtful person can become a better communicator.

A quiet person can become an excellent leader.

An energetic person can become more disciplined.

We remain ourselves while becoming better versions of ourselves.

Why Organising Competencies Helps

If every role asks for different competencies, one question naturally follows.

How do we make sense of so many competencies?

Should we simply memorise long lists?

Or is there a better way?

Just as a library arranges books into meaningful sections, competencies too can be organised into groups.

Some help us manage ourselves.

Some help us work effectively.

Some help us build relationships.

Some help us lead people.

Others help us perform specialised professional work.

Organising competencies does not make life more complicated.

It makes learning simpler.

Instead of wondering "Where do I begin", we begin to see a clear path.

A quite Conversation With Yourself

I suggest spend a few quiet moments thinking about these questions:

• Which roles are most important in my life today?
• Which new roles am I likely to take on in the next five to ten years?
• Which role do I find most challenging?
• What qualities do I think that role is asking me to develop?

There are no right or wrong answers.

The purpose of these questions is not to judge yourself, but to become more aware of the journey ahead.

The Building Blocks of a Good Life

I was delighted to receive a call from a younger one. He had read my post “Continuous Development – A Development Journey”. He pointed out that I had started with often repeated advices “develop yourself”, “build Competencies”, and “improve your skills”. He was being inquisitive and asked more clarity on “competencies”. He said knowledge, skills, abilities are familiar concepts. Where does competency fit in the development process? I thought it will help me clarify my own concepts. I dived deeper to find answers to the younger one’s questions and could arrive at the brief that follows.

Opening Reflection

Think of someone you genuinely admire.

It could be a parent, a teacher, a colleague, a leader, or even a friend.

What is it about that person that earns your respect?

Is it merely their intelligence? Their qualifications? Their wealth? Or is it something deeper—the way they think, the way they treat people, the way they keep their word, the way they respond to difficulties?

We admire people not only for what they know, but for who they have become.

What Makes a Person Effective?

Every day we play different roles.

At home we may be a son or daughter, a sibling, a spouse, a parent or a grandparent.

At work we may be a learner, a team member, a professional, a manager or a leader.

Beyond our homes and workplaces, we are neighbours, friends and members of society.

Each of these roles comes with responsibilities. Some responsibilities are simple; others are demanding. Yet one thing is common to them all.

To fulfil any responsibility well, we need certain qualities, abilities and habits.

These are called competencies.

What Is a Competency?

A competency is the ability to perform a responsibility effectively and consistently.

It is not just knowledge.

It is not merely a skill.

It is not simply a personality trait.

Rather, it is a combination of what we know, what we can do, how we think, what we value and how we behave.

For example, good communication is a competency. It requires listening with attention, expressing ideas clearly, respecting others and choosing appropriate words. Knowing the rules of communication alone does not make someone a good communicator. The competency is demonstrated through consistent behaviour.

Likewise, integrity is a competency. It is reflected not in what we claim to believe but in the choices we make when no one is watching.

Competencies are therefore visible through our actions.

The Good News

Many people believe that successful people are simply born different.

Experience suggests otherwise.

Most competencies are learned, practised and strengthened over time.

Just as our muscles become stronger through regular exercise, competencies become stronger through repeated practice, reflection and experience.

Every expert was once a beginner.

Every confident speaker once felt nervous.

Every respected leader once had to learn how to lead.

Growth is not reserved for a gifted few; it is available to anyone willing to learn.

A Journey, Not a Race

When people first hear the word "competency," they sometimes imagine a long list of qualities they must somehow master.

That is not the purpose.

Life itself teaches us what we need, one responsibility at a time.

As our responsibilities grow, new competencies become important.

A student needs competencies that help in learning.

A young professional needs competencies that help in building a career.

A manager needs competencies that help others succeed.

A parent needs competencies that strengthen a family.

The journey never really ends because life continues to present us with new opportunities and new responsibilities.

The goal is not perfection.

The goal is steady growth.

Becoming a little more capable today than we were yesterday is enough.

A Thought to Carry Forward

Every responsibility in life asks something of us.

Competencies are the qualities that enable us to fulfil those responsibilities with confidence, effectiveness and integrity.

The more we develop these qualities, the better prepared we become—not only for success, but also for service, relationships and a meaningful life.

Reflection

It will help if you pause for a few moments and ask yourself:

• Which roles in my life matter most to me today?
• What qualities do I admire most in people who perform those roles well?
• Which of those qualities would I like to strengthen in myself?

You do not need all the answers today.

The willingness to ask these questions is the first step in the journey of growth.

Continuous Development - A Development Journey

Today while looking at documents related to an exercise undertaken by colleagues, I wondered how often do younger ones hear advice like "develop yourself," "build competencies," "improve your skills" from elders at home and bosses at work and how would younger ones be reacting? My conclusion based on objective observations over last 60 years is that such advises repeated over time become background noise.

I consider it is necessary we understand the topic objectively in detail for our selfish interests.  

What are they really saying?

Imagine that your career is like growing a tree.

• Your knowledge is the roots.
• Your skills are the trunk and branches.
• Your attitude and character are the strength of the wood.
• Your results are the fruits.

People who have lived longer or worked longer have seen that those who keep strengthening these parts continue to grow, and those who stop growing often get left behind.

So, when an elder says, "Develop yourself," they are usually saying:

"Invest in yourself today so that tomorrow brings you more opportunities, confidence, and freedom."

Why should young people listen?

Not because elders are always right. They are not.

But because they have usually seen patterns repeat over many years.

For example, they have seen people who:

• kept learning and became leaders,
• communicated well and built strong relationships,
• managed money wisely and enjoyed greater security,
• ignored feedback and remained stuck, despite talent.

Experience cannot predict everything, but it often recognizes patterns before younger people can.

How can a young person know whether they need to improve?

A simple test is to ask:

1. Am I learning something new every few months?
2. Have I been able to impress people so they can rely on me?
3. Do I complete what I promise?
4. Do I receive the same feedback repeatedly?
5. Am I more capable today than I was a year ago?
6. If I lost my job tomorrow, would someone else gladly hire me?

If the answer to several of these is "No," then growth deserves attention.

Which areas matter most?

Almost every successful person keeps improving in these areas:

1. Character – honesty, responsibility, discipline.
2. Learning – acquiring new knowledge and skills.
3. Communication – listening, speaking, writing clearly.
4. Relationships – working well with others.
5. Problem solving – finding solutions instead of only identifying problems.
6. Self-management – managing time, emotions, health, and money.
7. Professional excellence – becoming really good at one's chosen work.

How much effort is enough?

You do not have to become perfect.

Just ask yourself:

"Am I becoming a little better every month?"

Small, steady improvements over several years create extraordinary results.

A thought worth remembering

A young person's greatest asset is time. An elder's greatest asset is experience.

When the energy of youth combines with the wisdom of experience, growth becomes much faster than either alone.

One saying captures this well:

"Your future is shaped less by what you know today and more by your willingness to keep learning tomorrow."

That is why thoughtful elders and good managers encourage development—not to criticize young people, but because they want them to build a life with greater capability, opportunity, and resilience.

And if you need help, I am here to help you design your development journey.

Family Discovery: Naming a Practice We Rarely Name

I had finished my morning round of calls with people in office back home and was waiting for call from young developer. There were messages, delayed responses to a forward written covering compilation of notes shared with members of extended ‘family’. And that was the trigger. Question that arose was ‘have presumed that each one of us has same definition of ‘family’?’ One question led to the other and responses collected results in to notes which I am sharing in installments, hoping you will read, form your views and share.

There’s a strange gap in how we talk about families. We have family therapy for when something is broken. We have family history for when we look backward. We have team-building for workplaces, borrowed wholesale from the language of productivity. But we don’t have a common word for the ongoing, unforced practice of a family simply understanding itself — not fixing anything, not archiving anything, just knowing who its members actually are, right now, in their own words.

I’ve started calling this practice family discovery. It is easier for me to say what is is not that to precisely say what it is.

What it isn’t

It isn’t therapy — you don’t need a problem to justify it. It isn’t genealogy — it’s not about the past for its own sake. And it isn’t a bonding exercise borrowed from a corporate offsite — it doesn’t need games or forced positivity. Family discovery is closer to something researchers call narrative identity — the idea, from psychologist Dan McAdams, that people (and by extension, families) become coherent to themselves by telling and hearing their own stories. Most families never do this deliberately. They accumulate shared history by accident, through proximity, and assume that living near each other is the same as knowing each other. It usually isn’t.

Why it matters more now, not less

Three quiet shifts make this harder than it used to be, and more necessary:

Geographic dispersion. Extended families used to share physical space by default — meals, porches, Sunday visits did the work of “discovery” without anyone naming it. That default is gone for most families now.

Generational stake. Sociologist Vern Bengtson’s long-running family studies found something counterintuitive: parents consistently overestimate how close and aligned they are with their children, while children underestimate it. Each generation has its own emotional incentive to believe a particular story about the family — which means nobody’s unprompted account of “how close we are” is fully reliable. You have to actually ask, and ask separately.

Family as construct, not consensus. Family therapist David Reiss proposed that every individual carries their own implicit “family paradigm” — an internal model of who belongs, what the family is for, what it owes its members. These paradigms are rarely identical inside the same family, and almost never spoken aloud. Two siblings can grow up in the same house holding quietly different definitions of what “family” even means.

Put together: closeness is often assumed rather than verified, and the assumption is usually wrong in both directions.

What it draws on

I don’t think family discovery needs to be invented from nothing — it’s closer to a synthesis of practices that already have real track records, even though nobody has bundled them under one name.

Family discovery borrows from all four: the listening posture of StoryCorps, the oral history project, the legacy intent of ethical wills, a centuries-old Jewish tradition, the ritual structure Gottman found effective, and the narrative coherence goal from family systems work — applied not after a crisis, and not only to elders, but as an ordinary, ongoing practice across every generation in the family.

What it actually looks like, in practice

Not a single deep conversation. Not a survey. Closer to:

•             One-on-one conversations, not group discussions — because people tell the truth differently when they’re not performing for an audience.

•             Questions that ask for stories, not opinions — “tell me about a time…” surfaces more real information than “do you feel close to the family?”

•             Letting each person define “family” in their own terms first, before assuming a shared definition exists.

•             Small, repeatable rituals rather than one grand gesture — a habit, not an event.

•             Treating what’s said as data to understand, not a problem to immediately solve.

An honest caveat

I want to be careful not to oversell this. “Family discovery” isn’t a proven field with a stack of longitudinal studies behind the name — I’m the one trying to give it a name, borrowing credibility from traditions that do have real evidence behind them. What I can say is that each of the underlying pieces — narrative identity, generational perception gaps, family paradigms, ritual over intensity — has decades of research behind it independently. Whether stitching them together into a single deliberate practice works as well as I suspect is something I intend to actually test, starting with my own family, before I claim more than that.

The next post in this series will get concrete: the actual practices — how to run a discovery conversation, a glossary for telling a real problem apart from a values statement or a wish, and the small rituals that seem to matter more than people expect.

---

This is Post 1 in a series on family discovery — a practice, not (yet) a proven field. Written as part of an ongoing habit of sharing what I find and think worth testing.

Peacock Feathers & Life

"જીવન જીવવું હોય તો મોરપીંછ થાવ" (Live life like a peacock feather), a very well known Gujarati thought leader called out his NRI audience. Obviously those starved of earthy Gujarati with Kathiawadi accent, were impressed. 

I wondered how did the speaker used 'peacock feathers' to describe life well lived. Topic worth exploring, I thought. My search revealed highly philosophical explanation, I consider it worth sharing. Do we all not want to live such colourful life???

That is a beautiful metaphor. A peacock feather is not just colorful—it is harmonious. Every color has its place, and together they create something striking. A colorful life is not necessarily a life of constant excitement or luxury. It is a life rich in experiences, relationships, growth, and meaning.

One way to think about it is as a life with many "colors":

• ❤️ Red – Love: Deep relationships with family, friends, and community.
• 🟠 Orange – Joy: Laughter, playfulness, celebrations, music, and humor.
• 🟡 Yellow – Curiosity: Lifelong learning, reading, traveling, exploring new ideas.
• 🟢 Green – Growth: Developing skills, overcoming challenges, and becoming wiser.
• 🔵 Blue – Peace: Quiet reflection, prayer, meditation, time in nature, inner calm.
• 🟣 Purple – Purpose: Serving others, mentoring, leaving a positive legacy.
• ⚪ White – Integrity: Living according to one's values with honesty and compassion.

A peacock feather also has an "eye" at its center. Symbolically, this can represent self-awareness—seeing yourself clearly and remaining conscious of what truly matters. The colors radiate outward from that center. Similarly, a meaningful life radiates outward from self-awareness.

A colorful life, may not mean adding more activities; it may mean ensuring that each important dimension receives its own time and attention.

You might periodically ask yourself:

1. Have I learned something new recently?
2. Have I strengthened an important relationship?
3. Have I created something of value?
4. Have I helped someone without expecting anything in return?
5. Have I cared for my health?
6. Have I experienced beauty—in art, music, nature, or literature?
7. Have I spent time in silence, gratitude, or prayer?

If you can answer "yes" to most of these over time, your life is becoming more colorful.

Perhaps the deepest interpretation is this:

A colorful life is not a life with many possessions, but a life with many dimensions—where love, learning, work, service, beauty, adventure, wisdom, and spirituality coexist in balance. Like a peacock feather, every color enriches the others, and together they create a life of grace and meaning.

Ten Beginnings

A young relative once showed me his phone — three language apps, two fitness trackers, a half-finished coding course, and a meditation app he'd opened twice. He laughed about it, called himself "easily distracted." I didn't laugh. I recognized it too well — I over a period of time in my youth, started on courses including ICWA, CS, Law, each begun with great resolve, each abandoned by the third month, for reasons that felt different each time but were, in fact, the same.

The feeling in both cases is a small thrill at the start — the pleasure of something new — followed by a quieter restlessness once the novelty fades. That restlessness usually gets blamed on the activity itself ("turns out I don't like Company Law after all") and dismissed.

What it actually reveals is a gap between appetite and discipline. Starting is not a skill many people lack; finishing is. Left unexamined, this gap doesn't just produce a phone full of unused apps — it teaches a person, repeatedly, that they cannot follow through, which becomes a belief long before it becomes a pattern worth questioning.

The tool worth naming: time-boxing. Pick one thing, commit to a fixed, short window — two weeks, not "indefinitely" — and at the end, make an actual decision: deepen or drop. The boundary itself removes the guilt of stopping and the vagueness of "someday."

My young relative still has three language apps open. I suspect, like most of us, he hasn't yet drawn the boundary that would turn restlessness into a decision.

 

Next: the feedback we ask for, then quietly resent.

If this resonates: Cal Newport's writing on "deep work" touches this gap well — the difference between sampling and committing. Worth a search if the book itself feels long.

The Feed

I sat near a young man at a coffee shop who put his phone down after a few minutes of scrolling and exhaled — not loudly, just enough that I noticed. Nothing had happened to him. No message, no event. Just images of other people's days.

I recognized that exhale. I felt its older cousin once myself, decades ago, reading a college reunion newsletter full of other people's achievements, and closing it feeling smaller than when I'd opened it.

The feeling is a soft, specific kind of deflation — not envy exactly, more a sense of quietly falling behind. It usually passes in minutes, dismissed as nothing, not worth a second look.

But underneath it is a real gap: not knowing how to measure one's own progress except by holding it up against someone else's. Left unexamined, this gap doesn't just create bad moments — it can quietly erode the ability to recognize one's own progress at all. Leon Festinger named this tendency social comparison seventy years ago; Dan Sullivan and Benjamin Hardy gave it a sharper edge more recently with their distinction between measuring against "the Gap" — an ideal, or someone else's curated highlight — and measuring against "the Gain" — who we were a week or a month ago.

The tool worth trying: once a day, before reaching for the feed, ask one question instead — what is one inch closer than where I was last week? It is a small redirection, but it returns the measuring stick to a hand that can actually use it.

The young man at the coffee shop closed his phone and looked out the window for a while. I don't know what he was thinking. But I suspect, like most of us, he didn't know there was a gap to look for in the first place.

Next: noticing these moments is one thing — staying with them long enough to learn something is another.

If this resonates: Look up Leon Festinger's original social comparison theory (1954) for the foundation, or for the modern, practical version, Dan Sullivan and Benjamin Hardy's The Gap and the Gain is a quick, useful read.

Visible Infrastructure - Invisible Institutions

It has been a month and a half we arrived here at Atlanta. Yesterday we traveled by road to Cincinnati. Starting from Georgia we passed through Tennessee, Kentucky, and entered Ohio. I have been to other states in past including Illinois, California, Washington, New York etc. observing the country side and wondering how unjust nature can be.

I was looking out of the hotel window. It had rained in the night but there were no puddles. Grass on the curbs was green. Mulch around the shrub appeared darker. I looked at the Mercedes show room and neatly parked cars. The college building appeared like it was built yesterday. Sharp edges where walls meet looked perfectly at right angle.

I have observed and noted in fair details Layouts, Building construction, Roads, Signage, Traffic, Landscaping, Horticulture, Shopping centres, Public schools, Community centers, Public parks and Libraries. I find from planning to engineering to development to maintenance and upkeep of these basic civic facilities, the entire country follows same pattern. I was wondering what must be root causes? Is that Society and their culture, Government, Laws, Enforcement? Are there studies to conclude? And I found what follows. Interesting details, if you have felt needs for such details read on….

Despite its size, the U.S. often feels remarkably consistent in its physical infrastructure. The reasons are deeper than architecture—they reflect history, institutions, economics, and culture working together.

Broadly, scholars point to several root causes.

1.      A strong rule-of-law culture

The U.S. is a federation, and states have considerable autonomy. Yet all states operate within a common constitutional and legal framework established by . Building codes, engineering standards, traffic control manuals, environmental regulations, and safety requirements are enforced consistently. This creates a common "language" for infrastructure.

2.      National engineering standards

Roads and highways are built using nationally accepted standards. A stop sign in Georgia looks the same as one in Ohio. Highway exits, lane markings, guardrails, bridge design, and traffic signals follow common manuals and specifications. Engineers across the country are educated using similar standards.

3.      Professional institutions

Much of this uniformity comes from professional organizations rather than politicians. Civil engineers, architects, urban planners, transportation experts, and landscape architects use nationally accepted best practices. Regardless of whether a project is in California or Kentucky, similar professional standards apply.

4.      Economic incentives

Uniformity reduces costs. If every state required different road signs, traffic lights, or construction materials, manufacturers would have to produce many variants. Standardization lowers manufacturing, maintenance, and training costs.

5.      Long-term planning

Infrastructure is planned for decades rather than election cycles alone. Highways, airports, water systems, and utilities are maintained through long-term capital improvement plans. Political leadership changes, but engineering departments continue implementing those plans.

6.      Culture of maintenance

Americans generally expect public infrastructure to be functional, predictable, and safe. Maintenance budgets, inspections, and accountability are integral parts of infrastructure management, even though quality still varies by region.

7.      Federal funding with state execution

Many highways and infrastructure projects are funded wholly or partly by the federal government but implemented by state departments of transportation. To receive funding, states often comply with national standards, which promotes consistency.

Is this primarily culture, government, or law?

It is all of them, operating together:

• Culture values order, predictability, safety, and compliance.
• Government establishes policies and provides funding.
• Law mandates minimum standards.
• Professional institutions define technical standards.
• Citizens generally expect and support consistent public services.

Each reinforces the others.

Have researchers studied this?

Several academic fields examine exactly these questions:

• Urban planning studies how cities and infrastructure are designed.
• Public administration examines how governments implement policies effectively.
• Civil engineering develops technical standards for infrastructure.
• Institutional economics explores how institutions and rules shape economic and social outcomes.
• Political science analyzes federalism, governance, and public policy.
• Sociology studies how cultural norms influence behavior and public life.

A recurring conclusion is that strong institutions matter more than individual leaders. Countries with durable institutions—clear rules, professional civil services, independent courts, and accountability—tend to produce more consistent public infrastructure over time.

You might appreciate an even broader way to view it:

A nation's visible infrastructure is the physical expression of its invisible institutions.

Roads, buildings, parks, signage, and utilities are not merely engineering achievements. They reflect a society's values, the effectiveness of its institutions, the professionalism of its workforce, and the trust that citizens place in shared rules.

That perspective is useful when comparing countries.

Here is a broader framework we can use whenever we visit a country.

1. Physical Environment (What we first noticed)

• Roads, bridges, airports
• Public buildings
• Residential layouts
• Parks and landscaping
• Utilities (electricity, water, internet)
• Signage and accessibility
• Waste management

Underlying causes

• Engineering standards
• Long-term public investment
• Maintenance culture
• Urban planning
• Stable institutions

2. Civic Behaviour

As we travel, we may notice:

• People queue patiently.
• Drivers generally stop at crosswalks.
• Public places are relatively orderly.
• Littering is less common.
• People respect personal space.
• Appointments are taken seriously.

Underlying causes

• Early childhood socialization
• School education
• Consistent law enforcement
• Social expectations
• High trust that others will also follow rules

3. Institutional Strength

Most visitors don't notice institutions because they are "invisible."

Examples include:

• Property registration
• Courts
• Police
• Fire departments
• Emergency medical services
• Public libraries
• Public schools
• Postal services

Their strength comes from:

• Professional management
• Stable procedures
• Documentation
• Accountability
• Independence from individuals

This is why systems continue functioning even when elected leaders change.

4. Economic Organization

Notice how businesses operate similarly across states.

Examples:

• Chain stores
• Fuel stations
• Hotels
• Banks
• Restaurants

Reasons:

• National regulations
• Consumer expectations
• Standard operating procedures
• Efficient supply chains
• Franchising

5. Work Culture

We may observe:

• Meetings begin on time.
• Emails receive responses.
• Processes are documented.
• Roles are clearly defined.
• Safety procedures are followed.

Underlying reasons:

• Professional education
• Performance measurement
• Legal liability
• Organizational culture

6. Community Life

Beyond government, communities contribute significantly.

Examples:

• Volunteer organizations
• Parent-teacher associations
• Faith communities
• Sports clubs
• Neighborhood associations

These organizations solve local problems without waiting for government.

7. Family Structure

Compared with many countries:

• Children become independent earlier.
• Elderly often live independently.
• Privacy is highly valued.
• Individual choice receives significant respect.

This has advantages and trade-offs, including greater autonomy but sometimes more social isolation.

8. Education

Schools emphasize:

• Problem solving
• Team projects
• Questioning teachers
• Research
• Practical application

Higher education is closely linked with innovation and industry.

9. Innovation

We may notice constant technological change.

Reasons include:

• Strong universities
• Venture capital
• Entrepreneurship
• Acceptance of failure
• Intellectual property protection

10. Diversity

Traveling from Georgia to Ohio, we encountered people from many ethnic, cultural, and religious backgrounds.

What unifies them is less a shared ancestry than a shared commitment to civic rules, institutions, and participation in public life.

11. Information Systems

Much of society functions because information is standardized.

Examples:

• Addresses
• ZIP codes
• Driver's licenses
• Emergency number 911
• Banking systems
• Credit history
• Digital records

These reduce friction and make services work consistently.

12. Culture and Values

Many observers identify several recurring values that influence everyday life:

• Respect for law
• Individual responsibility
• Initiative
• Volunteerism
• Community participation
• Professionalism
• Time consciousness
• Reliability

People do not always live up to these ideals, but they remain influential norms.

A Sociologist's View

One helpful way to think about a society is as a set of interconnected layers:

Layer	Question
Values	What do people believe is important?
Norms	How are people expected to behave?
Institutions	How are those expectations organized?
Laws	What is legally required?
Organizations	Who implements the laws and norms?
Infrastructure	What physical systems support society?
Daily Life	What do people actually experience?

The visible world—roads, buildings, parks, traffic—is the final output of all the layers above it.

In many ways, the quality of a nation's public life is the cumulative result of millions of ordinary people reliably doing ordinary things—following rules, maintaining standards, honoring commitments, and trusting institutions—day after day, across generations.

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.