> ## 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 Communicate a Process Change
- URL: https://blog.jestor.com/communicate-a-process-change/
- Published: 2026-09-17T22:37:14.000Z
- Updated: 2026-09-17T22:37:14.000Z
- Author: Bruno Bannach

To **communicate a process change** effectively, lead with what the reader has to do differently. Most announcements lead with context nobody needs and bury the instruction.

## Why announcements get ignored

They are written from the perspective of the person making the change.

- Opening with background rather than with the action
- No indication of who is affected
- No date, so it feels optional
- Sent once, with no reference afterwards

## What an announcement should contain

- **What changes**, in one sentence
- **Who it affects**, named by role
- **When it takes effect**, with a specific date
- **What you have to do differently**, concretely
- **Where to find it again**, since nobody retains it first time

## How to support it in Jestor

1. Make the change in **Jestor** in a draft version, published on the announced date.
2. Update the home page so affected users land on the right place.
3. Write the reasoning into a document attached to the process.
4. Attach that document to an **AI** agent so people can ask afterwards.
5. Use table following to watch whether behaviour actually changes.

## Why choose Jestor for managed change?

**Jestor** lets the publish date match the announced date, because app versioning separates making a change from releasing it.

Because the reasoning lives in a document attached to the process, the announcement is not the only record of why something changed — which matters when someone asks six months later.

## Frequently Asked Questions

### What should an announcement lead with?

What the reader has to do differently. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can I make the change before announcing it?

Yes, in a draft version published on the announced date.

### Where should the reasoning live?

In a document attached to the process.

## 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.