Your go-to tech blog

Rolling Out Company Values to Employees: 6 Mistakes That Turn a Launch Into a Poster

If you asked ten of your employees on a random Tuesday which company value shaped a decision they made that week, how many could answer? Not recite the list. Name a decision. In most companies that just launched new values, the honest number is one or two, and usually those are people who sat on the working group.

That gap is the real subject of a rollout. Writing the values took a few workshops. Getting 240 people to use them when a deadline, a customer and a colleague all want different things takes 6 to 12 months of small, unglamorous changes. The mistakes below are the ones that quietly eat that time.

Mistakes 1 and 2: the all hands reveal, and managers who hear it with everyone else

The classic launch goes like this. The CEO presents the values at an all hands, there is a short video, a slide with icons, a Slack emoji pack and maybe a set of laptop stickers. The meeting runs 45 minutes. People clap. On Wednesday a team lead is asked by a direct report what “own the outcome” means for the on call rota, and the team lead has no idea, because she heard the values for the first time in the same meeting.

That is mistake number two, and it does more damage than the theatre of number one. Employees do not learn what a value means from the CEO. They learn it from the person who approves their time off, reviews their work and decides who gets the interesting project. If that person shrugs, the value is dead in that team.

Reverse the order. Brief managers 2 to 3 weeks before anyone else hears the values, in groups of 8 to 12, and give each manager three things: the reasoning behind each value, the trade-off it settles, and two or three real situations from their own area where it would change the answer. Ask them to bring one disagreement back. If a manager cannot apply a value to a single situation in their team, you have found a wording problem before 240 people find it for you.

The all hands still has a place. Keep it short and put the weight on stories: one decision the leadership team made differently because of each value, including a decision that cost money. A value that never cost the company anything reads as decoration, and employees spot that within one meeting.

Mistake 3: values without behaviours, and behaviours without a price

“Integrity” is a word. Enron listed integrity among its four values, alongside respect, communication and excellence. A value statement on its own tells nobody what to do differently on Monday morning.

Each value needs 3 or 4 behaviours written in the plain language people use at work, and at least one of those behaviours should name what you give up. “We ship small changes daily, even when a bigger release would look more impressive in the demo” is a behaviour with a price. “We strive for quality” has no price, so it cannot guide a choice between two good options.

Patrick Lencioni made a related point in his 2002 Harvard Business Review article “Make Your Values Mean Something”: he separated core values from aspirational ones, from permission to play basics such as honesty, and from accidental values that just happen to exist. A rollout that mixes all four in one list confuses everyone.

Here is a worked example of what the translation work costs, using illustrative numbers for a 240 person software company with 22 people managers and 4 values. Writing behaviours: a working group of 6 people spends 3 sessions of 2 hours, so 36 person hours. Manager briefings: 22 managers in 2 groups, 90 minutes each, plus 2 facilitators, about 36 person hours.

Team sessions: each manager runs a 60 minute session with an average team of 10, so 22 sessions and roughly 240 person hours. Updating the review form and interview guides: about 40 hours of HR time. The total lands near 350 person hours, or about 1.5 hours per employee. Compare that with the launch event, which typically consumes 240 person hours in a single 60 minute block and changes almost nothing. The money is in the team sessions, where a value meets a real backlog.

Mistake 4: leaving hiring, reviews and promotions untouched

Employees read systems more carefully than they read slides. If the performance review form still has five boxes about output and none about how the work was done, the message is clear: the values are optional. If promotion committees still discuss only results, people conclude that results are the whole game.

Three systems carry most of the signal. Hiring comes first, because it is the cheapest place to protect a culture. Amazon is the obvious public example: its Leadership Principles, 16 of them at present, are used directly as interview themes, and candidates are told to prepare stories for them. You do not need that scale. Add one structured question per value to your interview guide, define what a weak and a strong answer look like, and score it separately from skills.

Performance reviews come second. Add a short section where the employee and the manager each describe one decision where a value helped and one where it was hard to follow. The hard one is more useful, because it shows where a value collides with targets or with another value.

Promotions come third, and they are where credibility is won or lost. When the first promotion round after the launch happens, employees will watch who goes up. If someone known for cutting corners is promoted on numbers alone, every team session you ran is undone in a week.

A word of caution here. Rating people on each value with a 1 to 5 scale tends to produce theatre and grievances. Most companies get better results from evidence written in sentences and a single check: did this person act against any value in a way that hurt colleagues or customers?

Mistake 5: exempting the leaders and the high performers

Nothing teaches values faster than an exception. Netflix put this in writing in its 2009 culture deck, the long slide presentation shared by Reed Hastings and Patty McCord, which stated that the real values of a company are shown by who gets rewarded, promoted or let go. The wording has changed over the years, but that principle has survived every revision of the Netflix culture memo.

An illustrative case shows how it plays out. A 120 person B2B company launches four values, one of which is “we tell customers the truth about timelines”. Six weeks later, the top account executive, responsible for about 18 percent of new revenue, promises a feature delivery date that engineering has already flagged as impossible. The deal closes. The customer escalates two months later when the date slips.

Leadership has three options. Ignore it, because the deal was large. Praise the deal publicly and handle the timeline issue in private. Or address it openly in the sales team, adjust the commission rules so that deals with unapproved delivery dates pay out only after delivery, and say why.

In this case the company chose the second path. Within a quarter, two other account executives were quoting optimistic dates, and the support team had stopped mentioning the value in its own meetings. The value had been tested once, and everybody saw the result.

The same applies to the leadership team itself. If executives ask employees to “debate openly” while decisions keep arriving fully formed from a closed meeting, the value becomes a joke. Before the launch, each executive should name one habit of their own that will change, and say it in front of their teams.

Mistake 6: measuring awareness instead of decisions

The usual metric for a values rollout is a survey question such as “I know our company values”, followed by a celebration when 85 percent agree. That number tells you the slides were seen. It says nothing about whether anyone decided differently.

Measure behaviour in places where it already leaves a trace. Count how often values are cited in written decision documents, post incident reviews or project kickoffs, using a simple sample of 20 documents per month. Track whether interviewers are filling in the values questions in the hiring system, and whether the scores spread out or cluster at the top, which suggests nobody takes them seriously.

In engagement surveys, replace the awareness item with “In the last month, I saw a leader make a decision consistent with our values when it was inconvenient” and look at the answer by team, not as a company average.

Then run a 90 day review with managers. Ask each one for a single story where a value changed an outcome in their team and a single story where it got ignored. With 22 managers you will collect about 44 stories, and the pattern in them is your real rollout report. Values that produce no stories after 90 days are either badly worded or contradicted by a system you have not changed yet.

There is a fair objection to all of this: some employees simply do not care about values, and pushing harder can feel like an ideology test. That is true, and it is the reason to keep values tied to work decisions rather than personal beliefs. People can disagree about almost anything and still agree on how to treat a customer or a broken release.

So the question worth asking at the 6 month mark is less about awareness and more uncomfortable. Which value has your company already broken quietly, and who noticed?