Opening: The moment that put this on your desk

• What is your role and which colleagues will be active in this discovery (names/titles if possible)? Options: VP of Field Operations, Director of Workforce Management, Head of Dispatch, IT/Integration Lead, Head of Inventory/Logistics, Operations Manager, Other — will specify in next field
• What single event or metric made this a priority today? Options: First‑visit completion < 75%, Quarterly ops review shock, $ loss from repeat truck rolls, New enterprise SLA requiring 4‑hour windows, Executive mandate, Other
• Tell the short story of when you first noticed schedules were failing — when was it and what happened?
• How do you currently calculate first‑visit completion, repeat roll costs, and SLA adherence? Options: Automated in WFM system, Manual spreadsheets, ERP reports, Third‑party analytics, We don't have a consistent method
• Day‑to‑day, does this feel like an operational nuisance, a recurring drain on budget, or an executive crisis? Options: Operational nuisance, Recurring budget drain, Executive‑level crisis, All of the above

Are you quietly accepting repeat truck rolls as the cost of doing business?

• How often do repeat truck rolls occur across a typical week or month in the pilot geography? Options: Daily, Several times a week, Weekly, Monthly, Rarely / Not tracked
• Roughly how much does a single repeat truck roll cost you (including labor, travel, lost revenue)? Options: <$100, $100–$300, $300–$600, $600–$1,000, >$1,000, Unknown / prefer not to say
• Describe one recent case where a technician arrived without the right skill or part — what were the downstream impacts?
• Which root causes tend to drive repeats in your ops? Options: Missing parts, Incorrect skill/certification, Bad customer windows, Routing inefficiencies, Incomplete job intake data, Other
• If repeat rolls fell by 25%, what immediate operational or financial choices would that unlock for you? Options: Reduce overtime, Reassign headcount, Invest in customer SLAs, Lower budget offsets, Improve margin, Other

What's quietly breaking in your dispatch flow?

• Which single element of your dispatch process most often fails silently — technician skills, truck inventory, routing, or customer availability? Options: Technician skills/certification, Truck parts/inventory, Routing/drive‑time planning, Customer appointment accuracy, Scheduling cadence/slots
• How accurate are the data points we would rely on for optimization: technician skills, parts inventory per truck, and expected job durations? Options: High (>=90%), Moderate (70–90%), Low (<70%), We don't have these datasets currently
• Where do those data live today and how frequently are they updated? Options: WFM system (real‑time), Inventory system (daily), Manual logs/spreadsheets, ERP (batch), Not tracked centrally
• On an average day, how many manual reassignments or out‑of‑schedule returns do dispatchers perform? Options: 0–5, 6–15, 16–30, 30+
• Walk me through the last time a schedule adjustment fixed a problem — what data/tip triggered that change?

Who really owns success — and who gets blamed when it fails?

• Which leader is accountable for first‑visit completion and repeat roll costs? Options: VP Field Ops, Director WFM, Head of Customer Care, COO/Operations, Shared/Multiple
• Who must approve budgets and contracts for a pilot like this? Options: Procurement, Finance, Field Ops leader, IT security, Executive sponsor
• Who in your organization is likely to be a vocal champion and who might resist? Please name roles and reasons.
• Which KPIs or scorecards drive compensation or incentives for dispatchers and technicians? Options: First‑visit completion, SLA adherence, Customer satisfaction (CSAT), Utilization/minutes worked, On‑time arrival
• How have past projects been governed—regular steering committee, weekly ops cadence, or ad‑hoc escalation? Options: Steering committee, Weekly ops review, Ad‑hoc escalation, No formal governance

If we could guarantee first‑visit completion, what would actually change?

• What target first‑visit completion rate would you consider a game‑changer (e.g., 85%, 90%, 95%)? Options: 85%, 90%, 92%, 95%+, Don't know yet
• Beyond the headline KPI, what secondary signals will prove value (select all that apply)? Options: Reduction in repeat roll cost, Lower drive‑time per tech, Improved CSAT, Reduced overtime, Higher technician utilization
• What dollar impact over 12 months would make this project a clear win for your executive team? Options: <$1M, $1–5M, $5–10M, $10–20M, >$20M, Unsure
• How would customers notice the change—faster appointments, more resolved calls, fewer missed windows? Options: Faster appointment windows, Higher first‑visit fixes, Fewer reschedules, Improved ETA accuracy, Other
• If you could pick one outcome that must be true at the end of a successful pilot, what would it be?

What could make you say 'no' after a pilot even if metrics look good?

• Have you run optimization pilots before and what caused them to succeed or fail? Options: Successful — scaled, Ran but stalled, Failed quickly, Never run one
• Which of these concerns would most likely derail a decision after a successful pilot? Options: Integration complexity, Data quality, Technician pushback, Budget reallocation, Contractual constraints, Security/compliance
• How do your technicians feel about mobile tools and scheduling changes—curious, wary, or hostile? Options: Curious/supportive, Cautious but open, Wary and resistant, Hostile
• What change‑management steps have helped teams adopt new scheduling tools in the past? Options: Hands‑on training, Field champions, Incentives, Gradual rollout, Didn't do CM
• On a scale from 1–10, how confident are you in your team's ability to absorb and act on route/schedule recommendations? Options: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10

Let’s design a pilot that will be undeniable

• Which district(s) would make the most persuasive pilot—high‑volume, highest repeat rate, mixed skills, or a cooperative district? Options: High‑volume urban, High repeat rural, Mixed‑skill suburban, Cooperative field leadership, Other
• What minimum duration and scale do you need to be convinced (e.g., 4 weeks / 100 techs)? Options: 2–4 weeks, 1–3 months, 3–6 months, Depends on data
• Which acceptance criteria will you require to sign off on pilot success (select up to 5)? Options: X% increase in first‑visit completion, Y% reduction in repeat roll cost, Improved SLA compliance, Stable or improved CSAT, Technician adoption rate threshold, Data integrity validated
• Which data fields can you commit to providing for the pilot (jobs, technician skills, truck inventory, ETA history)? Options: Job list + locations, Technician skill matrix, Per‑truck inventory, Historical job durations, Real‑time GPS
• Who will be the day‑to‑day owner for pilot execution and troubleshooting? Options: Field Ops Manager, WFM Director, Integration/IT Lead, Third‑party partner, Other

Red flags we should put on the table now

• Are there union rules, regional labor agreements, or commercial commitments that constrain routing or technician assignments? Options: Yes — major constraints, Yes — minor constraints, No, Unsure
• Do any of your contracts require specific parts carriers or approved technicians that would limit optimizer choices? Options: Yes — many restrictions, Some restrictions, No
• What security or data handling policies must we adhere to when accessing scheduling, inventory, or customer data? Options: Standard IT security review, SOC2 / ISO requirements, Data anonymization needed, On‑prem only, No strict policies
• Which legacy systems are most likely to cause integration delays (WFM, inventory, ERP, telematics)? Options: WFM, Inventory, ERP, Telematics/GPS, CRM
• If a critical risk surfaced during integration, who has final authority to pause or re‑prioritize the pilot? Options: IT/Infrastructure, Field Ops Exec, Procurement/Legal, Steering Committee

If we align, what do the next 60–90 days look like?

• If integrations and timeline could be guaranteed, would you be ready to start a pilot within the next 30, 60, or 90 days? Options: Within 30 days, Within 60 days, Within 90 days, Need longer
• What budget range is provisionally available for a pilot and initial enablement? Options: <$50K, $50–150K, $150–300K, $300K–$1M, >$1M, Not yet budgeted
• What are the key procurement or legal milestones we should plan for (PO, SOW, security review)? Options: Purchase Order, Statement of Work, Security review, Legal terms negotiation, Other
• When should we schedule a decision meeting to review pilot charter, owners, and acceptance criteria? Options: This week, Next week, In two weeks, Later than two weeks
• What channel do you prefer for ongoing coordination—email, Slack/MS Teams, weekly video, or on‑site workshops? Options: Email, Slack/MS Teams, Weekly video call, On‑site working session, Combination

• Solution Experience Pre-Read & Alignment
• Data & Scope Confirmation Workshop
• Pilot Simulation Run — Live Engine Execution
• Pilot Results Review & Business Case Validation
• Operational Acceptance & Technician Experience Walkthrough

• Identify remaining operational or integration risks and owners for mitigation.
• Introductions & Meeting Objectives
• Obtain explicit customer validation on whether the optimized outcomes match their expectations.
• Produce an immediate simulation report with baseline comparison and annotated job examples.
• Seller to deliver the full simulation report (baseline vs optimized) with annotated job examples within 48 hours.
• Customer to review job-level exceptions and assign owners for data fixes or rule clarifications.
• Seller to update run parameters and re-run targeted slices if customer requests adjustments.
• Baseline Metrics Recap
• Confirm simulation meets or exceeds the agreed success signals or identify shortfalls with remediation plans.
• Agree on the quantified business case and sensitivity to adoption/accuracy assumptions.
• Reach a clear decision on proceeding to a live pilot district and capture the immediate next steps.
• Customer articulates a crystal-clear current state in one sentence.
• Customer to sign the pilot go/no-go decision and provide pilot start date or list outstanding blockers.
• Seller to produce a short roll-out plan with timelines, owners, and a monitoring dashboard for pilot KPIs.
• Both parties to agree on a 30/60/90 day pilot governance cadence and reporting format.
• Recap Proofs that Impact Technicians
• Validate the mobile and field workflows for technicians align with the simulated assignments.
• Agree a training and change management plan with owners and schedule for the pilot district.
• Define monitoring metrics, escalation paths, and the governance cadence for the pilot.
• Secure operational sign-off from field leadership that the pilot is executable.
• Seller to schedule train-the-trainer sessions and provide quick reference guides for technicians.
• Customer to nominate field leads and confirm availability for pilot support shifts.
• Seller to configure a pilot dashboard and share access for daily KPI monitoring.
• Both parties to create an issues backlog and cadence for triage during the pilot.
• Consequence of the current state is explicit and quantified (or sensibly estimated).
• Future state and 3 measurable success signals are agreed for the simulation.
• All required data, access, and owners are identified and scheduled for delivery.
• Customer to deliver sample job file, 2 weeks of historical dispatch logs, technician profiles, and truck-level parts manifest.
• Seller to provision simulation environment and confirm credentials/API access.
• Seller and customer to document and sign off the three success signals and go/no-go criteria.
• Schedule the live simulation run and identify observers and single point of contact for data questions.
• Recap Current/Future State & Success Signals
• Confirm the datasets are sufficient and understand the quality gaps that must be fixed before simulation.
• Agree the exact field mappings and transformation rules required for the engine to run accurately.
• Select pilot district(s) and finalize scope and modules to enable a controlled, measurable simulation.
• Lock acceptance criteria and rollback conditions for the pilot simulation.
• Customer to correct or annotate top 3 data quality issues (fields & examples) and deliver updated sample file.
• Seller to provide field-mapping template and ETL checklist; begin data ingest validation runs.
• Customer to confirm pilot district boundaries and list of participating technicians.
• Both parties to sign-off the acceptance criteria document prior to the live run.
• 1-line Current State & Expected Outcomes
• Demonstrate clear, job-level improvements that directly tie to the customer's stated consequences.
• Surface and attribute any exceptions to data or rules so remediation can be assigned.
• Run Simulation Live
• Technician Profile & Mobile Workflow Walkthrough
• Simulation Results & KPI Delta
• Data Inventory Review
• One-sentence Current State
• Job-level Walkthroughs (Diagnosis -> Proof)
• Consequence Statement
• Edge Cases: Parts Shortage, Skill Mismatch, Mid-day Reroute
• Data Quality & Gap Analysis
• Financial Impact & Risk Assessment
• Field Mapping & Transformation Needs
• Exception Review & Root Cause Mapping
• One-sentence Future State & Success Signals
• Training, Coaching & Incentives Plan
• Operational Readiness & Change Risks
• Pilot Monitoring & Governance
• Pre-Work & Data/Access Checklist

• Install and enroll technician mobile app on devices
• Deploy paperless job forms with photo and signature capture
• Enable barcode parts scanning and truck manifest sync
• Integrate real-time parts inventory with enterprise WMS
• Sync technician certifications and skill profiles from HR
• Install GPS telematics feed for live technician location
• Deploy optimization engine runtime and connect job feed
• Activate real-time reroute and push notifications
• Enable offline mobile mode with automatic data sync
• Import historical job and technician data sets
• Run hands-on technician mobile training sessions
• Configure SLA timers and automated customer alerts

Install and enroll technician mobile app on devices

• Which device ownership model applies for enrolled devices? Options: Company-owned, BYOD (Bring Your Own Device), Mixed
• How many technician devices need app installation for the pilot district? Options: Less than 50, 50-200, 200-1000, 1000+
• Which mobile operating systems and minimum versions must be supported? Options: iOS 14+, iOS 15+, Android 9+, Android 10+, Other
• Do you require Mobile Device Management (MDM) enrollment or app provisioning? Options: Yes - MDM required, No - manual install, Already using MDM (provide details)
• Will enrollment be performed remotely, in-person, or a hybrid approach? Options: Remote enrollment, In-person provisioning, Hybrid
• Who will own device support and escalation during pilot (Field IT, vendor, third-party)?
• Define acceptance criteria for app enrollment (e.g., % of devices with successful install and login).

Deploy paperless job forms with photo and signature capture

• Do you require standard templates or custom job forms for different job types? Options: Standard templates, Custom forms per job type, Mix of both
• How many distinct form types will be used in the pilot? Options: 1-3, 4-10, 10+
• Are photo and/or signature capture mandatory for all jobs, some jobs, or optional? Options: Photo required, Signature required, Both required, Optional
• Are there compliance or audit fields (e.g., regulatory checklists) that must be included? Options: Yes, No
• Should forms support conditional logic (show/hide fields based on answers)? Options: Yes, No
• Define acceptance criteria for paperless forms (e.g., submission rate, required fields completed).

Enable barcode parts scanning and truck manifest sync

• Do parts and SKUs currently use barcodes, or will new labeling be required? Options: Existing barcodes in use, New barcode labeling required, Partial
• Which barcode symbologies must be supported? Options: UPC/EAN, Code128, QR, DataMatrix, Other
• Average number of SKUs carried per truck (or SKU categories)? Options: Less than 100, 100-500, 500+
• Will scanning be via mobile camera, dedicated handheld scanners, or both? Options: Mobile camera, Handheld scanner, Both
• How frequently should the truck manifest sync occur (real-time, scheduled, manual)? Options: Real-time/sync on change, Hourly, Daily, Manual sync
• Define success criteria for parts scanning and manifest sync (e.g., scan accuracy %, manifest match rate).

Integrate real-time parts inventory with enterprise WMS

• Which WMS or inventory platform(s) will we integrate with? Options: SAP EWM, Oracle WMS, Manhattan, In-house/Proprietary, Other
• Preferred integration method for inventory (API, SFTP/flat-file, EDI, middleware)? Options: API (preferred), Flat file / SFTP, EDI, Middleware/ESB, Other
• Is real-time inventory visibility required or is periodic sync acceptable? Options: Real-time (<1 min), Near real-time (1-5 min), Periodic (hourly/daily)
• Who owns the integration (customer IT, WMS vendor, CustomerNode implementation team)? Options: Customer IT, WMS vendor, CustomerNode/vendor partnership, Other
• List required inventory data fields to sync (e.g., SKU, quantity, lot, location, reserved qty).
• Define acceptance criteria for inventory integration (sync latency, reconciliation tolerance).

Sync technician certifications and skill profiles from HR

• Where are technician certifications and skills currently stored? Options: HRIS (e.g., Workday), LMS (e.g., Cornerstone), Spreadsheet/CSV, Dispatch system, Other
• What is the desired synchronization frequency for certifications and skills? Options: Real-time/on-change, Daily, Weekly, On demand
• Are there standard mappings from certification records to dispatchable skills, or will mapping rules be created? Options: Standard mappings exist, Mapping rules required, Partial mappings
• How should expired or lapsed certifications be handled (remove skill, flag for review, allow with warning)? Options: Remove skill, Flag for review, Allow with warning, Other
• Are there privacy or HR constraints for exposing certification details to dispatch/ops teams? Options: Yes, No
• Define acceptance criteria for skills sync (e.g., % of technicians with validated skill profiles, frequency match targets).

Install GPS telematics feed for live technician location

• Is telematics already installed (OEM vehicle telematics, third-party fleet device) or must devices be installed? Options: Already installed - OEM/provider, Installed - customer-owned devices, Not installed - new install required
• Preferred feed method for location (API webhook, streaming MQTT, periodic batch API)? Options: API/webhook, MQTT/stream, Periodic API/polling, Other
• What location update frequency is required for routing decisions (e.g., every 30s, 1 min, on status change)? Options: 30 seconds, 1 minute, 5 minutes, On job status change
• Are there privacy, union, or regulatory constraints on continuous location tracking? Options: Yes, No
• Will geofencing or location-based triggers be required (job arrival/departure, depot boundaries)? Options: Yes, No
• Define acceptance criteria for telematics feed (uptime, location accuracy, latency).

Deploy optimization engine runtime and connect job feed

• Do you currently have an optimization engine that we must replace or integrate with? Options: No - new deployment, Yes - integrate with existing, Pilot/test instance exists
• What is the job feed source and format (API, CSV batch, DB replication)? Options: API (JSON), CSV/flat file, Database replication, Other
• What is the typical daily job volume for the pilot district? Options: Less than 1,000, 1,000-5,000, 5,000-20,000, 20,000+
• Which optimization objectives should be prioritized? (select all that apply) Options: Maximize first-visit completion, Minimize travel time, SLA/appointment window compliance, Ensure parts-on-truck, Balance technician workload
• Where should the optimization runtime be hosted (Customer cloud, Customer on-prem, CustomerNode cloud)? Options: Customer cloud (provide details), Customer on-prem, CustomerNode-managed cloud
• Define measurable acceptance criteria for the optimization run (e.g., target % improvement in FVC, travel time reduction).

Activate real-time reroute and push notifications

• Which notification channels should be used for technicians and customers? Options: Mobile push, SMS, Email, In-app messages, IVR/Phone
• Which events should trigger a reroute or push notification (e.g., job cancel, tech finishes early, traffic variance)? Options: Job cancel, Technician finishes early, Traffic delay, Customer no-show, Emergency priority
• Should reroutes be applied automatically or require supervisor/technician approval? Options: Automatic reroute, Supervisor approval required, Technician must accept
• Are there quiet hours, rate limits, or customer opt-outs for notifications? Options: Yes - we have restrictions, No restrictions
• Do you need templated messages and localization for notifications? Options: Yes, No
• Define acceptance criteria for reroute and notifications (delivery rate, click/accept rate, time-to-route).

Enable offline mobile mode with automatic data sync

• What is the expected maximum offline duration technicians will operate (e.g., rural areas)? Options: Less than 1 hour, 1-8 hours, More than 8 hours
• Which data types must be available offline (select all that apply)? Options: Job details/forms, Parts manifest, Maps/routing tiles, Customer history
• How should sync conflicts be resolved when a device comes online (last write wins, user prompt, server authoritative)? Options: Last write wins, User prompt/manual merge, Server authoritative with audit
• Are there device storage or security constraints for caching data offline? Options: Yes, No
• Should offline mode include attachments (photos/signatures) queuing for later upload? Options: Yes, No
• Define acceptance criteria for offline mode and sync (sync success rate, conflict rate, data integrity checks).

Import historical job and technician data sets

• What historical time range should be imported for the pilot (e.g., 3/6/12 months)? Options: 3 months, 6 months, 12 months, Custom
• Which source systems contain historical job and technician data (dispatch DB, CRM, spreadsheets)? Options: Dispatch system, CRM/OMS, Spreadsheets/CSV, Other
• Estimate historical data volume (records/jobs) to be imported. Options: Less than 100k, 100k-1M, 1M+
• Are there known data quality issues (missing fields, inconsistent technician IDs) that must be remediated? Options: Yes, No
• Do you have mapping documentation for historical fields or will mapping need to be defined? Options: Mapping exists, Mapping needs to be defined

• Statement of Work (SOW)
• Master Services Agreement (MSA)
• Commercial Terms & Pricing Schedule
• Pilot Success Criteria & Acceptance
• Implementation Timeline & Rollout Plan
• Governance & Steering Committee Charter
• Data Access, Integration & Responsibilities
• Service Level Agreement (SLA) & Performance Guarantees
• Security, Privacy & Data Processing Agreement (DPA)
• Change Order & Scope Management
• Training & Change Management Commitment
• Pilot Purchase Order / Enrollment
• Escalation & Issue Resolution Process
• Termination, Exit & Rollback Agreement

• Pilot Outcomes Review (All Stakeholders)
• Lessons Learned & Root-Cause Workshop
• Backlog Prioritization & Scale Roadmap
• Adoption & Change Management Review

• Opening & Objectives
• Schedule the Lessons Learned workshop and backlog prioritization meeting.
• Framing: One-Sentence Current State and Consequence
• Identify concrete root causes for pilot failures and successes with supporting evidence.
• Create a prioritized, testable set of remediation items with explicit acceptance criteria.
• Assign clear owners and timelines for each remediation and quick validation experiment.
• Document RCA findings and attach evidence packets to each root-cause entry in the shared backlog.
• Create remediation tickets with acceptance criteria and schedule quick validation experiments in the pilot district.
• Identify data owners to correct parts/skills records and set deadlines for data fixes.
• One-Line Future State
• Create a prioritized, timeboxed backlog that supports a safe and measurable district-by-district scale plan.
• Agree rollout sequence, acceptance gates, and governance cadence.
• Secure stakeholder commitments for resources and ownership of top-priority items.
• Publish the prioritized backlog and scale roadmap into the shared workspace with owners and dates.
• Set up recurring backlog grooming and metric review cadence (e.g., weekly/biweekly).
• Define KPI targets per district wave and configure dashboard alerts for regressions.
• Adoption Current State
• Ensure a clear, evidence-backed plan to address adoption barriers before scale.
• Agree measurable adoption targets and monitoring cadence tied to business outcomes.
• Assign owners and dates for training and communication deliverables.
• Publish the training and communication plan with scripts, trainer schedule, and sample messaging.
• Launch a pilot adoption incentive or privacy communication and measure its impact over a defined period.
• Create an adoption dashboard with alerts for key regressions (mobile usage, job completion), and share access with ops and field leads.
• Achieve stakeholder alignment on whether pilot met predefined success signals.
• Surface and document top 3–5 root causes responsible for pilot gaps.
• Make a clear decision (scale, remediate, or extend pilot) and assign owners for follow-up.
• Publish consolidated pilot dashboard and raw data to the shared workspace for audit.
• Assign owners to the top 5 exceptions for RCA and mitigation proposals within 5 business days.
• Backlog Review
• Consequence of Low Adoption
• Success Case Analysis
• Current State Snapshot
• Prioritization Exercise
• Consequence Summary
• Barrier Diagnosis
• Structured RCA (5-Why + Data Evidence)
• Consequence Mapping
• Intervention Design
• Scale Sequencing & Timeline
• Success Signals Scorecard
• Validation & Monitoring Plan
• Remediation Brainstorm & Narrow
• Governance & Escalation
• Key Exceptions & Drill-ins
• Final Commitments
• Validation Checkpoint
• Define Acceptance Criteria & Quick Tests
• Ownership & Rollout
• Decision & Next Steps
• Confirmation & Ownership