DB FPX 8750 Assessment 4

Specific Business Problem

Crestline has put money into digital tools like a mobile app for field service, a scheduling and dispatch platform, and a new CRM. However, they have seen little use of these tools and have had to rely on old spreadsheets and phone-based workarounds.  So far, the expected gains in efficiency and accuracy have not happened. Contracts are having trouble with late invoicing, and leaders are unsure if more digital investment is worth it.

Gap in Practice

The gap in practice is that the Change & Digital Adoption capability isn’t very good yet.  Some of the things that make up the gap are no repeatable change-management method linked to IT rollout (sponsor model, stakeholder mapping, comms plan, training strategy); not enough frontline involvement during design/testing; not enough super-user networks and on-the-job coaching; no way to measure adoption/behavior change; and no way to lock in new ways of working (process updates, incentives, performance metrics).

Why the Specific Gap in Practice Was Chosen

People, not technology, usually create value.  The gap explains why digital projects keep failing to deliver the operational benefits they were supposed to: without careful change design and adoption mechanics, users fall back on workarounds they already know.  The issue is quantifiable (adoption rate, daily active users, percentage of process steps completed in the system, time-to-value), actionable (sponsor alignment, user engagement, training, measurement, and incentives), and strategically significant, as digital capability is a fundamental driver for future productivity and scalability.

Research and Effectiveness of Chosen Gap in Practice

Studies on implementation and organizational change show that structured change management (sponsor alignment, stakeholder engagement, coaching, role-based training, and reinforcement) makes it more likely that people will use new technology and get a good return on investment.  Prosci ADKAR-style approaches and practitioner syntheses show that clear sponsor coaching, frontline super-users, bite-sized training, and adoption KPIs (usage, compliance rates) all significantly increase long-term digital use.  Long-term success is guaranteed by including changes to processes in performance metrics and operator workflows.

DB FPX 8750 Assessment 4: Project of Interest

The “AdoptRight Digital Enablement Pilot” is a four-month program to get more people in two regions (about 120 field techs and 20 dispatchers) to use the field-service mobile app and scheduling platform.  Main parts:

1. Sponsorship and change team: Choose an executive sponsor and put together a change team with people from different departments, such as operations, IT, HR/learning, and frontline reps.
2. Stakeholder and readiness assessment: make a map of user groups, find out what is stopping them from adopting, and establish a baseline for current processes and the number of workarounds.
3. Co-design and super-user network: hold quick co-design sessions with techs and dispatchers from each area; hire and train eight super-users (peer coaches) in each area.
4. Role-based microlearning and on-the-job coaching: use 15–20 minute micro-modules, short job aids, and 1:1 coached shifts where super-users watch and coach their peers.
5. Adoption metrics and cadence: Set key performance indicators (KPIs) like daily active users, the percentage of jobs completed in the app from start to finish, scheduling accuracy, and time to invoicing. Publish a weekly adoption dashboard and hold a weekly adoption huddle to get rid of any problems.
6. Reinforcement and governance: Include important adoption metrics in dispatcher and tech performance reviews and shift huddles. Celebrate early adopters and quick wins.
7. Sustain and scale: After three months, improve the training and start a phased rollout plan with measured adoption thresholds.
8. Expected results: 70–85% of pilot techs using the tool every day, 40–60% fewer spreadsheet workarounds for scheduled jobs, a shorter time to invoice (target: −20–30%), and clear productivity gains that make scaling up worthwhile.

Observations within My Workplace

• Field techs and dispatchers say that older systems were “designed for HQ” and didn’t match what was really going on in the field, which led to low trust.
• Training has only happened once in the classroom, with little follow-up work; super-users are not identified or given power.
• Before the rollout, no adoption metrics were set, so IT considers deployments “done” after they go live.
• Leaders go back to old ways of doing things when incentives and daily routines (like shift huddles and pay talks) don’t work.
• These operational realities explain why digital tools are not being used and why it is necessary to have planned change mechanics.

Personal Biases

I like structured change frameworks and measurable adoption KPIs, but this could make simple coaching practices too formal.  I have to make sure that solutions stay lightweight and useful for busy field teams and respect the practical knowledge of technicians.

Reflection

This evaluation underscored that digital initiatives are as much organizational transformation endeavors as they are technical constructions.  It’s important to involve frontline users early on, have a strong sponsor, peer coaching, measurable adoption goals, and ways to reinforce them.  Starting with a targeted pilot with clear KPIs builds credibility for scaling and lowers the risk of a “big-bang” rollout.