A company should have the smallest set of core values that covers its distinct, nonnegotiable expectations for how people work. Choose the values by the decisions they guide, not by a fixed quota. A short list still needs clear behavioral expectations; cutting words without defining those expectations does not make your culture easier to understand.
TL;DR
- How many core values should a company have? Keep only distinct commitments that guide real decisions.
- Myculture’s recommendation: define observable behavior before using values alignment in hiring.
- Merge overlapping values, separate working rules, and test each commitment against a difficult trade-off.
- Culture fit should assess job-relevant expectations, not shared hobbies, backgrounds, or personality sameness.
Why this matters
A values discussion becomes useful when it changes what you ask candidates, recognize in employees, and expect from managers. Without that connection, choosing the list length is an editing exercise rather than a hiring decision.
For your 2026 values review, start with the behavior you need to explain. Your interview scorecards for structured hiring decisions should describe evidence of those expectations, rather than ask interviewers whether someone simply feels like a fit.
A candidate deserves to understand the expectation behind a culture-fit judgment. Your hiring team also needs a reason it can explain without relying on personal preference.
How many core values should a company have?
Keep a value only when it adds a distinct, observable expectation that another value does not already cover. Stop adding values when the next proposed statement repeats an existing commitment, describes a role-specific skill, or belongs in a workplace policy.
Use this sequence to decide what stays:
- Collect decisions. Gather examples of difficult hiring, feedback, customer, and teamwork decisions. Identify the behavior you wanted and the alternative you rejected.
- Name commitments. Turn those examples into plain-language expectations. Describe what employees should do, not just an admirable quality.
- Merge overlaps. Combine statements that would produce the same feedback or interview evidence. Different labels do not automatically describe different values.
- Test trade-offs. Ask what each commitment requires when following it becomes inconvenient. Remove statements that nobody can connect to a meaningful choice.
- Check evidence. Define what a manager or interviewer would actually observe. Keep the commitments you can explain and apply consistently.
This is a decision process, not a formula for producing a predetermined total. Your final list should reflect the distinctions your company genuinely needs to make.
Decide what each value changes before deciding how many values to keep.
Compare the ways to organize your values
You can keep the headline list concise without forcing every expectation into it. Separate enduring commitments from the practices that explain how a particular team works.
| Approach | Best for | Advantage | Limitation |
|---|---|---|---|
| Short core list | Companies with clearly distinct shared commitments | Keeps the central expectations easy to communicate | Broad labels need behavioral examples to be useful |
| Expanded core list | Companies that can explain a separate decision behind every commitment | Makes more distinctions explicit | Overlapping statements create unnecessary repetition |
| Core values plus working standards | Companies separating shared commitments from team practices | Preserves shared expectations while allowing different workflows | Requires a clear boundary between a value and a local rule |
Use core values plus working standards when the disagreement concerns how work gets done rather than what the company stands for. Do not turn every preferred meeting format, communication habit, or manager preference into a company-wide principle.
A short core list: keep the meaning specific
A short list works when each statement carries a clear expectation. Its strength is focus; its weakness is the temptation to use broad words that leave employees guessing.
Consider an illustrative value such as accountability. The label alone does not explain whether you expect someone to escalate a risk, acknowledge a missed commitment, or repair an error. Write the behavior underneath it.
A useful statement would explain that employees flag a threatened commitment, identify the impact, and agree on a next step. That gives a manager something concrete to discuss without treating every mistake as a values violation.
Keep the short list only if its supporting descriptions preserve the distinctions employees need. Brevity is not a reason to merge expectations that lead to genuinely different decisions.
An expanded core list: require a separate purpose
An expanded list needs a stronger editing test. Each additional commitment should answer a question that the existing values leave unresolved.
For example, ownership and accountability might describe the same expectation in your company. If managers would use the same incident to explain both, combine them or clarify their different meanings before keeping both.
The advantage of an expanded list is specificity. The drawback is the work required to explain where each value begins and ends.
Do not retain a value solely because someone prefers its wording. Keep it because removing it would erase an important behavioral distinction. Apply that test to the whole list, including statements proposed by senior leaders.
Core values plus working standards: separate principles from practices
A company-wide commitment should apply across roles, even when the behavior looks different. A working standard explains how a team puts that commitment into practice.
For example, sharing relevant information is a possible commitment. A particular reporting format is a practice. Treating them as identical would confuse the intended behavior with a preferred tool or routine.
For your 2026 culture documentation, give each layer a clear home:
- Core value: The enduring expectation that applies across the company.
- Behavioral description: What acting on that expectation looks like.
- Working standard: The role-specific or team-specific practice used to support it.
- Policy: A formal requirement that needs its own explicit documentation.
This structure keeps the headline list focused without hiding the details people need. Its limitation is maintenance: when a practice changes, update the working standard rather than quietly changing the meaning of the value.
Why the right number of core values varies
The right total depends on how much distinct meaning the list contains. Use these factors to evaluate your draft rather than comparing its length with another company’s list.
- Overlap between commitments. If separate labels describe the same behavior, merge them. Keep separate values when they resolve different choices.
- Clarity of work-style expectations. Decide which expectations are shared commitments and which are preferences about communication or workflow.
- Team compatibility requirements. Explain how people should collaborate without requiring everyone to have the same personality or approach.
Check values alignment before the interview
Values Alignment compares each candidate's values with the ones your team lives by, and shows where they match and where they may clash.
See Values Alignment- Use in hiring. Retain values you can translate into job-relevant questions and observable evidence. Rewrite labels that invite intuition alone.
- Use in feedback. Check whether managers can describe both behavior that meets the expectation and behavior that conflicts with it.
Do not add a value simply to cover every desirable characteristic. Skills, performance goals, working standards, and values serve different purposes; your documentation should preserve those differences.
How do you turn company values into hiring criteria?
Translate each value into an expectation, a question, and an evidence standard. Assess behavior relevant to the job, not whether a candidate resembles the existing team.
For an illustrative collaboration value, ask about a disagreement over a shared deliverable. Follow up on what the candidate did, how they handled competing needs, and what happened next. Do not substitute conversational warmth for evidence of collaboration.
Before using the question in your 2026 hiring process, define what a strong answer demonstrates. Also define what would leave the interviewer uncertain, so a lack of detail triggers a follow-up rather than an unsupported rejection.
Keep values alignment separate from personality sameness
Values concern what a person considers important; personality describes tendencies in how a person thinks, feels, and behaves. Do not treat a personality characteristic as automatic proof that someone shares or rejects a company value.
A reserved candidate can contribute to collaborative work. An outgoing candidate still needs to demonstrate how they listen, share responsibility, and handle disagreement.
Use the same job-relevant criteria across candidates. Allow different examples and communication styles to demonstrate the same underlying expectation.
Use an assessment to inform the conversation
Myculture is best suited to HR teams, recruiters, and staffing/RPO firms evaluating candidate values, work style, and team compatibility. The Myculture culture-fit and personality assessment platform addresses those hiring questions; it does not replace the work of defining your company’s expectations.
The useful distinction is scope: an assessment adds information about the candidate, while your hiring framework explains what matters for the role. Treat Myculture culture-fit assessment information as input to a structured conversation, not as a substitute for skills evidence or a documented hiring decision.
How do you test whether your values are usable?
Test the draft against a realistic disagreement before publishing it. Choose a situation where reasonable employees would have competing priorities, such as protecting quality while responding to an urgent customer request.
Ask managers to explain which value applies, what action they expect, and what evidence would change their judgment. If the same statement produces incompatible explanations, clarify the behavioral description.
Then ask employees to explain the expectation in their own words. Do not treat this as a memorization contest; check whether people understand the decision the value is supposed to guide.
For a 2026 rollout, record the examples alongside the value statements. A usable guide should help a new manager explain an expectation without having to reconstruct the original leadership discussion.
Should every department have the same core values?
Company-wide core values should express shared commitments, while departments can use different working standards to apply them. Keep the principle consistent and explain the role-specific behavior underneath it.
A customer-facing team and an internal operations team need not use identical workflows to demonstrate the same commitment. Do not mistake different practices for incompatible values.
5 minutes
to create your first hiring assessment
Add Values Alignment to a role and see where each candidate matches your core values before the first interview.
See Values AlignmentWhen should a company change its core values?
Change a core value when the company intentionally changes a fundamental expectation, or when the wording no longer describes the commitment accurately. Do not rewrite the list merely to refresh a presentation.
If your 2026 review exposes a gap between stated and rewarded behavior, decide which needs to change. Renaming the value does not resolve inconsistent management decisions.
Can a company have too few core values?
A company has too few core values when important shared commitments disappear inside broad statements that nobody can apply consistently. Add a separate value only after checking whether a clearer behavioral description would solve the problem.
The opposite problem is repetition: several values that all produce the same expectation. Edit for distinct meaning in both directions.
One last thing
Test a value where honoring it is inconvenient. A statement such as transparency becomes meaningful when a manager must share unwelcome information, not merely when there is good news to announce.
Before adding another value, ask what decision it would change. If you cannot explain the answer, improve the values you already have instead of lengthening the list.