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

# What to Do About the Person Still Doing It the Old Way
- URL: https://blog.jestor.com/person-still-doing-it-the-old-way/
- Published: 2026-09-17T22:37:12.000Z
- Updated: 2026-09-17T22:37:12.000Z
- Author: Bruno Bannach

Handling **someone bypassing the new process** starts with a question most rollouts skip: what does the old way still do better? The answer is often specific and fixable.

## Why the assumption of resistance is usually wrong

Bypassing takes effort. People do it for a reason.

- The new process is slower for their particular case
- A step they need is missing, so they work around it
- Their exception has no route, so it goes outside
- They lost a capability, such as bulk editing

## How to find out

| Check                 | What it reveals                          |
| --------------------- | ---------------------------------------- |
| **Stage dwell times** | Which step is slow enough to avoid       |
| **Blank fields**      | Requirements nobody can satisfy honestly |
| **Exception volume**  | Whether the standard path fits reality   |
| **Asking them**       | Usually the fastest route to the answer  |

## How to respond in Jestor

1. Review the **SLA** data in **Jestor** for the step being avoided.
2. Check the table view for fields consistently left blank.
3. Add an exception route if their case genuinely needs different handling.
4. Restore a lost capability — a table view for bulk editing, for instance.
5. Change the process in a draft version and publish once it fits.

## Why choose Jestor for responsive processes?

**Jestor** gives the process owner the ability to change the process directly, which means a legitimate complaint can be addressed in the week it is raised rather than in the next project cycle.

Because app versioning makes changes safe to test, adjusting a live process in response to feedback is a normal activity rather than a risk.

## Frequently Asked Questions

### Is bypassing always resistance?

Usually not — it often signals a real gap. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### How do I find the problem step?

Through the SLA dwell times.

### Can I fix it quickly?

Yes, in a draft version, then publish.

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