FirstHR

Company Values: A Practical Guide for Small Business

Company values for small business: definitions, real SMB examples, a 6-step workshop, and how to embed them in hiring and onboarding.

Company Values

A practical guide for small businesses, without the corporate gloss

The first time I tried to write company values at one of my early startups, I sat down at my laptop on a Saturday morning, wrote "Integrity, Excellence, Innovation, Teamwork" in 30 minutes, put it on the about page, and called it done. Six months later, those four words appeared on the careers page, in an investor deck, and exactly nowhere else. Nobody on the team referenced them. Nobody used them in a decision. They were corporate wallpaper, and we had wasted half a Saturday producing them.

This guide is how to avoid my mistake. I will explain what company values actually are, why they matter more (not less) for small businesses, how to create real ones in a single workshop, and how to embed them into hiring, onboarding, feedback, and the handbook so they actually drive decisions instead of decorating walls.

Most company values articles are written for enterprise teams or marketing departments. They list 50 famous examples (Google, Apple, Patagonia, Amazon, Netflix), describe lofty principles, and assume a Brand Strategy Director will oversee the rollout. This one is for small business owners and operators who do not have a Chief Culture Officer. I built FirstHR for this audience because most HR content ignores the people who run small businesses without dedicated HR staff.

TL;DR
Company values are the small set of principles a business uses to guide decisions when no rule applies. Useful ones are specific to your team, demonstrable in real behavior, and few enough to remember: 4-6 at most. They matter more at small scale, because the founder cannot be in every room. A half-day workshop produces them.
Why Values Matter for the Bottom Line
According to Gallup research on company values (2022), just 23% of US employees strongly agree that they can apply their organization's values to their work, and only 27% strongly agree that they believe in those values (Gallup). Gallup, in its State of the Global Workplace report (2026), puts the cost of low engagement at about $10 trillion in lost productivity, roughly 9% of global GDP. Written values only pay off when people believe them enough to use them in real decisions.

What Company Values Actually Are

Definition
Company values
Company values are the small set of principles a business uses to guide decisions, especially when no rule, policy, or precedent applies. They describe how the company operates, treats people, and resolves trade-offs. Useful values are specific to the company, demonstrable in real behavior, and small in number (typically 4-6) so the team can remember and reference them in daily work.

A simple working definition: values are how you choose between two options when both look reasonable. If a customer asks for a feature that would help them but slow your roadmap, what tips the decision? If a senior employee is technically excellent but consistently rude to teammates, what guides the conversation? Values are the answer to those questions when no rule covers them.

Three things are true about every set of values that actually works. First, they were chosen. Real values came from a deliberate decision, not from copying a template. Second, they cost something. Following the values means saying no to opportunities, candidates, customers, or projects that do not fit. Third, they are visible in behavior. You can identify someone living the values without them mentioning the values, because the behavior shows it.

Most company values fail one of those three tests. They were copied. They cost nothing. They are invisible in behavior. The rest of this guide is about how to write values that pass all three tests.

What Company Values Are NOT

Company values are not careers-page copy, a list of generic virtues, a wish list, or an HR deliverable. Each of those four misconceptions explains why most company values fail to do anything useful.

Common misconceptionWhat it actually is
Marketing copy for the careers pageAn operational tool used in real decisions. If your values only appear externally, they are not values; they are branding.
A list of words like 'integrity, excellence, teamwork'Principles specific enough that they would feel wrong on a competitor's site. Generic words describe everyone, which means they describe no one.
A wish list of how you want to beA description of how you actually operate today. Aspirational values that contradict real behavior produce cynicism, not culture.
Something HR creates for the handbookSomething the founder and senior team write together because they will live with the consequences. Delegating values to HR is delegating identity.

The misconception pattern is the same across all four: treating values as a deliverable instead of a tool. A deliverable gets produced once and filed away. A tool gets used. The first test of whether your values are real is whether anyone has used them in a decision in the last 30 days. If the answer is no, the values are not real, regardless of what the framed poster in the lobby says.

Why Values Matter More (Not Less) for Small Business

Values matter more at small scale than at enterprise scale, not less. The conventional view says the opposite: values are a luxury for small businesses, something you formalize when you grow up. Three specific reasons explain why that view gets it backwards.

First, the founder cannot be in every room. At enterprise scale, the CEO does not personally make most decisions; layers of managers and policies do. At a small business, decisions happen everywhere, all the time, often without the founder present.

Values are the mechanism for distributing the founder's judgment to people who cannot read the founder's mind. Without values, every decision either escalates to the founder (creating a bottleneck) or gets made arbitrarily (creating drift).

Second, every hire has outsized cultural impact. Hiring a misaligned person at enterprise scale is bad but recoverable. Hiring a misaligned person at a small business changes the culture immediately. Values are the screening tool that prevents this. A team without articulated values cannot easily explain why a candidate fits or does not, which means they hire on technical skill alone and discover misalignment after the offer is signed.

Third, small businesses cannot afford to compete on benefits, brand, or pay. They compete on culture. The reason talented people join a small business instead of Google is rarely compensation; it is the experience of working there. Values are the description of that experience. A small business without intentional values still has a culture, but it emerged by accident. Intentional values let you build the experience that attracts the people you want.

What Engagement Is Worth
According to Gallup's Q12 meta-analysis (11th edition, 2024), business units in the top quartile for employee engagement are 23% more profitable than those in the bottom quartile, and turn over 21% fewer people in high-turnover organizations (Gallup). For a small business, culture is not a soft topic. It is the primary mechanism for retention when you cannot match enterprise compensation.
What worked for me
At one of my earlier companies, I lost two great hires in their first 90 days because the team they joined was not what we had described in the interviews. The mismatch was not on skills. It was on how decisions got made, how disagreements were handled, and how much autonomy people had. After we wrote real values (the work-it-not-words kind) and started using them in interviews, the 90-day quit rate dropped to zero for the next 18 months. The values were not magic. They just made the implicit explicit, so candidates could self-select before the offer.

Values vs Mission vs Vision vs Culture

Mission is what the company does, vision is where it is going, values are how it operates, and culture is what it is actually like. All four come up in any conversation about company identity, and blurring them produces statements nobody can use. Here is how each one differs.

ConceptDefinitionExampleWhen you reference it
MissionWhat the company does and why it existsMake small business HR effortlessExternal communication, why someone would buy from you
VisionWhere the company is going (long-term aspiration)Every small business in the US runs HR without a dedicated departmentStrategic planning, why the team should care about the long game
ValuesHow the company operates and makes decisionsCustomer obsession, ship and learn, direct communicationDaily decisions, hiring, feedback, performance reviews
CultureWhat the company is actually like in practiceEmerges from real behavior, observable to anyone presentDescribing the team to a candidate, diagnosing problems

The relationship between the four: mission and vision describe the destination; values describe how you travel; culture is the actual experience of the journey. Most small businesses have a mission stated somewhere and the rest implicit. Bringing values up to the surface (and then aligning them with culture) is the work that pays off.

The blur is not academic. According to Gallup (2017), only 41% of employees strongly agree that they know what their company stands for and what makes it different from its competitors (Gallup). That is what four overlapping statements produce: people who can quote the mission back to you and still cannot say how the company decides anything.

The most common confusion is between values and company culture. Values are the principles you write down. Culture is what your company is actually like. The gap between them is where cynicism lives. The goal of writing values is not to invent an inspirational identity; it is to describe the culture you have or are willing to actively build, so the team has shared language for what was previously implicit.

Mission, Vision, and Purpose Statement Examples

The fastest way to tell these apart is to read all three for the same company, side by side. The table below does that for three small businesses. The pattern holds every time: the mission is present tense and concrete, the vision describes a state that does not exist yet and is slightly uncomfortable, and the values are how the team behaves on the way there.

CompanyMission statementVision statementTwo of its values
A 12-person product agencyWe do a small number of design projects properly, for clients who want the process as much as the fileEvery client we take on tells someone else to hire us, and we never need a sales teamWe say no often. Show the work, not the output
A 25-person B2B software companyWe make the operational side of running a small company boring, in the good wayA small business owner can run the whole back office in an hour a weekShip and learn. Disagree directly, then commit
A 7-person healthcare clinicWe give patients unhurried care in a practice small enough to know them by nameNobody in this town has to choose between a fast appointment and a good onePatients before paperwork. If you see it, you own it

Copy the format rather than the wording. Two things make these work. Every mission above describes work that is already happening, not an ambition. And every vision describes a state of the world, not a revenue number. A vision only your accountant would find motivating is not a vision.

Purpose is the fourth term people ask about, and at this size it is not a separate artifact. A company purpose statement answers why the business exists at all, which for most small companies is the mission sentence with the commercial half removed. For the clinic in the table, it could be as short as "unhurried care for every patient." Write one if it clarifies something, but do not run a separate exercise for it.

Team-level statements follow the same rules one level down. A support team, a clinic front desk, or a two-person marketing function can write a team mission in a sentence, as long as it says what that team does for everyone else and does not restate the company mission in smaller type.

For the clinic front desk, a team mission might read: "Every patient is checked in, informed, and billed correctly, so the providers only have to think about care."

A Visioning Exercise for a Small Team

Run the visioning exercise before the values workshop, not after. A vision is easier to argue about than a value, and it warms the room up. Give everyone the same prompt and fifteen minutes of silence: it is five years from now, the business has gone well, and a customer is describing us to a friend. What did they say?

Collect the answers and look for the sentence more than one person wrote without coordinating. That overlap is the real vision of an organization this size, and it is almost always shorter and less grand than anything the group would have produced by talking first.

Then cut it to one sentence a new hire could repeat on their second day. If it needs a paragraph of context to make sense, it is a strategy document rather than a vision. Park the long version somewhere and publish the sentence.

The Anatomy of a Useful Company Value

A value is more than a label. The label is the part everyone copies; the parts that make a value useful are usually missing. A complete value has four parts: a short label, a 1-2 sentence definition, 3-4 behavioral examples, and an example of what violating it looks like.

Anatomy of a useful company value
The value (short label)"Customer obsession"
What it means here (1-2 sentences)We make decisions by asking what is best for the customer, not what is easiest for us. When the two conflict, the customer wins.
What it looks like in practice (3-4 examples)
  • Support replies happen within 4 hours during business days, even when it slows engineering
  • We say no to features that hurt customer experience, even when they would increase revenue
  • Every team member talks to at least one customer per quarter, including engineers
  • Customer feedback is reviewed in our weekly team meeting, not buried in a backlog
What it looks like when violatedEngineering pushes back on a customer-requested fix because it is "not on the roadmap." The right response: review the request through the customer-obsession lens before defending the roadmap.

Each of the four parts does a different job. The label is a memory hook so the team can reference it. The definition turns the abstract noun into a concrete principle. The behaviors translate the principle into observable actions, which is what allows the value to actually drive decisions. The violation example calibrates everyone on what going against the value looks like, which makes enforcement possible.

Most companies stop at the label. "Customer obsession" appears on the careers page with no definition, no behaviors, and no violation example. The result is that "customer obsession" means whatever each person interprets it to mean, which is usually nothing in practice. Two people who claim to live the same value can make opposite decisions, because the label gives no guidance. The behaviors are what make the value operational.

The four-part structure also serves another purpose: it forces honesty during the writing process. If you cannot list 3-4 specific behaviors that show a value in your company, the value is probably not real yet. If you cannot describe a violation, you do not know where the value's edge is.

Writing the full anatomy is a self-test for whether the value belongs on the list. Many candidate values fail this test, which is exactly when they should be cut.

Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
See How It Works

Real Small Business Values Examples

Small business values look different from the enterprise lists most articles borrow from Google, Netflix, and Patagonia. Those lists are useful for inspiration, but they are calibrated for enterprise scale. The three examples below are calibrated for small teams, drawn from patterns that come up again and again in small businesses.

They are illustrative composites rather than real companies. The point is not to copy them but to see how complete values look at small scale: specific, behavior-driven, and unmistakably about a smaller team.

A 12-person product agency(Creative services, 12 employees)
"We say no often"We turn down 60-70% of inbound projects because we only do work we can do well. Saying yes to bad-fit projects hurts everyone.
"Show the work, not the output"Clients see drafts, dead ends, and revisions. We do not pretend to produce polished deliverables effortlessly. The process is part of the product.
"Senior people do junior work"Founders still answer support emails. Senior designers still resize logos when needed. No work is beneath the team.
"We talk before we email"If a Slack thread is hitting 10 messages, someone calls a 15-minute meeting. Email and Slack are for confirming, not deciding.
A 25-person SaaS company(B2B software, 25 employees)
"Customer truth, not customer comfort"We tell customers what is actually wrong, even when they will not like hearing it. Sycophancy hurts the relationship long-term.
"Ship and learn"We ship at 80% confidence and adjust based on real user behavior. Waiting for 100% confidence usually means waiting for 0% relevance.
"Disagree directly, then commit"Anyone can disagree with anyone in any meeting. After the decision is made, we commit to it fully, even if we voted against it.
"Keep the team small"We hire reluctantly. Adding people is the most consequential decision we make. We will work hard before adding headcount.
"No heroes, no martyrs"Working on weekends signals broken planning, not dedication. We solve the problem that produced the weekend work, not celebrate the work itself.
A 7-person healthcare clinic(Medical practice, 7 employees)
"Patients before paperwork"If a patient needs attention and a form is overdue, the patient comes first. We design our workflows so this rarely conflicts.
"We are a team, not a hierarchy"Front desk, medical assistants, providers, and billing all have equal voice in operational decisions. Clinical decisions follow clinical authority. Operational decisions follow team consensus.
"If you see it, you own it"Anyone who notices a problem owns getting it solved or escalated. 'Not my job' is not in our vocabulary. We are too small for silos.
"Slow medicine over fast medicine"We schedule longer appointments, even when it costs revenue. Rushing patients produces worse outcomes and worse trust.

Three patterns across these examples are worth noticing. First, none of them use the words "integrity," "excellence," or "teamwork." Those words describe every company. The values above describe specific companies.

The second pattern is that several of these values describe what the company will not do, not just what it will do. "We say no often." "No heroes, no martyrs." The negative space defines the values as much as the positive. The third is that every value is short enough to remember. The team can quote them in a meeting, which means they can use them.

How Many Values Should You Have?

The honest answer for most small businesses: 4-6 values. Fewer than 4 usually misses important dimensions of the culture. More than 6 stops being memorable, which means the team stops referencing them, which means they stop functioning as values.

Number of valuesWhat happens at this countWhen it might fit
1-3Easy to remember but usually misses key dimensionsA founding team where one or two principles dominate everything
4-6The sweet spot. Memorable, distinctive, usable in real decisionsMost small businesses
7-9Hard to remember. The team starts citing only their favoritesAlmost never. Usually a sign the team did not cut hard enough
10+A wish list, not values. Nobody can recite or reference themNever. This is values theater

The discipline of values is the discipline of cutting. When everything is a value, nothing is. The team that ends up with 12 values almost always wanted to please everyone in the room during the workshop and could not say no to any candidate. The 12-value list signals indecision, not depth. The 4-6 values list signals priority.

If you find yourself with 8-10 candidate values that all feel important, here is the test: take the proposed list, give it to a teammate who was not in the room, and ask them to memorize it in 90 seconds, then recite it back. If they cannot, neither will the rest of the team. Memory is not a soft constraint on values; it is the gate that determines whether values function operationally or decoratively.

The 6-Step Founding Team Workshop

A founding team can produce real values in a focused half-day workshop of six steps. Most articles describe a multi-day off-site retreat instead, which is enterprise consulting overhead a small business does not need. Below is the structure that has worked across multiple companies I have advised and run.

Who should be in the room: 2-5 people maximum. The founder or founders, plus the most senior 1-2 hires if any. Adding more people produces compromise values. Inviting the whole company turns it into a performance, not a working session. Values written by the team are usually weaker than values written by the founders and validated against the team.

1
Step 1: Solo brainstorm (15 min each)Each founder or senior team member writes 10 values they think actually drive how this team works. No discussion yet. The point is to surface different perspectives without anchoring.
2
Step 2: Pool and group (30 min)Combine all lists. Group similar values together. You will likely have 30-50 raw entries that cluster into 8-12 themes. Name each cluster with a short label.
3
Step 3: Pressure-test against decisions (45 min)Pick 3-5 hard decisions the team has made in the past year. For each cluster of values, ask: did this actually drive that decision? Cut clusters that fail the test.
4
Step 4: Cut to 4-6 (30 min)From the surviving clusters, pick 4-6 that feel most important. The cuts are painful and that is the point. If you cannot cut, the remaining values are not really priorities.
5
Step 5: Define each (1 hour)For each surviving value, write: a 1-sentence definition, 3-4 behaviors that show it in practice, and 1 example of what violating it looks like. This is what turns words into a tool.
6
Step 6: Sleep on it (1 week)Do not publish the values immediately. Live with the draft for a week. Notice when you reach for them naturally and when you forget them. Refine. Then publish.

Print one of these per person for the solo round, then use a single shared copy for the steps that follow. The pressure-test grid in the middle is the part that decides the outcome, so leave room to write badly in it.

Founding Team Values Workshop Worksheet
COMPANY VALUES WORKSHOP WORKSHEET

Company: Date: In the room:
STEP 1: SOLO LIST

Ten things you believe actually drive how this team works. No discussion until everyone has finished.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
STEP 2: CLUSTERS

Combine every list, group what repeats, and give each group a short label.
•Cluster: _______ Entries in it: _______
•Cluster: _______ Entries in it: _______
•Cluster: _______ Entries in it: _______
•Cluster: _______ Entries in it: _______
•Cluster: _______ Entries in it: _______
•Cluster: _______ Entries in it: _______
•Cluster: _______ Entries in it: _______
•Cluster: _______ Entries in it: _______
STEP 3: PRESSURE TEST

Name real decisions from the past year, then say which cluster actually drove each one. A cluster that drove nothing gets cut here, not later.
Decision 1:
Which cluster drove it:
Decision 2:
Which cluster drove it:
Decision 3:
Which cluster drove it:
Decision 4:
Which cluster drove it:
Decision 5:
Which cluster drove it:
Clusters that drove nothing, now cut:
STEP 4: CUT TO FOUR OR SIX

1.
2.
3.
4.
5.
6.
What we cut that hurt to cut, and why:
STEP 5: DEFINE EACH ONE

Copy this section once per surviving value. A value without all four parts is still a noun.
Value label:
What it means here, in one or two sentences:
What it looks like in practice:
•_______
•_______
•_______
•_______
What it looks like when violated:
What following it has cost us:
STEP 6: LIVE WITH THE DRAFT

•Draft finished on: _______
•Publish no earlier than: _______
•Times we reached for these values during the week: _______
•Times we made a decision and forgot them: _______
•Changes made before publishing: _______
•Published on: _______ Next review date: _______

Watch for two failure modes during this workshop. The first is letting one strong personality dominate. Solo brainstorming in Step 1 exists to surface different perspectives before they get steamrolled. If only the founder's words survive, you have written the founder's values, not the company's.

The second failure mode is skipping Step 3 (pressure-testing against real decisions). This is where most workshops produce inspirational nonsense. A value that did not actually drive any past decision is not a value of your company; it is a value you are claiming to have. Test before publishing.

The Founder Trap in Small Business Values
At very small scale, the founder's values almost always become the company's values. This is fine and unavoidable. The trap is pretending otherwise. If you run a values workshop with the whole team and let everyone vote equally on what makes the cut, you will likely produce mushy compromise values that please nobody. Better: founders write the first draft, then validate with the team. The team should be able to push back, but the values are the founder's call until the company is large enough that a leadership team, not a founder, sets the tone.

How Values Evolve by Company Stage

Values are not static. The values that work for a founding team usually need refinement once managers are hired, and again as the company moves past small business scale. Treating values as a one-time deliverable produces cultures that drift apart from their stated principles. Treating values as a living tool that gets reviewed annually produces cultures that stay aligned.

Company stageWhat values look like at this stageWhat to actually do
Founding teamFounder values are the company values. Do not bother formalizing yet.Live them. Talk about decisions out loud. Notice what you reject and why.
First hiresTime to write them down. Values are still mostly the founder's, but the team needs language to reference.Run the workshop. Document 4-6 values with behaviors. Share in onboarding.
Growing small businessValues stop being about the founder. Senior hires bring their own. Tension is normal.Re-do the workshop with the leadership team, not just founders. Refine based on what is actually working.
Established small businessValues become the primary mechanism for cultural transmission. The founder cannot be in every room.Embed values in hiring rubrics, performance reviews, and team rituals. Audit annually.
Mid-size and beyondValues need active maintenance. Drift is the default. New hires outnumber the original team.Designate a values steward. Reference values in every all-hands. Protect them from quiet erosion.

The transition that catches most companies off guard is the point where the founder stops being in every room. Before it, values transmit by osmosis; the team watches the founder decide and absorbs the pattern. After it, values must transmit through systems (hiring rubrics, onboarding, performance reviews).

The companies that handle this transition well are the ones that explicitly noticed it happening and built systems early. The companies that struggle are the ones that assumed values would keep transmitting on their own as the team grew. Values never do.

Common Categories of Company Values

While every company's values should be specific to that company, certain categories appear repeatedly across small businesses. The pattern is useful: it can prompt brainstorming during the workshop. Just remember that picking from a category is not the same as writing your value. The category is the prompt; your specific value is the answer.

CategoryWhat it coversExample for SMB
Customer orientationHow the company treats customers and weighs their needs"Customer truth, not customer comfort."
Decision-making styleHow decisions get made, who has authority, how disagreements resolve"Disagree directly, then commit."
Pace and urgencyHow fast the team moves, how it handles uncertainty"Ship at 80% confidence and adjust."
Communication normsHow the team communicates internally, what is direct vs polite"We say what we mean; we mean what we say."
Quality standardsWhat good work looks like, what gets shipped"Done is better than perfect, but only barely."
Team dynamicsHow team members treat each other, hierarchy and autonomy"Senior people do junior work."
Growth and learningWhether and how the team develops over time"Hire for the next role, not the current one."
Failure toleranceHow the team handles mistakes and risks"Mistakes get reviewed, not punished."
Boundaries and limitsWhat the company will not do, who it will not work with"We say no often."

The pattern that separates good values from generic ones: good values usually combine two categories or push hard against a default. "Customer truth, not customer comfort" combines customer orientation with communication norms, and pushes against the default of customer pleasing. "Senior people do junior work" combines team dynamics with humility, and pushes against the default of seniority bringing privilege. The friction in the value is what makes it distinctive.

Integrity as a Value: The Behaviors That Make It Mean Something

This guide has been hard on integrity as a label, and that is fair: on its own it describes every company that has ever printed a poster. The word becomes usable the moment it carries behaviors, and examples of integrity in the workplace are easy to name once you look at decisions instead of adjectives.

Where it comes upWhat integrity looks likeWhat the violation looks like
A mistake that cost somethingThe person who made it names it before anyone else finds it, with the number attachedThe mistake surfaces three weeks later, in a customer email
A quote that turned out to be too lowYou charge what you quoted and absorb your own scoping errorThe invoice quietly grows to cover it
A reference call about a former employeeYou describe the work honestly, including the parts that went badlyA warm reference for somebody you would not rehire
A customer about to buy the wrong thingYou talk them out of it and lose the saleYou take the order and let them find out later
Something said in a 1:1It stays there, including when other people ask about itIt becomes context in the next management meeting
A rule you set for the teamIt applies to you on the day it is inconvenientFounder exceptions that nobody says out loud

The right-hand column is the giveaway. Every violation there is the cheaper option in the moment, which is why the value only counts if you can name the last time it cost you money, a customer, or a hire. If nothing comes to mind, the word is still decoration.

Embedding Values in Hiring

The hiring process is where values either start working or get exposed as decoration. A company that claims to value direct communication but never tests for it during interviews has not actually committed to direct communication; it has committed to the marketing copy. If values never change who gets hired and who gets rejected, they are not real.

Values belong in three places in the hiring process. First, the job description: name the values explicitly so candidates can self-select. Many candidates will read "we say no often" or "disagree directly, then commit" and decide the company is not for them. That is success, not failure, because self-selection saves both sides time.

The interview is the second place: ask values-aligned questions that probe for behavior, not just opinions. The rubric is the third: score candidates on values fit explicitly, alongside skills.

Values-based hiring rubric (sample)
Value: Direct communicationInterview question:"Tell me about a time you disagreed with a manager and said so directly. What did you say, and what happened?"Score:
  • 4 (Strong fit): Concrete example. Spoke up early. Treated disagreement as normal, not dramatic.
  • 3 (Good fit): Concrete example but only after building courage. Functional in our culture.
  • 2 (Concerns): Avoided the disagreement. Vague answer about "going along."
  • 1 (Misaligned): Frames disagreement as conflict. Implies it is rude to speak up.

The rubric format above produces three benefits. First, it forces interviewers to score, not just react. Second, it creates consistency across interviewers, who are otherwise calibrating to their own preferences. Third, it generates documentation that protects against discrimination claims; the basis for hiring decisions is documented and tied to specific behavioral evidence rather than gut feel.

One caution before you build one. The Uniform Guidelines on Employee Selection Procedures define a selection procedure as any measure used as a basis for an employment decision (29 CFR 1607.16), and a values score is one of those measures.

The Guidelines reach private employers through Title VII, a federal law against employment discrimination, which the Equal Employment Opportunity Commission (EEOC) applies to employers with 15 or more employees. The smallest teams are outside them for now, but not once they reach that line.

Whatever your size, the practice is the same: keep the scored behaviors job-related, run the same rubric on every candidate for the role, and keep the sheets afterward.

The hardest moment in values-based hiring comes when a candidate is technically excellent but values-misaligned. The default move is to hire them and hope the misalignment will not matter. It always matters. A senior misaligned hire reshapes the team within months because they bring their own values and they have authority to enforce them.

The discipline of values-based hiring is rejecting talented misaligned candidates, especially when the role is hard to fill. Doing this once or twice is what makes the values credible to the team.

Embedding Values in Onboarding

Values that appear once in the welcome packet on Day 1 fade by week three. Values that appear at least three times in the first 90 days, in different formats, stick. The pattern that works has four touchpoints:

1
Day 1: Written introduction
Values appear in the welcome packet and handbook with full definitions, behavioral examples, and violation examples. The new hire reads them as part of orientation, not a separate values training.
2
Week 1: Manager conversation (30 min)
The new hire's manager walks through each value with concrete examples of recent decisions: 'Last quarter we turned down a $40K project because of [value X]. Here is what that looked like in practice.' Real examples make the values feel operational.
3
Day 30: Reflection check-in
Manager asks the new hire which values felt strong in their first month and which felt absent. This surfaces gaps between stated values and lived culture, plus shows the new hire that values are an ongoing conversation, not a Day 1 deliverable.
4
Day 60-90: Values applied to their work
The manager points out moments when the new hire's decisions or behavior matched a specific value, by name. 'That conversation with the customer was a great example of [value X].' Naming reinforces.

Values are not a separate onboarding workstream; they are how the broader onboarding process is delivered. Every onboarding touchpoint can either reinforce or undermine values. A company that says "direct communication" but produces a 47-page onboarding deck full of corporate hedging has already shown the new hire what values are real.

Onboarding Drives Values Adoption
According to Gallup (2018), only 12% of employees strongly agree that their organization does a great job onboarding new employees, and Gallup, citing SHRM research, reports that turnover can run as high as 50% in the first 18 months (Gallup). Values transmission is what a thin onboarding program drops first: nobody tells the new hire how decisions actually get made here.
What worked for me
The shift that mattered most was moving values from the welcome deck into the manager 1:1. When values are presented in a deck, they feel like corporate decoration. When the manager describes a real recent decision through the lens of a value, the new hire learns the values are tools that get used in real time. The deck is fine as a reference document, but the learning happens in conversation. We started having every manager prepare 2-3 real recent decision examples per value before the new hire's first week, and the engagement with values measurably improved.

Embedding Values in Feedback

Feedback is the third place values either start working or expose themselves as decoration. A company that has values but never references them in feedback has not made the values operational. They are wallpaper that nobody invokes when actual behavior is being evaluated.

Two simple practices embed values in feedback. The first is to name the value when giving positive feedback: "That decision to push back on the customer's scope expansion was a clear example of [value X]."

The second practice is to name the value when giving constructive feedback: "The way that meeting went, where we let the senior person dominate without pushback, was the opposite of [value Y]. Let's talk about why that happened." Both practices reinforce the values as an active framework, not a static document.

Feedback contextWithout valuesWith values
Positive feedback in 1:1"Great job on the customer call.""That call was a perfect example of customer truth over comfort. You told them their plan would not work, and they thanked you."
Constructive feedback after a missed deadline"You missed the deadline. Let's figure out why.""You missed the deadline. We say ship and learn, which means shipping at 80%, not waiting for 100%. What stopped you from shipping at 80%?"
Performance reviewGeneric ratings on competenciesSpecific behavioral examples tied to each value, both positive and constructive
Team meeting where someone got steamrolled"Let's make sure everyone gets heard.""That conversation was the opposite of disagree directly, then commit. We need to fix the dynamic that made [person] not push back."

Naming the value does four things. It connects abstract principles to concrete behavior. It teaches the team how to recognize the values in real time. It makes feedback feel principled rather than personal. And it builds the muscle of using the values, which is what eventually makes them feel natural rather than imposed.

The most consequential place to apply this is the performance review, where values either become real consequence or stay decorative.

Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
See It in Action

Documenting Values in the Employee Handbook

Where you put your values matters less than that you put them somewhere durable, accessible, and referenceable. Most small businesses use the employee handbook for this purpose. The format that works has four components.

  1. The values themselves, with full anatomy. Each value gets a label, definition, 3-4 behavioral examples, and a violation example. This is the format from earlier in this guide.
  2. Why these values, not others. A short paragraph explaining the choice. This guards against the "these were copied from another company" perception and grounds the values in the team's history.
  3. How values get used. A short section on where values appear in practice: hiring, onboarding, performance reviews, team meetings. This signals that the values are operational, not decorative.
  4. How values get updated. When values get reviewed, who has input, and how changes get made. Without this, values drift; with it, values stay alive.

The handbook section on values should be 2-3 pages, not 10. Longer treatments lose the team's attention. Shorter treatments lack the behavioral examples that make values usable.

One mistake to avoid: putting values in a separate document from the handbook (like a "Culture Deck" or "Values Manifesto"). Separation signals that values are special, which usually means they get filed somewhere and forgotten. Integrating values into the handbook signals that they are part of the operating system, like benefits and paid time off. The integration is what keeps them in the team's line of sight.

When Values Conflict With Each Other

One of the most useful tests of whether your values are real: do they ever conflict with each other? If the answer is no, your values are probably too vague or too universally applicable to be useful. Real values often pull against each other in specific situations, and the team needs to know how to resolve the tension.

Common value conflicts in small business:

Value 1Value 2Conflict scenarioHow to resolve
Move fastQuality mattersShipping a feature with known bugs to hit a deadlineRanking the values: which one wins by default? Document the priority order.
Customer obsessionSustainable teamCustomer demands work that requires team weekendsPre-decided exception rules: 'Customer obsession does not include weekend work without team consent.'
Direct communicationPsychological safetySenior person disagreeing publicly with junior person in a meetingRefining the value definitions: 'Direct, but in private; positive in public.'
Hire reluctantlyCustomer obsessionCustomer demand exceeds team capacity for two quartersTime-boxed temporary exceptions, with clear conditions for hiring or saying no to customers.

There are three ways to handle value conflicts. The first is ranking: explicitly stating which value wins when two collide. Some companies rank their values numerically (1-6) and treat the order as load-bearing. The second is exception rules: defining the specific situations where a value does not apply. The third is refining the definitions: making the values precise enough that the conflict resolves itself.

Whichever approach you use, the key is to acknowledge that conflicts will happen and have a pre-decided answer rather than improvising in the moment. Improvisation under pressure usually defaults to whichever value is more comfortable in that situation, which is rarely the same as which value should win on principle.

Enforcing Values When People Break Them

Values that are not enforced are not values. They are decorations. The hardest enforcement decision is when a high-performer consistently violates a stated value. Three options exist, and only one of them preserves the values: address the behavior directly, even if it costs the relationship or the role.

ApproachWhat happensResult for values
Ignore the violationThe high-performer continues to violate the value. Other team members observe the inconsistency.Values are exposed as fake. Team learns enforcement is selective. Cultural decay accelerates.
Address but tolerateManager discusses the issue once, gets a verbal commitment, but no behavioral change happens. No further action.Worst of both worlds. Values are stated but not real. Team learns there are no consequences.
Address and follow throughManager raises the issue, sets a clear expectation, and follows through with consequences if behavior does not change, including termination if necessary.Values become credible. Team learns the values are real. Difficult short-term, healthy long-term.

Following through is hard the first time, especially when the violator is senior, technically excellent, or hard to replace. The reason it matters: the rest of the team is watching to see if the values are real. The first time you tolerate a senior violation, you have communicated to everyone else that the values are negotiable. Cultural drift starts there.

This is also why values matter for legal protection in addition to culture. When values are documented, applied consistently, and enforced through documented decisions, they become part of the legitimate, non-discriminatory basis for employment decisions.

Inconsistent enforcement, where one person is held to the values and another is not, is exactly the kind of pattern that produces discrimination claims. The EEOC small business guide covers the basic anti-discrimination framework that applies to small employers.

The High-Performer Values Test
The single biggest predictor of whether a small business will preserve its values is whether the founder is willing to lose a high-performer over values. The first time this happens (and it will, eventually), the team learns whether the values are real. If the high-performer keeps violating the values and stays, the values are decorative. If the high-performer is held accountable, including being asked to leave if needed, the values become credible. There is no middle path.

When and How to Change Your Values

Values should be reviewed annually but changed rarely. The annual review confirms whether the values still describe how the team operates. Most years, the answer is yes and no changes are needed. The review itself is the discipline that keeps values alive. Skipping the review is what causes drift.

Three legitimate reasons to actually change values:

  1. The company has grown significantly. Values that fit the original team may not fit the company it has become. The company has changed; the values should reflect that.
  2. The business has shifted. Entering a new market, changing customer segments, or pivoting the product can shift what really matters operationally.
  3. The values are aspirational rather than descriptive. If the annual review reveals that the team consistently violates a stated value because it never matched reality, the value should be cut, not enforced harder.

Three illegitimate reasons to change values:

  1. A new senior hire wants to. Values are the company's, not the new senior hire's. If the misfit is significant, that is a hiring problem, not a values problem.
  2. The values are uncomfortable. Real values cost something. Cutting values because they are inconvenient eliminates the parts that actually function.
  3. It has been a while. Values do not get stale just because time has passed. They get stale when they no longer match reality. Change for its own sake destabilizes.

The cadence that works: annual review with most changes being refinements (clearer definitions, updated behavioral examples), occasional value additions or removals when the company has genuinely shifted, and major rewrites only at significant scale transitions (the move from a founder-led team to a managed one, or from small business to mid-size). The same lifecycle applies to organizational values as the company moves through larger stages.

The review is a one-hour meeting with evidence, not a discussion about wording. Fill the first four columns before the meeting starts and most of the argument disappears.

Annual Values Review Record
ABCDEFGHIJ
1ValueDecisions this year it actually droveTimes it was cited in a hiring decisionTimes it was named in feedback or a reviewViolation we let passStill describes how the team behaves? (Y/N)Verdict (keep, refine, cut)Change made to the wording or behaviorsReviewed byDate
2Example: We say no oftenTurned down two projects outside our scopeKeep
3
4
5
6
7
8

A value with an empty decisions column and an empty citations column is not being used, which is a finding rather than a failure. The violation-we-let-pass column is the uncomfortable one and the most informative, because a value nobody enforced for a year is already gone whether or not it is still written down.

Common Mistakes in Defining and Using Values

Eight mistakes come up again and again when small businesses define or start using values for the first time. All of them are avoidable once you see the pattern behind them.

Writing values that any company could put on its website"Integrity, excellence, teamwork" could sit on almost any company website without anyone noticing. If your values do not specifically belong to your company, they are corporate wallpaper. Write values that would feel wrong on a competitor’s site.
Choosing values you wish were true instead of values that are trueAspirational values that contradict actual behavior produce cynicism, not culture. If your team works late every night, "work-life balance" is not your value. Pick values you can demonstrate today, not ones you hope to grow into.
Not defining what each value means in practice"Customer obsession" without behavioral examples means nothing. Each value needs 3-4 specific behaviors that show what it looks like in real decisions. Without behaviors, values are just nouns.
Picking 8-10 values instead of 4-6When everything is a value, nothing is. Most teams cannot remember 8 values, let alone use them in decisions. Cut ruthlessly. The discipline of values is the discipline of choosing what matters most.
Setting values once and never revisiting themValues that worked with the founding team may not fit once you are hiring managers. Review values annually. Add, remove, or refine based on what actually drives the team. Values are a living tool, not a stone tablet.
Communicating values once during onboarding and never mentioning them againValues that appear in the handbook on Day 1 and never come up again are decorative. Reference them in feedback, hiring, performance reviews, and team meetings. Repetition is what makes values stick.
Treating values as a marketing exercise instead of a management toolValues written by the marketing team for the careers page are PR copy, not values. Real values come from the founder and senior team and get pressure-tested against actual decisions before being published.
Ignoring violations of stated valuesIf you say "customer obsession" and tolerate a senior employee who consistently dismisses customer feedback, you have shown the team your real values. Enforcement is what makes values credible. Without enforcement, they are noise.

The pattern across these mistakes: treating values as a static deliverable instead of an active management tool. Values that are written, posted, and forgotten produce nothing. Values that are written, used in decisions, named in feedback, and enforced when violated produce a coherent culture. Most companies stop after the writing.

Values vs Rules and Policies

One subtle but important distinction: values are not rules. Values describe the principles that guide decisions when no rule applies. Rules are the specific instructions for specific situations. A small business needs both, and confusing them produces problems in both directions.

Values
Guide decisions when no rule applies
Apply across every situation
Help people choose between two acceptable options
Are stable across years
Get cited when explaining why we did something unusual
Example: "We are direct with each other."
Rules and policies
Tell people exactly what to do
Apply to specific situations
Have a single correct answer
Change as the company grows
Get cited when enforcing compliance or process
Example: "Submit expense reports within 30 days."

The relationship between values and rules: rules implement values in specific cases. The expense report rule ("submit within 30 days") is downstream of values like accountability or operational discipline. The customer response rule ("reply within 4 hours") is downstream of customer obsession. Good rules can usually be traced back to values. Rules that cannot be traced are usually arbitrary holdovers worth questioning.

The error in the other direction is treating values like rules. "We are direct with each other" is a value, not a rule. It does not specify exactly what to say in every meeting. It guides how to think about communication, with the team applying judgment in specific situations. Trying to operationalize values down to rule-level specificity destroys their flexibility, which is precisely what makes values useful for situations rules cannot anticipate.

Can You Measure Whether Values Are Working?

You cannot measure values directly, but you can measure whether they are working through proxy indicators that are surprisingly clear. Values are squishy by nature, which makes some founders skeptical of measuring them. The skepticism is misplaced.

SignalWhat it indicatesHow to track
Team members reference values unprompted in meetingsValues have entered the operating vocabularyManager observation, periodic notes
Values appear in performance reviews and feedbackValues are operational, not decorativeAudit reviews quarterly for values references
Hiring decisions cite specific valuesValues are functioning as a screening toolTrack scorecard data, look for values-based decisions
New hires can recite the values within 30 daysOnboarding is transmitting values effectivelyQuick informal poll at the 30-day check-in
Engagement scores correlate with values alignmentValues are connected to actual experienceAnnual or pulse engagement survey, segmented by values fit
The team can name decisions that came from valuesValues are visible in real choicesQuarterly leadership team review of recent decisions

The single most predictive signal is whether team members reference values unprompted. When values come up naturally in real conversations (without management nagging), the values have crossed from decoration to operating system. Conversely, when values only come up in scheduled values-related meetings, they are still decorative.

If you want to measure values alignment more formally, surveys are the most practical tool at small business scale.

According to a Gallup and Stand Together survey fielded in August 2025, 50% of employees with a strong sense of purpose in their work are engaged, against 9% of those with a weak one (Gallup). That is why measuring engagement is partly measuring whether your values are landing.

First-year turnover is another signal worth watching. According to the Work Institute, more than a third of newly hired employees quit inside their first year. In one Work Institute case study of nurses who left a health system within their first year, job expectations were the number one reason for leaving, and pay was not.

A new hire's expectations cover the duties, the hours, the manager, and the way the place operates, so an early voluntary exit is worth reading as feedback on the whole picture, values included, rather than assumed to be a pay problem.

The Long-Term View on Company Values

The honest case for company values at small business scale is not that they are magic. They are an operational tool that, when used consistently for years, produces a team where decisions, hires, feedback, and conflicts all reference the same shared principles.

The compound effect is large but slow. Every team I have watched abandon its values did it within a year or two, because the compounding is invisible while it is happening. The teams that keep at it for 8-10 years build cultures that are hard to replicate.

The work of values is mostly in the using. Writing values takes a half day. Embedding them into hiring takes a quarter. Embedding them into onboarding takes 6-12 months of refinement. Embedding them into feedback takes years of practice. By year 5, the values either are the company or they are not. There is no third state.

One number is worth keeping in view while you do it. According to Gallup (May 2026), 20% of US employees strongly agree that they feel connected to their organization's culture (Gallup). Gallup describes culture as "how we do things around here," which is the same job a working set of values does. For the other 80%, nobody ever spelled out how things are done around here.

For small businesses, the honest payoff of doing this work is not in branding or marketing. It is in the daily decisions that go more smoothly because everyone understands the principles, the hires that work out more often because misalignment was caught earlier, the conflicts that resolve faster because there is shared language for the disagreement, and the team that stays longer because they actually like working there.

None of these gains is large on its own. Together, they are the difference between a small business that grinds itself down through cultural drift and one that compounds its operating advantage year after year. The first step is small: block a half day with your founding team and run the six-step workshop above, starting with the solo list.

How FirstHR Fits

The honest disclosure: FirstHR is not a values or culture platform. We do not have a values dashboard, a culture survey tool, or a recognition module. The platform handles onboarding, employee profiles, document management, org charts, and the operational HR foundations that most small businesses need. Values, when you adopt them, will live in your handbook, your hiring rubrics, and your team rituals.

That said, values work better when the underlying people operations are working. A team running values workshops on top of broken onboarding will struggle no matter how well the values are written. A team running values on top of consistent onboarding, clear roles, and structured feedback will compound the benefits over years. FirstHR exists to handle the operational HR foundation at flat, predictable pricing ($98 to $198 per month), so that owners and operators can focus on the higher-impact work of writing real values, embedding them into hiring, and protecting them through enforcement.

Key Takeaways
Company values are the few principles that guide everyday decisions when no rule applies, and they describe how the company actually operates.
Useful values are specific to your team (not generic), demonstrable in actual behavior (not aspirational), and small in number (4-6 maximum) so the team can remember them.
Values matter more (not less) at small scale because the founder cannot be in every room and values become the primary mechanism for distributing judgment.
Write every value in four parts (a short label, a 1-2 sentence definition, 3-4 behavioral examples, and a violation example), because a label on its own is just a noun.
Run a focused half-day workshop with 2-5 founding team members: solo brainstorm, pool, pressure-test against real decisions, cut to 4-6, define each fully, then live with the draft for a week.
Embed values in hiring (rubrics, scorecards, interviews), onboarding (a written Day 1 introduction, a Week 1 conversation, and a Day 30 reflection), feedback (name the value when giving praise or criticism), and the handbook.

Frequently Asked Questions

What are company values?

Company values are a short list of principles that tell your team how to decide when no rule or policy settles the question. They cover how the business makes choices, how it treats employees and customers, and which way it leans when two good options compete. Mission says what the company does and vision says where it is going; values say how it behaves along the way, every day. The ones that work are specific to one company, visible in what people actually do, and few enough that everyone can name them from memory.

What are good company values for a small business?

Good values for a small business are ones that are specific to your team, demonstrable in your real behavior, and small in number (4-6 maximum). Avoid generic words like 'integrity,' 'excellence,' or 'teamwork' that apply to any company. Instead, name what is genuinely distinctive about how your team operates. If your values would feel wrong on a competitor's website, you are on the right track. Values should also be calibrated to your stage: a founding team needs simpler values than a company that already runs through managers.

How many core values should a company have?

Most companies should have 4-6 core values, whatever their size. With fewer than 4 values, some part of how the team really works usually goes unnamed. Past 6 values, people stop remembering the list, and a value nobody can recall never shows up in a decision. That makes cutting the real work. Ending up with 10 candidates that all feel essential means you are still holding a wishlist, not a set of values. Before you publish, try a simple check: show the list to a colleague who missed the discussion, give them a minute and a half with it, and ask them to say it back. If they struggle, so will everyone else. Settle on the smallest number that still captures what sets your company apart.

What is an example of a company value?

A good example of a company value is 'Customer obsession,' as long as it is written out in all four parts. The label comes first. Next is a 1-2 sentence definition: we choose what is best for the customer over what is easiest for us. Then come 3-4 behaviors that show it, such as answering support requests within 4 hours, having every team member talk to a customer each quarter, and reviewing customer feedback every week. Last is the violation to watch for: waving off a customer request as not on the roadmap without first weighing it from the customer's side. On its own, the word tells a new hire almost nothing; the four parts together make it something they can act on.

What is the difference between company values and mission?

Mission describes what the company does and why it exists. Values describe how the company operates. A company mission might be 'Make small business HR effortless.' Company values might be 'Customer obsession, direct communication, ship fast and learn faster.' The mission tells you what you are building. The values tell you how you build it. Most companies need both, plus a vision (where the company is going) and a strategy (how it will win). Values are the most operational of the four because they get used in daily decisions.

How do I create company values for my small business?

Run a 6-step workshop with the founding team or senior leaders. Step 1: each person solo-brainstorms 10 values they think drive the team. Step 2: pool and group similar entries. Step 3: pressure-test each cluster against 3-5 real past decisions. Step 4: cut ruthlessly to 4-6. Step 5: define each value with a 1-sentence definition, 3-4 behavioral examples, and a violation example. Step 6: live with the draft for a week before publishing. Avoid the trap of writing values you wish were true; pick values you can demonstrate today.

What are the most common company values?

The most common company values are integrity, collaboration, customer focus, and respect. A 2020 MIT Sloan Management Review analysis of the official values statements of 562 large companies found integrity on 65% of them, collaboration on 53%, customer focus on 48%, and respect on 35%. Innovation, accountability, excellence, transparency, and continuous improvement are familiar too, but no other value appeared on more than a third of the lists. The problem with these is precisely that they are common. They describe almost any company, so they fail to differentiate yours. Better small business values are usually more specific: 'we are direct with each other,' 'we ship and learn,' 'we say no often.' If your values would not feel out of place on a Fortune 500 website, you have not done the work yet.

Should small businesses have written company values?

Yes, once you are hiring past the founding team. While the company is only its founders, their values are the company's values; formalizing them adds bureaucracy without benefit. Once you are hiring people who were not in the original room, you need shared language to discuss decisions, especially as new hires bring their own assumptions. Written values are not about putting them on the careers page; they are about having a vocabulary the team can use. The test of whether your values are working is whether anyone references them in actual decisions, not whether they are framed in the lobby.

What is the difference between values and culture?

Culture is how your company really behaves; values are the principles you have written down and committed to. Culture grows out of daily behavior: what people do, what gets rewarded, and what gets let slide. Values are the deliberate, written part. Ideally the two describe the same company, but they drift apart easily, and when the written version promises something the daily version does not deliver, people stop believing either one. So do not write values to sound inspiring. Write them to describe the culture you already have, or one you are prepared to put real effort into building.

How do you communicate company values to new hires?

Teach new hires your values at least three times in the first 90 days, not just once on Day 1. Start with the welcome packet and handbook, where each value appears with its full definition and behavioral examples. During the first week, the manager holds a 30-minute conversation walking through how each value shaped a recent decision. At the 30-day check-in, the manager asks which values the new hire has seen in action and which seemed missing. After that, keep naming values when the new hire's own work reflects one. A value that exists only in writing fades by week three; one that keeps coming up in real conversations stays.

How often should you update company values?

Review your company values once a year and change them only occasionally. The yearly check asks one question: do these values still match how the team really works? Usually they do, and nothing needs to move. Real changes tend to follow big shifts, such as a founder-led team starting to run through managers, a move into a new market, or a change in leadership. Frequent rewrites unsettle the team, while never changing them at all suggests nobody is using them. A yearly review with the occasional real edit is the rhythm that keeps them honest.

Can company values be enforced?

Yes, and they have to be, because values nobody enforces turn into decoration. Enforcement runs through three channels. Hiring is the first: you turn down talented candidates whose way of working clashes with the values. Feedback is the second: you say out loud, as it happens, when someone's behavior fits a value or breaks one. Performance reviews are the third, and they can end in termination: someone senior who keeps breaking a stated value should face real consequences, up to and including being asked to leave. The toughest case is a star performer who ignores the values. Keep them on without consequences, and everyone else concludes the values were never real.

Ready to transform your onboarding?

7-day free trial No credit card required
Start Your Free Trial