# Product Principles

A small set of memorable decision rules that translate product strategy and learned values into guidance for recurring tradeoffs.

- Type: principle
- Domain: Strategy & discovery
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/product-principles/>)

## What it means

Product principles are durable guidelines for how a team chooses, designs, and builds. They turn strategic intent and accumulated learning into opinionated rules that can resolve recurring tensions when the vision is too broad and detailed standards are too narrow.

## Why it matters

Distributed teams cannot escalate every decision. Useful principles create consistency without prescribing identical solutions, make tradeoffs discussable, preserve hard-won lessons, and help new team members understand the reasoning behind the product’s quality bar.

## When to use it

Use principles when teams repeatedly debate the same tensions, when a product scales across squads, or when strategy needs behavioral expression. Develop them from real choices and evidence rather than inventing abstract values in isolation.

## How it works

1. Collect consequential product decisions, tensions, successes, and failures.
2. Identify recurring beliefs that distinguish this product and strategy.
3. Write each principle as a clear, opinionated instruction with a rationale.
4. Add examples showing what the principle favors and what it rejects.
5. Test the set against current decisions and revise ambiguous or redundant items.
6. Review occasionally as strategy and evidence change, not for every release.

## A practical example

A healthcare portal adopts “show the consequence before the control” after users accidentally changed care preferences. The principle guides confirmation language, permissions, and notification settings across squads while allowing each flow to use an appropriate interaction pattern.

## Where it breaks

Principles can conflict, become generic slogans, or preserve outdated beliefs. Without examples and leadership behavior, they have little force. They should not override accessibility standards, regulation, research evidence, or context-specific judgment.

## Common mistakes

- Choosing universal virtues such as “simple” that offer no distinctive tradeoff.
- Publishing principles without examples of decisions they change.
- Creating so many principles that teams cannot remember or prioritize them.

## Sources

1. [Foundations to Build On: Intercom’s Principles for Building Product](<https://www.intercom.com/blog/intercom-product-principles/>) — Intercom · Company practice guide
2. [Why Your Organization Needs Product Principles](<https://slack.design/articles/why-your-organization-needs-product-principles/>) — Slack Design · Company design practice

## Related topics

- [Product Vision](<https://wiki.soroush.uk/topic/product-vision/>)
- [Design Thinking](<https://wiki.soroush.uk/topic/design-thinking/>)
- [Lean UX](<https://wiki.soroush.uk/topic/lean-ux/>)
