The 27 models

    WCRC-GLC-05 — The Bhakti Saints

    Sant Jnaneshwar

    The WCRC Pasayadan Translation Model

    Translate the highest idea into the language of the front line.

    Sant Jnaneshwar

    THE MODEL

    The WCRC Pasayadan Translation Model

    The Pasayadan Translation Model holds that a strategy only the boardroom understands has not yet become strategy. A leader masters the source, translates it into the language people actually use, tests it with the front line, and ends by wishing good for every stakeholder, including the adversary.

    Anchor teaching: Pasayadan: "May all beings form bonds of heartfelt friendship" (Jnaneshwari 18.1795)

    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

    Source knowledgeDistilled meaningPeople's languageFront-line useGoodwill for all

    Master the source

    Translation starts with deep understanding: the leader must know the strategy, its logic and its limits thoroughly before simplifying it.

    In practice: The CEO can explain the strategy's reasoning, trade-offs and risks without slides.

    Translate to the people's language

    As the Gita was carried from Sanskrit into Marathi, strategy is carried from boardroom terms into the words each team uses daily.

    In practice: The CEO asks each unit head to restate the strategy in their team's own language and checks it for meaning, not jargon.

    Test with the front line

    The Varkari movement carried his teaching on foot, among ordinary people. A translation is only proven when the front line can use it to make decisions.

    In practice: The CEO asks front-line staff to say what the strategy changes in their work this month, and revises the message where they cannot.

    Wish good for all stakeholders

    Pasayadan

    The plan is framed to seek the good of employees, customers, partners, communities and even competitors and critics, without wishing their ruin.

    In practice: The CEO reviews major plans for their effect on every stakeholder, including rivals and critics, before announcing them.

    TEACHING AND CONTEXT

    The thinking behind it

    Around 1290, at Nevasa, Jnaneshwar, then about 15, completed the Jnaneshwari, a Marathi commentary on the Bhagavad Gita, so that ordinary people could read the Gita for themselves. Devotees recount that at the end of the work, instead of asking anything for himself, the teenage saint asked God for the good of the whole world, even of the wicked. That closing prayer, the Pasayadan, is still sung today.

    Spiritual knowledge in the people's language: he put the Gita's teaching into Marathi so that everyone, not only Sanskrit scholars, could understand it.

    Britannica; Eco-Heritage, CPREEC, as given in brief

    Universal goodwill: he asks God not to destroy the wicked but to remove their crookedness ("May the wicked shed their crookedness").

    Pasayadan, Jnaneshwari 18.1795, as given in brief

    Each one's own dharma: let the world see by the sun of its own duty (svadharma).

    Pasayadan, as given in brief

    Humility over powers: yogic powers are nothing beside love and true knowledge, as Changdev learned.

    Maharashtra Tourism, Changdev temple page, as given in brief

    OPERATING MODEL

    From principle to practice

    Inputs

    • Strategy and its full reasoning
    • Leaders who understand it deeply
    • Front-line teams and their language

    Practices

    • Unit-level restatement of strategy
    • Plain-language test with front-line staff
    • Stakeholder goodwill review before launch
    • Revising messages that fail the test

    Outputs

    • Strategy people can explain and use
    • Fewer misread priorities
    • Plans checked against all stakeholders

    Outcomes

    • Faster, aligned execution
    • Trust among staff, partners and critics
    • Strategy that travels across regions and cultures

    BENEFIT MODEL

    Who it is for

    leader

    The leader sees strategy carried out as intended, because people understand it in their own terms.

    employees

    People are given the reasoning in words they use, which lets them act with judgement instead of waiting for instructions.

    customers

    Customers meet staff who can explain what the company stands for and why it acts as it does.

    investors

    Investors get a strategy that is understood and executed at the front line, not only presented well.

    society

    A company that wishes good even to rivals and critics lowers conflict and earns standing in the communities it serves.

    WCRC MODEL PARAMETERS

    Model emphasis

    The scores describe this model's emphasis on each parameter. They are not scores for a person or organisation.

    VisionQuotientImpactIndexInnovationScorePeopleLeadershipStakeholderTrustResilienceFactorGlobalMindset

    Vision Quotient4 / 5

    Impact Index3 / 5

    Innovation Score2 / 5

    People Leadership4 / 5

    Stakeholder Trust5 / 5

    Resilience Factor2 / 5

    Global Mindset5 / 5

    THE AI AGE

    Why it matters now

    An AI decision, or a transformation plan, that nobody can explain in plain language will not earn trust. Microsoft's 2026 Work Trend Index found that only 26% of AI users say their leadership is clearly and consistently aligned on AI [1]. Gartenberg, Prat and Serafeim found that firms whose employees perceive both strong purpose and high clarity from management showed higher subsequent financial performance [2]. Jnaneshwar's work is a model for explainability: master the source, then say it so the front line can act on it, and wish good for everyone affected.

    EXECUTION

    Put the model to work

    On Monday, explain the company's strategy, its trade-offs and its risks to a colleague without slides, and note where you falter.

    Founder and CEO

    • Explain strategy without slides: In the first week, explain the strategy's reasoning, trade-offs and risks to a small group without slides. Where you hesitate is the part you have not yet mastered.
    • Ask heads to restate it: Ask each unit head to restate the strategy in their team's own language and review each version yourself for meaning, not jargon. In a small company, ask each team lead directly.
    • Hear the front line monthly: Each month, ask front-line staff what the strategy changes in their work that month. Where they cannot answer, revise the message yourself.
    • Review effects on all stakeholders: Before announcing a major plan, review its effects on employees, customers, partners, communities, rivals and critics. Write down the hard choices it still requires so goodwill does not become avoidance.
    • Return to the source: Each quarter, re-read the full strategy and its reasoning so translation does not drift into dilution. Check that the simplified versions still carry the substance.

    Company

    • Test current strategy recall (Internal communications with HR): Sample front-line staff, ask them to state the top priorities in their own words and score the answers against the board's version. This sets the baseline for strategy restatement accuracy.
    • Pilot translation in one unit (One unit head): Have one unit restate the strategy in its own language and test it with front-line staff who are not hand-picked, for a quarter. Revise messages that fail and log each revision.
    • Embed restatement and stakeholder review (CEO office and strategy team): Make unit-level restatement part of every planning cycle and require a documented stakeholder goodwill review before any major plan is launched. Add the ability to explain strategy plainly to promotion criteria for managers.
    • Train managers to translate (CHRO with internal communications): Train all people managers to put strategy into the words their teams use daily without losing substance, and to run honest front-line tests. Include translation into regional languages where teams work in them.
    • Measure translation quality (Internal communications): Track strategy restatement accuracy, message revision rate, clarity of direction and stakeholder review coverage, and report them to the leadership team every quarter. Treat a revision rate that never moves as a sign that testing is staged.
    • Scale across regions and review (CEO and board): Extend translation and testing to every region and function once the pilot shows clearer understanding, and review the approach each year. Check that plans still make the hard choices some stakeholders will dislike.

    Readiness check

    Before starting

    • Can the CEO explain our strategy's reasoning and trade-offs without slides?
    • Will we test our messages with front-line staff who may tell us they do not understand?
    • Are we willing to review a plan's effects on rivals and critics before we launch it?
    Days 0–30

    Phase 1 · Diagnose and commit

    Find out how much of the strategy survives the trip from boardroom to front line today.

    • Sample front-line staff across levels and regions and score their restatement of the top priorities against the board's version.
    • The CEO explains the strategy, its trade-offs and risks to a small group without slides and notes where they falter (Master the source).
    • Collect current strategy messages and mark the jargon a front-line employee would need translated.
    • Choose one unit, and the working languages its teams use, for the pilot.

    Deliverable: A strategy recall baseline by level and region, and a jargon list.

    Gate: Baseline recorded for every KPI, the CEO has explained the strategy without slides, and one unit head has agreed to pilot.

    Days 31–90

    Phase 2 · Pilot and prove

    Prove that restating strategy in a unit's own language raises understanding without diluting substance.

    • The unit head restates the strategy in the team's own language, and the CEO checks it for meaning and trade-offs (Translate to the people's language).
    • Test the restatement with front-line staff who were not involved in writing it, sceptics included (Test with the front line).
    • Revise every message that fails the test and log the revision.
    • Run a stakeholder review on one plan, covering rivals and critics, and write down the hard choices it still requires (Pasayadan).

    Deliverable: A tested and revised unit restatement and one completed stakeholder review.

    Gate: Restatement accuracy in the pilot unit has improved against baseline, messages have been revised after tests with unfamiliar or sceptical audiences, and the stakeholder review records hard choices alongside goodwill.

    Days 91–180

    Phase 3 · Embed and scale

    Make restatement and stakeholder review standard for every unit and every major plan.

    • Require each unit head to restate the strategy in each planning cycle.
    • Train managers with internal communications to translate and test messages themselves.
    • Make a documented stakeholder review a condition for announcing any major plan.
    • Translate restatements into the regional languages teams actually work in.

    Deliverable: A restatement library by unit and language, and a stakeholder review template attached to major plans.

    Gate: Every unit has a tested restatement on file, and every major plan announced in the period went through a documented stakeholder review.

    Month 7 onwards

    Phase 4 · Sustain and renew

    Keep translation faithful to the source as the strategy changes.

    • The CEO re-reads the full strategy and its reasoning each quarter and checks restatements against it.
    • Repeat the recall test across levels, regions and languages each year.
    • Refresh restatements whenever the strategy shifts.
    • Review a sample of messages for dilution, checking that trade-offs and risks survived.

    Deliverable: An annual translation quality report.

    Gate: Restatement accuracy holds across regions after a strategy change, and the revision log shows testing is still finding gaps.

    Governance

    sponsor: The CEO, because only the author of the strategy can judge whether a translation keeps its meaning.

    lead: The head of internal communications, working with the strategy team.

    forum: Monthly in the leadership meeting for message revisions; quarterly at the board for restatement accuracy and stakeholder review coverage.

    decision_rights: The lead can send back any restatement that fails front-line testing; changes to the substance of the strategy, and any decision to proceed with a plan despite a hard stakeholder finding, go to the CEO.

    Cadence

    Weekly: Managers link one piece of the week's work to a strategic priority, in the team's own words.

    Monthly: A front-line test session where staff say what the strategy changes in their work that month.

    Quarterly: The CEO returns to the full strategy and checks restatements against it, and the board receives the translation KPIs.

    Annually: A recall survey across levels, regions and languages, followed by a refresh of the restatement library.

    By company stage

    startup

    The founder explains the strategy without slides at the all-hands and asks each person to say it back in their own words. Testing happens in conversation each month while everyone still works closely together.

    scaleup

    Unit heads write restatements in their teams' language, and internal communications tests them with front-line staff before release. Major plans carry a short stakeholder review that names who gains and who loses.

    enterprise

    Restatements are maintained in each working language and region, and recall is surveyed across the group every year. The board asks for stakeholder reviews on major plans and checks that front-line understanding matches what was presented to it.

    Success looks like

    • Front-line staff explain the priorities in their own words, including what the company has chosen not to do.
    • Strategy messages are revised after testing, and leaders treat a failed test as useful.
    • Major plans are announced with their effects on every stakeholder group, critics included, already worked through.

    MEASUREMENT AND LIMITS

    What to watch

    Strategy restatement accuracy

    Share of sampled front-line staff who can state the company's top priorities in their own words, scored against the board's version.

    Message revision rate

    Number of strategy messages revised after front-line testing, logged by internal communications, as a sign that testing is real.

    Clarity of direction

    Survey items on whether people understand how their work connects to strategy, tracked by level and region.

    Stakeholder review coverage

    Share of major plans that went through a documented review of effects on all stakeholder groups before launch.

    Failure modes

    • Translation becomes dilution: the message is simplified until its substance is gone.
    • Front-line testing is staged with friendly audiences, so failures of understanding are never found.
    • Goodwill to all is used to avoid hard choices that some stakeholders will dislike.

    Execution risks

    • Translation slides into dilution.: Staff can repeat the priorities but cannot say what the company has chosen to stop doing. Mitigation: The CEO checks every restatement against the source, trade-offs and risks included.
    • Front-line tests are staged with friendly audiences.: Every test passes and the message revision rate falls towards nothing. Mitigation: Let internal communications, not the unit head, choose test audiences, and include sceptics and unfamiliar teams.
    • Goodwill to all becomes a reason to avoid hard choices.: Stakeholder reviews list only benefits, and decisions are delayed to keep every group content. Mitigation: Require each review to name who loses and why the plan proceeds anyway.
    • The message changes by region or language, or leaders tell different versions.: Recall is lower in regions working in languages other than head office's, or different leaders describe different priorities. Mitigation: Translate with local managers into working languages, and compare senior leaders' messages against the source each quarter.