August 26, 2025
7 min read
This post is part of our Understand Feedback pillar. Explore more:
The design choices behind our seven-competency model and how it turns feedback into action
TL;DR: Most 360s are long on insights and short on action. Ours focuses on observable behavior, simple language, and a predictable pattern that makes next steps obvious.
See the current survey preview (PDF).
Leaders tell us the same thing. Traditional 360s generate long reports, yet it is hard to know what to try next. Our goal was different. Build a survey that points to one or two practices a leader can start this week, and make the debrief faster, calmer, and more useful.
Behavior over labels. Most 360s drift into vague traits. We chose observable, coachable behaviors so leaders know exactly what to practice next week, not just who they “are.”
Development first. We placed an improvement prompt inside every section so raters suggest one concrete shift, right where they’re thinking about that skill. Less abstraction, more action.
Plain language. Items are grounded in widely used leadership models (e.g., Transformational Leadership, Emotional Intelligence, and Big Five‑linked behaviors) but written with everyday words. Leaders shouldn’t need a glossary to grow.
Our model sits on well-known leadership research. We use these findings to shape behavior-based competencies and items. We do not display personality labels in reports.
We kept the model tight enough to finish in one sitting, but broad enough to cover the real work of leading. You’ll see these sections reflected in the survey itself:
Why these seven? Together they balance how leaders show up (EQ, integrity) with how work moves (clarity, alignment, adaptability) and how teams grow (coaching, collaboration). Anything missing typically fits as a behavior inside one of these domains rather than needing its own section.
Each section uses three question types that unlock different signals. Research affirms that structured items (like Likert scales and scenario-based ratings) deliver fast, comparable feedback, while open-ended prompts reveal the underlying “why,” offering rich context for coaching and action.
What we ask: “Rarely / Occasionally / Sometimes / Often / Consistently.”
Why we chose it: We use frequency anchors rather than agree–disagree or quality labels, because they track habits, reduce defensiveness, and make change clearer (Sometimes → Often). You’ll see this scale throughout the survey. Leaders can connect the dots: How often do I do the thing? That maps directly to practice.
What we ask: Short, real‑world forks in the road—e.g.,
Why we chose it: These items reveal approach tendencies (how someone typically handles friction or change) that straight ratings miss. They’re quick for raters and highly diagnostic for coaching.
What we ask: Tight prompts like “What’s one thing this person could do to communicate more effectively?” or “Describe a time they handled a major change—what did they do?”
Why we chose it: Specific examples create the “aha” moments that move a leader from insight to action. Placing the question right after the ratings reduces recall bias and surfaces richer, on‑topic stories.
Every competency follows the same rhythm for a predictable, low‑friction rater experience:
The consistency helps raters stay focused; the variety keeps them engaged.
Feedback only works if the instrument is tight. These guardrails prevent the usual traps and keep the focus on observable behavior.
We cut elements that add noise or stall action so leaders can decide what to practice tomorrow
By surfacing behaviors, not labels, the 360 helps employees move quickly from insight to coaching to measurable change
A well-built survey still needs a simple playbook. Use these moves to turn insight into practice within 30 to 60 days.
A good 360 isn’t about the cleverness of its model; it’s about whether a busy leader can read it, recognize themselves, and know what to try on Monday. That’s the bar we designed for.
Want to peek? Here’s the 360 Survey Preview we’ve been iterating on.
If you’d like this adapted for a specific program or role family, we can tailor examples and scenarios while preserving the core structure above.