Role-based training, go-live floor support and adoption measurement for new business software
Adoption work starts after launch. Each role is trained at its own screen on its own tasks, such as billing returns, goods receipts or closing job cards. Support stands on the floor at go-live. Afterwards the records are reviewed to find which steps staff skip, which fields stay blank and why the stores or field team still reach for a notebook. Share your requirements and we will plan it with you.
- Training runs in the staff’s own language.
- Support stands on the floor at go-live.
- Failed steps lead to configuration changes.
This work covers counter staff, storekeepers, service advisors, field technicians, accountants and branch managers, on systems GullySystem built and on systems bought from other vendors. Some engagements are short: a run of role sessions before go-live, then a week standing on the floor beside the staff who bill, receive and close job cards. Others run much longer. They add champions in each branch, reference cards in the language of the floor and a monthly review of the fields the team still skips, with findings fed back into configuration.
Where Software Adoption Falls Short
One Session for Every Role
One projector, every module, one hall. The storekeeper sits through invoicing while the accountant sits through goods receipt, and hardly anyone touches a keyboard long enough to remember where the buttons were.
Spreadsheets Kept Beside the New System
Staff enter data as told. They also keep a personal sheet, which leaves two records that are both incomplete, so any report drawn from either one disagrees with the work done at the counter.
Knowledge Held by One Coordinator
One person answers every question. That coordinator also corrects other people’s entries, so a resignation or a long leave removes the only working knowledge of the system.
Mandatory Fields Filled With Placeholders
A new mandatory field blocks saving. Staff type a full stop to get past it, and the report built on that field later shows a column of placeholders where customer names or reasons should be.
Training Held Before the System Was Ready
Sessions ran early, on a demo. Staff arrive on the first day having learnt screens that were later renamed, moved or removed during configuration, and they trust the old layout.
New Joiners Learning by Observation
Nobody teaches the newcomer. Habits pass from desk to desk, workarounds included, so a step someone invented in the first month becomes the accepted method and the newcomer copies it.
Reviews Run From a Spreadsheet
The review runs from a sheet. Staff are told the system matters, yet the weekly meeting is driven from a spreadsheet someone prepared by hand, and the team reads that as the signal.
Low adoption is rarely refusal. Staff are usually protecting the day’s work from a system that adds steps, so adoption follows only when the software saves them time. Training must fit the person’s own role and language, and managers must open the live records in every weekly review instead of asking for a sheet.
Training Built Around the Job Rather Than the Menu
Watch first, teach second. Each role is observed at work before any session is planned, then trained at its own screen on its own tasks, using its own customers and items. Support staff stand beside them at go-live. Afterwards, skipped steps are counted by branch and role, and the fix goes into the training when staff are unsure or into the software when the screen is wrong.
One Session Per Role at Their Own Screen
Nobody sits through modules they will not open. The counter clerk learns billing, returns and the day close, while the storekeeper learns receipts and issues, each on a machine loaded with the real item list.
Support at the Desk During Go-Live
Habits form in week one. Support staff stand at the counter and in the stores, answer questions as they arise and write down each small irritation so the configuration can be corrected.
Adoption Measured and Acted On
Logins prove access, nothing more. Records are checked for completeness, such as deals without a next step or receipts with no purchase order, and a step everyone skips is treated as a design fault.
What Changes When Adoption Is Planned as Work
What the business gets, before any talk of technology.
Support Available From the First Day
Help arrives on day one. Questions raised at the counter are answered at the counter by someone who knows the system, and each early problem is logged against its screen.
Sessions Limited to Each Person’s Tasks
Nothing irrelevant is taught. Training covers the screens a role uses, on that role’s own data and at its own desk, and anything the person will never open is left out.
Everyday Questions Handled Within the Team
Branches stop waiting for the central team. Two or three trained people in each branch answer routine questions about returns, receipts or reports, so support no longer depends on one coordinator.
Reports Based on Complete Entries
Gaps stop reaching the reports. Follow-up dates, goods receipts matched to purchase orders and closed job cards become part of the checked record, so reports rest on data, not blank cells.
Duplicate Registers Retired
The notebook loses its job. Where the system does a task as fast as the notebook, the duplicate register has no reason to continue, and the monthly review checks that it has stopped.
A Standard Route for New Joiners
Newcomers get the current method. A short programme, a checklist and a reference card give each new joiner the way the screen is used today, so the workaround invented months ago stops travelling.
What Training and Adoption Work Covers
Everything from the first discovery session to production and long-term upkeep.
Role and Task Analysis
One shift per role is observed. The notes record what people do, in what order, under what pressure and where the new system fits into that work, including the paper slips it replaces.
Role-Based Training Plan
Every session has a named audience. A plan sets out who is trained on what, in which language, in what group size and in what order, with the machines and rooms each session needs.
Hands-On Training Sessions
Participants type from minute one. Small groups work at their own screens with realistic practice data, so a billing clerk enters lifelike invoices and a storekeeper books a receipt against a purchase order.
Quick Reference Cards and Job Aids
Each card fits one page. It lists the daily tasks of one role with screenshots and exact steps, in the language used on the floor, and is printed for the desk.
Short Screen Recordings
Every routine task gets its own recording. Staff open it on a phone, watch the steps once at the counter and carry on, so a refresher costs nobody’s time but the viewer’s.
Champion and Train-the-Trainer Programme
Two or three people per branch go deeper. They receive training and answers to the questions colleagues ask most, and support continues until each can teach the next person without us in the room.
Go-Live Floor Support
We stand where the work happens. GullySystem staff work at the counter, the stores and the accounts desk in the first days, answer questions when they are raised, and note each stumble.
Manager Enablement
Managers get their own session. It covers the reports a supervisor or branch manager should run, what complete data looks like, and how to hold the weekly review inside the system.
Adoption Measurement
Reports count what people actually did. They cover record completeness, blank fields, late entries, unused features and branches falling behind, and they are reviewed with the client in a standing meeting.
Friction Removal
The design is blamed first. Fields may be removed, defaults set, screens shortened and mobile flows cut to what a person can do standing at a shop counter.
Refresher and Phase Two Training
Real questions arrive later. A second round, held some weeks later, covers the features left out at launch and the habits that have formed since, using problems staff actually met.
New Joiner Induction Pack
Supervisors can run it themselves. The short programme teaches the system on purpose, with a checklist and practice exercises, so a new joiner does not simply copy whatever the next desk does.
Where Adoption Work Applies
The processes this service is most often asked to set up and automate.
Distributor Billing Counters at Go-Live
Go-live lands on a busy counter day. A distributor trains each billing clerk beforehand on their own machine with the real customer list loaded, and support staff stand behind the clerks on the day. Screens that slow billing are simplified afterwards.
Field Sales Teams Updating a CRM
Visit notes are written at night from memory. Sales representatives who update the CRM that way produce vague notes, so the mobile visit entry is cut to a few taps and a voice note. Training happens at a shop counter. Completeness is reviewed weekly with the sales head.
Clinic Reception on Existing Tablets
Receptionists already use the tablets. A clinic group trains them at the front desk, removes a registration field that adds time to every patient, and places reference cards in the local language at each counter.
Service Engineers Working on Phones
Engineers are never in one place. A manufacturer’s service engineers work across many regions, often without signal, so training is delivered as short recordings, one per task, with offline behaviour taught first. Senior engineers become the champions.
School Offices Before Admission Season
Admissions set the deadline. A school office planning to go live before the season schedules training well ahead, and runs the fee counter in parallel with the old process for a period. The most resistant clerk is trained first. That clerk becomes a champion.
Cases Where Training Is Not the Fix
Sometimes training is not the fix. A professional firm asks for more training because staff avoid a purchased tool, but a day of observation shows the tool takes longer than the spreadsheet. So configuration changes first. The training that follows is shorter.
Is this the right service for you?
It suits businesses that have outgrown manual processes and want a system they can rely on.
Businesses About to Go Live
Implementation is almost done. The plan lists training but does not decide who is trained, on what, when and in which language, so the days before launch fill with guesses.
Companies Working Back in Excel
The software is paid for and running. Daily work still happens in a sheet beside it, so the reports the owner reads no longer match what the business actually did that week.
Owners With an Unused CRM
Licences are paid every month. Logins look reasonable, yet deals carry no next step, no date and no owner, so the pipeline view tells the owner nothing about what will close.
Multi-Branch and Field Operations
Field teams cannot be gathered. They work across branches, sites or routes on phones rather than desks, and no single room ever holds all of them at once.
Teams Reliant on One Person
One employee understands the system. Everyone else asks that person, which is a business risk, and spreading the knowledge across champions and written aids removes the dependence before the person leaves.
When Training Is Not the Answer
Some problems are not training problems. If a task takes longer in the software than on paper, more training does not fix it and can harden staff resistance. The same holds when the system follows a process the business does not run, or when its data is wrong often enough that staff stop trusting any report. The problem sits upstream. Fix configuration or data first.
What it can do, in plain terms.
Role-Based Curriculum
One track per job. Each covers only the screens and decisions that role meets in a normal day, such as a returns approval for the counter or a stock adjustment for stores.
Training on Real Data
Practice uses your own records. The practice environment is loaded with the client’s own customers, items and rates, so exercises resemble the actual work and mistakes cost nothing.
Regional Language Delivery
Language follows the floor. Sessions and printed aids are available in whichever languages the staff at each branch speak among themselves.
Printed Job Aids
Cards are made to be used. One-page step cards with screenshots cover the daily tasks and are designed to stand beside a monitor, so staff glance at them mid-task instead of filing them.
Short Video Library
Each clip lasts one task. Staff open the recordings on a phone, and the library is kept current as screens change, so nobody learns from a video of a layout that was retired.
In-App Guidance
Help sits beside the field. Tooltips, validation messages and first-use walkthroughs can be added inside the software, so the answer appears at the moment and place where the question is asked.
Champion Network
Named people, not a helpline. Staff in each branch or department receive deeper training and a direct line to GullySystem while they gain confidence, until colleagues ask them first.
Go-Live Floor Presence
A person stands at the desk. In the first days a small unanswered question can turn into a permanent workaround, so support staff stay at the counter, the stores and the accounts desk.
Adoption Dashboards
The owner gets one view. It shows record completeness, blank fields, late entries, unused features and branch comparisons, so a branch falling behind is visible without anyone asking for a report.
Data Quality Checks
Reports catch the dodges. Scheduled checks flag placeholder values, duplicate customer records and back-dated entries, so weak adoption becomes visible early instead of at month end.
Feedback Loop Into Configuration
Struggles reach the configuration. Each difficulty a trainee raises lands on one shared list. We trace each one to the field, screen or permission behind it. Someone is named to fix it, and its progress shows on the list for all.
Induction Pack for New Joiners
Supervisors run it themselves. A checklist, exercises and printed aids let a supervisor induct each new joiner, so training continues after the engagement ends and does not leave with the trainers.
How the work runs, step by step.
From the first conversation to a release your team uses every day. Each step says what you provide and what you get back.
- 01
Watch the Work
Nothing is designed yet. Each role is observed during a normal shift, and the client gives permission to observe and tells staff beforehand that the visit is not an inspection.
- 02
Training Plan and Materials
Then the materials are built. Tracks, practice data and job aids are produced, and the client supplies the frozen configuration, sign-off on each role’s process and a decision on languages.
- 03
Champions First
Champions are trained before everyone else. Two or three people per location are named by the client, chosen for respect among colleagues rather than seniority, and released from their desks to attend.
- 04
Role Sessions Close to Go-Live
Sessions come just before the switch. Short practical sessions for a few people at a time fall just ahead of go-live. The client provides a room or counter, devices running the live system, and relief for those away from the floor.
- 05
Go-Live Floor Support
Problems are logged as they happen. GullySystem staff stay through the first days, and a quick fix route on the client side lets an issue raised in the morning be corrected by evening.
- 06
Measure, Refresh and Hand Over
Then the work is handed over. Adoption is reviewed at agreed intervals and a refresher follows once real questions exist, then a manager on the client side runs the weekly review inside the system. The induction pack passes to supervisors.
What you receive when the work is done.
Everything needed to run, maintain and extend the software without depending on us.
It connects to the systems you already use.
Tools that work stay. The new system is joined to them rather than replacing them.
Business Systems Being Adopted
- Custom ERP and portals
- Zoho CRM and Zoho One
- Odoo
- QuickBooks and Xero
- Salesforce and HubSpot
Communication and Support
- WhatsApp support groups
- Microsoft Teams
- Google Meet
- Shared helpdesk inbox
Learning and Documentation
- Google Drive and Workspace
- Microsoft SharePoint
- Notion and Confluence
- Internal knowledge base
Adoption Measurement
- Application audit logs
- Usage analytics
- Metabase and Power BI dashboards
- Data quality reports
Field and Mobile
- Android apps on staff handsets
- Offline capture and sync
- SMS reminders
- QR-coded job aids
Chosen for reliability and a long life.
Picked to match your scale and to stay maintainable for years.
Training Delivery
In-App Guidance
Materials
Measurement
Support Channels
Why owners choose GullySystem.
The Job Is Observed Before the Screen Is Taught
A shift beats a requirements document. Watching the counter through a working day shows what no specification records, such as phone calls and paper slips, and training built from that holds up in use.
Support Present on the First Morning
A person, not a phone number. Adoption is largely settled in the first week, at the desk, and a support number in a handover document does not replace someone standing next to the clerk.
Delivery in the Language of the Floor
Staff learn in their own language. Sessions and job aids are offered in the language staff speak on the floor, so nobody translates an English instruction in their head before doing the job.
Skipped Steps Treated as Design Faults
Skipped steps are a design signal. When everyone avoids the same field, that field is reviewed, the software is changed and staff are not simply told to try harder.
Client Staff Trained to Train Others
Knowledge stays in the business. Champions with a handbook and a direct line to GullySystem answer routine questions, so not every question returns to the vendor and the skill stays with the client.
Measurement Based on Records, Not Logins
Records matter more than logins. A login count shows access only, so reporting checks deals for a next step, goods receipts against purchase orders and job cards for same-day closure.
How the engagement can be shaped.
Each model says what it suits and how the work is scoped. Pick the one that fits, or ask which one we would suggest.
Go-Live Training and Floor Support
For a launch where staff must work in the new system from the first day. Training is scoped by role. A trainer prepares sessions and job aids, trains champions and stands on the floor in the first days. A manager releases staff and picks champions. Extra roles or sessions are estimated before preparation. The materials remain with the client, and a written list of changes closes the engagement.
Adoption Review for a Live System
Fits software that was bought but is barely used. The review is invoiced once, before any retraining is priced. An adoption analyst interviews staff and checks records, and a department manager explains the daily routine. Configuration fixes and retraining by role follow as distinct scoped jobs. Stopping after the review is open to both sides. Findings and materials stay with the client.
Champion and Trainer Programme
For a business that wants its own people to train new joiners and new branches. Fees run per cohort of chosen staff. A trainer delivers sessions, a handbook and exercises, and an HR or operations lead selects the staff and frees their time. Added topics get a priced note before materials are made. The programme ends when champions run a session alone. All materials are handed over.
Ongoing Adoption Support
Suits a business adding branches or hiring steadily. A monthly fee covers adoption reporting, refresher sessions, updated materials and induction for new joiners. The same trainer stays familiar with the software and the routines, and one named person receives the reports. Routine updates are absorbed. Extra sessions are priced first. Notice closes it, and the materials pass to the client.
Questions owners ask first.
Plain answers to the questions asked before work starts.
Our staff already had training and still avoid the system. What is different here?
Start by finding the reason. The software may be slower than the notebook, a mandatory field may force placeholders, or the mobile screen may be a shrunk desktop page. Retraining cannot fix extra work. Fix the cause first, then train. The training that follows is shorter.
Can you train in our staff’s own language?
Yes. Sessions run in whichever language people speak on the floor, and the one-page job aids are printed in it. Labels can sometimes be renamed. Managers are often more comfortable in English, so their sessions can run separately, with the reports and the review routine they will actually use.
How long before go-live should training happen?
Train in the days before go-live, not weeks earlier. Hands-on sessions run in the days before go-live, because anything taught a month early is often forgotten and the screens may change in between. Champions are the exception, trained earlier. The usual sequence is configuration frozen, champions trained, role sessions in the last week before launch, then floor support on the day, with a debrief each evening.
What does floor-walking at go-live actually involve?
A GullySystem team member stands at the billing counter, in the stores and at the accounts desk, answers questions as they arise and writes down every stumble. Small irritations are fixed that evening. The notes separate a wrong design from an unfamiliar one, and they decide what the next morning’s fixes and refreshers will cover.
How do you measure adoption?
Never by logins alone. Logins show access only. The measures come from records: deals with a next step and a date, goods receipts that cite a purchase order, and job cards closed the same day. Back-dated, blank and placeholder entries are counted too. Comparing branches shows where the next round of effort belongs, whether that is a distant depot, a new counter or a team that joined after the first sessions.
What are champions and how do we choose them?
Champions are two or three people per location, trained deeper than the rest, who become the first place a colleague asks when stuck. Choose for respect, not rank. The person counter staff already turn to when something goes wrong is often the right choice, and a sceptic given a role may move from arguing to explaining. Champions need time allowed for the role. Never add the duty to a full day.
Do you provide training documents and videos we can keep?
Yes. You receive one-page job aids for every routine task, short screen recordings for use on a phone, the champion handbook and an induction pack for supervisors. Source files are handed over, so your team can edit a card or re-record a clip when a screen changes, without waiting for us. Material only we can maintain goes stale.
Can you train on software your company did not build?
Yes. Accounting software such as QuickBooks or Xero, and Zoho, Odoo and Salesforce, are covered. Other vendors’ systems are fine too. We need time in the system, the configuration decisions and their reasons, and a person who can settle which path the business follows where the software allows two.
How many people can attend one session?
Usually six to ten people of one role. In larger groups the people at the back watch instead of typing, and watching teaches very little software, so attention drifts to phones within minutes. Mixed-role sessions waste half the room. Field teams that cannot be gathered get recordings for routine tasks, while their champions are trained in person at the nearest depot or branch.
What drives the cost of a training and adoption programme?
The scope sets the cost. Roles, locations and languages come first, then the length of floor support and the volume of material to produce and translate into each language. Travel to other sites is agreed in advance. Dashboards, refresher rounds and induction are separate items, priced once roles and locations are reviewed, and a champion programme is proposed wherever it costs less than visiting a branch.
Our team is spread across branches and the field. How does that work?
Champions carry most of it. Two or three people per location are trained in person, given the handbook and supported directly while they teach the rest of the team. For field staff, short recordings on a phone suit better than a session nobody can attend, and the app’s offline behaviour is the first thing they are shown. Where a location is large or the go-live is risky, travel is agreed in advance and the plan says who goes where.
What do managers need to do differently?
Managers run the weekly review inside the system. When a manager opens the live pipeline or stock position in the meeting, staff see that current records matter and that last night’s entry was read. When a manager keeps asking for a separate sheet, staff conclude that the system is optional, and training does not change that.
How soon should we run a refresher?
Run it some weeks after go-live. By then people have met situations the training did not cover, so the session corrects habits while they are still forming and covers the features left out at launch. Another round suits a major software change. Induction for later joiners should be permanent.
Read before you decide.
Practical notes on the questions this service raises, not product marketing.
How to Plan Staff Training Before a Software Go-Live
Plan training for new business software by role: who learns which screens, when sessions run, which language, champions first and support on the floor.
Signs Staff Are Not Really Using Your Business Software
Login counts hide weak adoption. Check records for blanks, placeholders and late entries, spot side spreadsheets, and tell training gaps from design faults.
Group Training or Role-Based Sessions: Which Suits New Software
Compare one large training session with role-based sessions, recordings and champions for new business software, and choose the mix that fits each role.
What Happens After Your Software Goes Live?
The first 90 days of running a new system: adoption, data corrections, who to call, what to measure and when to ask for changes, from the owner’s side.
More guides on this page’s topic
- How to measure software adoption without relying on logins
- How to choose and train software champions in each branch
- Support plan for go live week: what floor staff do each day
- Staff still avoid the software: retrain or change the setup?
- Why staff type a full stop into mandatory fields, and what to do
- Live sessions, recordings or job aids: which suits which role
- Quick reference card template for a daily software task
- Why new joiners copy workarounds, and how to induct them properly
- Why the weekly review still runs from a spreadsheet after go live
- Should software training be in the language staff speak?
Let’s Build the Right Software for Your Business
Tell us about your current operational challenge, spreadsheet bottleneck, or software requirement. An experienced engineer will review your workflow and reply within one business day.
- No obligation consultation
- Senior engineer reviews your brief
- Your operational details stay 100% confidential
Start with your requirements
Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.
Share your requirementsRelated services.
ERP, CRM and Business Software Implementation
Selection, configuration and rollout, where adoption is planned from the start rather than added as a session at the end.
Data Migration and Moving Off Spreadsheets
The data behind the training. Staff trust a system whose opening numbers match the ones they closed with.
UI/UX Design and Prototyping
When a screen keeps defeating people, the fix is the screen. Journeys redesigned and tested with the staff who use them.
Software Maintenance, Support and Rescue
Ongoing support for the system after adoption, so the questions and small changes keep getting answered.