360 feedback templates by context: which to run when

Most 360 feedback uses one form for everything. The same thirty questions go out whether you just wrapped a hard project, stepped into a bigger role, or want a read before a specific 1:1 — and then everyone wonders why the answers come back so generic. It's the wrong tool for most of the moments it's used in, the way one wrench is the wrong size for most bolts. A 360 is only as good as the specific thing it asks about, and specificity comes from context: what just happened, what you're trying to learn, and who was actually in a position to see it. Match the template to the moment and the answers get sharp. Use one generic form for all of them and you get the same vague reassurance every time.

Why one generic 360 underperforms

The problem with the all-purpose form is that its questions can't anchor to anything. "Rate this person's project management, 1–5" forces the respondent to average every project they've ever seen you run into a single number — which is exactly the kind of blended, contextless question that produces useless answers. Compare it to "On the launch that just shipped, what's one thing you'd change about how it was run?" That question has a moment attached, the moment is fresh, and the answer will contain a specific, usable detail. Same topic; completely different information, because one is anchored to a context and the other floats free of any.

Context does three things a generic form can't. It makes the question concrete (a real, recent event to react to). It narrows who you ask to the people who actually saw that event. And it sets the right cadence — a post-project round happens when the project ends, not on a calendar. Strip the context out and you lose all three at once.

The moments that each deserve their own template

Different moments surface completely different things, which is why a good 360 practice is really a small set of context-specific templates, not one master form. The ones worth having:

• After a project ships. A retrospective read while it's fresh: what worked in how you ran it, what you'd change. Pairs with project-based feedback and asking for feedback after a project ends.
• A quarterly check-in. The recurring baseline on your core behaviors, run on a cadence so you can see change over time. This is the quarterly structure in practice.
• After a promotion or role change. New scope means new behaviors to calibrate — the things that made you effective before aren't the things the bigger role turns on.
• Before a 1:1. A focused read to prep a specific conversation, so the meeting starts from data rather than a blank page — the structured cousin of asking well in the 1:1 itself.
• Upward, from your team. Your reports on how you manage, specifically — a different question set than peers, because they see a different slice of you. Which slice is which is the whole point of 360 vs peer vs upward.
• A new role's first 90 days. An early baseline while habits are still forming, calibrated to the transition rather than to steady-state performance.

Notice that each of these implies a different question set, a different group of respondents, and a different trigger. That's the whole argument for templates by context: the moment does the calibration for you.

The generic form vs the context-matched template

How to pick the right template

1. 1

   Start from the trigger, not the calendar

   Ask what just happened or what you're trying to learn — a project closed, a promotion landed, a 1:1 is coming up. The moment is what tells you which template you need; don't default to "it's review season."
2. 2

   Match the respondents to what they can see

   Only ask people who were actually in a position to observe the thing. The right raters for a post-project round aren't the right raters for an upward-management read. Context narrows the list for you.
3. 3

   Keep the questions behavioral and few

   Whatever the context, ask about specific observable behaviors in that moment, and keep it short. A handful of sharp, anchored questions beats a long generic form every time.
4. 4

   Run it on the cadence the context implies

   A post-project template fires when projects end; a quarterly one fires quarterly. Let the moment set the rhythm, and keep the core questions stable across repeats so you can still track change.

Korn Ferry's research on 360 design lands here too: what separates a 360 that changes behavior from one that doesn't is far more about fit — the right questions for the right situation — than about the length or polish of the instrument. And Harvard Business Review's long critique of the one-size-fits-all annual review is really the same point at the process level: a single generic ritual can't do the job that context-specific feedback does.

What this looks like in practice

A team lead finishes a bumpy product launch and wants to know how she handled it. The generic-form instinct is to wait for the annual 360 and hope the launch comes up — but by then it's five months cold and buried under everything else, so it doesn't, and she learns nothing about the one thing she actually wanted to understand. The context-matched version: the week after launch, she sends four questions specifically about that launch to the five people who worked on it — how clear were priorities under pressure, where did decisions stall, what would you change about how it was run. The answers come back concrete. Two people independently name the same mid-launch pivot that never got communicated cleanly — something a generic "rate her communication, 1–5" would have averaged into oblivion. She changes one thing for the next launch and re-runs the same four questions when it ships. That's the whole difference between a form that documents and a template that teaches, and the only variable that changed was matching the round to the moment.

Where Mirorly fits

This is the idea Mirorly's template library is built around. Instead of one master form, the templates are organized by the moment they're for — after a project, a quarterly check-in, a new role, upward from your team, prepping a 1:1 — each a short, research-backed, behavioral question set calibrated to that context. You pick the one that matches what just happened, answer it about yourself, and send the same questions to the people who saw it. The post-project retrospective and the quarterly check-in are good places to start; you can read every question in each before you ever sign up. The point is never "fill out the big form" — it's "run the right small one for the moment in front of you."

Common questions

The one-line summary

A 360 is only as good as the specific thing it asks about, and specificity comes from context — so one generic form run for every moment produces the same vague answers, while a small set of templates matched to the moment (after a project, quarterly, after a promotion, before a 1:1, upward, a new role) surfaces concrete, usable feedback, because the context makes each question concrete, narrows who you ask, and sets the right cadence.