Friday, September 11, 2026

The Weight of Being Reliable


I am not a mother. I have been reminded of this often enough, particularly when I have ventured an opinion about motherhood.

The reminder is not entirely unfair. There are dimensions of being a mother that I cannot claim to know. But I have been a daughter, sister, sister-in-law and aunt. I have watched the mothers closest to me love their children fiercely, take pride in raising them—and still become exhausted by everything they believe that choice requires them to carry.

In the past week, I watched two mothers struggle with two very different teenage daughters.

One daughter protects herself through silence. Conversations about her future are difficult. Her mother finally burst into tears. After seventeen years, she felt she had failed to create a relationship in which her daughter could talk to her.

The other daughter responds through anger, screaming and exhausting tantrums. Her mother is bringing her up largely alone because circumstances have required it. She, too, is tired—not of her daughter, but of the relentless emotional energy motherhood demands.

One daughter withdraws. The other erupts. Yet both mothers arrive at the same question: Where did I fail?

A mother is responsible for providing love, safety, guidance, boundaries and the possibility of conversation. But can she also be responsible for whether her child chooses to speak, how the child expresses anger, or what kind of person the child eventually becomes?

There are responsibilities attached to motherhood. Omnipotence cannot be one of them.

None of these women regrets motherhood. On the contrary, they take pride in it. The conflict is between motherhood and individuality—between the role they cherish and the person who must somehow keep existing within it.

Perhaps that is why exhaustion comes with guilt.

If I chose this, what right do I have to complain about its consequences?

But a choice is not a lifelong contract with every consequence that follows.

I wonder whether women carry this understanding of responsibility into the workplace.

I think many of us do.

The setting changes. Family relationships acquire corporate titles. The consequences appear in reports and spreadsheets. But the internal equation remains remarkably similar:

If something matters, I must protect it.

If someone depends upon me, I must not fail them.

If the system is inadequate, I must compensate.

Consider a senior woman who has spent decades building a business. She has established teams, entered new markets and grown into a global leadership role. Yet she continues without enough capable people beneath her. Attrition remains high. Knowledge sits with individuals rather than systems. Whenever someone leaves, she moves closer to the work to protect continuity.

Every time she rescues the system, she postpones the moment when the system must learn to function without her.

She becomes the bridge across every gap. Because the bridge still holds, nobody feels enough urgency to repair the road.

This is how we miss the forest for the trees.

The trees are urgent: the employee who may resign, the client who needs an answer NOW, the deadline that cannot move and the work that is not good enough.

The forest asks quieter questions. Why is the organisation dependent on one person? Why have successors not been developed? What is the organisation avoiding because she continues to compensate for it?

There is also the forest within her.

Who am I apart from the roles I perform? Am I still choosing this, or am I simply continuing it? What am I preserving by carrying everything—and what am I losing?

Many women have built their careers believing that they must work twice as hard for half the gain. Once a reputation for competence has been earned, it becomes something to protect.

An ordinary failure no longer feels ordinary. A man’s failure may be read as a failed decision. A woman often fears that hers will be read as evidence that appointing her was the failed decision.

And so she intervenes again. When the outcome is successful, the belief is reinforced:

It succeeded because I carried it. At one point, that sentence felt like proof of my strength; now it sounds like an account of everything that strength has cost me.

Organisations often benefit from this. They praise commitment and delay providing resources because the woman somehow keeps delivering.

Her reliability becomes the business model.

Having lived five decades without becoming a mother, I do not want to stand only beside the mothers. I want to stand in the same corner as my nieces and, together, look at the women we call our mothers.

Not to judge them. Not to excuse everything they do. And not to ask teenage girls to become responsible for their mothers’ happiness.

Your mother is not only your mother. She was a person before you arrived, with fears, ambitions, disappointments and unfinished dreams.

As you ask her to see the person you are becoming, can you also become curious about the person she has always been? Accepting your silence does not mean approving of it. Accepting your anger does not mean permitting every way in which it is expressed. Similarly, accepting a daughter’s silence or anger need not mean approving of it—or accepting blame for it.

I have not admired every choice my mother made. I have hated some of them. I resented decisions I did not understand and certainly did not enjoy the occasional whack. Today, I can hold two truths together: I disliked what she did, and I understand more of the woman who did it.

Acceptance does not require approval. It requires us to stop putting our mothers, our younger selves, our work and our teams permanently on trial.

Reflection is valuable. Accountability is necessary. But an inquiry intended to help us learn can quietly become a prosecution intended to establish guilt.

“Things fall apart; the centre cannot hold,” wrote Yeats. It is the line from which Chinua Achebe drew the title of his novel. But many of us gradually convince ourselves to believe a different version:

Things fall apart. The centre must hold. And we must be that centre.

The mother must hold. The daughter must understand. The leader must compensate. The reliable woman must somehow prevent the family, the team, the business, the revenue, and the organisation from coming apart.

But what happens to the woman who makes herself the centre of everything? Who holds her while she is holding it all? But perhaps “Who will hold her?” is the wrong question. No one else is responsible for rescuing the woman who has made herself responsible for everything. That acceptance is critical.

Her task is not to find someone else to carry her while she continues carrying it all.  Perhaps maturity (perhaps even common sense) is not ensuring that nothing ever falls apart. It is recognising what is ours to hold, what others must learn to carry and what may need to fall apart before it can be built differently.

 

Thursday, May 28, 2026

The Saviour in Feminist Clothing

 https://www.youtube.com/watch?v=-vVHK97hJkA


There is a reel going viral. Eleven million views in under twenty-four hours, if the LinkedIn post announcing it is to be believed. The creator — earnest, articulate, and clearly skilled with AI tools — has made a thirty-second video in which she steps into iconic Bollywood scenes and pulls women away from their men. The mission, as she calls it: saving women from toxic men.

I watched it. I read her explanation. And I found myself with that particular feeling you get when something is clever enough to be convincing but not quite honest enough to be true.

Let me tell you what bothered me. Not in the way of outrage — I am not outraged. More like a quiet, persistent itch that refuses to be scratched away by eleven million approving thumbs.

The first problem: the films she is rescuing women from are not quite what she says they are.

The most iconic scene in the reel features DDLJ. Raj. Simran. The train. The outstretched hand. The moment when India collectively held its breath.

But here is what actually happens in that scene, if you remember it without the revision that nostalgia sometimes performs on memory. Simran's father — Bauji — turns to her and says: Ja Simran, ja. Jee le apni zindagi. He releases her. She runs. She reaches for Raj herself.

She is not dragged. She is not trapped. She chooses.

Now, one can absolutely have a conversation about whether the film's broader structure — where a father's permission is the pivot of a woman's freedom — is itself worth examining. That is a legitimate and interesting conversation. But that is a conversation about patriarchal family structure, not about Raj being a toxic man. Conflating the two is not analysis. It is a convenient simplification dressed as insight.

If your feminist reel interrupts a moment of female agency and replaces it with a rescue, you have not liberated anyone. You have just changed the rescuer's gender.

The second problem: the premise is built on a misreading, and the misreading is the product.

The creator is thoughtful enough to admit, in her own words, that she changed the narrative. She did not claim the films were secretly feminist all along. She said she reimagined them. That is an honest creative choice.

But the LinkedIn post then frames the eleven million views as evidence of deep emotional truth — as proof that women always knew, somewhere inside, that these relationships were wrong and that someone should have intervened. That is a very different claim. It moves from I made a fun AI edit to I tapped into a collective wound.

She makes two claims simultaneously. Claim one: I changed the narrative — an honest admission that the films did not originally carry an anti-toxic message. Claim two: eleven million women connected with this deeply — implying the reel struck something true and long-suppressed.

But these two claims cannot both be right. If she changed the narrative, the emotional resonance cannot be proof of pre-existing truth. You cannot rewrite a story and then cite the applause as evidence that the original story was always secretly yours.

And if Simran was free to run, if the nostalgia is for something more complicated than victimhood, then the reel did not tap into suppressed truth. It tapped into the far more available thing: flattery. It told women they were always smarter than the culture around them — that they saw through it even as they loved it. That is a beautiful thing to be told. It is also precisely what lets everyone off the hook. Real cultural critique leaves a small bruise. It asks you to reckon with what you accepted, not just celebrate that someone has finally arrived to save you from it.

The third problem — and this is the one that stayed with me longest — is that the rescuer in a feminist video is still a rescuer.

The visual grammar of the reel is unchanged from the structure it claims to critique. A powerful figure enters the story. The woman in peril is passive. She is moved from one situation to another by someone else's intervention. The camera follows the person doing the saving, not the person being saved.

The reel's message, if you strip away the AI filmmaking and the nostalgia and the cinematic editing, is this: women were too conditioned to recognise the problem themselves. So someone had to come in and fix it for them.

That is not empowerment. That is the oldest story in the world, with a woman in the hero role.

Genuine feminist storytelling — the kind that actually costs something to make and something to watch — would show the woman herself seeing the pattern. Choosing differently. Walking away on her own terms. The power in that story comes from within. It does not arrive on a rescue mission.

There is a particular irony in the fact that Simran's moment of agency — running towards a choice she made — is the scene being "corrected." In the name of feminism, she has been made passive again.

I want to be fair. The creator clearly has talent. The technical execution is impressive. And the underlying cultural point — that Bollywood has a long history of romanticising control, possession, and boundary-crossing as love — is worth making. Kabir Singh exists. Darr exists. There is genuine material to work with.

But eleven million views built on a shaky premise are not the same as eleven million people having a genuine awakening. It might just be eleven million people enjoying the comfort of being told they were always, already, right.

The most useful question a piece of cultural commentary can ask is: what did you miss, and why? The reel never asks it. It only answers: you missed nothing. You always knew. Someone just had to come and get you out.

That is a very satisfying thing to be told. It is also, quietly, the problem.

 

Wednesday, April 15, 2026

Rest Days Are Part of Training

Leadership during ERP implementation | Learning cycles, retrospectives, psychological safety

There is a particular kind of discipline the gym teaches that many leaders overlook. It is not the discipline of lifting heavier, pushing harder, or adding one more set. It is the discipline of knowing when not to push. The discipline of recovery. The discipline of pausing. The discipline of rest.

Progress in training does not happen only when the weight is moving. It happens after the workout — when the body repairs, adapts, and returns stronger. Without recovery, training becomes strain. Strain becomes fatigue. Fatigue becomes injury.

ERP implementations are no different. However, many leaders manage these projects as if constant pressure is the only way to succeed. They push for more reviews, escalate issues, emphasize urgency, work late, and demand rapid progress. But intensity does not equal progress. Moving quickly does not mean successful adoption. And exhaustion doesn’t prove true commitment.

The best implementations understand something more fundamental. Rest days are part of training.

The Hidden Fatigue Inside ERP Projects

An ERP implementation asks people to do two jobs at once.

They must run today’s business while helping to build tomorrow’s operating model. They must meet customer deadlines while attending workshops, validating masters, testing transactions, learning new screens, and adapting to new controls.

On the project plan, these are tasks. Within the organisation, there are loads.

A finance executive is reconciling old habits with new approval workflows.
A production planner is concerned that data accuracy will disrupt scheduling.
A sales user is anxious about capturing every lead and follow-up in the CRM.
A warehouse supervisor fears dispatch delays after go-live.

This is why some projects look healthy in meetings but feel heavy on the ground. The dashboard may be green even as people run out of energy.

In the gym, that is the athlete smiling through overtraining. The numbers may still look fine — right up until the breakdown begins.

Go-Live Is Not the Finish Line

One of the most common leadership mistakes is treating go-live as the final rep.

The system launches. Emails are sent. Photos are taken. Leadership congratulates the team. Attention then shifts to the next priority.

But anyone who has lived through an ERP implementation knows the real work often begins after go-live.

That is when users face live pressure.
That is when process gaps become visible.
That is when confidence is tested.
That is when small frustrations can turn into resistance.

In gym terms, go-live is not racking the weight and walking away. It is the moment you ask: was the lift strong, or did we compromise form to finish it?

Retrospectives: Checking Form After the Lift

Strong leaders create pauses during implementation, not because the project is failing, but because learning requires space.

A retrospective is the organisational equivalent of checking the form after a lift. You do it not because something went wrong, but because improvement requires feedback.

After blueprint sign-off.
After UAT.
After training waves.
After the mock migration.
After the first month’s close on the new system.

The questions are simple and powerful:

  • What worked well?
  • Where did users struggle?
  • What surprised us?
  • Which assumptions were wrong?
  • What must we improve before the next phase?

Without these pauses, teams repeat friction until it becomes the norm.

Psychological Safety Is Recovery for the Mind

Physical recovery repairs muscles. Psychological safety repairs trust. 

Every ERP project depends on people speaking honestly and early. Yet many stay silent.

They do not admit to confusion.
They hide adoption problems.
They understate risks.
They say “all good” when they mean “we are stuck.”

Why? Because honesty can feel unsafe. Psychological safety is not softness. It is a form of implementation intelligence. When people feel safe, they say:

  • “Training was not enough.”
  • “This workflow is slowing us down.”
  • “Master data needs cleanup.”
  • “Users need support on the shop floor.”
  • “We made the wrong design choice.”

That honesty saves projects. Silence delays failure until it becomes costly. In the gym, ignored pain becomes injury. In ERP, ignored truth becomes rework.

Great Implementations Use Cycles

The best training programmes do not require maximum effort every day. They work in cycles: push, recover, adapt, repeat.

ERP leadership should do the same.

There are phases for design intensity.
Phases for testing discipline.
Phases for hypercare support.
Phases for stabilisation.
Phases for optimisation.

If every phase is treated like an emergency, people burn out and judgment declines.

Sometimes the best leadership move is not another escalation meeting. It is a day of focused user support.
Sometimes the fastest decision is not more pressure. It is less confusion.
Sometimes the smartest way to move forward is to pause and restore confidence.

What Leaders Should Do Now

§  Build recovery into the plan- Stabilisation is not optional. Schedule it.

§  Run retrospectives at every milestone - Capture lessons while they are fresh.

§  Measure energy, not just status - A green tracker can hide a tired workforce.

§  Reward early truth - Thank the person who raises a problem early.

§  Stay visible after go-live - Leadership presence matters most when confidence dips.

Final Lift

Any leader can ask for one more sprint. Mature leaders know how to sustain performance.

ERP implementation is not won by endlessly pushing people. It is won by helping people learn, adapt, recover, and grow stronger through change.

Because in the gym, and in transformation, recovery is not the opposite of progress.

It is where progress becomes tangible.

 

The Weight of Being Reliable

I am not a mother. I have been reminded of this often enough, particularly when I have ventured an opinion about motherhood. The reminder is...