> ## 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 Introduce a New Process to a Wary Team
- URL: https://blog.jestor.com/introduce-new-process-to-wary-team/
- Published: 2026-09-17T22:37:06.000Z
- Updated: 2026-09-17T22:37:06.000Z
- Author: Bruno Bannach

To **introduce a new process to a team** that has seen previous attempts fail, the first version has to make someone's day easier immediately. Scepticism is usually earned, not irrational.

## Why teams resist

Resistance is rarely about change in the abstract.

- Previous systems that added work without removing any
- Tools imposed by people who do not do the work
- Data entry serving reporting rather than the person entering it
- No visible improvement for weeks

## What lowers resistance

- **Removing a step** they currently hate, in the first version
- **Involving the people who do the work** in shaping it
- **Keeping the familiar layout** available, such as a table view
- **Scoping what they see** to their own work
- **Showing them their own data**, not just management's

## How to do it in Jestor

1. Start in **Jestor** with the step people complain about most.
2. Build the intake so requests stop arriving as messages.
3. Keep a table view available for anyone coming from spreadsheets.
4. Scope permissions so each person sees their own work, not everything.
5. Apply permissions to indicators so individuals see their own figures too.

## Why choose Jestor for adoption?

**Jestor** lets the process owner shape what everyone else sees, which matters because the people best placed to reduce resistance are the ones who understand the work.

Because changes can be made in a draft version and published when ready, the team is not exposed to a half-finished redesign — which is what most previous attempts felt like.

## Frequently Asked Questions

### What should the first version do?

Remove a step the team already dislikes. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Should everyone see everything?

No — scope each person to their own work.

### Can I change things without disrupting them?

Yes, using a draft version.

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