In my organization, nothing moves until there’s a Single Source of Truth (SSOT). Fragmented lists create fragmented realities, wasting time and derailing execution. I enforce SSOT by immediately stopping discussions when I detect competing versions, declaring the SSOT location, assigning a guardian to maintain it, and refusing to engage with side lists until they’re merged. This discipline isn’t bureaucracy—it’s operational survival. SSOT ensures clarity, accelerates decisions, and preserves the integrity needed to scale work effectively.

---

In my company, there’s an unspoken rule: when the truth is fragmented, everything stops. I don’t care how urgent the sprint is, how many meetings are scheduled, or how excited people are to “keep pushing forward.” If we’re working off multiple competing lists, I hit the brakes. Dead stop. Nothing moves until there’s a Single Source of Truth (SSOT).

The Problem: Multiple Versions, Multiple Realities

Every project, every sprint, every initiative—people naturally create their own lists. One person prefers Notion, another starts a personal Google Sheet, someone else is jotting down items in a notebook. It’s human nature to organize things the way that feels right for you.

But the moment multiple lists exist, multiple realities exist. People start operating with different assumptions about priorities, timelines, and deliverables. That’s how teams waste hours debating which list is correct instead of solving the actual problem.

This is why fragmented truth is unacceptable to me. It’s operational poison.

The Rule: SSOT or Nothing Moves

Over the years, I’ve adopted an unwavering rule: “If there’s no SSOT, I don’t touch it. Nothing moves until we fix that.”

As the acting head of product, the SSOT is the Product Dashboard. That is the definitive version of reality. Team members are free to organize ideas in their own spaces, but if it’s not reflected in the Dashboard, it doesn’t exist in my decision-making process. It’s not up for debate. It’s not a preference. It’s the operating principle.

How I Enforce It (Tactically, Not Politely)

Enforcing SSOT isn’t a casual request—it’s a hardline operational stance. I don’t “suggest” we align documents or “encourage” people to sync their lists. I intervene the moment I see fragmentation and make it explicitly clear: until there’s one truth, this discussion is paused. It’s not about being rigid for the sake of control—it’s about protecting the integrity of our workflow. Here’s exactly how I enforce it, step by step.

1. Immediate Stop: The moment I detect fragmentation, I call it out and stop the discussion: “Stop. We have competing lists. We’re fixing this first.”
2. Declare the SSOT Location: I make it clear where the truth lives. In this case: “The Product Dashboard spreadsheet is the only source of truth.”
3. Assign a Guardian: Someone owns the SSOT. Their job is to consolidate inputs, align all contributors, and protect the integrity of the dashboard. This isn’t project management—it’s truth management.
4. Immutable IDs: Every item in the Dashboard gets a unique ID that never changes. Even if someone makes a local copy, that ID must stay intact. When updates loop back, the ID ensures it re-aligns with the SSOT without creating chaos.
5. Reject “Sidecar Realities” Until Synced: Team members can draft plans, explore ideas, and build side lists. But until they’re merged into the SSOT, I won’t engage with them. It’s not about micromanaging—it’s about enforcing operational clarity.

This process might seem intense and inflexible, but it’s the only way to prevent operational drift. Fragmentation is like a leak in a ship—you don’t keep sailing and hope it doesn’t matter. You fix it immediately. By enforcing SSOT with precision and zero tolerance for side realities, I ensure that every conversation, decision, and action is grounded in a shared understanding. That’s not micromanagement—that’s how you build a disciplined, high-velocity organization.

Why This Works

Enforcing SSOT at the operational level creates immediate clarity. Once you eliminate competing lists, the noise disappears. Teams stop wasting time reconciling versions and focus purely on execution. There’s no confusion about what’s real and what’s not.

It also accelerates decision-making. When everyone is anchored to a single source, decisions happen faster because there’s no ambiguity. Meetings don’t start with “which version are we looking at?”—they start with problem-solving.

Beyond efficiency, SSOT reduces emotional friction. Fragmented truth often leads to frustration, with team members feeling unheard or sidelined. A shared, visible SSOT eliminates these emotional undercurrents. The conversation becomes objective and focused.

More than anything, enforcing SSOT conditions the team to respect structure—not as a bureaucratic annoyance, but as a necessary foundation for scaling work without collapsing under its own weight. SSOT is not a preference—it’s survival.

SSOT is a Leadership Discipline

Enforcing SSOT isn’t a tactical choice—it’s a leadership discipline. If you allow the truth to fragment, you lose control. You cannot scale, you cannot move fast, and you certainly cannot build an autonomous organization on a foundation of competing narratives.

The real work of leadership is not just making decisions—it’s ensuring that when you make them, everyone is looking at the same map. That’s why, in my world, SSOT comes before everything else. Until there’s one truth, nothing moves.

…