How to Establish a Baseline Before Improving

To establish a baseline before improving, you measure the process as it currently runs, for long enough that normal variation is visible. Without it, any result can be explained away.

Why improvements go unproven

The measurement usually starts after the change.

No comparable figure from before
Improvement claimed and disputed
Seasonal variation mistaken for effect
The next change proposed without evidence from the last

What a usable baseline includes

A period long enough to cover normal variation
Segmentation, since an average across types hides the effect
Volume alongside timing, so a quiet period is not mistaken for improvement
One change at a time, so the effect is attributable
The same indicators, used before and after

How to capture it in Jestor

Enable log metrics on the phase field in Jestor before making any change.
Let the process run, so the timing data accumulates on its own.
Segment by request category or by responsible person.
Record volume alongside timing so a quiet period is not misread.
Change one thing, then compare the same indicators over a comparable period.

Why choose Jestor for measurable improvement?

Jestor records stage timing automatically as cards move, which means a baseline usually already exists even when nobody planned to capture one.

Because the same indicators serve before and after, comparison is a date filter rather than a separate analysis — which is what makes quarterly review sustainable.

Frequently Asked Questions

What if I did not capture a baseline?

Timing is recorded automatically, so it may already exist. See jestor.com.

How long should a baseline run?

Long enough to cover normal variation.

Why change one thing at a time?

So the effect is attributable.

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,