It's the second week of review season and your inbox is a graveyard of "just a reminder" emails. Meanwhile Microsoft Teams has been open on every manager's screen since 8:40 this morning. Only one of them gets answered, and it isn't the inbox.
If you run reviews for a company of 50 to 300 people and nobody owns HR ops, the cheapest fix is also the least glamorous: run the cycle where your people already are. This post lays out a four-week plan for doing that in Microsoft Teams, week by week, with the decisions you need to make before week one.
Why Teams Is a Good Place to Run a Review Cycle
Review cycles fail on participation long before they fail on question design. A form behind a separate login gets opened by the people who were going to answer anyway. A prompt that shows up in Teams, next to the conversation a manager is already in, gets a two-minute answer.
Teams isn't a performance tool, but it is where the attention is, and a review process that borrows attention beats one that has to earn it. If you're still weighing chat against a standalone app, Slack feedback or a separate HR app: where to draw the line works through the trade-offs, and the logic carries over to Teams.
What Teams can't do on its own is keep a structured record, run calibration, or turn a year of scattered comments into a review draft. That part needs software behind the chat. WorkStory is built that way: prompts and responses happen in Teams, and the structure lives behind it. See the Microsoft Teams integration for what that looks like.
Before Week One: Four Decisions to Make
Don't open the cycle until these are settled. Each one takes ten minutes and saves a week of confusion.
Who runs it. One named person, not a committee and not the CEO. They own the dates, the reminders and the questions people ask. At your size this is usually a People lead, an ops manager or an office manager with a few hours a week.
Who reviews whom. Write down the manager for every person and any peers you want to ask. Fix reporting-line mess now, not in the middle of the cycle when someone changed teams last month.
What you'll ask. Keep it short. Three or four questions beat fifteen. A person answering in Teams between meetings will not write an essay, and shouldn't have to.
When it ends. Pick the delivery date first and work backward. A cycle without a date drifts.
Week 1: Start Collecting Before Anyone Writes a Review
Don't treat week one as the start of review writing. It's when you start collecting input, so the people writing reviews in week three have something to work from.
Turn on feedback prompts
Connect your review tool to Teams and let prompts go out to peers and managers where they already read messages. A prompt is one question, a short scale if you want one, and a comment box. Keep the ask small enough to answer from a phone.
Tell managers what's coming
One short message, in the same Teams channel managers already use. Say what's changing, what you need from them this week, and the date it ends. Skip the training deck. If the request lands inside Teams, you won't need one.
Week 2: Ask for Peer and Manager Input
Now widen the circle. Ask peers and, where it makes sense, direct reports for feedback on the people being reviewed. Anonymous input tends to be more candid, and a 360 view gives managers a fuller picture than their own memory does. WorkStory supports 360-degree feedback in the same flow, so peers answer in Teams like everyone else.
This is also where reminders matter. A nudge that appears in the same Teams thread as the original request gets acted on. A separate reminder email gets read later, which means never.
Watch response rates, not just completion. If one team is at 40% by Wednesday, the fix is a one-line message from that team's manager, not another system-wide blast.
Week 3: Draft From Evidence, Not From Memory
This is where most cycles turn generic. A manager sits down with a blank field and six months of fuzzy impressions, and writes "strong communicator, could be more proactive."
Give them the evidence instead. With feedback collected all through the cycle, AI can group it into themes and produce a first draft the manager edits. The manager still owns every word and every rating. The draft just means they start from real comments instead of an empty box. For where AI drafting should stop, read AI drafts performance reviews, a human still makes the call.
Ask managers to do two things with each draft: cut anything that doesn't match what they saw, and add the context only they have. That's ten or fifteen minutes per person, not an evening.
Week 4: Calibrate, Then Deliver
Before anything reaches an employee, look across managers. One person's "exceeds expectations" is another's "meets," and at 100-plus people that gap becomes a pay conversation fast. A short calibration step, even one meeting with a shared view of ratings, catches it before delivery.
Then deliver. Give managers a few days to hold the conversation rather than just sending a document. The review is the start of a discussion, and the feedback collected along the way is what makes that discussion specific.
Mistakes That Sink Teams-Based Cycles
Treating Teams as the system of record. Messages scroll away. Make sure responses are stored somewhere you can search and report on a year from now.
Asking too much per prompt. If it doesn't fit on a phone screen, it's too long. Split it across the cycle instead.
Skipping the manager briefing. People will answer a prompt they understand. A thirty-second explanation of why it's coming and how long it takes does the work of a training session.
Letting the draft go out unedited. Employees can tell. The manager's pass is what makes it theirs.
Waiting for review season to collect anything. If all your input arrives in November, you've rebuilt the memory problem in a new tool.
Run It With Your Own Team
If you're choosing software for this, how to choose review software for 100 people with no HR and seven rules to write down before you demo give you the questions to ask. For the buyer's view of Teams specifically, see employee review software that works in Microsoft Teams, or browse performance review software if you're comparing options.
Want to see a cycle run in your own Teams workspace? Book a demo.
FAQ
Can you run performance reviews in Microsoft Teams?
Yes, with software behind it. Teams handles the conversation and the prompts. A review tool such as WorkStory adds the structure: cycles, a stored record, calibration and AI-drafted summaries. People respond inside Teams instead of logging into another system.
Do employees need another login to give feedback?
Not with a Teams-native setup. Requests arrive in Teams and people answer there, which is the main reason participation tends to hold up better than with a separate portal.
How long should a review cycle take for a company of 100 people?
The four-week plan above is a reasonable starting point, not a benchmark. The key is to collect input from week one so writing doesn't start from a blank page. Adjust the length to how often your managers can realistically respond.
Does AI write the performance review?
AI can draft a starting point from feedback that was already collected. The manager edits the draft and owns the final review and rating.
