21 leadership 360 questions, with the competencies behind them
A free set of 21 leadership 360 questions across 7 competencies, 8 statements for other staff and 2 open questions, rated from 1 Rarely to 5 Almost always.
· 9 min read · Convergo360 team
A good leadership 360 survey asks raters how often they see specific behaviours, grouped under a small number of leadership competencies. The set below has 21 statements across 7 competencies, 8 shorter statements for staff who work with the leader without reporting to them, and 2 open questions. Raters score each statement from 1 Rarely to 5 Almost always, or choose Not observed.
You can copy the questions as they stand. Later sections explain the scale and how to adapt the set.
What competencies does a leadership 360 cover?
The leadership survey covers 7 competencies with 3 statements each. Self, Manager, Peers and Direct Reports all answer the same 21 statements, which lets you compare how the leader sees themselves with how everyone else sees them.
| Competency | What it covers |
|---|---|
| Vision & Direction | Setting goals and explaining where the team is going |
| Communication | Speaking clearly, listening and keeping people up to date |
| Developing People | Feedback, coaching and career support |
| Recognition & Engagement | Noticing good work and making it safe to speak up |
| Decision-Making & Accountability | Deciding on time, owning outcomes and holding people to account |
| Collaboration | Working across departments and handling disagreement |
| Results & Execution | Delivering, solving problems quickly and improving how work gets done |
The 21 leadership 360 questions
In the survey each statement starts with the leader's name, so a rater reads "Jordan sets clear goals and priorities for the team". The third column explains what a low or high score tends to point to in a debrief.
Vision & Direction
| # | Statement | What it tells you |
|---|---|---|
| 1 | Sets clear goals and priorities for the team | Whether people know what matters most this month |
| 2 | Explains the reasons behind decisions | Whether the team understands why, as well as what |
| 3 | Connects the team's work to wider business goals | Whether people can see how their work fits the company plan |
Communication
| # | Statement | What it tells you |
|---|---|---|
| 4 | Communicates clearly and concisely | Whether messages land the first time |
| 5 | Listens actively before responding | Whether people feel heard in conversations |
| 6 | Keeps people informed of changes and progress | Whether the team hears news from the leader or from the grapevine |
Developing People
| # | Statement | What it tells you |
|---|---|---|
| 7 | Gives regular, constructive feedback | How often people hear how they are doing |
| 8 | Coaches team members to build their skills | Whether the leader teaches or simply takes over |
| 9 | Supports team members' career growth | Whether people see a future for themselves |
Recognition & Engagement
| # | Statement | What it tells you |
|---|---|---|
| 10 | Recognises good work promptly and specifically | Whether praise is timely and tied to the work |
| 11 | Makes people feel valued | How the leader's team experiences day to day contact |
| 12 | Creates an environment where people can speak openly | Whether people raise problems early or keep quiet |
Decision-Making & Accountability
| # | Statement | What it tells you |
|---|---|---|
| 13 | Makes timely decisions | Whether work stalls waiting for the leader |
| 14 | Takes ownership of decisions and their outcomes | Whether the leader stands behind calls that go wrong |
| 15 | Holds the team accountable fairly and consistently | Whether standards apply equally to everyone |
Collaboration
| # | Statement | What it tells you |
|---|---|---|
| 16 | Works effectively with other departments | How other teams experience working with this leader |
| 17 | Handles disagreement constructively | Whether conflict gets resolved or avoided |
| 18 | Shares information and resources willingly | Whether the leader builds bridges or silos |
Results & Execution
| # | Statement | What it tells you |
|---|---|---|
| 19 | Delivers on commitments and deadlines | Whether others can rely on the leader's promises |
| 20 | Shows urgency in resolving issues | How fast problems get dealt with |
| 21 | Looks for better ways of doing things | Whether the leader improves processes or keeps the status quo |
What should other staff be asked in a 360?
Other Staff are people who deal with the leader regularly without reporting to them, such as an administrator in another department or a team leader two levels down. They see a narrower slice of the leader's work, so they answer a separate, shorter survey of 8 statements on the same 1 to 5 scale.
| # | Other Staff statement |
|---|---|
| 1 | Treats staff with respect |
| 2 | Treats people fairly and consistently |
| 3 | Is approachable when I have a concern |
| 4 | Responds to requests within a reasonable time |
| 5 | Follows through on issues raised |
| 6 | Keeps sensitive matters confidential |
| 7 | Communicates clearly |
| 8 | Works cooperatively with my team |
Their results appear in their own section of the report and stay out of the main leadership averages. That way a leader's scores on coaching or strategy come only from people who see that work. For help deciding who belongs in this group, read our guide on choosing 360 raters.
What open questions should a 360 include?
Every rater group, including Other Staff, answers the same 2 open questions:
- What I appreciate most about this person
- How this person could be even more effective
The first question gives the leader something to keep doing and makes the second easier to hear. The second asks for improvement without inviting a list of faults. Comments often explain a score better than the number does, so leave enough space for a few sentences. Raters should know before they write that comments are read for anything that identifies them. Our article on 360 feedback anonymity covers how that review works.
What rating scale should a 360 survey use?
Use a five point frequency scale that runs from 1 Rarely to 5 Almost always, with a separate Not observed option. A frequency scale asks "how often do you see this", which is easier to answer than "how good is this person", and it gives every rater the same reference point.
Reports built on this scale usually colour code scores so leaders can scan them quickly. The Convergo360 report uses three bands:
| Average score | What it suggests |
|---|---|
| 4.0 and above | A consistent strength |
| 3.0 to 3.9 | Present but uneven |
| Below 3.0 | A clear development area |
Averages are calculated at full precision and shown to one decimal place. You can see how this looks on a full report in our sample report.
Why do 360 statements describe observable behaviour?
Raters can only judge what they have seen or heard. "Listens actively before responding" is something a direct report notices in every one to one. "Is a good listener" asks the rater to guess at a trait, and two people will mean different things by it.
Behaviour statements also make the debrief easier. When a leader scores 2.8 on "Keeps people informed of changes and progress", the coach and leader can name specific moments and agree on one change, such as a short Monday update. A low score on a vague trait gives them nothing to work with. Our guide to the 360 feedback debrief shows how to turn a low statement score into a development goal.
Why does Not observed matter?
People rate leaders from different positions. A peer in finance rarely sees how a sales manager coaches their team. If that peer must pick a number, they guess, and guesses tend to land in the middle of the scale. Enough of those pull every average towards 3 and hide both strengths and gaps.
Not observed answers are left out of the averages. If fewer than 3 people in a group rated a statement, the report shows a dash for that cell, so one or two scores never stand in for a whole group. Tell raters in the survey introduction that Not observed is a normal answer. Many people feel they are being unhelpful when they choose it.
How do you write good 360 statements?
Each statement should describe one thing a rater can see the leader do, in plain words that every rater group understands. These rules cover most problems:
- Describe a behaviour. Write what the leader does, such as "Explains the reasons behind decisions", instead of what they are.
- Keep to one behaviour per statement. "Communicates clearly and listens well" forces a rater who sees one and misses the other to average the two in their head.
- Avoid double barrelled items. Watch for "and" joining two separate actions. Words like "fairly and consistently" describe one action from two angles and work as a pair, so judge each case.
- Write it so the leader's name fits at the start. "Jordan sets clear goals" reads naturally, which keeps the survey quick.
- Skip jargon and internal acronyms. Other Staff and new direct reports need to understand every word.
- Keep the wording positive. Raters move faster when a higher score always means more of the behaviour.
Some common fixes:
| Weak statement | Problem | Better version |
|---|---|---|
| Is a strong leader | A judgement with no behaviour | Sets clear goals and priorities for the team |
| Communicates well and develops staff | Two behaviours in one item | Communicates clearly and concisely |
| Never ignores concerns | Negative wording confuses the scale | Is approachable when I have a concern |
| Drives synergy across BUs | Jargon | Works effectively with other departments |
How do you adapt the question set for your organisation?
Start with the 21 statements and change as little as you need. Every edit makes it harder to compare results with earlier cycles or with other leaders.
- Check the competencies against your leadership framework. If your company values name "Customer Focus", swap one statement in Results & Execution rather than adding an eighth competency.
- Keep 3 statements per competency. Competency averages are the mean of their statement averages, so an uneven count gives some competencies more weight.
- Translate with care. If raters will answer in isiZulu, Afrikaans or another language, have a fluent speaker check that each statement still describes the same behaviour.
- Test the set on 3 or 4 people before launch. Ask them which statements they had to read twice.
- Freeze the wording for at least two cycles so leaders can track progress against the same items.
If you are planning your first cycle, our South African 360 feedback guide explains the full process from rater lists to debriefs.
Next step
Copy the tables above into a shared document and mark any statement that clashes with your leadership framework, then fix those first. To see how the questions run inside a full cycle, read how Convergo360 works.
Common questions
How many questions should a leadership 360 survey have?
The Convergo360 set uses 21 rated statements, 3 for each of 7 competencies, plus 2 open questions. Three statements per competency give you a usable competency average without making raters work through dozens of items.
What rating scale works best for 360 feedback?
A five point frequency scale from 1 Rarely to 5 Almost always suits behaviour statements, because raters judge how often they see something happen. Add a Not observed option so people can skip what they have not seen.
Why should a 360 survey include Not observed?
Without it, raters guess or pick the middle of the scale, and those guesses pull averages towards 3. Not observed answers are left out of the averages, so the scores come only from people who saw the behaviour.
What should other staff be asked in a 360 review?
Staff who work with a leader but do not report to them see less of the leader's day. Give them a shorter survey about respect, fairness, approachability, responsiveness, confidentiality and cooperation.
Can I change the 360 questions for my organisation?
Yes. Keep the structure of 3 observable statements per competency, swap wording that clashes with your values or language, and avoid changing the set between cycles if you want to compare scores over time.