A 360 review template for startups (copy and customise)

A usable 360 review template for a startup needs three pieces: a short questionnaire, a kickoff message your team will actually read, and a debrief meeting structure that turns the responses into a conversation. All three are below, copy-paste ready, no download required, calibrated for a 5-30 person team. If you came here because you want something to use today rather than a 2,000-word article on theory, scroll: the templates are first.

Brief disclosure before the templates: I sell software in this category, and the templates below work perfectly well without it. If you read this and run your first round with a Google Form and a shared document, that’s the right outcome.

Key Takeaways

• A workable startup 360 review template is three short artifacts: a questionnaire (5-7 open questions plus 4 competency ratings), a kickoff email (100-130 words, founder voice), and a 30-minute debrief structure.
• Keep the questionnaire under 15 minutes per reviewer. The single biggest predictor of low-quality responses at startup scale is question fatigue, not bad questions.
• Start with four competencies, not ten. Ownership, collaboration, communication under ambiguity, and growth velocity cover what actually matters at 5-30 people.
• Customise four things: the competency names (match your values), one role-specific open question, the anonymity disclosure, and whether the round includes upward feedback on the founder. Don’t customise question count, timing, or compensation linkage.
• If you’re tempted to add a fifth competency or a ninth question, delete one instead. The template that fits a startup is the one your team will actually finish.

Template 1: The questionnaire (the core of any 360 review template for startups)

Designed to be filled in under 15 minutes per reviewee. Four startup-calibrated competencies plus 5-7 open questions, paste it into a Google Form or a shared doc and you’re ready.

Competencies (1-5 scale)

• Ownership and bias to action. Takes initiative without being asked. Closes loops. Notices when something’s broken before it’s a fire.
• Collaboration in a small fast-moving team. Makes the people around them better. Hands off cleanly. Asks for help early enough.
• Communication under ambiguity. Writes and speaks clearly when priorities aren’t fixed yet. Surfaces confusion early. Doesn’t perform certainty they don’t have.
• Growth and learning velocity. Visibly better at something this quarter than last. Asks for feedback. Changes their behaviour when they hear it.

Rate each from 1 (significant gap) to 5 (clear strength). Optional sixth competency for anyone who has interviewed: Hiring judgment. Optional seventh for anyone who manages: Working dynamics with the team they lead.

Open questions (pick 5-7)

1. Where has this person shipped something without being asked, in a way that actually mattered?
2. When the team has been confused about priorities, what’s their move? Does it help?
3. What’s one habit they bring to working sessions that you’d want copied across the team?
4. Where do they hand off well? Where do they drop something assuming it picked itself up?
5. What would they need to be doing differently in six months for the company to feel their growth?
6. When you’ve disagreed with them on something that mattered, how did the conversation go?
7. If you could change one thing about how they show up at this company, what would it be?
8. Anything else worth saying that the questions above didn’t ask?

That’s the whole questionnaire. Four ratings, five to seven open questions, fifteen minutes per reviewer per reviewee. Don’t add a ninth open question because the form feels thin. Form fatigue is the failure mode, not form depth.

What to delete from a generic template

Most templates on the first page of Google ship with patterns that don’t fit a startup yet. Delete these:

• 10+ competencies. A small team can’t meaningfully evaluate someone across ten dimensions; the responses get vague past four. Cut.
• Behaviourally anchored rating scales (“3 = consistently demonstrates the following six behaviours…”). These exist because large-company calibration committees need them. You don’t have one. Use a plain 1-5.
• Strategic planning, long-range vision, executive presence. None of these mean much at 12 people. Replace with bias-to-action and ambiguity tolerance.
• A “development priorities” multi-select grid. Delete it. The debrief conversation is where development priorities get set, not the form.

For the question design principles behind why these specific cuts work, the pillar on 360 feedback questions covers the construction rule (observable behaviour, specific situation, never personality traits) in full.

Template 2: The kickoff email

Send this five business days before the deadline. Founder voice, not corporate. About 120 words.

Subject: 360 feedback for [Name], your input matters

Hi everyone,

We’re running a short 360 feedback round for [Name]. The goal is straightforward: help them see what’s landing, what’s growing, and where their work could matter more. This is developmental. It is not tied to compensation, promotion, or any performance decision.

Four competency ratings plus 5-7 short questions. About fifteen minutes total. Your responses are anonymous to [Name]. I will see who has submitted (so I can chase laggards), but I will not see who said what.

Deadline: [date, ideally 5 business days out].

Reply if anything’s unclear. Genuinely specific feedback, the kind only you can give, is the part that makes this worth doing.

[Your name]

The last line does quiet work: it signals that vague positivity isn’t what’s wanted. Most templates skip that line because it feels uncomfortable to write. Leave it in.

Template 3: The 30-minute debrief

Once responses are in and you’ve synthesised them into two or three strength themes and one or two development themes, this is the structure for the conversation.

• Minutes 0-3. Frame the meeting. “Here’s what we ran, here’s how I read it, the goal of the next half hour is to help you see what’s landing.” Set the rule that comp is not on the table.
• Minutes 3-13. Strengths first. Walk through two or three themes with representative quotes (still anonymous). Pause after each. Ask them to say something back, not just nod. The strengths landing properly is what makes the development section receivable.
• Minutes 13-23. Development areas. One or two themes. Specific behaviour, not character. Specific situations from the responses, not abstractions. Pause again. Ask what’s recognisable and what isn’t.
• Minutes 23-28. One commitment. “What’s one thing from this you want to work on by [a date 90 days from now]?” One. Not five.
• Minutes 28-30. Close. Confirm the one thing, confirm what support they’d need, schedule a 15-minute check-in 30 days out.

The deeper version of this conversation, including the five hard moments that show up in the room and what to say when they do, is in how to deliver 360 feedback results without breaking trust.

How to customise a 360 review template for your startup

The templates above are a starting point. Four customisations are worth making before your first round.

Rename the competencies to match your values. If your team uses different language for what we called “Ownership and bias to action” (some teams say “drives outcomes” or just “ownership”), use your language. The labels need to feel native; the underlying behaviours don’t change.

Swap one open question for something role-specific. If you’re running a round on an engineer, replace question 3 with something craft-specific (“In code review or technical design, what habit do they bring that you wish more of the team copied?”). If it’s a salesperson, a designer, a People Ops lead, calibrate the same way. The 360 feedback questions by role spoke has ready-made question sets cut by reviewee seniority if you want a starting point.

Decide the anonymity disclosure deliberately. The template above says “anonymous to [Name], I will see who submitted.” That’s the right default at startup scale, where pretending to fully anonymise responses is a polite fiction anyone could see through. If you have a specific reason to attribute (a founder running an upward round on themselves, say), say so directly in the kickoff.

Decide whether the founder is included in the round. The single most useful move available to a startup running its first 360 is the founder being a reviewee. It signals that the process applies to everyone. If you decide not to (which is fine, especially in round one), name that decision instead of being silent about it.

Two things not to touch in round one. Don’t extend the deadline beyond seven business days; longer windows reduce completion rates, not improve them. Don’t bundle the round with compensation or promotion decisions, ever. The moment a 360 informs someone’s raise, honest feedback goes away.

When the templates don’t fit

Some teams aren’t in the right place to run a structured round at all. If the team is in the middle of a layoff aftermath, if the team is too new for raters to have meaningful working overlap, or if the leader being reviewed has a track record of punishing honest feedback, the template won’t fix any of that. When not to run a 360 review covers five specific situations where running a round will do more damage than good, and what to do instead in each one.

Imagine a 15-person seed-stage startup that closed its first funding round nine months ago, has a stable team, and has never run structured feedback before. The founder wants to start. This is the textbook fit. Pick five raters per reviewee, paste the questionnaire into a Google Form, send the kickoff email above, give it seven business days, synthesise the responses on a Friday afternoon, run a 30-minute debrief the following week. Total time investment: under three hours per reviewee. That’s the version where the template earns its keep.

The reframe

A template is a starting point, not a process. The starting point is the conversation you’re about to have, and the form is the support structure that makes the conversation specific. If the template ever feels like the point of the round, you’ve inverted the value: paperwork over development. The 360 worth running is the one where the reviewee walks out with one specific thing they want to change in the next quarter, owned by them, recognisable from the responses. Everything above exists to make that more likely.

When you’re ready to run a round without spreadsheets, start your first 360 in Lynxify, no annual contract, no credit card required. Or paste the templates above into a Google Form and run the next round manually. The version you actually run beats the version you keep planning.

FAQ: 360 review template for startups

What should a startup 360 review template include?

Three pieces: a short questionnaire (four competency ratings plus 5-7 open questions, designed to be completed in under fifteen minutes per reviewer), a kickoff email written in founder voice and sent five business days before the deadline, and a 30-minute debrief meeting structure that turns the responses into a development conversation. Anything more than that becomes paperwork; anything less leaves the responses untranslated into action.

How many questions should a 360 review have for a startup?

Four to seven open questions plus four competency ratings is the right shape. Beyond eight or nine questions, completion rates start to collapse and the responses get visibly rushed. The number that holds up at startup scale is five open questions plus the four ratings: about fifteen minutes per reviewer per reviewee, which scales realistically when one rater has to fill it in for four colleagues.

Should startups use a generic 360 template or build their own?

Use a generic template and customise four things: rename the competencies to match your values, swap one open question for something role-specific, decide the anonymity disclosure deliberately, and decide whether the founder is included in the round. Building from scratch in round one is overhead you don’t need. The first round’s value is the conversation, not the form.

Is a Google Form enough to run a 360 review at a startup?

Yes, for the first one or two rounds and for teams under about fifteen reviewees. A form collects the responses, a shared document holds your synthesis notes, and a calendar invite books the debrief. The point at which a form starts hurting is when you’re synthesising responses for six or more people every quarter; that’s days of work per round by hand, and a focused tool starts paying for itself. Before that point, save the cost and run it manually.