Love
PremTreat every person, at every level, as worthy of full regard.
In practice: Greet the newest employee with the same attention as the largest shareholder.
The 27 models
WCRC-GLC-26 — The Modern Sages
Neem Karoli Baba
The WCRC ServeHeart Model
Serve first, lead quietly.
THE MODEL
The WCRC ServeHeart Model
Leadership begins with care for people, shows itself as practical service, and is held steady by remembering the larger purpose. Feeding people is the most literal form of that service, and holding possessions lightly keeps the leader free of the need for credit. Each turn of the cycle strengthens the next.
Anchor teaching: "Love everyone, serve everyone, remember God" (as summarised by Ram Dass)
This is a selection of teachers linked with the Hindu tradition, not a ranking. The models offer management reflection, not religious instruction.
WCRC is not affiliated with or endorsed by any teacher or organisation discussed.
MODEL STRUCTURE
How it works
Serve
SevaAsk what people need to do their best work and supply it.
In practice: Open each one-to-one by asking what is blocking the other person.
Feed people
Meet basic needs first: time, tools, fair pay, a meal, a hearing.
In practice: Fix one practical hardship for staff or community each month.
Hold lightly
Keep few possessions, titles and claims to credit.
In practice: Pass public credit for a success to the team that delivered it.
Remember
SmaranKeep the larger purpose in view so service does not become routine.
In practice: Begin leadership meetings by naming who the work is finally for.
TEACHING AND CONTEXT
The thinking behind it
In 1962 he began work at Kainchi with nothing more than a simple platform at the site; the Hanuman temple at Kainchi Dham was consecrated on 15 June 1964. That date is still marked each year with a large fair and the distribution of prasad. The institution he left is organised around feeding people, which is the model's service step made visible.
Love, serve, remember: love all beings, serve them, and keep God in mind.
Ram Dass, Miracle of Love (1979); Love Serve Remember Foundation (as given in brief)Feed people: he constantly urged devotees to feed the hungry, and food (prasad) was central to his ashrams.
Maharajji Seva Trust (as given in brief)Non-attachment: he owned almost nothing beyond a blanket and moved freely.
Divine Life Society (as given in brief)Seeing God in all: every person is a form of God.
NKB Meditation Foundation (as given in brief)OPERATING MODEL
From principle to practice
Inputs
- Leaders willing to serve before being served
- Time set aside for people's needs
- A purpose stated in human terms
Practices
- Needs-first one-to-ones
- Basic welfare fixed before perks
- Credit passed down, blame taken up
- Purpose recalled at every leadership forum
Outputs
- People who feel seen and supported
- Teams that serve customers the same way
- Low dependence on the leader's ego
Outcomes
- Deep loyalty and lower attrition
- Trust across stakeholders
- A service culture that outlasts the founder
BENEFIT MODEL
Who it is for
leader
Is freed from the need to be noticed, which leaves more attention for the work and the people.
employees
Have their basic needs met first and see credit flow to them, which makes them willing to give more.
customers
Are served by people who have themselves been served well, and it shows in how they are treated.
investors
Back a culture with low key-person risk, because it rests on habits of service rather than one personality.
society
Gains a company that feeds and looks after the people around it as a matter of course.
WCRC MODEL PARAMETERS
Model emphasis
The scores describe this model's emphasis on each parameter. They are not scores for a person or organisation.
Vision Quotient2 / 5
Impact Index4 / 5
Innovation Score1 / 5
People Leadership5 / 5
Stakeholder Trust5 / 5
Resilience Factor3 / 5
Global Mindset3 / 5
THE AI AGE
Why it matters now
As routine tasks are automated, the human work that remains is care, attention and service. Greenleaf's test of servant leadership asks whether those served grow "healthier, wiser, freer, more autonomous" [1], a test no tool can pass on a leader's behalf. Brynjolfsson warns of a 'Turing Trap' when AI is built to automate rather than augment people [3]; a serve-first leader asks how AI can feed people's capability. With Gallup reporting global engagement at 20% in 2025 [4], service-first leadership is a human advantage.
EXECUTION
Put the model to work
Open every one-to-one this week by asking what is blocking the other person, and fix one of those blockers yourself by Friday.
Founder and CEO
- Ask what blocks people: From the first week, open each one-to-one by asking what is in the way of the other person's best work and write it down. Close the loop on it at your next meeting.
- Greet everyone equally: Give the newest employee the same attention and time you give the largest shareholder or customer. In a large company, make this visible on site visits and in town halls.
- Fix one hardship monthly: Each month, personally see that one practical hardship for staff or community is fixed: time, tools, fair pay, a meal, a hearing. Basic needs come before perks.
- Pass credit down: In every announcement of a success, name the team that delivered it and take the blame yourself when things go wrong. Hold few titles and claims to credit.
- Name who the work is for: Begin every leadership meeting by naming who the work is finally for, so service does not slide into routine. Pair service with hard decisions and do not use quiet leadership to avoid them.
Company
- Find unmet basic needs (CHRO with operations head): Survey and interview staff on practical blockers and hardships, and check engagement data on whether managers help people do their best work. This sets the baseline for needs-resolution rate and felt support.
- Pilot needs-first one-to-ones (One business head): In one unit, run one-to-ones that open with blockers, log every need raised, and set a period within which each must be resolved or answered. Review the log monthly with the unit head.
- Embed welfare and credit rules (CHRO and communications head): Put basic welfare fixes ahead of perks in budget rules, and set a communications standard that names teams in credits. Add needs resolution and credit-sharing to manager reviews and promotion criteria.
- Train managers to serve (Learning and development head): Train all people managers to run needs-first one-to-ones and to resolve blockers within their own authority. Teach them where service ends and hard decisions, including on poor performance, still have to be made.
- Track service KPIs (CHRO): Report needs-resolution rate, credit direction in communications, felt support by team and community service hours every quarter. Watch for community work turning into publicity or patronage.
- Scale and guard against burnout (CEO and executive team): Extend needs-first one-to-ones to every team once the pilot shows faster resolution and higher felt support. Each year, review leaders' own workloads so service does not become martyrdom.
Readiness check
Before starting
- Are our leaders willing to ask what blocks people and act on the answer within a set period?
- Will we fix basic welfare gaps before adding perks?
- Are we prepared to give public credit to teams and take blame at the top?
Phase 1 · Diagnose and commit
Find the practical blockers and hardships people face and how far managers help them now.
- Survey and interview staff on blockers and basic needs for the Feed people component.
- Pull the engagement item on whether managers help people do their best work, by team.
- Count named credits to teams and to senior leaders in recent communications for the Hold lightly component.
- Have the CEO open every one-to-one with the Serve question about what is blocking the other person.
Deliverable: A list of unmet basic needs, baselines for felt support and credit direction, and the CEO's first log of blockers raised.
Gate: Baseline recorded for needs-resolution rate, felt support and credit direction, and the CEO has closed the loop on blockers raised in one-to-ones.
Phase 2 · Pilot and prove
Prove in one unit that needs-first one-to-ones resolve blockers faster and raise felt support.
- Run one-to-ones in one unit that open with blockers and log every need raised.
- Set a period within which each need must be resolved or answered.
- Fix one practical hardship each month in the unit before any new perk.
- Open the unit's leadership meetings by naming who the work is finally for, for the Remember component.
Deliverable: A needs log for the pilot unit showing items raised, resolved and answered within the set period.
Gate: The pilot unit has logged and answered every need within the set period, and felt support in the unit has been measured again.
Phase 3 · Embed and scale
Make needs-first service, welfare before perks and credit passed down the company norm.
- Extend needs-first one-to-ones to every team.
- Put basic welfare fixes ahead of perks in budget rules.
- Set a communications standard that names teams in credits and leaders in blame.
- Add needs resolution and credit-sharing to manager reviews and promotion criteria.
Deliverable: A company needs log, revised budget rules and a communications credit standard.
Gate: All teams log needs from one-to-ones, and the credit direction count shows teams named in success announcements.
Phase 4 · Sustain and renew
Keep service real and sustainable so it neither burns out leaders nor becomes publicity.
- Review leaders' own workloads every year so service does not become martyrdom.
- Check community feeding and welfare work for publicity or patronage.
- Confirm hard decisions, including on poor performance, are still being made.
- Renew the statement of who the work is finally for.
Deliverable: An annual service review for the executive team covering all four KPIs and leader workloads.
Gate: The executive team has reviewed leader workloads and hard decisions within the year alongside the service KPIs.
Governance
sponsor: The CEO, whose own one-to-ones and credit habits set the tone everyone else follows.
lead: The CHRO, who runs the needs log, welfare budget rules and manager training.
forum: The needs log is reviewed monthly by unit heads and the four KPIs go to the executive team every quarter.
decision_rights: Managers resolve needs within their own authority and the CHRO can approve welfare fixes within budget; changes to pay or policy go to the CEO.
Cadence
Weekly: Every one-to-one opens with what is blocking the other person, and the answer is logged.
Monthly: Each leader sees one practical hardship for staff or community fixed, and unit heads review the needs log.
Quarterly: Report on needs-resolution rate, credit direction, felt support and community service hours.
Annually: Executive review of leaders' own workloads, hard decisions taken and whether community work has stayed free of publicity.
By company stage
startup
The founder asks every person each week what is in their way and fixes small hardships directly. Credit for wins goes to the team by name in every update to investors and customers.
scaleup
Needs-first one-to-ones become a manager standard with a shared log, and welfare comes before perks in budgets. HR trains managers on where service ends and hard decisions begin.
enterprise
Needs resolution and credit direction are reported by business unit, and community service is planned from local need. The board reviews whether leaders take blame publicly and pass credit down.
Success looks like
- People raise blockers freely because they expect them to be answered.
- Success announcements name the teams who delivered, and senior leaders take public responsibility for failures.
- Basic welfare gaps are closed before new perks are announced.
MEASUREMENT AND LIMITS
What to watch
Needs-resolution rate
Share of staff-raised blockers or hardships resolved within a set period, logged from one-to-ones.
Credit direction
In internal and external communications, count named credits given to teams versus to senior leaders.
Felt support
Engagement survey item on whether the respondent's manager helps them do their best work, tracked by team.
Community service hours
Hours of staff time given to community feeding or welfare work, from volunteering records.
Failure modes
- Service becomes martyrdom: the leader exhausts themselves and calls it devotion.
- Quiet leadership becomes absence, and hard decisions are avoided.
- Feeding people turns into publicity or patronage instead of meeting real needs.
Execution risks
- Managers ask about blockers but do not act, and people stop raising them.: The number of needs raised falls while the resolution rate stays low. Mitigation: Publish resolution times by team and give managers authority to fix common blockers directly.
- Quiet, serving leadership becomes a way to avoid hard decisions.: Performance problems stay unresolved and teams report unclear direction. Mitigation: Review hard decisions taken alongside the service KPIs in every leadership review.
- Feeding people and community work turn into publicity or patronage.: Community events are planned around coverage rather than need. Mitigation: Choose community work from needs raised by staff and the community, and limit external promotion.
- Leaders burn out serving everyone and call it devotion.: Senior leaders work long hours on welfare items while core duties slip. Mitigation: Delegate needs resolution to managers and review leader workloads each year.
RESEARCH SOURCES
Sources and notes
- Greenleaf, R. K. (1970). The Servant as Leader (essay). Robert K. Greenleaf Center for Servant Leadership.
- Collins, J. (2001). Level 5 leadership: The triumph of humility and fierce resolve. Harvard Business Review, 79(1), 66–76 (reprinted HBR July–August 2005, R0507M).
- Brynjolfsson, E. (2022). The Turing Trap: The promise & peril of human-like artificial intelligence. Daedalus, 151(2), 272–287.
- Gallup. (2026). State of the Global Workplace: 2026 Report. Washington, DC: Gallup.
The WCRC Guru Management Codex and its 27 models are proprietary WCRC models. © WCRC. All rights reserved.