Core Values Survey Questions (Employee Template + Results Guide)
Use this core values survey to measure three things fast: (1) do employees understand your values, (2) do they see the values modeled in day-to-day behavior and decisions, and (3) do they feel safe speaking up when values are compromised. You will get a ready-to-copy question bank, rollout checklist, and a score-to-action workflow you can use to brief leaders and run follow-up workshops.
Trusted by 5000+ Brands
Core Values Survey Questions, Organized by What You Need to Learn
Use this section to pick questions that separate "we say it" (awareness) from "we do it" (observed behavior) and "we protect it" (accountability + speak-up safety).
- Default set: 24-32 items total (8 themes x 3-4 items) + 1-2 narrative prompts.
- Default response options: mix of Agreement (5-point) and Frequency (5-point) so you can spot value-behavior gaps.
- Default timing: 5-8 minutes; cut items until you hit that target.
Agreement (5-point): Strongly disagree / Disagree / Neither / Agree / Strongly agree
Frequency (5-point): Never / Rarely / Sometimes / Often / Always
Examples (open text): Use 1-2 open-ended questions to capture concrete examples and barriers.
Awareness and recall (do people know the values?)
"I can name our core values without looking them up."
Why it matters: If recall is low, later "behavior" scores are hard to interpret because people are answering from guesswork.
When to use: Include in baseline runs and after a values refresh.
"I understand what each core value means in practical terms."
Why it matters: Clarity reduces "multiple interpretations" that create inconsistent decisions across teams.
When to use: Always; trend this item run over run.
"I know where to find examples of what our values look like in action."
Why it matters: People need easy access to examples (stories, decision principles, playbooks) to apply values under pressure.
When to use: Add when you have (or plan to create) a values-in-action library and want to track adoption.
Clarity and usefulness (do values help people do the work?)
"Our core values help me make day-to-day decisions."
Why it matters: Values that do not change decisions become posters, not operating rules.
When to use: Include in every run; use as a leading indicator for behavior items.
"I can describe what behaviors are expected for each core value."
Why it matters: Behavior definitions reduce vague debates like "That is not respectful" without shared criteria.
When to use: Use before/after you publish behavior examples per value.
"When priorities conflict, our values help clarify what to do."
Why it matters: Tradeoffs are where values get tested; this item predicts whether values will survive deadline pressure.
When to use: Add if you want your results to feed a decision-principles workshop.
Observed behaviors (do people see values lived?)
"In my area, people demonstrate our core values in how they treat each other."
Why it matters: This captures the day-to-day social norm, not a policy statement.
When to use: Always; treat as a core outcome item for values adoption.
"I have seen teams change a plan or decision to better align with our values."
Why it matters: Values show up as course corrections, not perfect behavior.
When to use: Use after major launches, reorganizations, or policy changes.
"I have seen people prioritize our values even when it slowed things down."
Why it matters: This checks whether "speed" wins every time, which often signals values drift.
When to use: Add in high-pressure environments where shortcuts are tempting.
Leadership modeling (do leaders walk the talk?)
"Senior leaders model our core values in their actions."
Why it matters: If employees do not see modeling at the top, "values" reads as branding, not expectations.
When to use: Always; compare senior leader perceptions to employee perceptions.
"My manager reinforces our values in day-to-day coaching and feedback."
Why it matters: Manager reinforcement is where values become weekly habits.
When to use: Include whenever you plan to run manager action planning off the results.
"Leaders explain decisions in a way that connects back to our values."
Why it matters: Explanation builds trust and teaches people how to apply values under ambiguity.
When to use: Add when you want leaders to improve decision transparency.
Decision tradeoffs (what wins when values compete with targets?)
"We talk openly about tradeoffs between hitting targets and living our values."
Why it matters: Silence around tradeoffs pushes people to guess, and many will guess "results at any cost."
When to use: Use when you have measurable targets that can pressure behavior (sales, delivery, productivity).
"I feel pressure to compromise our values to get work done."
Why it matters: This is an early warning signal for values breakdowns and "ends justify means" norms.
When to use: Include in every run; treat hotspots as priority follow-up areas.
"When a value conflicts with a short-term goal, leaders support the values-aligned choice."
Why it matters: Support (or lack of it) determines whether employees take the personal risk of doing the right thing.
When to use: Add when you want actionable leader commitments tied to results.
Recognition and accountability (do values get rewarded and enforced?)
"People are recognized for demonstrating our core values."
Why it matters: Recognition teaches "what good looks like" faster than value statements.
When to use: Include if you have (or plan) a recognition program tied to values.
"When someone acts against our values, it is addressed appropriately."
Why it matters: Unaddressed violations train everyone that values are optional.
When to use: Always; pair with speak-up safety to understand why issues do or do not surface.
"Performance expectations in my area include how results are achieved (not just what is achieved)."
Why it matters: If "how" never matters, you will get values drift even with strong messaging.
When to use: Include if you want to update performance review criteria or manager coaching.
Speak-up safety (do people feel safe raising values concerns?)
"I feel safe raising a concern when I see behavior that conflicts with our values."
Why it matters: Low safety means you will under-detect issues because people stay quiet.
When to use: Always; treat this as a gating metric for how much you can trust other results.
"When people speak up about values concerns, leaders respond constructively."
Why it matters: Response quality determines whether employees speak up again next time.
When to use: Include if you want a clear leader behavior target after results sharing.
"I believe I can raise a values concern without negative consequences."
Why it matters: Fear of retaliation drives socially desirable answers and suppresses real examples.
When to use: Always; treat low scores as a priority risk area.
Alignment in people processes (do systems support values?)
"Our hiring process evaluates candidates on behaviors connected to our core values."
Why it matters: Hiring for value-related behaviors increases person-organization fit over time.
When to use: Use if Talent Acquisition and hiring managers will act on the findings (interview guides, rubrics).
"Onboarding helped me understand what our core values look like in my role."
Why it matters: Onboarding is your fastest window to set behavior norms and reduce future drift.
When to use: Include if you will segment new hires (0-90 days) as a separate cut.
"Performance reviews and promotions reflect how well people demonstrate our values."
Why it matters: If promotions ignore values, the org will learn that results outweigh behavior.
When to use: Add when you have a clear owner (HRBP or Talent) to adjust criteria after results.
Do this: For each value, write 2-4 observable behaviors and turn each behavior into a neutral item (no "always/never").
Example mapping: Value "Ownership" — Behavior "fixes issues without blame" — Item "People focus on solving the problem rather than assigning blame."
Quality check: Delete any double-barreled item by testing: can someone agree with one half and disagree with the other?
Choose themes you can act on
- Only include a theme if you can name an owner and a concrete next step for it. If you cannot, cut it and keep the survey short.
- Baseline: Pick 3-4 themes for your first run.
- Pulses: Add one optional theme per follow-up pulse once you have actions underway.
Design Choices That Change Candor (Scales, Anonymity, and Wording)
Use this section to set scales and reporting so your data is comparable over time and employees feel safe answering honestly.
- Default scales: 5-point for speed, with consistent anchors in every run.
- Default mix: Agreement for clarity + Frequency for observed behaviors and reinforcement.
- Default reporting: Anonymous results + small-n suppression for any subgroup below your minimum.
Scale: 5-point (see Likert scale options and best practices if you are deciding between 5 and 7).
Question mix: 60-70% frequency/behavior items, 30-40% agreement/clarity items, plus 1-2 open text prompts.
Completion target: 5-8 minutes. If your draft is longer, cut items before you launch.
| Design choice | Best for | Watch out for | Default |
|---|---|---|---|
| Agreement items ("I understand...", "Leaders model...") |
Clarity, usefulness, perceived leadership modeling; easy to trend. | Can sound aspirational; people may agree with the idea even if behavior is inconsistent. | Use for awareness/clarity and policy/process alignment. |
| Behavior frequency items ("I have seen...", "People address...") |
Day-to-day reality, reinforcement, accountability; surfaces gaps between words and actions. | Needs clear time frame if you want precision (example: "in the past 3 months"). | Use for observed behaviors, recognition, accountability, speak-up response. |
| 5-point scale | Fast completion, lower drop-off, easier comparisons across pulses. | Slightly less sensitive to small changes than 7-point. | Default to 5-point for most org-wide employee surveys. |
| 7-point scale | More sensitivity when you need fine-grained movement (example: mature programs). | Slower; more "middle" confusion; harder to explain to managers. | Use only if you already have stable trend data and need more resolution. |
| Anonymous reporting | Maximum candor because responses cannot be traced back to individuals. | Limits follow-up; requires strong open-text hygiene (no names) and suppression rules. | Default for values surveys, especially if trust is uneven. |
| Confidential reporting (identity known to admin, not to managers) |
Targeted follow-up with employees when you have a clear process and high trust. | Lower candor if people doubt confidentiality; can damage participation if misused. | Use only with a documented follow-up process and tight access controls. |
| Neutral wording | Cleaner measurement because items do not push people toward a "correct" answer. | Leading phrasing and double-barreled items reduce data quality; test each item for one idea. | Keep items single-idea, behavior-based; avoid "always/never" absolutes. |
Tourangeau, Rips, and Rasinski summarize how question wording and response processes shape accuracy; use that takeaway to keep items neutral and easy to answer under time pressure (The Psychology of Survey Response).
Do this next: lock your scale and anonymity setting before you edit question wording so you do not rewrite later.
Who Should Take a Core Values Survey (and How to Segment Safely)
Use this section to decide who to invite and how to segment without putting employee privacy at risk.
- Default audience: all employees.
- Default key cuts: manager vs individual contributor, department, location, tenure band.
- Default privacy rule: set a minimum group size (example: 5-10) and suppress anything smaller.
Org leaders see: org-wide results + top 3 hotspot cuts (example: Function A, Location B, Tenure 0-1 year), using small-n suppression (do not show any cut under your minimum).
Managers see: their team vs org benchmark only when the team meets the minimum response threshold; otherwise roll up to department.
Set your minimum now: Pick 5, 7, or 10 and document it in your reporting rules. If teams are small, then raise the threshold and roll up results.
Recommended respondent groups
- All employees (baseline): Use this to measure shared understanding and day-to-day norms across the org.
- People managers (must-have segment): Use this cut to compare "manager view" vs "employee view" on modeling, accountability, and speak-up response.
- New hires (optional cut, 0-90 days): Use this to validate whether onboarding messages match lived experience.
Safe segmentation defaults (use only what you will act on)
Start with these fields because they map to real owners: department (leader), location (site leader), level (leadership development), tenure (onboarding/retention), manager status (manager enablement).
- Use sampling and subgroup reporting rules to prevent re-identification.
- If a slice creates small groups, then roll it up (team → department → function) until it meets your minimum.
- Write down subgroup rules before you look at the data so you do not "hunt" for identifiable cuts.
ISO 20252 is a widely used standard for market and opinion research; use its spirit here by writing down your subgroup rules before you look at the data (ISO 20252 overview).
Do this next: confirm your reporting threshold and your top 3 segment cuts with leadership before you launch.
How to Customize and Roll Out a Core Values Survey (Checklist + Comms)
Use this section to launch cleanly — with neutral wording, a short field window, and clear privacy language that supports candid answers.
- Default build: map each value to 2-4 observable behaviors, then write items from those behaviors.
- Default fielding: 2-week window with 2 reminders (day 4-5 and day 10-11).
- Default trust setting: anonymous reporting + small-n suppression explained up front.
-
Translate values into behaviors: Write 2-4 observable behaviors per value, then convert each behavior into a single-idea item (no "and" chains, no "always/never").
-
Keep wording neutral: Remove loaded terms (example: "courageously") and swap for observable actions (example: "raises concerns"). Test each item by asking: can someone answer without guessing what you want to hear?
-
Pilot before you send org-wide: Run a 10-15 person pilot across functions/levels. Ask: "Which items were unclear?" and "Which items felt risky to answer?" Then edit.
-
Limit demographics to what you will use: If you will not report or act on a cut, remove the question. Fewer fields also lowers re-identification risk in small teams.
-
Set and explain privacy rules: State whether results are anonymous vs confidential, who can access raw data, and your minimum reporting threshold. Point employees to your privacy and confidentiality overview so expectations are consistent.
-
Run a tight invite cadence: Send the invite from a senior leader + HR, keep the survey open for 2 weeks, and send exactly 2 reminders. Add a final 24-hour reminder only if response is below target.
-
Pre-commit to sharing back: Tell people what you will share (themes, priorities, actions), what you will not share (raw comments with identifiers), and when (example: "within 2 weeks of close").
Subject: Core values check-in (5-8 minutes)
Message: We are running a short survey to understand (1) how clear our core values are, (2) where you see them show up in day-to-day work, and (3) whether you feel safe speaking up when values are compromised. The survey is [anonymous/confidential] and we will not report results for groups below [minimum N] to protect privacy. Please complete it by [date]. We will share a summary and 2-3 priorities by [share-back date].
AAPOR best practices emphasize clear communication, transparent use of results, and protecting respondents; turn that into a simple rule: tell employees exactly how you will use the data and when you will report back (AAPOR Best Practices for Survey Research).
Do this next: finalize your invite list and your reporting threshold, then schedule the two reminders on your calendar before launch day.
How to Analyze Core Values Survey Results and Turn Scores into Actions
Use this section to turn scores into actions — without over-slicing, exposing small teams, or getting stuck in "interesting" findings that do not change behavior.
- Default cleaning: suppress subgroups under your minimum N and scrub open text for names.
- Default scoring: build 4 indices (clarity, observed behaviors, leadership modeling, speak-up safety) plus per-value behavior scores.
- Default action output: 2-3 priorities per org, 1-2 per team, each with an owner and a 60-90 day checkpoint.
Focus first where (1) behavior frequency is low, (2) speak-up safety is low, and (3) accountability is low. That combo signals "values are not protected" and usually needs leader action, not more comms.
Quick interpretation: If agreement is high but behavior frequency is low, then your message is landing but systems and reinforcement are failing. If clarity is low, then write behavior examples before you push accountability.
-
Step 1: Clean, suppress, and protect identitiesApply your minimum group size rule before you build charts. Then review open-text responses and remove names, customer identifiers, or any detail that could point to a person or a small incident.
-
Step 2: Build indices you can trendAverage related items into 4 indices: Clarity (understand/apply), Observed behaviors (see values lived), Leadership modeling (leaders/managers), and Speak-up safety (safe to raise + constructive response). Keep the same items each run so you can trend movement.
-
Step 3: Score each value using behavior itemsFor each core value, use 2-4 behavior frequency items and compute a simple average. Do not score a value using only "agreement" statements — behavior is the point.
-
Step 4: Run hotspot cuts (few, intentional)Compare leaders vs individual contributors, new hires vs tenured employees, and your top-level org units (department/function/location). Look for the largest gaps and the lowest absolute scores, then pick the top 3 hotspots to investigate.
-
Step 5: Turn hotspots into 2-3 actions (not 20)Write each action as: Owner + behavior to change + system lever (coaching, recognition, performance criteria, decision principles) + date. If you cannot name the owner, the action is not real.
-
Step 6: Share results safely and clearlyUse a one-page outline: (1) what we heard (top 5 strengths, top 5 gaps), (2) what we will do (2-3 priorities), (3) what will not change now, (4) when we will check progress. Avoid quoting comments that reveal teams or people.
-
Step 7: Run a 60-90 minute action-planning workshopAgenda: 10 min results recap, 15 min pick 1-2 behaviors to improve, 20 min identify barriers, 10 min choose actions and owners, 5 min define measures, 5 min set dates. End with a written plan managers can repeat back.
-
Step 8: Equip managers with 3 promptsUse these prompts: (1) "Where do we see this value in action on our team?" (2) "Where do we feel pressure to compromise it?" (3) "What is one change we control in the next 30 days?" Capture commitments and follow up in 2 weeks.
-
Step 9: Pulse in 60-90 daysRe-run a short pulse (8-12 items) using the same index items for your top 1-2 priorities. Trend the indices and share progress so employees see follow-through.
Values alignment has been linked to engagement and related outcomes in applied settings; use that takeaway as a practical rule: treat your lowest "behavior + safety" hotspots as priorities, not as comms problems (study on organizational values, leadership, and staff outcomes).
Do this next: pick your minimum reporting threshold, then build a one-page results brief with 2-3 priorities and owners before you schedule leader readouts.
Frequently Asked Questions
How many core values survey questions should we ask?
Keep it to a 5-8 minute survey — often 18-30 items total. Start with one short module per theme (clarity, behaviors, leadership modeling, accountability, speak-up safety), then rotate optional modules (like hiring/performance) into later pulses.
Should a core values survey be anonymous or confidential?
Default to anonymous reporting because candor is usually the constraint for values topics. Use confidential reporting only if you already have a clear follow-up process and high trust, and still apply minimum reporting thresholds so small teams cannot be identified.
What response scale works best for core values (agreement vs frequency)?
Use both: agreement items measure clarity and usefulness, while frequency items measure what people actually observe day to day. Stick to a consistent 5-point scale across runs so you can trend changes without re-teaching the scale each time.
How do we customize generic values questions to our exact values without leading people?
Define 2-4 observable behaviors per value, then write neutral items that describe those behaviors (avoid words like "always" and "never"). Example: Value "Respect" — Behavior "listens and includes" — Item "In meetings, people listen to different viewpoints before decisions are made."
How do we analyze results to find where values are breaking down?
Run a small set of hotspot cuts: leaders vs individual contributors, new hires vs tenured employees, and department/location. Look for the lowest behavior frequency and the biggest gaps, then suppress any subgroup under your minimum N to protect privacy.
What should we do after we share the results?
Share findings plus 2-3 priorities and owners, then run team action planning with managers using the same priorities. Recheck progress with a short pulse in 60-90 days and close the loop by stating what changed and what will not change yet.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED