How ISKCON Can Build Unity Without Enforcing Uniformity

If you serve in an ISKCON temple or congregation and wonder whether a disagreement threatens the movement’s unity, do not begin by asking which side is more loyal. Ask what kind of disagreement it is. A question about foundational teaching is not the same as a dispute over a festival schedule, a budget, a language choice, or a local outreach method. When those categories blur, every difference starts to feel existential.

ISKCON is already treating unity in diversity and its institutional future as connected questions. The phrase becomes useful when it is translated into practice: what all centers owe one another, what local communities may adapt, who has authority to decide, how a decision can be reviewed, and how responsibility passes to the next generation.

Separate principle, policy, and preference

The simplest way to reduce needless conflict is to stop treating unity as a single undifferentiated demand. Most institutional disagreements contain one or more of three elements:

• Principle: A foundational teaching, spiritual commitment, ethical duty, or movement-wide standard. Principle is not changed merely because a local majority wants another arrangement. It should be interpreted through authorized teachings and the institution’s legitimate spiritual authorities.
• Policy: A rule adopted to apply principle under particular conditions. Policy requires a clearly identified decision-maker, a stated jurisdiction, and a way to review whether it still serves its purpose.
• Preference: A local choice about style, language, presentation, scheduling, or method. Preference normally belongs close to the devotees and communities affected by it.

A single matter can contain all three. A festival may have a shared spiritual purpose, an institutional policy governing safety or finances, and local choices about language and presentation. The answer is not to force the entire matter into one category. Separate its parts and assign each part to the right level.

This distinction protects ISKCON in both directions. It prevents a local preference from being moralized into a test of devotion, and it prevents a foundational commitment from being dismissed as cultural variation. It also gives a meeting chair a practical rule: before debate begins, record the category of the question, the authority responsible for it, and the teaching or policy that governs it.

The common center should be explicit but not improvised. For ISKCON, fidelity to A.C. Bhaktivedanta Swami Prabhupada’s teachings belongs at that center. A short institutional covenant can point devotees to the authorized teachings, shared purpose, standards of conduct, and governing responsibilities without trying to replace the books with managerial slogans. The point is to give members a reliable map of what is binding and where legitimate diversity begins.

Make authority legible before a conflict begins

People can live with many decisions they would not personally have chosen when they understand who decided, under what authority, after hearing which concerns, and with what opportunity for review. Suspicion grows when those answers appear only after a controversy has started.

Spiritual organizations cannot borrow a corporate chart and call the work complete. Authority must be exercised as seva. Yet seva still needs defined limits, competent administration, records, recusal when interests conflict, and accountability for results. Humility does not require opacity, and respect for authority does not make a fair process unnecessary.

The following matrix is a working template, not a description of current ISKCON law. Each community should replace the general labels with the office actually authorized under its governing arrangements and local jurisdiction.

Kind of decision	Default decision level	What members should be able to see
Foundational teaching or a shared spiritual standard	The competent movement-wide spiritual and governing authority	The authoritative basis, scope of the decision, responsible office, and whether clarification or review is available
Safeguarding or a serious ethical allegation	A properly mandated process with trained personnel and conflict safeguards	How concerns are received, how decision-makers are screened for conflicts, what protection is available, and how findings may be reviewed
Property, finance, or binding institutional obligations	The legally and institutionally responsible authority	Approval, material conflicts of interest, reporting duties, and the limits placed on the decision
Regional coordination, education, or leadership development	The relevant regional body	Its jurisdiction, reporting relationship, objective, and review process
Local outreach, language, schedules, and cultural presentation	The local leadership or council closest to the affected community	The local objective, responsible person, constraints, and point at which the choice will be evaluated

For any consequential decision, publish a short decision note containing six items: the question decided, the person or body authorized to decide it, the inputs considered, the reason for the decision, its scope, and the route for review. This need not become a long legal document. A clear page is often more useful than a vague announcement followed by weeks of explanation.

If nobody can identify the responsible authority, the decision is usually not ready for permanent implementation. An urgent safety or legal obligation is different: take the necessary protective step, mark it as an interim measure, and send the larger question to the proper process. Emergency action should not quietly become permanent policy through inertia.

Turn conflict into a process, not a loyalty contest

Disagreement is not automatically disunity. The greater danger is an unmanaged dispute in which devotional standing, personal networks, institutional office, and factual claims become entangled. Once that happens, people argue about motives instead of resolving the question.

1. State the issue in one sentence. Name the decision required and the people directly affected. If the disagreement cannot be stated without accusing someone’s character, it has not yet been defined well enough.
2. Classify each part. Mark it as principle, policy, preference, or a combination. Identify the authorized teaching, rule, mandate, or local responsibility that applies.
3. Separate facts from interpretations. Record what is known, what is disputed, and what is a judgment. Devotional language and public popularity are not substitutes for evidence.
4. Check authority and conflicts. Confirm that the decision-maker has jurisdiction. A person with a material personal interest should disclose it and recuse where the applicable process requires it.
5. Hear the people directly affected. Give them a defined way to present relevant information. Public campaigning should not replace direct fact-finding.
6. Decide at the lowest legitimate level. Local matters should not be escalated merely to recruit a powerful ally, while movement-wide obligations should not be privatized as local preference.
7. Give reasons and define review. A written outcome should explain its basis and scope. Review should focus on material new information, a serious process failure, or action beyond the decision-maker’s authority – not endless relitigation because one side dislikes the result.

Confidentiality must also be distinguished from secrecy. Personal allegations and sensitive evidence may require privacy. The existence of the process, its safeguards, the authority responsible, and an appropriately stated outcome should still be intelligible to the community. Where abuse, immediate danger, illegality, or credible retaliation is alleged, protection and applicable local duties come before informal reconciliation or concern about appearances.

Once a matter is closed, leadership should state what the decision does and does not establish. That boundary prevents a narrow ruling from being turned into a universal precedent, and it prevents rumor from filling the space left by silence.

Build succession before a vacancy forces it

An institution dependent on a few experienced personalities can appear united until one of them becomes unavailable. The weakness then surfaces all at once: undocumented responsibilities, informal permissions, relationships known to only one person, and unresolved questions that were being held together by personal authority.

Every important office should therefore have a handoff file. It should contain:

• The purpose of the role, its authority, and its limits.
• Recurring decisions, scheduled responsibilities, and outstanding commitments.
• The teachings, policies, governing instruments, and legal duties relevant to the office.
• Open risks, unresolved disputes, and decisions that need review.
• The people being trained to assist or succeed, with the work they have already practised.
• A secure plan for transferring access and records. Passwords and other secrets should be transferred through an appropriate secure method, not copied into a general handoff document.

Succession training should move through observation, supervised responsibility, independent responsibility, and review. A title conferred without prior responsibility creates dependence on advisers behind the scenes. Responsibility given without review creates avoidable risk. The aim is not to produce a replica of the outgoing leader; it is to prepare someone who understands the mission, exercises sound judgment, accepts correction, and can account for decisions.

The same discipline helps a community remain united when devotees follow different authorized spiritual guides. Personal spiritual relationships deserve respect, but the duties attached to an institutional office should not change with factional allegiance. A temple president, educator, trustee, or council member should be accountable to the responsibilities of that role and to the shared institutional covenant.

The phrase “Books are the Basis” points to a stable inheritance, but a book-centered movement still needs disciplined institutional memory. Keep three layers distinct: authorized spiritual teachings, current policies, and past decisions with their reasons and limits. Mixing them makes temporary policy look eternal or allows a foundational principle to be treated as optional. Clear records help future leaders remain faithful without pretending that every administrative choice is timeless.

Use this five-question unity test

Before approving a proposal or escalating a dispute, put it through this test:

1. What must remain shared? Name the precise teaching, duty, standard, or institutional bond involved.
2. What may legitimately vary? Identify the local method, cultural form, or practical preference that does not need movement-wide uniformity.
3. Who has authority to decide? Name the office or body, its jurisdiction, and the mandate under which it acts.
4. What makes the process fair? Specify how relevant people are heard, how conflicts are handled, what reasons will be recorded, and what review is available.
5. How will the result be evaluated? Define the intended outcome and the point at which the decision will be reviewed, changed, retained, or allowed to expire.

If a committee cannot answer these questions, it has found an institutional gap rather than proof that one faction must defeat another. Fix the missing mandate, policy, record, or review mechanism. Do not cover a structural weakness with an appeal for harmony.

You do not have to settle ISKCON’s entire future at the next temple meeting. Choose one recurring disagreement. Separate its principle, policy, and preference; identify the legitimate decision-maker; record the reason for the outcome; and set a review point. Unity becomes durable when devotees know what holds them together and can see that authority is being exercised as accountable service. That is how a worldwide movement can remain recognizably one without making every community identical.

References

• Dandavats – Today’s Featured Video: Unity in Diversity & The Future of ISKCON | HG Govardhan Prabhu

---