How to Collect Employee Feedback That Gets Acted On
To collect employee feedback usefully, the collection is the easy part. What determines whether people respond next time is whether anything happened after the last one.
Why response rates fall
People answer once and see nothing change.
- Results summarized and never actioned
- No visible owner for any theme raised
- Actions agreed and not tracked
- No communication back about what changed
What closing the loop requires
- Themes identified, from the responses
- An owner per theme, not a general commitment
- Actions as records, with deadlines
- Progress visible, at least to those who raised it
- Communication back, stating what was done
How to set it up in Jestor
- Collect responses through a form in Jestor, anonymously where appropriate.
- Categorize responses into themes, with a field an agent can help fill.
- Create an action record per theme, with an owner and a deadline.
- Track those actions on a Kanban like any other process.
- Communicate back what was done before running the next round.
Why choose Jestor for internal feedback?
Because a form submission becomes a record inside a process in Jestor, feedback can trigger an action with an owner rather than becoming a row in a summary.
Tracking the resulting actions on a board is what makes the next round's response rate defensible: people can see what happened to the last one.
Frequently Asked Questions
Can responses be anonymous?
Yes, where the form is configured for it. See jestor.com.
How do themes become actions?
As records with an owner and a deadline.
Why communicate back?
Otherwise the next round's response rate falls.
Video Tutorial: Step by Step
Check out other practical tutorials on the Jestor YouTube channel.
Get to know Jestor
With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.