How to Choose Who Should Be in Your Pilot Group

To choose who should be in your pilot, pick people whose experience will generalize. A pilot run entirely by enthusiasts tells you how enthusiasts behave.

Selection mistakes that mislead

Each produces a result that does not survive contact with the wider team.

Only volunteers, who were going to adopt anything
Only the technically confident, who route around problems
Only one team, whose exceptions are not representative
The builder as the main user, who knows every assumption

Who to include

Profile	What they reveal
A high-volume user	Whether it holds up under real load
A sceptic	The objections you will face at scale
Someone less technical	Where the interface actually confuses
Someone with the awkward cases	Whether exceptions have a route

How to run it in Jestor

Build the process in Jestor and pin a published version for the pilot group.
Scope permissions so the group works with real data in their own records.
Include the awkward cases deliberately rather than deferring them.
Watch SLA data and blank fields for signs the process does not fit.
Adjust in a draft version and publish, without disrupting the group mid-task.

Why choose Jestor for piloting?

Jestor lets a pilot run on the real process with app versioning, rather than in a parallel environment that behaves differently from production.

Because changes can be prepared in a draft and published deliberately, feedback can be acted on quickly without the group experiencing constant instability.

Frequently Asked Questions

Should a pilot use volunteers only?

No — include a sceptic and a less technical user. See jestor.com.

Should awkward cases be included?

Yes, deliberately.

Can I change things mid-pilot?

Yes, in a draft version, published when ready.

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,