Performance reviews that catch the drift early.

A quarterly check that catches the drift before it becomes the norm. Dips get flagged early and supported, and no one lands on a performance plan cold.

Why performance management breaks

Someone on the team has been slightly off their game since spring. Their manager noticed, meant to say something, and didn't. Then review season arrives, everyone gets a rating, and the first time that person hears there's a problem is in a meeting about a performance improvement plan (PIP).

Most underperformance goes that way. It is rarely about severity. It is about duration: someone a little below the bar, for too long, with nobody naming it.

A heavier process doesn't fix that. Rating everyone takes weeks, and most of the effort goes to people who are doing fine.

“Big and heavy formal performance reviews take time and effort - when you're growing quickly, this might not be something you have the luxury or energy to do. It's better to find an agile way to do smaller ones.”

Nobody should be surprised by a review

In the same guide, Kristen Sinch, VP of People at Wild Earth, gives the test of a review process: an employee is not surprised by the evaluation. Whether someone is underperforming, overperforming, or somewhere in the middle, they should already know where they stand.

That only happens if feedback arrives while the dip is still small. Feedback that is hard to give gets put off, and a formal review once or twice a year gives a manager months to put it off in.

No two companies run it the same way

“Never have I seen the same performance review process work at two companies.”

What worked at 400 people broke at 1,000. So we have no opinion about how you should run performance reviews. We think you should have one. The rest of this page is the part that holds under any process: catch dips early, give managers the words, keep the cycle on time, and show people what the next level looks like.

A quarterly check that catches the drift

Drift is a quarterly performance check. It doesn't rate everyone. It puts the energy into the few cases that drag a team down, while they are still easy to fix.

What a manager is asked

Once a quarter, each manager gets one request, in Slack or by email: flag anyone on your review list who had a performance dip. They pick the type of dip (craft, personal leadership, or behaviors and values) and add a short note on the support they're giving. If no one needs flagging, they confirm that, and they're done.

A dip is often temporary, so the ask is to flag early.

What happens when a name comes back

Support steps up each time the same person is flagged.

First time
Usually a temporary dip. The manager gives feedback in the next 1:1 and considers narrowing the person's scope for a while to rebuild confidence.
Second cycle in a row
The pattern persists, so it goes in writing. The manager coaches explicitly, names the pattern, and writes down the feedback and the agreed actions. The HR business partner gets an FYI.
Third cycle or more
A direct sit-down, expectations in writing, and a PIP to consider. The manager brings in their HR business partner before that conversation.

The list works in the other direction too. No manager should have to put someone on a PIP who was never flagged.

Who sees a flag

HR, the person's HR business partner, and the viewers named on Drift's config sheet. The person doesn't see it, and managers see only their own team. A named leader confirms the flags for their assigned teams. That sign-off is light-touch and doesn't block anything.

What Drift doesn't do

Drift is not a ratings system. It doesn't score everyone, rank anyone, or decide pay. And today it opens as a playground with sample data: you can click through each role's view, then request access to the secure single sign-on version from inside it. Open Drift.

Managers get the words when they need them

A flag only helps if a conversation follows. That conversation belongs to the manager, and most managers have never been shown how to have it.

Pyn sends managers the nudge, the context, and the words at the moment they need them (the manager effectiveness page covers the other moments). The words are already written:

“Thanks for making time. I want to be direct about why we're here.”

Softening the start doesn't make the news kinder. And nothing in a PIP should be new to the employee. If it is, the process failed months earlier.

Make it part of the manager's job

“If you want managers to have development conversations and put time and effort into performance reviews, doing so should be bundled into their own performance reviews and be considered an expectation of all managers.”

The review cycle, on a calendar

Formal reviews run on company dates, not on anyone's start date. So HR rebuilds the same sequence of emails every cycle, and loses track of which deadline moved.

In Pyn the cycle sits on one calendar with the rest of the year's company communications. Start from the performance-cycle templates (introduce the review cycle, evaluations, review discussions) and edit the words. Put a button on the ask that links to your review form, and you can see who has started. Next cycle, duplicate it with new dates.

The library has what people need that week: four tips to write your performance self-evaluation, prepare for your performance review meeting coming up next week, and three tips for giving actionable 360 feedback.

How often, and how long

That's your call. Every People leader we interviewed for the library guide reviewed performance more than once a year, and their formal cycles took two to three weeks from start to finish. Remote ran two formal reviews a year, with smaller pulse reviews in the quarters between.

On the stack you have

No rip-and-replace. Pyn reads your HRIS and acts where people already work. See every integration.

Show people what good looks like at the next level

People can't grow toward a level nobody has described. At most companies the career framework is a forgotten spreadsheet, or it sits in an expensive platform locked inside a bigger HR suite.

Grow is a free, visual career framework. It shows what “good” looks like at every level of a role, with real behavioral examples. Level up a competency and you see how to move up the ladder, from Senior through to Lead, Principal, and Head of. People can grow by excelling in different competency areas, not only in the technical skills of the role.

It comes with 11 sample role frameworks, including engineering, sales, design, product, and HR. To build your own, download a role as a CSV, edit it in a spreadsheet, and upload it. No code needed. Grow runs in your browser and nothing leaves your device. It needs a laptop screen, not a phone. Open Grow.

Then have the conversation

A framework doesn't develop anyone. A manager does, in conversations that are easy to postpone. Pyn sends the reminder and the guide.

Three months in
A “love and loathe” conversation: which parts of the role give this person energy, and which drain it. Your report hit their 3 months mark has the invite and the pre-work.
Ten months in
A full career conversation that ends in a short-term and a longer-term action plan: How to have a career development conversation with your employee.
Afterwards
Write it down. The Career Action Plan template covers role adjustments, upskilling, and networking.

Internal mobility: the next role is often inside

Internal mobility is wider than promotions.

“Internal mobility includes lateral moves, promotions, transfers, and development opportunities.”

Someone has to push it. In that article Jeff Diana, a former Chief People Officer, says it has to be whoever does the HR business partner work, wherever that work sits. Keep the program small enough to run: a simple, manageable plan beats an ambitious one nobody can support.

Three moments carry most of it:

Pyn doesn't match people to roles, and it isn't a talent marketplace. It makes sure the moments around a move are handled.

Measure duration, not ratings

A ratings distribution tells you how managers score. It doesn't tell you whether anyone got help. Drift keeps a history of every cycle, and four things in it are worth watching.

Response
Did every manager answer? Drift's reminders go only to the people who haven't responded.
Recurrence
How many names are on the list for the first time, the second cycle running, or the third. The second and third are where the work is.
Outcomes
What happened next for each person: improved and off the list, still on it, on a PIP, or exited.
Cold PIPs
Any PIP for someone who was never flagged. The aim is none.

Start with one quarter

Keep the review process you have. Add the check that catches what it misses.

  1. Open Drift and Grow.Both run in a browser with sample data, and both are free to try. Use them as they are, or copy the idea and build your own.
  2. Agree the rules.Who flags, who confirms, who can see a flag, and what happens the second time a name appears.
  3. Run one cycle.Ask every manager to flag a dip or confirm they have none. Keep the note short.
  4. Put the next review cycle on the calendar.The ask, the deadline, and the nudges before it.
  5. Add the career conversations.Three months in, then ten months in, for every report.

Book a demo. Bring your review calendar and the career framework you have, even if it's a spreadsheet. We'll show you Drift, Grow, and a review cycle on the calendar.

FAQ

Is Drift a performance review tool?
Not in the usual sense. Drift is a quarterly check that flags performance dips early. It doesn't rate everyone, and it doesn't replace a review cycle if you run one.
Does an employee see that they have been flagged?
No. A flag is visible to HR, the HR business partner, and the viewers named on the config sheet, and managers see only their own team. The feedback itself comes from the manager, in the next 1:1.
Do we have to replace our performance review software?
No. Pyn works alongside existing systems. The review cycle messages can link to the review form you already use.
How often should we review performance?
That depends on your company. Every People leader we interviewed for our library guide reviewed performance more than once a year, and their formal cycles took two to three weeks. Drift runs quarterly.
When should a manager start a performance improvement plan?
Our manager's guide suggests it once performance has been a challenge for two months or more. A PIP should be a genuine last opportunity, so only start one if you believe it could succeed. Nothing in it should be new to the employee.
Can we change the career framework to fit our own roles?
Yes. Grow comes with 11 sample role frameworks. To adapt one or add a role, download it as a CSV, edit it in a spreadsheet, and upload it. No code needed.
Are Drift and Grow free to try?
Yes. Grow runs in your browser, and nothing leaves your device. Drift opens as a playground with sample data, and you can request access to the secure single sign-on version from inside it.

Your HR stack, with superpowers.

Pick the tools you need. Launch in a day. Cancel anytime.