Most companies can tell you their mission statement. Fewer can tell you, clearly and consistently, how their team is supposed to behave when a customer is upset, a deal is at risk, or something's gone wrong at 6pm on a Friday. That gap is where culture actually gets tested, and it's usually the part nobody wrote down.
A mission statement answers the wrong question
A mission statement tells you where the company is headed. It doesn't tell a new hire what to do when a customer is furious and the playbook doesn't cover the exact situation. That's a different document entirely, and most companies never write it.
What this actually looks like in practice
Think of it less as a values poster and more as a short, specific set of defaults. A few examples of the kind of thing worth putting in writing:
- Who gets to make an exception, and how big can that exception be without anyone else signing off?
- When something breaks, does the team lead with an apology and a fix, or with an explanation of whose fault it wasn't?
- If a customer is clearly wrong about something, does the team correct them bluntly, or find a way to be right without making them feel small?
None of these have a universal right answer. That's exactly why they need to be decided on purpose, instead of improvised differently by every rep every time.
Why this has to be written, not just understood
"We all just kind of know how we operate" works fine until the team doubles in size, or until the founder isn't in every customer call anymore. Writing it down is what lets it survive growth instead of quietly diluting with every new hire who never got the unwritten version.
A simple way to start
Grab three recent situations where a customer-facing decision genuinely could have gone either way. Write down what your team actually did, and whether it's what you'd want every future employee to do in the same spot. If the answer's yes, that's a principle. Write it down properly. If it's no, that's worth a harder conversation before it happens again.
A philosophy nobody wrote down isn't a philosophy. It's just whatever the last person who handled it happened to decide.
Common questions
What is a written customer philosophy?
A short, specific set of defaults for how your team behaves when a customer is upset, a deal is at risk, or something goes wrong. It covers the situations a mission statement and playbook don't.
How is a customer philosophy different from a mission statement?
A mission statement tells you where the company is headed. A customer philosophy tells a new hire what to do when a customer is furious and the playbook doesn't cover the situation.
Why does a customer philosophy need to be written down?
"We all just kind of know" works until the team doubles or the founder isn't on every call. Writing it down lets it survive growth instead of diluting with every new hire.
How do you start writing a customer philosophy?
Pick three recent customer decisions that could have gone either way. Write down what your team did and whether you'd want every future employee to do the same. If yes, that's a principle worth recording.