> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Handle Feedback During a Rollout
- URL: https://blog.jestor.com/handle-feedback-during-a-rollout/
- Published: 2026-09-17T22:37:18.000Z
- Updated: 2026-09-17T22:37:18.000Z
- Author: Bruno Bannach

To **handle feedback during a rollout**, separate three kinds: things that are broken, things that are harder than before, and things people would prefer differently. Each deserves a different response.

## Why feedback becomes noise

Everything arrives through the same channel with the same urgency.

- Preferences presented as blockers
- Real blockers lost among cosmetic requests
- Every change made immediately, destabilizing the rollout
- Nothing changed, so people stop reporting

## How to triage

| Type                     | Response                                  |
| ------------------------ | ----------------------------------------- |
| **Broken**               | Fix now — it prevents work                |
| **Harder than before**   | Investigate — a capability may be missing |
| **Preference**           | Collect, batch, and decide later          |
| **Process disagreement** | A separate conversation from the tool     |

## How to manage it in Jestor

1. Collect feedback in **Jestor** as records in a small pipeline, with a type field.
2. Fix blockers immediately in a draft version and publish.
3. Investigate "harder than before" reports against the **SLA** data.
4. Batch preferences and decide on them together rather than individually.
5. Tell people what was done, so reporting continues.

## Why choose Jestor for iterative rollout?

**Jestor** makes changes cheap to apply and safe to test, which means the response to a genuine blocker can be same-day rather than next-sprint.

Because app versioning separates making a change from releasing it, batched preferences can be applied together on a predictable schedule instead of destabilizing the rollout daily.

## Frequently Asked Questions

### Should every request be actioned?

No — fix blockers, batch preferences. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### How do I check a "this is harder" report?

Against the SLA data for that step.

### Why tell people what was done?

Otherwise reporting stops.

## 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](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.