From Seed to Canopy: Growing Core Values for a Future We Can't Yet See

Every organization, team, or community that hopes to last beyond a single product cycle faces the same quiet challenge: how do you build a set of values that will still make sense twenty years from now, when the market, the technology, and the people have all changed? The easy answer—write down some nice-sounding principles and hang them on a wall—doesn't work. We've seen too many mission statements that feel hollow within a year, too many 'core values' that get quietly abandoned the first time they conflict with a quarterly target. This guide is for leaders, founders, and anyone responsible for shaping a group's ethical DNA. Our goal is to give you a practical, honest framework for growing values that can adapt without breaking—values that function like a living canopy, not a concrete pillar.

The metaphor matters: a seed contains the potential of a tree, but it needs the right soil, water, and light to grow. It also needs to be able to bend in the wind without snapping. The values we plant today must be strong enough to guide decisions, yet flexible enough to evolve as we learn what the future actually looks like. This is not about crafting perfect words; it's about building a process for continuous ethical growth.

Field Context: Where Values Actually Get Tested

Values don't live in a handbook. They live in the moments when something goes wrong—when a deadline looms and the easy shortcut looks tempting, when a customer complains and the refund policy is unclear, when a team member suggests something that feels off but you can't quite articulate why. These are the real testing grounds. In our experience working with dozens of early-stage teams and established departments, the most revealing context for values is not the annual retreat but the Tuesday afternoon crisis.

Consider a typical scenario: a small product team has a core value of 'transparency.' They've written it into their charter, they mention it in onboarding. Then a major client asks them to sign a non-disclosure agreement that would prevent them from sharing certain metrics with the rest of the company. Suddenly, 'transparency' butts up against 'customer trust' and 'business practicality.' The team has to decide which value takes precedence, or how to honor both. This is where the seed either grows roots or gets pulled out.

Another common context is the hiring process. A company that values 'innovation' might be tempted to hire only candidates with bold, unconventional ideas. But if 'innovation' is defined too narrowly, they may overlook people who bring reliability, mentorship, or deep domain expertise—qualities that also support long-term growth. The tension between competing values is not a bug; it's the feature. A healthy value system provides a framework for navigating these tensions, not eliminating them.

Why Context Matters More Than Words

The specific words you choose for your values matter far less than how they are interpreted in real situations. Many teams spend weeks agonizing over a single adjective, only to discover that their real challenge is not the wording but the lack of shared understanding. For example, 'integrity' can mean 'always tell the truth' to one person and 'don't actively lie' to another. Without concrete examples and repeated discussions, the value remains abstract and useless.

We recommend that every value be paired with a 'stress test' scenario—a short description of a situation where that value might be hard to follow. This forces the team to think about trade-offs and builds a shared mental model. One startup we observed had a value of 'customer obsession' but never discussed what to do when a customer's request would harm another customer or the broader community. When that conflict arose, the team had no decision-making framework and ended up making an inconsistent choice that eroded trust on both sides.

The Soil of Organizational Culture

Values don't grow in a vacuum. They are shaped by the existing culture, incentives, and power structures. If a company's bonus system rewards short-term revenue above all else, no amount of 'sustainability' talk will take root. Before you plant new values, you need to assess the soil: what behaviors are currently rewarded? What gets celebrated in all-hands meetings? What decisions are made behind closed doors? These are the real indicators of what the organization values today, and they will either support or strangle any new principles you try to introduce.

Foundations Readers Confuse: Principles vs. Fashion

One of the most common mistakes we see is confusing a genuine core value with a temporary industry trend. In the last decade, terms like 'agile,' 'disruption,' and 'growth hacking' have been treated as values by many teams, only to be dropped when the next buzzword arrived. A core value should be something that would still be relevant even if your industry changed completely. It should guide behavior across different products, markets, and generations of employees.

Another confusion is between values and strategies. 'Innovation' is often cited as a value, but for many companies, it's actually a strategy for staying competitive. If the market shifts and innovation becomes less critical than reliability, should you drop the value? Probably not—but you might need to reinterpret it. A value like 'curiosity' or 'learning' might be more durable because it describes a mindset rather than a specific outcome.

Differentiating Core from Peripheral

We find it helpful to sort principles into three layers: core values (non-negotiable, timeless), operational principles (important but context-dependent), and aspirational goals (nice to have, may change). Core values are the ones you would keep even if they cost you money or market share. They are the hill you are willing to die on. Operational principles are how you implement core values in the current environment—they can and should evolve. Aspirational goals are things you hope to become but aren't yet.

For example, a company might have a core value of 'respect for individuals.' An operational principle could be 'we hold regular one-on-ones'—that might change as the team grows or goes remote. An aspirational goal might be 'we want to have a diverse leadership team within five years.' Mixing these layers up leads to confusion: treating an operational principle as a core value makes the organization brittle; treating a core value as an aspiration makes it toothless.

The Myth of Universal Values

Another foundational confusion is the belief that there is a single set of 'right' values that every good organization should adopt. Different contexts call for different emphases. A hospital's core values will reasonably include 'safety' and 'compassion' in ways that a design studio's might not. A nonprofit focused on advocacy might prioritize 'courage' and 'solidarity,' while a research lab might prioritize 'rigor' and 'openness.' The goal is not to copy someone else's list but to discover what your group genuinely stands for, given its mission and the people involved.

Patterns That Usually Work

After observing many teams that have successfully grown lasting values, we see several recurring patterns. These are not guarantees, but they significantly increase the odds that your values will take root and survive.

Start Small and Test

Instead of launching with a full set of five or seven values, start with one or two that feel most critical. Test them in real decisions for a quarter. See how they hold up. Do they help resolve conflicts? Do they feel natural or forced? Based on that experience, refine the wording or add another value. This iterative approach mirrors how seeds actually grow: you don't plant a full tree; you plant a small seed and nurture it.

One team we know started with a single value: 'we finish what we start.' It was simple, measurable, and addressed a real pain point (too many abandoned projects). Over a year, they added two more values that emerged from challenges they faced. By starting small, they avoided the common pitfall of a long list that everyone nods at but no one remembers.

Embed Values in Rituals

Values need to be reinforced regularly, not just during onboarding or annual reviews. Effective teams weave values into existing rituals: stand-up meetings, retrospectives, performance reviews, and even informal check-ins. For example, a team that values 'candor' might start each retrospective with a round of 'hard truths'—a structured moment to say the thing that's uncomfortable but important. Over time, these rituals become second nature, and the values become part of the culture's muscle memory.

Celebrate Value-Driven Decisions

When someone makes a choice that exemplifies a core value, especially at a cost to themselves or the team's short-term efficiency, make it visible. Share the story in a company-wide channel. Thank them publicly. This signals that values are not just words but are actually honored. Conversely, when a decision violates a value, address it directly and constructively—not as punishment, but as a learning opportunity. This reinforces that the value system is alive and enforced.

Review and Revise Periodically

Values should not be carved in stone. We recommend a formal review every 12 to 18 months, where the team revisits each value and asks: Is this still serving us? Has our context changed? Do we need to add, remove, or reinterpret anything? This keeps the values relevant and prevents them from becoming stale artifacts. The review itself is a value-affirming practice: it shows that the organization is committed to learning and growth.

Anti-Patterns and Why Teams Revert

Even well-intentioned teams often slip back into old habits. Understanding these anti-patterns can help you spot them early and course-correct.

Values as Marketing

The most common anti-pattern is treating values as external branding rather than internal guidance. When values are crafted primarily for a website or recruitment brochure, they tend to be generic and aspirational—'innovation,' 'integrity,' 'teamwork'—without any teeth. Employees quickly sense the gap between the stated values and the real priorities, and cynicism sets in. Once that trust is broken, it's very hard to restore.

Values as a Stick

Another anti-pattern is using values to enforce conformity or punish dissent. If 'collaboration' is used to shut down healthy debate, or 'respect' is used to avoid necessary conflict, the values become tools of control rather than guides for growth. This drives away the very people who could help the organization evolve. Values should empower decision-making, not replace it.

Ignoring Trade-offs

Many teams fail because they refuse to acknowledge that values sometimes conflict. They pretend that it's always possible to honor all values simultaneously, which leads to paralysis or hypocrisy. A healthy value system includes an understanding of how to prioritize when values clash. For example, a team might decide that 'safety' always trumps 'speed' in their context, or that 'customer trust' outweighs 'short-term profit.' These priorities should be explicit and discussed openly.

The Reversion Trigger

What causes teams to abandon their values? Typically, it's a crisis: a missed deadline, a financial shortfall, a key employee leaving. Under pressure, the brain defaults to short-term survival mode. If the values haven't been deeply internalized through practice and ritual, they are the first thing to go. The team reverts to whatever behavior got them results before—often the very behaviors the values were meant to replace. To prevent this, we recommend creating a 'crisis protocol' that explicitly names which values should guide decisions under pressure, and rehearsing it in advance through tabletop exercises.

Maintenance, Drift, and Long-Term Costs

Maintaining a value system over years requires ongoing attention. Like any living thing, it can drift if not tended. Drift often happens slowly: a small compromise here, an exception there, until the original values are barely recognizable. The cost of drift is not just ethical inconsistency; it's also practical. Teams that lose their value alignment suffer from slower decision-making, lower trust, and higher turnover.

Signs of Drift

Watch for these indicators: decisions that used to be easy become contentious; longtime employees start saying 'we used to do things differently'; new hires struggle to understand what the team stands for; or values are cited only in meetings about other people's behavior, never one's own. If you notice any of these, it's time for a focused reset—not necessarily a rewrite, but a deliberate re-engagement with the original principles and their current meaning.

The Cost of Neglect

Ignoring value maintenance has real costs. A team that neglects its values may find itself making decisions that alienate customers, partners, or employees. In the worst cases, it can lead to public scandals or legal trouble. But even in less dramatic scenarios, the erosion of shared values creates friction: meetings take longer, trust erodes, and talented people leave because they no longer feel aligned with the direction. The long-term cost of neglect is often invisible until it's too late.

Maintenance Practices

We recommend three simple maintenance practices: (1) a quarterly 'values pulse' check—a short survey asking team members how well they feel the values are being lived, with open-ended space for examples; (2) a semi-annual 'values retrospective' where the team discusses one value in depth, sharing stories of when it helped and when it felt absent; and (3) a 'values champion' role rotated among team members, responsible for keeping values visible in meetings and decisions. These practices are lightweight but keep the values alive.

When Not to Use This Approach

As much as we believe in the power of intentional values, there are situations where a formal value-setting process may not be the right first step—or may even be counterproductive.

When the Team Is in Crisis Mode

If your organization is facing an immediate existential threat—a cash crunch, a major legal issue, a product failure—trying to define core values is likely a distraction. In crisis mode, the priority is survival. Once the immediate threat is resolved, you can invest in values work. Attempting to build a value system during a crisis can feel performative and may breed resentment if people feel you're focusing on the wrong thing.

When There Is No Trust

Values work requires a baseline of psychological safety. If the team is deeply divided, if there is active conflict or a history of broken promises, starting with values may backfire. The process could become another battleground, with different factions pushing for values that serve their interests. In such cases, it's better to first invest in trust-building, conflict resolution, or even restructuring before attempting a shared value system.

When the Group Is Too Homogeneous

If everyone on the team shares the same background, perspectives, and incentives, values may feel obvious and unspoken. In that case, a formal process might feel forced or unnecessary. However, this homogeneity itself is a risk: the team may be blind to blind spots. A better approach might be to first diversify the group or bring in outside perspectives before defining values. Otherwise, the values you create may simply codify existing biases.

When Values Are Used to Avoid Hard Decisions

Sometimes leaders turn to values as a way to avoid making tough calls. They hope that if they articulate the right principles, the team will self-organize and they won't have to make unpopular choices. This is a misuse of values. Values are a tool for decision-making, not a substitute for leadership. If you're not willing to make the hard trade-offs yourself, don't expect your values to do it for you.

Open Questions / FAQ

We've collected the most common questions we hear from teams working through this process. These answers are based on our collective experience and should be adapted to your specific context.

How many values should we have?

Most successful teams settle on three to five core values. Fewer than three can feel incomplete; more than five become hard to remember and prioritize. But the number matters less than the depth of understanding. Better to have two well-understood values than seven that are vaguely recalled.

What if our values conflict with profit?

This is the most common tension. If a value consistently conflicts with the financial survival of the organization, you may need to re-examine either the value or the business model. Sometimes the conflict is a signal that the business model is not sustainable in the long term. Other times, the value needs to be refined to allow for practical trade-offs. We recommend discussing specific scenarios rather than abstract principles. For example, if 'environmental sustainability' conflicts with 'affordability' for your customers, explore what trade-offs are acceptable and where you can innovate to reduce the conflict.

How do we revive values that have died?

Reviving dead values is harder than starting fresh, but possible. The first step is to acknowledge publicly that the values have been neglected. Then, gather the team to discuss why they faded—was it lack of reinforcement? Changing priorities? Hypocrisy from leadership? Based on that diagnosis, you can either recommit to the original values with new practices, or retire them and develop new ones that better reflect the current reality. Be honest about the past; people appreciate authenticity.

Should values be the same for everyone in the organization?

Core values should be shared across the entire organization, but different teams may interpret them differently or have additional operational principles that support their specific work. For example, a customer support team might have a value of 'patience' that is not explicitly listed in the company-wide values but is derived from the core value of 'respect.' That's fine—as long as the core values remain the common thread.

How do we handle a founder who embodies values but also violates them?

This is a delicate and common situation. Founders often set the initial values, but they are also human and may fall short. If a founder consistently violates a core value, the team must find a way to address it respectfully but firmly. This might involve a private conversation, a mediated discussion, or, in extreme cases, a governance change. Ignoring the gap between the founder's behavior and the stated values will undermine the entire value system. The founder's willingness to be held accountable is a test of whether the values are real.

We hope this guide gives you a practical starting point for growing values that can last. The future is uncertain, but the process of tending to your values—like tending to a garden—is something you can start today. Plant one seed. Water it. See what grows.