# KFC — Async Decisions for Distributed Engineering Teams

> KFC (Kollective Feedback Center) is an async decision room. Engineers contribute privately before seeing others' input (anti-anchoring), and Claude synthesizes consensus, dissent, blind spots, and confidence so the team closes the call in 48 hours without another meeting.

- Site: https://www.kfc.ma
- Full content for LLMs: https://www.kfc.ma/llms-full.txt
- Sitemap: https://www.kfc.ma/sitemap.xml
- Contact: https://www.kfc.ma/contact

## Core

- [Home](https://www.kfc.ma/): Product overview, how-it-works, FAQ.
- [Try solo (no signup)](https://www.kfc.ma/solo): Pose a decision, submit your position, and Claude generates 3 diverse imaginary teammates + structured synthesis in 60 seconds.
- [About](https://www.kfc.ma/about): What KFC believes about decisions, anchoring, and meetings.

## Guides

- [How to run an async RFC process for distributed engineering teams](https://www.kfc.ma/guides/async-rfc-process): A complete playbook for running technical decisions asynchronously across timezones: framing the question, gathering independent input, synthesizing the call, and shipping the decision in 48 hours.
- [Anchoring bias in engineering decisions: what it is and how to defeat it](https://www.kfc.ma/guides/anchoring-bias-engineering): Why the first opinion in any technical discussion shapes the rest, what the research says, and three concrete protocols that remove anchoring from your architecture decisions.
- [Async vs sync engineering decisions: how to choose](https://www.kfc.ma/guides/async-vs-sync-decisions): Not every decision should be async. A practical framework for choosing the right mode based on reversibility, stakes, urgency, and team size — and the failure modes of each.
- [Why every distributed engineering team needs a decision log](https://www.kfc.ma/guides/distributed-team-decision-log): A decision log is the highest-leverage document a distributed engineering team can maintain. Here's why, what to put in it, and how to keep it alive past the first month.

## Decision templates

- [Pivot or persevere](https://www.kfc.ma/templates/pivot-or-persevere): When the metrics aren't lying anymore. — Three quarters of flat growth
- [Hire this senior candidate](https://www.kfc.ma/templates/hire-senior-role): After the loop, before the offer. — Director-level+ hires
- [Run a layoff](https://www.kfc.ma/templates/layoff-decision): The hardest decision a leadership team makes. — Runway pressure
- [Build vs buy](https://www.kfc.ma/templates/build-vs-buy): Before engineering writes a line. — Vendor evaluation that drifted into 'we could just build this'
- [Strategic shift (board)](https://www.kfc.ma/templates/board-strategic-shift): When the board needs to bless or block. — Market expansion
- [Adopt a new policy](https://www.kfc.ma/templates/policy-change): Internal governance, externally auditable. — Remote-work policy

## Comparisons

- [KFC vs Slack threads for engineering decisions](https://www.kfc.ma/vs/slack-threads): Slack threads are fast, but the first reply anchors the room and there's no synthesis. KFC enforces private contribution and produces a structured synthesis of agreement, dissent, and blind spots.
- [KFC vs Notion docs for async decisions](https://www.kfc.ma/vs/notion): Notion docs are great for capturing decisions. They are not built to make them. KFC handles the contribution and synthesis phase; Notion handles the long-term record.
- [KFC vs Loom for async engineering decisions](https://www.kfc.ma/vs/loom): Loom is one-way broadcast. KFC is multi-way structured decision-making. Different tools for different phases.

## Optional

- [Privacy](https://www.kfc.ma/privacy)
- [Terms](https://www.kfc.ma/terms)