Action plans
From survey comment to action plan in one 1:1 cycle
Key points
- Read comments for themes, never for authors, and pick one theme you can change.
- Tell the team what you heard and the one thing you will try within two weeks.
- Write a small plan: one behavior, two to four steps, a date and a baseline score.
- Test the change in your 1:1s, then let the next pulse judge whether it worked.
A survey comment only matters if something changes for the people who wrote it. This is a four-week cycle that takes one theme from the comment box to a small plan, a short conversation with your team, and a second look at the numbers. It fits inside the 1:1s you already hold.
The cycle in four weeks
- Week 1: read the comments for themes and choose one theme you can change.
- Weeks 1 to 2: tell the team what you heard and the one thing you will try.
- Weeks 2 to 4: use your 1:1s to test the change and adjust it.
- Next pulse: compare the score and the comments with where you started.
One theme at a time is the rule that makes the rest work. Three half-finished changes teach a team that surveys produce promises. One finished change teaches them that two honest minutes are worth it. With a monthly two-minute manager pulse the cycle fits the rhythm. With a quarterly one, stretch weeks 2 to 4 across the quarter.
Week 1: read for themes, not authors
Read all the comments once without a pen. Then read them again and sort them into two or three piles: schedule changes, feeling unheard in decisions, unclear priorities, too little recognition, or whatever your team keeps coming back to.
Do not try to work out who wrote what. You will sometimes be wrong, and acting on a guess turns an anonymous channel into a guessing game. People notice, and the next round of comments gets careful and empty. That is also why results stay hidden until enough people respond, as the anonymity threshold explains.
Then pick one theme with three tests.
- Can you change it yourself? A habit of yours or of your unit beats a budget line.
- Did more than one person raise it? A theme in several comments is a pattern. A single sharp comment is worth reading, but rarely the place to start.
- Would the team notice within a month? Choose something people can see or feel soon, so the cycle earns trust quickly.
Weeks 1 to 2: say it back to the team
Within a week or two, tell the team what you heard. Cover four things: what you heard, the one thing you will try, what you are not doing yet, and when you will check back.
Thank you to everyone who filled in the pulse. Here is what I heard: several of you find out about schedule changes too late to plan around them. I am going to try one thing. When I decide on a change, I will post it within 24 hours, and if I can't, I will tell you why. I heard other things too, and I am not ignoring them. I am starting here so that I finish. I will ask about it in our 1:1s, and we will see what the next pulse says.
Keep it under two minutes, and do not defend yourself. On a nursing unit, say it at a huddle and post it where the other shifts will see it, so the night team hears it the same week as the day team.
If your tool lets you reply to a comment publicly, use it. In Retrain and Retain, a manager can reply so the whole team sees the answer. Without that, a huddle and a note on the board do the same job.
Write a plan small enough to finish
A plan is not a mission statement. It has one behavior, two to four steps, a date, and a baseline, which is the starting score on the dimension the theme belongs to. When the next pulse arrives, the baseline is what you compare against. The gap between a weak response and a useful one is usually size.
| Comment theme | Weak response | Better small plan |
|---|---|---|
| "I find out about schedule changes too late." | Remind everyone to check the schedule more often. | Post every change within 24 hours of deciding it. Review the last two weeks of changes in your 1:1s. |
| "Decisions get made without asking us." | Announce a quarterly town hall. | For the next two decisions that touch the unit, ask for input for two days, then report what you changed, what you kept, and why. |
| "I only hear from my manager when something goes wrong." | Say thank you more often. | Each week, name one specific thing one person did and what difference it made. Rotate until everyone is covered. |
| "We are always short and nobody listens." | Promise to fix staffing. | Log the shifts that ran short and the effect on care. Bring it to your director with one clear ask, then report back whatever the answer. |
Notice what the last row does. You cannot fix staffing alone, so the plan is about what you do control: evidence, an ask, and a report back.
Weeks 2 to 4: use your 1:1s to test it
Your 1:1s are where people can tell you, privately, whether anything changed. Put the plan on the agenda as a standing item for the next three meetings. Two minutes is enough. Ask for evidence, not approval.
Two weeks ago I said I would post schedule changes within a day. Did you see that happen? Where did I miss?
Since I started this, what is different for you, even a little?
Is there anything about how I am doing this that I should stop or change?
Write down what you hear, and adjust in week 3. If a step is not working, change the step, not the goal. If people did not notice, say it again somewhere else.
Then let the next pulse judge
When the next pulse closes, compare it with your baseline and read the comments on the same theme.
- Up, and the comments changed. Tell the team, thank them, and decide whether to continue or pick a new theme.
- Flat. Check whether people noticed. If they did, the step was wrong, so change it.
- Down. On a small team one answer moves an average a lot, so read what people wrote and look at two pulses first.
Comments you cannot act on, and comments that worry you
When you cannot act on it
Some comments ask for things outside your control: pay, a new policy, the floor layout. Do not skip them, and do not promise them. Say what you heard, why it is out of your hands, and what you will do instead, even if that is only passing it up.
I can't change the pay scale. What I can do is raise it with our director this week and tell you what I hear back by Friday.
A clear no with a reason earns more trust than silence.
When a comment worries you
Some comments are not feedback. They describe a safety risk, harassment, discrimination, a threat of harm, or a patient safety concern. Do not investigate, do not try to identify the writer, and do not question the team. Take the comment, word for word, to HR or the formal channel your organization uses for that kind of report, the same day. If you do not know the route, ask HR today. This is a practical rule of thumb, not legal advice.
Before your next 1:1
- Block 30 minutes and sort the comments into two or three piles.
- Choose one theme, using the three tests.
- Write two or three sentences for your next huddle, and say them.
- Write the plan: one behavior, two to four steps, a date, a baseline.
- Add one question to each of your next three 1:1 agendas.
To see what comments and tips look like before you have your own, the live demo with sample data shows a manager dashboard end to end. The best first theme is often the smallest one. Finish it, and the next gets easier.
Written by the Retrain and Retain team. This guide is general information, not legal, clinical or HR advice for your specific situation.