Sarada Devi and the discipline of judging yourself before anyone else

From the Nahabat room to Mother of an Order

For about thirteen years, Sri Sarada Devi lived in a tiny room in the Nahabat at the Dakshineswar Kali Temple, serving Sri Ramakrishna and the stream of devotees who came to see him. The room is now a place of pilgrimage. It is worth holding its size in mind, because a very large life was lived from it.

She was born on 22 December 1853 in Jayrambati, a village in the Bankura district of West Bengal, to Ramachandra Mukhopadhyay and Shyama Sundari Devi. The family was poor and devout. As a small child, around five or six, she was married to Sri Ramakrishna and stayed on with her own family. The marriage was a spiritual partnership and was never consummated. In 1872, at about eighteen, she walked to Dakshineswar to join him, and he received her as a spiritual companion.

That same year, on the night of the Phalaharini Kali Puja, Sri Ramakrishna ritually worshipped her as the Divine Mother. It is a remarkable act to sit with. Sri Ramakrishna chose to honour the Mother in the young woman beside him, and she spent the next years cooking, serving and praying in that small room.

After his death in August 1886 she went on pilgrimage and then lived in near-poverty at Kamarpukur, his village. From the late 1880s she began initiating disciples and guiding the young monks who would build the Ramakrishna Order. Swami Vivekananda called her the ideal for women of the modern age. Swami Saradananda built Udbodhan House in Kolkata for her, and she divided her later years between Kolkata and Jayrambati. Monks and lay devotees alike, Sister Nivedita among her Western disciples, treated her as their spiritual mother, and the Order reveres her as Sangha-janani, Mother of the Order.

She wrote nothing. What we have comes from devotees who recorded her words, mainly in The Gospel of the Holy Mother. She died at Udbodhan House on 21 July 1920. She was far more than a great saint's wife: Belur Math and Britannica both present her as a realised teacher in her own right, and that is how this chapter reads her.

Five days before the end: a counsel about other people's faults

Five days before she died, Sarada Devi gave the counsel her followers remember above all others. It was short and practical.

If you want peace of mind, do not find fault with others.

Sarada Devi. As translated in Gospel of the Holy Mother, Sri Ramakrishna Math, Chennai

She went on, in the same passage, to say that one should rather see one's own faults, and learn to make the whole world one's own, because no one is a stranger. Read slowly, the counsel has a direction of travel. It starts with the self and moves outward. The first act is an audit of one's own conduct. Only after that does the circle widen to include everyone else.

Leaders tend to read it the other way round. They hear the call to make the world their own as a warm instruction about culture, and skip the harder first half. Sarada Devi put self-scrutiny first for a reason. A person busy cataloguing the failings of others has no room to take anyone in.

Her other teachings fill in the picture. She saw herself as mother to everyone who came to her, and is quoted by Belur Math as saying, "I am the mother of the virtuous as well as the wicked." She treated ordinary duties, cooking, serving and nursing, as spiritual practice when done with love and balanced with prayer. She asked her disciples to keep the mind steady with regular repetition of the Name, sitting at least morning and evening. And she carried a complete trust in God and in Sri Ramakrishna through hardship. Together these make a demanding programme: judge yourself first, refuse no one, honour plain work, and keep a daily discipline that holds you steady when people test you.

A robber on the Telo-Bhelo fields, and another at the door

Devotees recount a story from her walk to Dakshineswar. The way crossed the lonely Telo-Bhelo fields, and she was walking alone when she met a robber and his wife. She spoke to them as their daughter.

In the telling, the couple saw the Divine Mother in her. They gave up crime, and later came to visit her. Whatever a reader makes of the details, the shape of the story is clear. She met a threat by extending the circle of belonging to include it, and the threat dissolved.

The second story is set years later in Jayrambati. Devotees there recount that Amjad, a dreaded local robber, used to come to see her. The villagers were frightened of him. She received him warmly and fed him as her own son.

This one is harder for a modern reader, and more useful. Amjad did not stop being Amjad because she fed him. The village's fear was reasonable. What she refused to do was let his record decide whether he was one of hers. She held two facts at once: that he had done wrong, and that he was still her child.

Most organisations manage only one of those facts at a time. Either a person who has failed is cast out, or the failure is quietly ignored to keep the peace. The stories of Telo-Bhelo and Amjad describe a third course, in which the person is received back and the wrong is still named. That third course is the heart of the model below.

Saying "I got this wrong" in front of the machines

AI is changing the work of almost every team at once. The people doing that work now have to admit, often in public, that they do not yet understand a tool, a result or a new way of working. Teams where such admissions are risky will hide confusion, and hidden confusion is where expensive mistakes grow.

Amy Edmondson's 1999 study in Administrative Science Quarterly defined team psychological safety as "a shared belief held by members of a team that the team is safe for interpersonal risk taking." Studying 51 work teams in a manufacturing company, she found that this safety was associated with team learning behaviour, which in turn related to team performance. Google's Project Aristotle, which studied 180 teams, later placed psychological safety first among the five dynamics of effective teams.

The question is how such safety starts. Owens and Hekman's 2012 study in the Academy of Management Journal, based on 55 in-depth interviews with leaders, identified three humble leader behaviours: acknowledging personal limits, faults and mistakes; spotlighting followers' strengths; and modelling teachability. The authors describe this as leaders modelling to followers how to grow.

Sarada Devi's order of operations fits that finding closely. If the most senior person in the room names their own fault first, the room learns that faults can be named. In an AI transition, where a chief executive may understand the new tools less well than a graduate hire, that example matters more than any training budget.

The WCRC Make-It-Your-Own Belonging Model

Created by Abhimanyu Ghosh · A proprietary model of Abhimanyu Ghosh and WCRC

WCRC calls this the Make-It-Your-Own Belonging Model. It takes Sarada Devi's last counsel as a sequence and draws it as the concentric rings in the diagram above: the leader's own faults at the centre, then the leader's own team, then the difficult people most organisations would rather exclude, and finally the whole world the organisation touches. Five building blocks hold it together, from looking at one's own faults first to the steady daily discipline that keeps a leader calm enough to receive difficult people without reacting. The model is WCRC's reading of her teaching for business; it carries no endorsement from the Ramakrishna Math, the Ramakrishna Mission or Sri Sarada Math.

The Make-It-Your-Own Belonging Model starts with self-scrutiny: the leader looks first at their own faults before judging anyone. From there belonging widens outward, from the close team to difficult people and finally to everyone the organisation touches, with second chances and steady daily discipline holding it together.

The building blocks

1. 01Look at your own faults first

   The leader's first audit is of their own conduct, which removes the habit of blame from the top.

   In practiceOpen every post-mortem by the senior leader naming what they personally got wrong.

2. 02No stranger in the team

   Everyone, including contractors, new joiners and remote staff, is treated as one's own.

   In practiceGive every new and peripheral team member the same access to the leader as long-standing insiders.

3. 03Second chances

   People who have failed or behaved badly can be received back when they turn around, as the robber of Telo-Bhelo was.

   In practiceSet a clear, fair route back for people after a serious mistake, with expectations stated plainly.

4. 04Work as worship

   Ordinary, unseen work done with care carries as much dignity as visible achievement.

   In practiceRecognise the maintenance, support and care work that keeps the business running, by name.

5. 05Steady faith

   A fixed daily discipline keeps the leader calm enough to hold difficult people without reacting.

   In practiceKeep a short reflection at the start and end of each working day, whatever the schedule.

What the chief executive gives up: the comfort of the verdict

Chief executives are paid to judge. They judge plans, people, markets and results, many times a day. The model leaves that work in place and changes the order in which they do it, putting their own conduct first in the queue.

That is costly in a specific way. A leader who opens a post-mortem by naming their own part in a failure gives up the comfort of the clean verdict. They can no longer stand outside the problem. Owens and Hekman's work suggests this is exactly what teaches a team that admitting error is survivable, and the first move in the playbook below starts there for that reason.

The habit that sustains it is small. Sarada Devi asked her disciples to sit for japa and meditation at least morning and evening. The business translation is a short reflection at the start and end of the working day, kept whatever the schedule. Its purpose is steadiness. A leader who has already looked at their own conduct that morning is less likely to lash out at the first difficult person who walks in.

The blind spot is the one the model names among its failure modes. Refusing to find fault can slide into tolerating harm. Amjad was fed, but no one in the story suggests his robberies were acceptable. A CEO who uses this model as a reason never to confront a bully has misread it. Self-scrutiny comes first; standards stay in place.

There is a second blind spot, quieter and common among conscientious leaders: martyrdom. A chief executive who absorbs every failure personally teaches the team that it never has to own anything. Sarada Devi served, and she also guided and initiated. Her own faults came first, and so did the team's growth.

Founders and the small company where everyone is family until they are not

Early companies love family language. It feels honest when there are twelve people around one table. The model contains a warning about it, and founders should take the warning seriously: family language must never be used to ask for unpaid loyalty and effort that a real family would never demand.

What Sarada Devi offers founders is something more exact than warmth. She refused no one who called on her as mother, yet her care had content. She fed people and she guided them. A founder can do the same by treating freelancers and first hires as insiders in the room, and by being plain about what is expected of everyone in it.

The hardest founder moment is the one the Amjad story prepares for. An early employee makes a serious mistake. The pressure to remove them is strong, and so is the pull to look away because they are a friend. The model's answer is a clear, fair route back with stated expectations, decided by the founder in person, and closed where others have been harmed.

If you run a twenty-person start-up, the most useful thing you can do this month is small. At your next retrospective, speak first, and speak about yourself. The team will notice what you chose to say before you say anything about them.

Large companies, boards and the people at the edge of the circle

In a large organisation the outer rings of the diagram become real populations. Contractors, remote staff, recent acquisitions and new joiners often sit outside the circle of trust without anyone deciding they should. They are the strangers inside the company, and they are frequently the first to see a problem and the last to be asked about it.

The operating model below treats them as a measured group. They are invited to reviews, surveyed separately and given the same access to leaders as long-standing insiders. That is how a five-ring diagram becomes something a CHRO can report on.

Boards have two jobs here. The first is to ask, at least once a year, whether senior leaders actually name their own mistakes first, and to look at the evidence rather than the anecdote. The second is to check that belonging has not loosened standards. A board that sees repeat incidents after second chances, or complaints from people who were harmed, should treat that as a governance matter.

Sarada Devi's blessing of the Varanasi hospital work in 1912 offers boards a further thought. Devotees recount that she said she found Sri Ramakrishna himself present in the service of the sick, and her words settled doubts about the monks' social work. Large companies carry their own doubts about the value of maintenance, support and care work that never appears in a strategy deck. A board that asks to see that work recognised by name is applying her view of work as worship in a form any audit committee can follow.

The business model

Inside a company, the model runs on four inputs: the leader's daily self-scrutiny, clear standards with a defined route back after failure, equal access for every team member, and respect for unseen work. These feed four practices, the most visible of which is the leader-first post-mortem, where the most senior person names their own part before anyone else speaks. The outputs are practical and countable: less blame, earlier admission of errors, fewer outsiders inside the company and talent retained after recoverable failures. Over time they add up to the outcomes shown in the operating model below: psychologically safe teams, higher trust in leadership and faster learning from mistakes.

The benefit model

The leader gains first, because starting with their own faults frees them from constant judging and makes them easier to approach. Employees gain the right to admit a mistake and still belong, and those on the edges of the organisation are treated as insiders. Customers benefit because problems surface and get fixed sooner when staff are unafraid to report them. Investors get a culture that learns from mistakes instead of hiding them, and so fewer unpleasant surprises. Society gains from second chances given fairly and with structure, which help people rebuild working lives that might otherwise be lost.

How to implement the WCRC Make-It-Your-Own Belonging Model

If you are the founder or CEO

1. 1

   Open with your own faults

   From the first week, begin every post-mortem and review you attend by naming your own part in the problem. Keep it short and specific, then let others speak.

2. 2

   Keep a daily reflection

   Take a few minutes at the start and end of each working day to look at your own conduct before judging anyone else's. Hold to it whatever the schedule.

3. 3

   Make no one a stranger

   Give new joiners, contractors and remote staff the same access to you as long-standing insiders, through open time every week. In a large company, visit the teams furthest from head office first.

4. 4

   Receive people back fairly

   When someone has failed badly and turned around, take a direct part in their route back and state the expectations plainly. Never let this excuse harm to others.

5. 5

   Thank the unseen work

   Each month, name and thank people whose maintenance, support or care work keeps the business running. Do it in person where you can.

Rolling it out across the company

The execution roadmap

Four phases, each closed by a gate. Do not move on until the gate is met.

1. Days 0–30

   Phase 1 · Diagnose and commit

   Find where blame starts and who sits outside the circle, beginning with the leader's own conduct.

   • Review the past year's post-mortems and record how many were opened by the most senior person naming their own part.
   • Measure the time between a mistake occurring and it being reported to someone who can fix it.
   • Run a short validated survey on safety to speak up, by team.
   • List the peripheral groups, such as contractors, remote staff and new joiners, and check what access each has to the leader.

   Deliverable

   A blame-and-belonging baseline, plus the CEO's own written note on what they got wrong in the last review they chaired.

   Gate to proceed

   Baseline recorded for every KPI, and the CEO has opened at least one review by naming their own faults first.

2. Days 31–90

   Phase 2 · Pilot and prove

   Prove that leader-first post-mortems bring errors to light sooner in one business.

   • The pilot business head opens every review by naming what they personally got wrong before anyone else speaks.
   • Invite contractors, remote staff and new joiners into those reviews, so there is no stranger in the team.
   • Each week, name one piece of unseen maintenance or support work and the person who did it, treating work as worship.
   • The head keeps a short reflection at the start and end of each day to stay steady with difficult people.

   Deliverable

   A record of every pilot review, the time-to-report data and the pilot team's safety survey.

   Gate to proceed

   Every pilot review was opened by the senior person, early error reporting has been measured for the pilot period, and the pilot team's safety score is at or above baseline.

3. Days 91–180

   Phase 3 · Embed and scale

   Write second chances and standards into policy and make leader-first reviews the norm.

   • The CHRO and legal write a route back after a serious mistake, with stated expectations and a clear exclusion where others have been harmed.
   • Make leader-first opening the standard for every post-mortem and review across the company.
   • Train managers in self-scrutiny, using their own recent decisions as the material.
   • Give peripheral staff the same access to leaders as long-standing insiders, and ban 'family' language in requests for extra effort.

   Deliverable

   An approved second-chance policy with its standards clause, a company-wide review standard and a trained manager group.

   Gate to proceed

   The second-chance policy is approved with the standards clause intact, and every unit is running leader-first reviews.

4. Month 7 onwards

   Phase 4 · Sustain and renew

   Keep belonging warm and standards firm as the company grows.

   • Check a year later how many people given a second chance remain and perform well.
   • Audit for martyrdom: in reviews, does the team also own its part, or does the leader absorb every failure?
   • Re-run the safety survey and the time-to-report measure and compare them with the baseline.
   • Review working hours where 'family' language is common, to catch unpaid loyalty being asked for.

   Deliverable

   An annual belonging review covering leader-first admissions, safety, early reporting and recovery after setbacks.

   Gate to proceed

   Recovery after setbacks is tracked for every second chance granted, and early error reporting is faster than the baseline.

Implementation risks and how to handle them

By stage of company

Habits to start this quarter

1. 1

   Write your line before theirs

   When a colleague's mistake makes you angry, write one sentence about your own part in the situation before you reply to them. Send nothing until that sentence exists. Most weeks it will change the tone of what you send.

2. 2

   Host the person you avoid

   Pick the one stakeholder you find hardest to deal with, inside or outside the company, and meet them on your ground this quarter with no agenda but to listen. Sarada Devi fed the man the village feared. A meal or an unhurried hour is the modern version.

3. 3

   Do one ordinary task yourself

   Once a fortnight, do a piece of plain work that others usually do for you: answer a customer query, clear a support ticket, fix a broken process by hand. Notice how much care it takes. It will change how you speak about the people who do it every day.

4. 4

   Keep a private list of people you have written off

   Write down, for your eyes only, the names of people you have privately decided are beyond help. Choose one this quarter and have a fresh conversation, with your expectations stated plainly. If the list is long, that is information about you.

5. 5

   Hold a two-minute steadiness before hard meetings

   Before any meeting you expect to be difficult, take two quiet minutes to settle your mind and recall your own faults in the matter at hand. The aim is to arrive steady enough to receive the person, whatever they bring.

What to measure

Where the model goes wrong

• !Belonging without standards: refusing to find fault turns into tolerating harm to others.
• !Self-scrutiny becomes martyrdom, with the leader absorbing every failure and the team never owning its part.
• !"Family" language is used to ask for unpaid loyalty and effort that a family would never demand.

A small room and a wide circle

Sarada Devi governed nothing in the corporate sense. She wrote no policy and left no book of her own. Yet an Order of monks treated her as its mother, devotees recount that a feared robber was fed at her door, and her last counsel is still quoted by the institutions that carry her name, more than a century after she gave it. WCRC reads that as evidence of a kind of authority that title cannot confer: the authority of a person who has already judged herself, and so has room for everyone else.

Leaders who want that authority will find the path short and steep. Look at your own faults before anyone else's. Then widen the circle, one difficult person at a time, until no one in the company is a stranger. In her counsel, peace of mind begins exactly where the fault-finding ends.