What to Do About the Person Still Doing It the Old Way

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

Review the SLA data in Jestor for the step being avoided.
Check the table view for fields consistently left blank.
Add an exception route if their case genuinely needs different handling.
Restore a lost capability — a table view for bulk editing, for instance.
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.

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 and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,