Rostering, time and attendance · working file 1 of 2

Interview synthesis

Four methods, one service. The interviews, the role-branched survey, the restaurant visits and the support-queue analysis all landed on the same problems, which is what made each finding defensible in the vendor conversation.

Employment workKFC South PacificResearch and synthesis

Method, four converging

InterviewsSemi-structured, from team members to area coaches, IT support, people-systems and payroll
200role-branched survey responses
10restaurant visits, equity and franchise
Support queuethe mobile-app ticket cluster, read as failure demand

Each method was chosen to cover a gap in the others. The survey reached the people who were never interviewed. The visits turned reported problems into observed ones. The ticket queue showed what people gave up on and rang about. Every role was covered by at least two methods, and where a survey branch returned nothing the interview round covered the role instead.

Role spread

RoleWhat the evidence added
Team membersPhone-first behaviour; no view of their own breaks or clock-ins; some did not know the platform showed pay at all.
Shift supervisorsMost adjusted forgotten clock-ins themselves; break handling at the five-hour boundary was where the rules got bent.
Rostering managersCopy-week rostering; the five-hour auto-break misfiring; the deployment chart printed and rewritten by hand.
Restaurant managersRostering craft; labour-cost estimates that drifted at scale; drops, swaps and the workaround gallery below.
Area coaches and a franchiseePer-restaurant labour compiled by hand; payroll and platform figures disagreeing; exceptions spot-checked manually.
IT supportRegistration failures; integration latency; open shifts excluded from hours; version deployment.
People-systemsImplementation history; feature enablement varying by restaurant; the training gap; compliance mapping.
Payroll, equity and franchisePay-period rigidity; the phantom-shift correction; leave balances updated only at the pay run.

The survey's area-coach and franchisee branches returned nothing. That was read as a sampling signal rather than a finding: those roles do not fill in surveys. The triangulation rule caught it, and the above-restaurant interview round, with a franchisee, two area coaches and payroll, covered both roles.

Pain-point taxonomy

Every pain point was classified twice: once by solution type, once by backlog status. The two-way split separates what the vendor should own from what the business should own from what needs a different owner entirely.

Solution typeShare of pain pointsMeaning
Technology41 per centPlatform features, configuration, mobile parity
Education26 per centTraining and communication, a category with no delivery vehicle at the time
Integration21 per centData flow between systems: latency, syncs, feeds
Process11 per centRules and workflows, including the rules that create workarounds
Other1 per centUnclassified at triage
Backlog statusOwner
Already plannedOn the vendor's release calendar, itemised
Solvable but unplannedVendor or business, with no backlog item yet
Outside the platform's scopeEducation, process change, other systems
UnclassifiedReviewed at the half-yearly gate

Workaround archaeology

The visits made the findings physical. Every recurring workaround is a missing feature made visible, and the gallery became the prioritised design brief.

WorkaroundWhere it livesWhat it proves
Paper deployment chart transcribed from the platform once or twice a dayBack office, near the scheduleDeployment generation is missing
Whiteboard above the time clock for breaksKitchen wallNo break visibility for team members or managers
Spreadsheet roster kept alongside the platformManager's deskThe readable roster does not exist in the product
Printed break sheetsShift handoverBreak compliance depends on paper memory
Missed pay added as an empty shift in the next weekPayroll correctionReopening a pay period is effectively unavailable
Shared logins to fix one's own timekeepingManager devicesManagers cannot edit their own records
Every pain point in the register carries its source: the interview, survey answer, visit note or ticket it came from. Nothing entered the register without one.

Working file from employment at KFC South Pacific, anonymised: no restaurant, colleague or vendor is named, and the figures are the ones the case study states. Back to the case.