> ## 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 run an internal ideas pipeline
- URL: https://blog.jestor.com/run-an-internal-ideas-pipeline/
- Published: 2026-09-16T18:56:35.000Z
- Updated: 2026-09-16T18:56:35.000Z
- Author: Bruno Bannach

An **internal ideas pipeline** survives only if every idea receives a decision. In **Jestor**, ideas are records with owners, stages and outcomes, so contributors learn what happened rather than watching their suggestion disappear.

## Why suggestion schemes stop receiving suggestions

Ideas are collected enthusiastically. A few are implemented, most receive no response, and within months submissions stop.

The failure is not that ideas were rejected. It is that contributors were never told, which reads as indifference.

What a functioning pipeline requires:

- Every idea acknowledged
- A visible stage, so nobody wonders
- A decision within a stated period
- Reasons given, including for rejections
- Implemented ideas credited publicly

## Stages of an idea

| Stage        | What happens                   | Deadline        |
| ------------ | ------------------------------ | --------------- |
| Submitted    | Captured with its author       | Immediate       |
| Acknowledged | Author told it was received    | Automatic       |
| Under review | Assessed by the relevant area  | A stated period |
| Decided      | Accepted, deferred or declined | With a reason   |
| Implemented  | Delivered and credited         | Tracked as work |

## Step by step to run it

1. **Make submission trivially easy**, ideally under a minute.
2. **Acknowledge automatically**, so nobody wonders.
3. **Route to the area** that would own the implementation.
4. **Set a review deadline**, and honour it.
5. **Give a reason on every decision**, especially declines.
6. **Track accepted ideas** as work with owners.
7. **Credit the contributor** when something is implemented.

## Why declining well matters more than accepting

Most ideas will not be implemented, so the experience of the majority is defined by how declines are handled. A short, honest reason maintains willingness to contribute. Silence ends it, and the people who stop contributing first are the ones paying most attention.

## Why choose Jestor

In **Jestor**, ideas arrive through a simple form, acknowledgement is an automation, routing sends each to the area that would own it, **SLA** measures review time, accepted ideas become tracked work, and the contributor stays connected to the record through to implementation.

## Frequently Asked Questions

### Why do suggestion schemes stop receiving ideas?

Because contributors are never told what happened. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Should declined ideas get a reason?

Yes. Most ideas are declined, so that experience defines the programme.

### What keeps the pipeline credible?

Honouring the stated review deadline and crediting implemented ideas.

## Video Tutorial: Step by Step

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