Close the loop: show users what you shipped

Silence teaches users to stop asking

Someone takes the time to suggest an idea. Weeks pass, nothing happens that they can see, and the idea may even ship without anyone telling them. The next time they miss something, they do not write. They leave a three-star review instead, or they leave.

Closing the loop means showing people what happened to their idea. It costs you a click per request, and it turns a one-way inbox into a conversation.

Five statuses are enough

Status	What it tells the user
Open	We have it. Vote for it if you want it too.
Planned	We decided to build it.
In Progress	We are building it now.
Shipped	It is in the app. Update and try it.
Declined	We will not build it. This is still an answer.

Resist adding more. “Under review”, “Needs more votes” and “Maybe later” all mean Open to the user, and they make the list harder to read.

Declined is a kindness

Many developers never decline anything, because it feels rude. But an idea that stays Open for two years tells the user “maybe”, again and again. A clear “Declined”, with a short reason in the description if you like, lets people stop hoping and move on. It also stops new votes landing on something you will never build.

Habits that keep the loop closed

• Triage weekly. Fifteen minutes: read new requests, fix unclear titles, set a status on the top few.
• Mark Shipped on release day. Do it when the update goes live, not when you merge the code. Users check the app, not your repository.
• Pin what you want feedback on. A pinned request stays at the top, so you can ask a specific question for a week.
• Add your own ideas at zero votes. Your board should measure your users, not you.

Show the status where the user is

A status only helps if people see it. A changelog on a website reaches the few who look for it. A status next to the idea, inside the app, reaches everyone who opens the board again.

How InsightsKit does it

In the InsightsKit dashboard, each status is a column, ranked by votes with pinned requests first. Drag a card to another column and the status changes. Your users see it the next time they open the feature screen. Requests you add yourself start at zero votes. If an app should not show statuses at all, you can turn them off for that app in Setup & keys.