Principles Are Constraints, Not Posters
A product principle that everyone agrees with is probably a slogan. A useful principle makes a salesperson unhappy sometimes. That is how you know it is doing work.
We keep four.
1. Default to the Workflow, Not the Role
B2B buyers purchase seats. Users purchase a way to finish Tuesday. Design for the workflow that crosses roles. Roles can be permissions later.
2. Configuration Is Not a Strategy
If a customer asks for a toggle, ask which job they are trying to finish. Often they need a better default, not another fork in the settings maze.
3. One Source of Truth per Object
Duplicate records feel like flexibility in a demo and like lawsuits in year two. If two teams need different views, give them views. Do not give them two databases wearing a UI.
4. Say No in Writing
Verbal nos evaporate. A short note — what we will not build, why, and what we offer instead — keeps sales and product in the same reality.
Frequently Asked Questions
What Makes a B2B Product Principle Useful?
It constrains decisions enough to make someone unhappy sometimes. Principles everyone loves are usually slogans.
Why Default to Workflow Instead of Role?
Buyers purchase seats, but users purchase a way to finish Tuesday. Design for the cross-role workflow first.
How Should Teams Refuse Feature Requests?
Say no in writing: what you will not build, why, and what you offer instead, so sales and product stay aligned.
Principles Under Pressure
Review these four at the start of every roadmap cut. If a deal requires violating more than one, escalate consciously. Principles that only live on posters will not protect the product when quarter-end pressure arrives and every toggle suddenly feels free.