The survey has closed, the results are in and leadership has seen the presentation. In most organizations, this is exactly where things slow down. Reports are shared, a few meetings are held, then the agenda moves on and the topic is forgotten until the next survey. From employees' point of view, the picture is very clear: "They asked for our opinion, and then nothing happened."
- The value of a survey is decided in the 90 days after the results are released. If employees see no concrete change in that period, both participation and honesty drop in the next survey.
- The 90 days fall into three phases: reading and sharing the results and choosing priorities in the first 30 days, launching actions in days 31–60, and measuring progress and reporting back to employees in days 61–90.
- Actions should be planned at three levels: company-wide, department and team. Team-level actions are often the changes employees notice first.
- A good action has an owner, a date, an outcome employees will notice and an indicator that shows whether it is working.
The value of an employee survey is decided not by the survey itself but by the 90 days that follow it. If employees see concrete change in this period, they take part in the next survey more willingly and more honestly. If they don't, the survey becomes a tool that erodes trust instead of building it.
In this article we explain how to plan the 90 days after the results are released: the three levels of action, the team action planning session, what makes a good action, a sample action plan table, a follow-up rhythm and how to measure progress.
If your results came in lower than expected, you can find a more detailed roadmap for the first month in our article what to do when employee survey results are bad. This article covers that first month too, but focuses mainly on what comes after it.
Why 90 days?
Ninety days meets two needs at once:
- It is short enough for employees' patience. After the results are released, employees expect a signal within a few weeks. An organization that stays silent for six months will struggle to change the perception that "nothing happened after the survey", whatever it does later.
- It is long enough for real change. Managers need time to talk with their teams, launch actions and see the first effects. For most actions, 30 days is only the beginning.
Ninety days is also a checkpoint. At the end of this period, a short measurement shows whether the actions are on track and lets you correct course if needed. The rest of the annual cycle builds on these first 90 days.
The three phases of the 90 days
| Phase | Focus | Key outputs | |
|---|---|---|---|
| Days 1–30 | Understand and share | Results analysis, 2–3 company-wide priority areas, company-wide communication, manager reports, a first visible step | |
| Days 31–60 | Plan and launch | Team action planning sessions, department and team action plans, actions launched | |
| Days 61–90 | Follow up and measure | Progress reviews, "You said, we did" communication, a short pulse measurement, course correction |
Days 1–30: Understand and share
The goal of the first month is to read the results correctly and show employees they have been heard.
- Analyze the results. Read the overall picture, the breakdowns and the open-ended comments together. Key driver analysis is the strongest tool for seeing which areas affect engagement most. We cover the steps of the analysis in our guide how to analyze employee survey results.
- Choose company-wide priorities. Agree on no more than 2–3 priority areas with senior leadership. Assign a sponsor from senior leadership to each area.
- Share the results. First announce the company-wide results and the chosen priorities, then give managers their own team reports. We cover what to share, when and how in our article sharing employee survey results with employees.
- Take a first visible step. Even if the plan isn't finished, one easy change should go live within the first month: for example, removing a process obstacle that comes up often in the comments, or restarting a communication channel.
Days 31–60: Plan and launch
The focus of the second month is the team level. Company-wide priorities matter, but employees notice change most in their own team and in their own manager's behavior.
- Each manager holds an action planning session with their team (details below).
- Teams choose 1–2 actions and write them up in a shared action plan format.
- Department heads review their teams' plans and take on issues that are common across the department.
- Sponsors of company-wide actions set up working groups and launch the first steps.
By the end of this phase, around day 60, every team should have at least one written action that is already under way.
Days 61–90: Follow up and measure
The goal of the final month is to keep the actions alive and make the first progress visible.
- Hold progress reviews. Make the action plan a regular agenda item in leadership meetings, department meetings and team meetings.
- Tell people what has been done. Share short "You said, we did" updates that pair an issue raised in the survey with the step taken in response. If employees don't connect the change to the survey, the actions lose much of their trust-building effect.
- Run a short measurement. Around day 90, run a 5–10 question pulse survey made up of the items from your priority areas.
- Correct course. Revisit actions that aren't making progress together with the teams.
The three levels of action
A common mistake in action planning is expecting HR or senior leadership to fix everything. In practice, many of the issues in survey results need to be handled at different levels.
| Level | Owner | Typical topics | Example action | |
|---|---|---|---|---|
| Company-wide | Senior leadership sponsor | Strategy and direction, pay and benefits policy, career framework, company-wide communication | Writing down and publishing career levels and promotion criteria | |
| Department | Department head | Cross-functional collaboration, processes, workload distribution, department-specific tools | Simplifying the cross-departmental approval process | |
| Team | Team manager | Recognition, feedback, team communication, meeting habits, development conversations | Starting monthly one-to-one meetings |
When deciding which level an issue belongs to, ask a simple question: "Who has the authority to change this?" A team manager cannot change the pay policy, but can change how recognition and feedback work in their team. Assigning an action to a level without the authority to deliver it disappoints both the manager and the team.
The strength of team-level actions is that they are the closest and most visible. An employee may notice that a company-wide policy has changed a year later, but will see right away that their manager has started sharing updates in the weekly team meeting. We explain why manager items matter so much in the anatomy of first-line manager questions.
The team action planning session
The most effective route to team-level action is a session in which the manager discusses the results with the team and chooses actions together with them. For a 60–90 minute session, this flow works well:
- Set the frame (10 minutes). Explain that the purpose is not to find out who answered what, but to talk about what the team can do better. State clearly that anonymity will be protected.
- Share the results (10–15 minutes). Show the team's strengths and its 2–3 lowest areas. Share the findings worth discussing, not the whole report.
- Discuss what they mean (20–30 minutes). Ask open questions such as "What do you think this result is telling us? What do you find most difficult in this area?" Focus on listening, not on defending or explaining the results.
- Choose actions (15–20 minutes). Agree together on 1–2 actions within the team's own control. Note the issues outside the team's control and say you will take them to the next level.
- Set owners and dates (5–10 minutes). For each action, agree on an owner, a start date and a review date.
Some managers, especially those with low results, are wary of this session. HR can make it much easier for both the manager and the team by giving these managers one-to-one support beforehand and, where needed, co-facilitating the first session with an HR business partner.
What makes a good action
"Improving communication" is not an action; it is an intention. A good action has four qualities:
- Concrete: It is clear what will be done. Instead of "improving communication", "sharing a short summary of board decisions in the department meeting on the first Monday of every month".
- Owned: A named person is responsible, not a committee or "HR".
- Visible: Employees can notice the change in their daily work. Process work behind the scenes can be valuable, but unless it is explained to employees, it won't be connected to the survey.
- Measurable: How success will be judged is decided up front: a change in the related items, an operational indicator, or simply whether the action was carried out as planned.
The table below shows how weakly worded actions can be made stronger.
| Weak action | Strong action | |
|---|---|---|
| Develop a recognition culture | Use the first 5 minutes of the team meeting to name one standout contribution from that week | |
| Increase career opportunities | Hold a career conversation with every employee by day 60 and explain the internal job posting process in the department meeting | |
| Reduce workload | Review the team's recurring reports and drop at least two; declare Tuesday afternoons meeting-free | |
| Strengthen communication with leadership | Have the CEO hold a Q&A session at two locations every quarter |
Sample action plan table
An action plan doesn't need to be a long document. Using the same format across the organization makes follow-up easier. A simple action plan can have these columns:
| Priority area | Action | Owner | Start | Review date | Success indicator | |
|---|---|---|---|---|---|---|
| Recognition | Naming one contribution in the weekly team meeting | Team manager | Day 35 | Day 90 | Increase in "I receive recognition for good work" in the pulse survey | |
| Career development | Individual career conversation with every employee | Team manager | Day 40 | Day 75 | Share of employees who had the conversation; increase in the career item in the pulse survey | |
| Cross-functional collaboration | Cutting the purchasing approval process from three steps to two | Operations director | Day 45 | Day 90 | Average approval time; fewer related open-ended comments |
Collecting action plans in one place lets HR see which teams have built a plan, which need support and which issues come up in more than one team. When the same issue appears in many teams, it is usually a sign that it should really be handled at department or company level.
Follow-up rhythm: How to keep the action plan alive
Most action plans fail not because they were badly designed but because they were forgotten. To keep a plan alive, it has to become part of the existing meeting rhythm:
- Team level: Once a month, a 5–10 minute action plan review in the team meeting. "What did we do, did it work, what should we change?"
- Department level: Once a month, a look at team progress and escalated issues in the department leadership meeting.
- Company level: At days 30, 60 and 90, sponsors report on the priority areas in the senior leadership meeting.
- HR: Identifying teams that haven't built a plan or aren't making progress, and supporting their managers.
How to measure progress
The measurement around day 90 is the first chance to see whether the actions are working. When designing it:
- Focus on the priority areas. Don't repeat the whole annual survey. A 5–10 question pulse survey with the items from your priority areas, a few core engagement items and one open-ended question is enough. We cover which questions to choose in pulse survey questions.
- Ask the same items in the same words. To compare results, the items must be worded exactly as they were in the annual survey.
- Ask whether the actions were noticed. An item such as "Concrete changes have been made in my team since the last survey" shows directly whether employees noticed the actions. If this item scores low, the problem may lie in communication rather than in the actions themselves.
- Interpret change carefully. In small groups, a change of a few points may not be statistically meaningful. Keep sample size and margin of error in mind when interpreting the results.
- Look beyond the survey. If an action has an operational counterpart (turnover, absenteeism, training participation, process times), track that as well.
When the next annual survey comes around, these interim measurements also make it easier to interpret year-over-year change. We cover how to make that comparison in comparing engagement survey results year over year.
Common mistakes
- Too many actions: A plan with ten priority areas and several actions for each won't produce visible change in any of them.
- Leaving everything to HR: HR runs the process, but the actions belong to the business and its managers. An action plan driven only by HR stays "an HR project" in employees' eyes.
- Only company-wide actions: Without team-level actions, most employees won't see any change in their day-to-day work.
- Treating training as the only answer: It is easy to respond to every low score with a training program, but if the root cause is a process, workload or manager behavior, training alone won't fix it.
- Not telling people what was done: Even when actions go live, if employees don't connect them to the survey, the perception that "nothing happened after the survey" persists.
- Stopping at day 90: Day 90 is the first checkpoint, not the end of the process. Following up on actions throughout the year shapes both the participation and the results of the next survey.
In short, a survey is a conversation that starts with a question, and the action plan is the answer. When you plan the 90 days after the results with clear priorities, actions assigned to the right levels, regular follow-up and visible communication, employees see that their input actually changed something. That experience goes a long way toward deciding how many people take part in the next survey, and how honestly they answer.
Frequently asked questions
How soon after an employee survey should the action plan be ready?
Company-wide priorities should be clear within 2–4 weeks of the results being released, and team action plans should be complete by day 45 at the latest. Taking the first concrete step within 30 days shows employees that the survey is being taken seriously.
How many actions should an action plan have?
Two to three company-wide priority areas with 1–3 actions each, and 1–2 actions per team, is usually enough. More than that spreads resources thin and makes it harder for employees to notice any change.
Who owns the action plan, HR or managers?
HR designs the process, supports managers and tracks progress, but the actions belong to the business and its managers. Company-wide actions belong to a sponsor from senior leadership, and team actions belong to the team manager.
How do you measure whether the actions are working?
Run a short pulse survey made up of the items from your priority areas around day 90 and compare the results with the baseline from the annual survey. You can also track an operational indicator for each action, such as absenteeism, turnover or training participation.
What if there is no change after 90 days?
First check whether the actions were actually implemented and whether employees noticed them. If they were implemented and nothing has changed, go back to the team and revisit the root cause. In some areas, especially culture and trust, change can take longer than 90 days to show.
