The Fizzio Fix: When a Community Disagreement Forged Our Startup's Core Values

Who Needs This and What Goes Wrong Without It

If you've ever watched a team meeting devolve into finger-pointing over a decision that seemed trivial—like which feature to prioritize or how to respond to a customer complaint—you've seen the raw material of core values. Most startups draft their values in a weekend retreat, picking words like 'integrity' and 'innovation' from a list. Those values sit on a wall and never get tested. But the real test comes when a community disagreement erupts: a public argument on your forum, a split among early adopters, or a clash between what your team believes and what the market demands.

Without a deliberate process to navigate that conflict, you get one of three outcomes: a toxic culture where the loudest voice wins, a bland compromise that pleases no one, or a slow exodus of the very people who made your community vibrant. We've seen teams spend months recovering from a single poorly handled dispute—lost trust, lost contributors, lost direction. This guide is for anyone who wants to turn that painful moment into a defining strength: founders, product leads, community managers, and team leads who sense that their values are hollow and need real pressure-testing.

The core problem is that most teams don't have a shared language for talking about values under stress. They default to 'we need to be more respectful' or 'let's just agree to disagree' without digging into the underlying principles that actually guide behavior. That's where the Fizzio Fix comes in: a structured but human process for extracting values from conflict, not from a whiteboard brainstorming session. We'll walk through the exact steps, the tools you'll need, and the common mistakes that derail the whole effort.

What You'll Be Able to Do After Reading

By the end of this guide, you'll have a repeatable framework for turning a community disagreement into a set of values that your team actually believes in—because they lived through the argument that created them. You'll also know what to watch out for when the process gets messy, which it will.

Prerequisites and Context to Settle First

Before you dive into the Fizzio Fix, you need to be honest about where your team is right now. This process is not for teams that are still in denial about having a conflict. If everyone is pretending the disagreement doesn't exist or that it was just a 'misunderstanding,' you'll hit resistance when you try to surface the real tensions. The first prerequisite is a shared acknowledgment that something significant happened—a moment where trust was strained or where a decision left a group feeling unheard.

Second, you need a neutral facilitator. This can be an external consultant, a team member who wasn't deeply involved in the dispute, or even a rotating role if you're a small group. The facilitator's job is not to take sides but to keep the conversation structured and ensure everyone gets a turn to speak. If the founder or team lead tries to facilitate their own conflict, the process will feel like a power play. We strongly recommend bringing in someone who has no stake in the outcome.

Third, you need a clear boundary around the 'community' you're serving. Is it your internal team? Your beta testers? Your broader user base? The values you extract will be different depending on whose voices you include. For the scenario we'll use throughout this guide—a startup's internal team that also runs a public community forum—the community includes both employees and active contributors. But you can adapt the scope to your situation.

When Not to Use This Process

The Fizzio Fix is not appropriate when there is active harassment, legal liability, or a power imbalance that makes open conversation unsafe. In those cases, address the immediate harm first—through HR, legal counsel, or a formal mediation process. This tool is for disagreements about direction, priorities, and principles, not for resolving abuse or discrimination.

Also, if your team is too small (fewer than three people) or too large (more than 30), you'll need to adapt the format. For very small teams, the process can feel forced; for very large groups, you'll need breakout sessions and a synthesis phase. We'll cover those variations later.

The Core Workflow: From Conflict to Values in Five Steps

This is the heart of the Fizzio Fix. The process takes about three to four hours in a single session, but you can split it into two shorter sessions if needed. The key is to keep the momentum—don't let a week pass between steps.

Step 1: Map the Disagreement

Start by asking each person involved to write down, in one paragraph, what they think the disagreement is really about. Not the surface issue (like 'we should use Slack vs. Discord'), but the deeper principle at stake (like 'we value accessibility over feature richness'). Collect these anonymously if possible, and read them aloud without attribution. This step surfaces the hidden values that are already driving people's positions.

Step 2: Identify Value Candidates

As a group, list every value that appears in those paragraphs. Don't filter yet—write down everything: transparency, speed, quality, inclusivity, autonomy, alignment, experimentation, stability, etc. You'll likely end up with 10–20 candidates. Cluster similar ones together (e.g., 'speed' and 'agility' might be the same thing).

Step 3: Stress-Test Each Candidate

For each value, ask: 'If we truly lived by this value, what decision would we have made in the conflict? What would we do differently next time?' This is where the real work happens. You'll find that some values sound nice but don't actually guide behavior—they fail the stress test. For example, if 'transparency' would have meant sharing the data earlier, but the team wasn't ready, then transparency isn't a lived value yet. Keep only the values that survive the test.

Step 4: Write the Values as Principles

Each surviving value gets turned into a principle: a short statement that describes how you'll act, not just what you believe. For instance, instead of 'Integrity,' write 'We share bad news early and in full.' Instead of 'Community-first,' write 'When in doubt, we ask the community before deciding.' These principles become your core values because they were forged in the fire of a real disagreement.

Step 5: Commit and Communicate

Publish the principles internally (and externally if relevant) with a brief explanation of the conflict that inspired them. This transparency builds trust—people see that your values are not marketing copy but scars from a real fight. Then, in every future decision, refer back to the principles. When a new disagreement arises, you'll have a shared language to navigate it.

Tools, Setup, and Environment Realities

The Fizzio Fix doesn't require expensive software. A simple shared document (Google Docs, Notion, or even a whiteboard) works. But the environment matters more than the tool. You need a space where people feel safe to speak honestly—no recording, no attribution unless agreed, and a clear rule that what's said in the session stays in the session until the group decides to share it.

Physical vs. Remote Setup

For in-person sessions, arrange chairs in a circle or around a table—no head of the table to avoid hierarchy cues. Provide sticky notes and markers for the mapping step. For remote sessions, use a video call with a shared screen and a digital whiteboard like Miro or Mural. Make sure everyone has a stable connection and a quiet space. The facilitator should monitor the chat for side conversations and ensure everyone unmutes when they want to speak.

Time Constraints and Energy Management

The full process takes three to four hours. If your team can't spare that, you can shorten Step 1 by having people submit their paragraphs beforehand, and you can combine Steps 3 and 4 into a single discussion. But don't skip Step 5—that's where the commitment happens. Also, schedule a break after Step 2; the emotional labor of surfacing conflict is real. Provide snacks or a virtual coffee break.

Facilitation Tools

A timer is essential. Set time limits for each step (e.g., 15 minutes for Step 1, 20 minutes for Step 2, 30 minutes for Step 3, etc.) and stick to them. The facilitator should have a list of neutral questions ready: 'What would that look like in practice?' 'Who would be affected if we chose this value?' 'Is there a counterexample where this value would have led to a worse outcome?' These questions keep the discussion grounded.

Variations for Different Constraints

Not every team looks like the startup we described. Here are three common variations and how to adapt the Fizzio Fix.

Variation 1: Remote, Asynchronous Teams

If your team spans time zones and can't meet live, adapt the process to run over a week. Use a forum or Slack channel for each step. Step 1: everyone posts their paragraph in a thread. Step 2: the facilitator compiles the value candidates and posts a poll. Step 3: a shared document where people add comments stress-testing each value. Step 4: the facilitator drafts principles based on the comments and asks for final feedback. Step 5: the team votes to adopt the principles. The downside is loss of real-time synthesis, but it gives introverts more time to think.

Variation 2: Non-Hierarchical or Flat Organizations

In a flat team, the facilitator role is even more critical because there's no formal authority to enforce boundaries. Use a rotating facilitator who has no stake in the current conflict. Also, be explicit about decision rights: after the values are codified, who gets to interpret them in a specific situation? In flat organizations, we recommend a 'values council' of three rotating members who serve as interpreters for six months. This prevents any one person from weaponizing the values.

Variation 3: Deeply Entrenched Positions

If the conflict has been simmering for months and people are dug in, start with a separate 'pre-work' session where the facilitator meets individually with each party to understand their perspective. Then, in the group session, use a 'pre-mortem' technique: ask everyone to imagine that the team has failed because it couldn't resolve this conflict, and write down what went wrong. This shifts the focus from blame to shared problem-solving.

Pitfalls, Debugging, and What to Check When It Fails

The Fizzio Fix is not a magic wand. Here are the most common ways it can go wrong and how to recover.

Pitfall 1: Rushing to Consensus

Teams often feel pressure to end the session with a nice list of values, so they skip the stress-test or water down the principles to avoid conflict. The result is a set of values that no one truly believes in. If you feel the group is glossing over disagreements, pause and ask: 'What's the hardest part of this value for someone here? Let's hear that voice.' If no one speaks, assign someone to play devil's advocate.

Pitfall 2: The Loudest Voice Dominates

In any group, some people talk more. The facilitator must actively invite quieter members to share, using techniques like round-robin or anonymous written input. If one person keeps steering the conversation, the facilitator should say, 'I hear you—let's hold that thought and hear from others first.' After the session, check in privately with quieter members to ensure they feel heard.

Pitfall 3: Values That Are Too Vague

If your principle is 'We value respect,' it's too vague to guide decisions. A better principle is 'We assume good intent but call out impact.' If you're stuck with vague values, go back to Step 3 and ask for a specific example of a decision that would change if you lived by that value. If you can't think of one, the value is not operational.

Pitfall 4: No Follow-Through

The most common failure is that the values are written and then forgotten. To prevent this, assign a 'values steward' for each principle—someone who will remind the team when a decision conflicts with the value. Also, schedule a quarterly review where the team revisits the values and asks if they still hold. If a new conflict arises, use the same process to update them.

What to Check When the Process Feels Stuck

If the group is stuck on Step 2 with too many candidates, use a dot-vote: each person gets three stickers to place on the values they think are most important. The top five become the focus. If Step 3 feels like an attack on someone's pet value, remind the group that stress-testing is not rejection—it's making the value stronger. If the session ends with no clear principles, schedule a follow-up within a week, but don't let it drag.

Finally, remember that core values are not permanent. They evolve as your community and challenges change. The Fizzio Fix is a process, not a destination. Use it whenever a new disagreement surfaces that your current values can't handle. That's how you build a culture that can weather any storm.