WL-0002 · Collaboration · release Scope reduction
Remove team chat feature
AcceptedCaptured from #scope-reduction thread
Why
The team briefly considered comments inside WhyLedger, but users already had Slack and Linear. Adding chat would create another conversation silo instead of solving fragmented context.
Alternatives considered
Add comments to every decision card
Rejected because it made WhyLedger compete with Slack instead of organizing decisions from Slack.
Add lightweight reactions only
Rejected because it did not solve a high-priority workflow.
Evidence
Slack: Scope discussion in #productDoc: MVP principles: no new chat silo
What happened after release
ValidatedBeta feedback · Apr 26, 2026
Beta users said they wanted source links and outcomes more than another commenting surface.