Daily Rambam · Startup Mensch · Deep-Dive
Mishneh Torah, Rebels 2
Hook
Founders, let’s cut through the noise. You’re building something from nothing. Every decision is a tightrope walk between audacious vision and the brutal reality of execution. You're juggling investor demands, team morale, market pressures, and the relentless pursuit of growth. Amidst this storm, there's a quiet, insidious challenge that can derail even the most promising ventures: the erosion of trust. Not just trust from your customers or investors, but trust within your own organization. It’s the subtle shift from a culture of shared purpose to one of suspicion, where good intentions are questioned, and decisions are second-guessed.
This Mishneh Torah passage, "Rebels 2," speaks directly to this founder dilemma. It grapples with the authority of courts, the weight of precedent, and the imperative to adapt while maintaining fidelity to foundational principles. Think about your company’s early days. You made decisions based on the best information and understanding you had at the time. Perhaps you implemented a specific hiring practice, a sales strategy, or a product roadmap. These were your “decrees” and “edicts,” born from the wisdom of your founding team.
Now, fast forward. Your company has scaled. New leaders have joined, bringing fresh perspectives. The market has evolved, rendering some of your initial assumptions obsolete. Your team is larger, more diverse, and potentially has different interpretations of what’s best for the company. This is where the tension arises. A new set of leaders, or even a significant faction within your existing team, might look at your original decisions and say, "We see a better way." They might have new data, new methodologies, or simply a different vision.
The core question this text forces us to confront is: When and how should a new generation of leadership or a new perspective within a company be allowed to challenge and potentially overturn the decisions of the founders or earlier leadership?
This isn't about petty power struggles. It's about the fundamental question of organizational evolution and the delicate balance between honoring the past and boldly shaping the future. If you rigidly adhere to every past decision, you risk stagnation, becoming brittle and unable to adapt. Your company becomes a museum of past glories, not a dynamic engine of future success. On the other hand, if you allow every decision to be overturned on a whim, you create chaos. There’s no stability, no foundation, and trust evaporates. Employees will feel their work is constantly being undermined, leading to cynicism and disengagement. Investors will question your strategic coherence.
The Mishneh Torah, in its wisdom, provides a framework for navigating this. It’s not a simple "yes" or "no." It’s a nuanced understanding of when established practices can be challenged, and under what conditions. The text differentiates between laws derived through interpretation ("principles of exegesis") and those established as safeguards ("decrees" or "edicts"). This distinction is crucial for founders. Your core mission, your fundamental values – these are like the bedrock of Torah law. But the specific strategies, operational procedures, and even some product features you implemented early on – these are more akin to the "decrees" and "edicts." They were designed to protect and advance the core, but they are not immutable.
Consider a startup that initially focused on a niche, high-touch customer service model. This was their "decree" to safeguard the value proposition. As they grew, this model became unsustainable and a bottleneck to scaling. A new VP of Operations, armed with data on customer satisfaction across different service tiers and operational costs, proposes a more scalable, technology-driven approach. Do they just scrap the old model? Or do they apply the principles from Rebels 2?
The text states, "The following rules apply when a court issued a decree, instituted an edict, or established a custom... The later court does not have this authority unless it surpasses the original court in wisdom and in its number of adherents." For a startup, "wisdom" translates to data, market insight, and strategic foresight. "Number of adherents" isn't just about headcount; it's about the collective buy-in and support from key stakeholders – the leadership team, the board, and crucial functional heads.
This passage also highlights the concept of a "safeguard." Sometimes, early decisions are made not because they are the best way, but because they are the safest way to avoid a known pitfall. For example, a startup might initially forbid any external data sharing for competitive reasons. This is a safeguard. As the company matures and partners with other entities, this strict prohibition can become a barrier to collaboration and innovation. The text discusses how such safeguards, if they become too onerous, might be temporarily suspended, but not fundamentally uprooted from the "Scriptural Law" of the company.
The real founder dilemma this text speaks to is: How do you foster an environment where necessary evolution and innovation can occur, allowing new insights to challenge established norms, without creating instability or undermining the foundational principles and trust that are essential for long-term success? It’s about creating a mechanism for legitimate challenge and adaptation, a process for discerning which "decrees" are foundational and which are merely scaffolding, and ensuring that the "wisdom" and "adherence" of the new perspective are truly greater than the original. This is not just an ethical consideration; it’s a strategic imperative for sustainable growth and resilience.
Full Experience in the App
Listen. Chat. Go deeper.
Audio playback, interactive chevruta, Hebrew tools, and every daily learning track — only in Derekh Learning.
Text Snapshot
"When, using one of the principles of exegesis, the Supreme Sanhedrin derived a law through their perception of the matter and adjudicated a case accordingly, and afterwards, another court arose and they perceived another rationale on which basis, they would revoke the previous ruling, they may revoke it and rule according to their perception. This is reflected by Deuteronomy 17:9: 'To the judge who will be in that age.' This indicates that a person is obligated to follow only the court in his own generation.
The following rules apply when a court issued a decree, instituted an edict, or established a custom and this practice spread throughout the Jewish people and another court arose and sought to nullify the original order and eliminate the original edict, decree, or custom. The later court does not have this authority unless it surpasses the original court in wisdom and in its number of adherents. If it surpasses the original court in wisdom, but not in the number of adherents, or in the number of adherents, but not in wisdom, it cannot nullify its statements.
Even if the rationale for which the original court instituted the decree or the edict is nullified, the later court does not have the authority to negate their statements unless they are greater.
What is implied? If a court sees that it is necessary to strengthen the faith and create a safeguard so that the people will not violate Torah law, they may apply beatings and punishments that are not sanctioned by Torah. They may not, however, establish the matter for posterity and say that this is the halachah. Similarly, if they saw that temporarily it was necessary to nullify a positive commandment or violate a negative commandment in order to bring people at large back to the Jewish faith or to prevent many Jews from transgressing in other matters, they may do what is necessary at that time."
Analysis
Insight 1: The Distinction Between Foundational Law and Expedient Decrees – A Matter of Strategic Pillars vs. Operational Tactics
The Mishneh Torah, in its opening lines, draws a critical distinction: "When, using one of the principles of exegesis, the Supreme Sanhedrin derived a law... and afterwards, another court arose and they perceived another rationale... they may revoke the previous ruling." This applies to laws derived through interpretation, akin to your company's core mission, values, and fundamental strategic direction. These are the bedrock principles, the "why" behind your existence. The text then pivots: "The following rules apply when a court issued a decree, instituted an edict, or established a custom... The later court does not have this authority unless it surpasses the original court in wisdom and in its number of adherents." These are the "decrees," "edicts," and "customs" – the operational policies, specific strategies, and even product features that were implemented to uphold the foundational principles.
For a founder, this translates directly to differentiating between your company’s immutable core values and its changeable operational strategies. Your core mission statement, your ethical guidelines, your commitment to customer well-being – these are your "principles of exegesis." They are derived from a deep understanding of your purpose. Changing these requires a fundamental re-evaluation of your company's identity and should be rare and exceptionally well-justified. However, the specific hiring policies, the marketing channels you initially prioritized, the product development cycles, or the sales compensation structures – these are your "decrees" and "edicts." They were the best tools you had at that time to achieve your core mission. As the company evolves, as market conditions shift, and as you gain more data and experience, these "decrees" are subject to review and potential change.
The key takeaway here is about strategic agility without identity erosion. You must empower your organization to adapt its tactics while remaining steadfast on its strategic pillars. The conditions under which these "decrees" can be changed are significant: the challenger must demonstrate superior "wisdom" (data, insight, foresight) and "number of adherents" (organizational buy-in, support). This prevents capricious changes and ensures that any proposed shift is well-supported and demonstrably better.
Case Study: Consider Netflix. Their initial "decree" was DVD-by-mail. This was a brilliant operational tactic designed to achieve their core mission of providing convenient entertainment access. It was not their foundational "principle of exegesis," which was about delivering entertainment. When streaming technology emerged, it presented a new "rationale." A new "court" (the leadership team, driven by data and foresight) recognized that streaming surpassed the DVD model in wisdom (scalability, cost-efficiency, global reach) and rapidly gained "adherents" (customer adoption). They didn't revoke the core mission; they revoked the decree of DVD-by-mail and embraced the new "rationale" of streaming. The transition was not without its challenges (remember the Qwikster debacle, a poorly executed "decree" change), but the underlying principle of adapting their operational tactics to their core mission of entertainment delivery remained intact. Had they rigidly clung to the DVD model, believing it to be an immutable "law," they would have been quickly outmaneuvered by competitors who embraced the new "wisdom."
Decision Rule: Operational tactics (decrees, edicts) can and should be revised when a new approach demonstrably offers superior wisdom and has significant organizational buy-in, provided these changes do not contradict the company's core mission and values (principles of exegesis).
Metric Proxy: Track the rate of adoption and success of new operational initiatives vs. the persistence of older, potentially outdated ones. A high success rate for new initiatives, coupled with a willingness to sunset underperforming older ones, indicates healthy adaptation. KPI Proxy: Percentage of strategic initiatives launched in the last 18 months that met or exceeded their primary success metrics, divided by the total number of initiatives launched in the same period.
Insight 2: The "Safeguard" Principle – When Expediency Demands Temporary Deviation for Long-Term Adherence
The Mishneh Torah introduces a fascinating concept: "If a court sees that it is necessary to strengthen the faith and create a safeguard so that the people will not violate Torah law, they may apply beatings and punishments that are not sanctioned by Torah. They may not, however, establish the matter for posterity and say that this is the halachah. Similarly, if they saw that temporarily it was necessary to nullify a positive commandment or violate a negative commandment in order to bring people at large back to the Jewish faith or to prevent many Jews from transgressing in other matters, they may do what is necessary at that time." This is the "safeguard" principle – the idea that sometimes, to ensure long-term adherence to core principles, temporary measures that might seem to deviate from established norms are permissible, even necessary.
For a founder, this is about understanding that sometimes, to preserve the long-term health and adherence to your company's core values and mission, you might need to implement policies that are intentionally temporary or even seem counterintuitive in the short term. These are not changes to your fundamental "laws," but rather emergency interventions designed to prevent a greater transgression or to re-establish adherence. The key is that these are temporary and for the purpose of "strengthening faith" or "preventing transgression" in the broader sense.
This can manifest in various ways in a startup. Imagine a scenario where a company's core value is “integrity.” However, a new, aggressive competitor is engaging in ethically questionable but legally permissible tactics that are rapidly stealing market share. The temptation might be to retaliate in kind. The Mishneh Torah would suggest that such a response, if it compromises the core value of integrity, is not permissible, even if it’s a "safeguard" against losing market share. Instead, the "safeguard" principle suggests a different approach: perhaps a temporary, more aggressive marketing campaign that highlights the company's integrity and the competitor's questionable practices, or a temporary relaxation of a non-core policy to free up resources for a focused competitive response. The text explicitly states, "They may not, however, establish the matter for posterity and say that this is the halachah." This means these "safeguard" measures cannot become permanent policy. They are crisis tools, not new operating procedures.
Another example: a startup that values “collaboration” might find itself in a situation where a critical project is stalled due to internal disagreements between two key departments. The "safeguard" principle, applied to business, might mean the founder steps in and makes a temporary, decisive executive order to push the project forward, even if it means overriding the usual collaborative process for that specific instance. The goal is to prevent the project from failing and causing broader damage (the "violation of a negative commandment"), thereby enabling future adherence to the collaboration value. The founder must then, with urgency, work to resolve the underlying conflict so the temporary measure can be rescinded.
Case Study: Consider Amazon's early days. Jeff Bezos’s relentless focus on customer obsession, while a core value, sometimes led to operational "decrees" that seemed harsh or inefficient for employees. For example, the infamous two-pizza rule for meetings, while promoting efficiency, could also be seen as a "safeguard" against lengthy, unproductive discussions that would detract from the core mission of rapid innovation and customer service. It was a temporary measure to ensure focus. Similarly, Amazon's initial aggressive pricing strategies, even if they strained short-term profitability, were a "safeguard" to capture market share and prevent competitors from dominating. The "safeguard" was to ensure long-term customer adherence by offering unparalleled value, even at a short-term cost. Crucially, these were not presented as the permanent "halachah" of how Amazon would operate forever, but as necessary steps to achieve a greater good – customer obsession and market leadership.
Decision Rule: Temporary deviations from standard operating procedures or policies (safeguards) may be authorized in extraordinary circumstances to protect core company values, prevent significant harm, or ensure future adherence to fundamental principles. These deviations must be clearly defined as temporary, with a clear exit strategy, and must not alter the company’s foundational mission or ethical framework.
Metric Proxy: Measure the impact of these temporary interventions on key metrics they were designed to protect. For example, if a temporary measure was implemented to prevent customer churn, track churn rates before, during, and after the intervention. KPI Proxy: Reduction in the targeted negative metric (e.g., customer churn, project delays, ethical breaches) during the period of the safeguard implementation, compared to a projected baseline without the intervention.
Insight 3: The Nuance of Authority – Wisdom and Adherence as the Arbiter of Change
The text's emphasis on the conditions for overturning previous rulings is profound: "The later court does not have this authority unless it surpasses the original court in wisdom and in its number of adherents. If it surpasses the original court in wisdom, but not in the number of adherents, or in the number of adherents, but not in wisdom, it cannot nullify its statements." This is the core mechanism for institutional change and stability. It’s a sophisticated model for ensuring that progress is not arbitrary but is driven by genuine improvement and broad acceptance.
For a founder, this provides a critical framework for managing organizational change and succession. When new ideas or leadership emerge, they must be evaluated not just on their brilliance, but on their practical applicability and their ability to gain traction. "Wisdom" in a business context translates to data-driven insights, market understanding, strategic foresight, and operational expertise. "Number of adherents" isn't about popularity contests; it’s about demonstrated support from critical stakeholders – the executive team, key department heads, influential employees, and even the board. A brilliant idea that only a handful of people understand or support will not, and should not, overturn established practices.
This insight directly addresses the founder’s role in fostering a culture of healthy challenge. You want your team to bring forward new ideas. But you also need to ensure that those ideas are rigorously vetted and have the potential to truly improve the organization. The text warns against situations where a court might be "greater in wisdom, but not in the number of adherents, or in the number of adherents, but not in wisdom." This perfectly describes a situation where a charismatic but strategically flawed leader has gained popularity, or where a technically brilliant but practically unworkable solution is proposed by an isolated expert. Neither scenario should be allowed to overturn established, functional practices without demonstrating both superior insight and broad organizational support.
This also has implications for how founders transition leadership. A successor or a new executive team must prove they possess both the strategic acumen ("wisdom") and the ability to rally the organization ("number of adherents") to justify significant changes to the founder's legacy. It’s a safeguard against both radical, unsupported disruption and stagnant, entrenched mediocrity.
Case Study: Consider Apple under Steve Jobs's return. Jobs possessed immense "wisdom" regarding product design, user experience, and market vision. When he returned, he had the "adherents" of a significant portion of the company's loyalists and a board desperate for a turnaround. He was able to overturn many of the previous management's "decrees" (e.g., streamlining the product line, focusing on key innovative projects) because he demonstrably surpassed them in both wisdom and adherents. Conversely, consider a startup where a popular, long-tenured engineer proposes a radical, unproven technology shift. They might have many "adherents" among junior engineers who admire them, but if their "wisdom" (in terms of market viability, cost-effectiveness, and strategic fit) is not demonstrably superior to the current, functioning product strategy, their proposal should not overturn the existing "edicts."
Decision Rule: Proposals for significant organizational change or the overturning of established policies must demonstrate a clear superiority in both strategic insight (wisdom) and the capacity to garner widespread organizational support (number of adherents) compared to the existing practice. Proposals lacking in either dimension should not supersede the current status quo.
Metric Proxy: Track the success rate of new strategic initiatives proposed by individuals or teams who are challenging existing norms. This success rate should be evaluated against the metrics of the existing practices they aim to replace. KPI Proxy: The ratio of successful strategic initiatives (meeting defined success criteria) that involved overturning prior decisions, to the total number of such initiatives proposed, weighted by the degree of demonstrated wisdom (e.g., measured by ROI, market share gain) and adherence (e.g., measured by cross-functional adoption rates, employee engagement scores related to the change).
Policy Move
Policy: The "Wisdom & Adherence" Review Board for Significant Policy Revisions
Policy Draft:
I. Purpose: This policy establishes a formal process for the review and approval of proposed significant revisions to existing company policies, decrees, or established customs. The aim is to ensure that any such changes are made with careful consideration, are demonstrably superior to the current practice, and have broad organizational support, in accordance with the principles outlined in Mishneh Torah, Rebels 2.
II. Scope: This policy applies to any proposed change that:
- Significantly alters a core operational process.
- Impacts a substantial portion of the workforce or customer base.
- Introduces a new strategic direction or significantly deviates from an existing one.
- Overturns a policy established more than 12 months prior.
III. The "Wisdom & Adherence" Review Board: A standing "Wisdom & Adherence" Review Board (WARB) shall be convened to evaluate proposed significant policy revisions. The WARB will comprise:
- The CEO (or designated executive sponsor).
- The Chief Legal Officer.
- The Chief Financial Officer.
- The Head of Human Resources.
- Two senior leaders from departments directly impacted by the proposed change, rotating quarterly.
- The proposer of the policy revision.
IV. Submission and Review Process:
Proposal Submission: Any individual or team seeking to propose a significant policy revision must submit a formal proposal to the WARB. The proposal must clearly articulate:
- The current policy or practice being challenged.
- The specific rationale for the proposed change, detailing the "wisdom" (data, market analysis, strategic foresight, ROI projections, risk assessment) that supports the revision.
- The proposed new policy or practice.
- The anticipated benefits and drawbacks of the proposed change.
- Evidence of "adherence": demonstrated support from key stakeholders, including potential impact assessments on different departments and proposed strategies for broader organizational buy-in.
- A clear designation of the proposed change as either a permanent policy update or a temporary safeguard, with defined duration and exit criteria if temporary.
WARB Evaluation Criteria: The WARB will assess proposals based on the following:
- Superior Wisdom: Does the proposed change present demonstrably superior data, insights, strategic advantage, or financial benefit compared to the current policy? Is the risk assessment robust?
- Sufficient Adherence: Is there evidence of broad organizational support and buy-in from relevant stakeholders? Is there a credible plan to achieve wider acceptance? Does the proposal consider potential resistance and outline mitigation strategies?
- Alignment with Core Values: Does the proposed change align with the company's foundational mission and core values?
- Feasibility and Implementation: Is the proposed change practically implementable within the company's resources and capabilities?
Decision Making: The WARB will vote on the proposal. A proposal is approved if it receives a unanimous vote. If the vote is not unanimous, the proposal may be revised and resubmitted, or it may be escalated to the Board of Directors for final decision if the proposer and at least one WARB member advocate for escalation. The decision will be clearly communicated to the proposer and relevant stakeholders.
V. Implementation: Upon approval, the WARB will oversee the implementation of the revised policy. This includes developing communication plans, training programs, and monitoring mechanisms to ensure successful adoption and measure its effectiveness against the projected benefits.
VI. Temporary Safeguards: If a proposal is for a temporary safeguard, the duration, specific objectives, and exit criteria must be clearly defined and approved by the WARB. Regular reviews of temporary safeguards will be conducted to ensure they remain necessary and are discontinued once their objectives are met.
Implementation Steps:
- Board Approval: Present this policy to the Board of Directors for formal approval and endorsement.
- WARB Formation: Identify and appoint the initial members of the WARB. Establish a rotation schedule for departmental representatives.
- Develop Proposal Template: Create a standardized template for policy revision proposals to ensure all necessary information is provided.
- Communication and Training: Announce the new policy to all employees, explaining its purpose and process. Conduct training sessions for managers and employees on how to submit proposals and what to expect during the review process.
- Pilot Program (Optional but Recommended): Initially, pilot the WARB process with a few non-critical policy changes to refine the workflow and gather feedback before full rollout.
- Establish Review Cadence: Set a regular schedule for WARB meetings (e.g., monthly or bi-monthly) to ensure timely review of proposals.
- Documentation and Archiving: Maintain a clear record of all submitted proposals, WARB decisions, and implemented changes.
Potential Pushback and Mitigation:
"This will slow down innovation and decision-making."
- Mitigation: Emphasize that this policy is designed to ensure that changes are better, not just faster. Highlight that it prevents costly mistakes from poorly considered changes. Frame it as a quality control mechanism for strategic evolution. For truly urgent, minor operational tweaks, delegate authority to department heads with clear guidelines.
"It's too bureaucratic and will stifle individual initiative."
- Mitigation: Clearly define what constitutes a "significant" policy change requiring WARB review. Encourage minor adjustments and local decision-making within defined parameters. Position the WARB as a mechanism to empower well-reasoned, well-supported proposals, not to block them. The inclusion of the proposer in the board meetings ensures their voice is heard directly.
"The WARB will be dominated by established interests, making it hard for new ideas to gain traction."
- Mitigation: Ensure diverse representation on the WARB, including rotating members from different departments. The criteria for "wisdom" and "adherence" are objective, data-driven assessments, not simply majority opinion. The escalation path to the Board of Directors provides an avenue for challenging potentially biased WARB decisions. The clear articulation of "wisdom" (data, ROI) required in the proposal itself mitigates subjective bias.
"What about temporary 'safeguards' that are needed quickly?"
- Mitigation: The policy explicitly includes a section for temporary safeguards, allowing for expedited review and implementation for urgent situations, provided they are clearly defined as temporary with exit criteria. The CEO or designated sponsor can authorize immediate, but temporary, measures with a mandate to bring it before the WARB for formalization or discontinuation.
Board-Level Question
Question: How do we ensure our organization can adapt to evolving market realities and internal insights without undermining the foundational principles and trust that define our long-term success?
The question, "How do we ensure our organization can adapt to evolving market realities and internal insights without undermining the foundational principles and trust that define our long-term success?" is paramount for any board of directors, particularly for a growing startup. It directly addresses the tension inherent in organizational evolution, a tension that the Mishneh Torah passage "Rebels 2" so eloquently dissects. The core challenge for leadership is to foster a dynamic environment where new ideas can emerge and challenge existing norms, but to do so in a way that preserves the company’s identity, stability, and the trust that underpins all its relationships – with employees, customers, and investors.
The Mishneh Torah differentiates between immutable laws derived from fundamental principles and temporary decrees or edicts enacted for specific purposes. Applying this to a business context, the "foundational principles" are akin to a company's mission, vision, and core values – the enduring "why" behind its existence. The "decrees" and "edicts" are the operational policies, strategies, and tactical decisions that were implemented to serve those principles at a particular point in time. The danger lies in treating operational tactics as if they were foundational laws, thereby stifling necessary adaptation, or conversely, in allowing foundational principles to be eroded by the constant flux of tactical changes. The question, therefore, probes the mechanisms by which the organization can discern between these two, and manage the tension between them.
Different answers to this question imply vastly different strategic paths for the company. If the answer leans towards rigidity, prioritizing stability and established practices above all else, the company risks becoming obsolete, unable to capitalize on new market opportunities or respond to competitive threats. It might project an image of steadfastness, but internally, it could foster a culture of stagnation and disengagement as employees see opportunities for improvement being ignored. This approach implicitly values the "original court" above all else, even when "wisdom" and "adherence" might clearly favor a new perspective. This can lead to a brittle organization, susceptible to disruption from more agile competitors.
Conversely, if the answer leans towards radical flexibility, where every decision is constantly up for review and change is the only constant, the company risks losing its identity and unraveling the trust it has built. Employees will feel a lack of direction, investors will question strategic coherence, and customers may become confused by a shifting value proposition. This approach, while appearing innovative, can lead to chaos, inefficiency, and a breakdown of operational discipline. It fails to recognize the wisdom in established practices and the importance of consistent adherence to core principles. This represents a scenario where "another court arose and sought to nullify the original order" without meeting the crucial criteria of superior "wisdom and number of adherents."
A balanced approach, aligned with the text's nuanced wisdom, suggests that adaptation should be strategic and principled. It requires a clear framework for evaluating change, one that assesses not only the merits of new ideas ("wisdom") but also their potential for broad acceptance and integration ("number of adherents"). This fosters a culture of continuous improvement where evolution is encouraged but must be well-justified and aligned with the company's enduring purpose. The board's role is to ensure that such a framework exists and is effectively implemented, safeguarding both the company's future adaptability and its foundational integrity.
Takeaway
Founders, your company’s journey is a constant negotiation between honoring precedent and embracing the future. The Mishneh Torah’s "Rebels 2" offers a powerful, pragmatic guide: Don't mistake your operational tactics for your core mission. Your foundational values are immutable; your strategies and policies are subject to rigorous review. When change is proposed, demand demonstrable superiority in both insight and support – that’s the twin engine of legitimate progress. Build a system, like the proposed "Wisdom & Adherence" Review Board, that enforces this discipline. It’s not about slowing down; it’s about ensuring every change makes you stronger, more resilient, and more aligned with your ultimate purpose. This isn’t just good governance; it’s the bedrock of sustainable, trust-based growth.
derekhlearning.com