360-Degree Feedback for Project Leaders

Core premise: 360-degree feedback has been called "perhaps the most notable management innovation of the 1990s". Nearly every large-enterprise company uses it. And yet — in the supplied research meta-analysis — over one-third of feedback interventions actually decreased performance. Feedback alone changes nothing. This article unpacks the mechanics, the hard evidence, and the conditions under which 360 feedback becomes a genuine development tool rather than an expensive ritual.

1. The "Why" — Why Self-Awareness Is a Business-Critical Asset

On a complex defence acquisition programme — say, the integration phase of a complex naval-platform combat system, or the certification of a complex capability programme turret — a senior project manager's blind spots do not stay hidden. They cascade. The supplied research put it bluntly: lack of self-awareness can jeopardise projects by contributing to sub-optimal individual performance, or by creating increased stress and anxiety in others.

The reason is structural. In the traditional industrial economy, a company's value was in its property. In a modern defence prime, the majority of the value is in its people — the cleared engineers, the PMO veterans, the systems architects with twenty years of programme history in their heads. The supplied research makes the economic case plainly: if a large portion of that talent becomes frustrated with their co-workers or bosses and quit, the economic results could be devastating — a substantial amount of value could end up employed by a competitor, or become the competition. In a market where major delivery organisations and a growing tier of mid-sized sovereign primes are all competing for the same security-cleared engineering talent pool, a project manager whose team is quietly stewing is a direct capability risk.

360-degree feedback exists to surface those blind spots before they do damage.

2. The "What" — Definitions and Assumptions

Practice note: Definition 360-degree feedback (also multi-source or multi-rater feedback) is a method of systematically collecting perceptions of an individual's performance from the entire circle of relevant viewpoints. Rating sources typically include peers, direct reports, supervisors, and occasionally external stakeholders such as customers or suppliers.

2.1 The Core Assumption

An important assumption underlies the approach: performance varies across contexts, and people behave differently with different constituencies. An executive who is diplomatic with the executive sponsor may be abrasive with direct reports. A technical lead who is collaborative with peers may be dismissive of customers. A single supervisor rating cannot capture this variance. Multi-source feedback can.

2.2 What the Research Actually Shows About Rater Agreement

A finding that surprises most newcomers: research consistently shows that ratings across sources correlate only moderately. Some newcomers interpret this as a flaw — "the raters don't agree, so the instrument must be unreliable." the supplied research flips the interpretation:

Practice note: The Disagreement Is the Point "Rather than being a problem, this finding suggests that performance may be different, and may be perceived differently, across various constituencies. Multi-source or 360-degree ratings are needed to capture this variety of behaviour and perspective."

Additionally, the supplied research found little evidence of within-source agreement — even among raters with similar observational opportunities. The psychometric implication is clear: use multiple raters within multiple rating sources. A single peer's opinion is noise; the aggregate of five peers is signal.

2.3 Where It Fits in the Development Framework

The supplied research's classic tripartite framework for development says effective experiences combine assessment, challenge, and support. 360-degree feedback is overwhelmingly an assessment tool. This is the central design problem with 360 feedback: it delivers assessment brilliantly but provides little challenge and no support. On its own, it tells a project manager what others think without giving them any help in deciding what to do about it.

3. The "How" — Running 360 Feedback That Actually Develops People

3.1 The Development Target: Human Capital

360 feedback's primary contribution is to intrapersonal competence — self-knowledge, self-awareness, and the capacity to see one's own impact on others. Source proposition 1a:

Practice note — source Proposition 1a: "The use of 360-degree or multi-source feedback is associated with the development of human capital (intrapersonal competence) in organisations."

There is an indirect link to social capital — if the feedback process enhances an individual's trustworthiness and trusting intentions toward others, it can support the relational trust that leads to cooperation. But this is a second-order effect, not the primary mechanism.

3.2 source finding — The Single Most Important Design Decision

If you remember one finding from this article, remember this one. The supplied research conducted a five-year study of upward feedback and found:

Practice note — supplied research: — The Decisive Finding Managers who met with their direct reports to discuss their upward feedback demonstrated significantly greater performance improvement than managers who did not discuss their feedback.

The act of private receipt is nearly useless. The act of structured conversation is transformative.

This is not a minor implementation detail. It is the difference between a programme that works and a programme that does not. For a prime contractor PMO running upward feedback across its project management community, the design question is not "how do we collect the ratings?" but "how do we structure the follow-up conversation, and how do we hold managers accountable for having it?"

3.3 The Four Preconditions for Change

The supplied research identifies the preconditions a participant must meet for feedback to change behaviour:

1. Willingness to accept feedback as relevant and useful
2. Openness to change
3. Realism and resilience — recognition that change is rarely a simple path forward
4. Time and energy — a large investment before change enters the behavioural repertoire

Absent any of these, feedback bounces off well-developed defence mechanisms. Some recipients recognise feedback as accurate but simply do not want to change.

3.4 Organisational Support Matters

The supplied research found that perceived organisation support enhances the usefulness of subordinate feedback over and above the overall favourability of the feedback. Interestingly, for peer ratings, only favourability predicted usefulness — a finding that says something uncomfortable about how we receive critique from people we consider equals.

The practical implication for a defence prime: 360 feedback programmes succeed when the organisation is visibly supportive. If the PMO is seen as cynical about the process, or if feedback recipients believe the ratings will be used punitively, the intervention will fail regardless of instrument quality.

3.5 The Measurement Problem

Measuring change from a 360 instrument is technically difficult. Two concepts from the supplied research:

Because beta and gamma changes contaminate simple pre-post comparisons, some researchers have adopted a retrospective methodology — asking at Time 2 how much the target has perceptibly changed — rather than relying on difference scores. The supplied research argues this methodology deserves greater research attention.

4. The Pitfalls — Where 360 Feedback Goes Wrong

1. The "report and forget" trap. Delivering a 360 report without a structured follow-up conversation is the single most common failure. The supplied research shows this doesn't work.
2. Overwhelming the recipient. 360 feedback delivers a lot of data. Without interpretation support, recipients either latch onto the most negative item and spiral, or latch onto the most positive and ignore the rest.
3. No guidance on how to change. The instrument tells you what is wrong, not how to fix it. This is where executive coaching (source proposition 1b) becomes essential as a follow-up intervention.
4. Insufficient rater anonymity. In a small team — say a 12-person defence IPT — even aggregated ratings can be de-anonymised by context. Recipients can identify who said what, which poisons future candour.
5. Using it for performance management and development simultaneously. The instrument cannot serve both masters. When ratings feed into compensation decisions, raters rate politically and recipients receive defensively. The supplied research and others are clear: separate the two uses or abandon the developmental intent.
6. Ignoring the feedback interventions meta-analysis. the supplied research found over one-third of feedback interventions decreased performance. A programme lead who has not read this paper and designed around its findings is rolling a loaded die.
7. Confusing acceptance with usefulness. A recipient who says "that's fair" is not the same as a recipient who has a concrete plan and the support to execute it.

5. Key Takeaways

Practice note: Seven Things to Remember

1. Multi-source disagreement is a feature, not a bug — it captures real behavioural variance across contexts.
2. Use multiple raters within multiple sources for psychometric reliability.
3. 360 feedback is strong on assessment, weak on challenge and support — it cannot stand alone.
4. the supplied research rule: managers who discuss their feedback with direct reports change; managers who merely receive it do not.
5. the supplied research: over one-third of feedback interventions actually reduce performance. Design accordingly.
6. Perceived organisational support amplifies feedback usefulness.
7. Always link 360 feedback to a follow-up intervention — typically coaching (source proposition 1b).

6. Knowledge Check

Practice note: Test Your Understanding

1. A defence prime's PMO reports that its 360-degree feedback programme generated "excellent engagement" — 92% completion rates, high recipient satisfaction, glowing exit surveys. Six months later, performance reviews show no measurable change. Using the source finding, identify the most likely design gap.
2. Explain why the supplied research argues that low correlation between rater sources (peer, supervisor, direct report) is evidence for the method rather than against it.
3. Distinguish alpha, beta, and gamma change. Why does their presence complicate simple pre/post measurement of development impact?
4. A project manager on a complex naval-platform programme IPT tells you: "I got my 360 report last week. The peer ratings were harsh — I think some of them had axes to grind." What does the supplied research's finding about favourability and peer ratings suggest about this reaction?
5. Source proposition 1b states that the effectiveness of 360 feedback for social capital development depends on linkage to follow-up coaching. Why can't 360 feedback produce social capital on its own?

Applying the Guidance as a Controlled Practice

Use this subject as a decision aid, not as a label applied after the event. Start by defining the delivery problem, the people affected, the authority available and the consequences of a poor decision. Record assumptions before selecting an intervention. That simple discipline makes later review possible and prevents a preferred leadership style from being treated as the answer to every situation.

Six-Step Application Cycle

1. Define the trigger. State the decision, behaviour, team condition or delivery risk that requires attention. Separate observation from interpretation.
2. Map the context. Identify the project phase, task uncertainty, dependencies, stakeholder interests, time pressure, team capability and formal authority.
3. Choose a proportionate response. Select the smallest intervention capable of improving the condition. Explain why it fits the evidence and what alternatives were rejected.
4. Agree ownership and boundaries. Make decision rights, escalation points, review dates and non-negotiable safety or ethical limits visible to the people involved.
5. Act and observe. Monitor both delivery indicators and human signals such as challenge, information sharing, participation, trust and follow-through.
6. Review and adapt. Compare the result with the original intent. Retain, adjust or stop the intervention, and capture the learning for the next phase.

Evidence and Verification

Evidence should be proportionate to the project's risk and governance needs. A short decision note may be sufficient for a routine team adjustment; a high-consequence change may require sponsor approval, formal consultation, controlled records and a scheduled assurance review. Documentation must support judgement rather than replace it.

Review Questions

• What observable condition are we trying to change, and how will we know if it improves?
• Whose perspective is missing from the diagnosis or decision?
• Are authority, accountability and capability aligned, or are we asking someone to own an outcome they cannot control?
• Could the intervention suppress challenge, conceal risk or create dependency on one individual?
• What evidence will trigger escalation, adaptation or closure?

Practice boundary: Frameworks in this article organise thinking; they do not guarantee performance. Project context, contractual obligations, safety duties, workplace requirements and approved governance remain controlling.