Embed
Embed: Making Sure the System Gets Used, Not Just Switched On
Technology only creates value when people actually use it. In this step we translate the deployed platform into daily habits — training control-room engineers and site technicians, defining who owns what data, setting up a support desk with clear SLAs, and tracking adoption metrics for the first 90-180 days so the investment doesn't quietly revert to spreadsheets and WhatsApp.
Typical duration · 6-10 weeks (plus 90-day hypercare support window)
Samples generated 05 Sept 2026, 11:27 pm ISTWhat happens in this step
- 01Map every user role (control-room operator, site O&M technician, asset manager, finance) to the specific workflows they must perform in the new system
- 02Design and deliver role-based training — classroom, on-site shadowing and short video modules — with a competency sign-off checklist for each user
- 03Build a change-management plan addressing resistance points identified during Diagnose (e.g. staff comfortable with manual logs, fear of performance transparency)
- 04Stand up a tiered support model: L1 helpdesk, L2 platform vendor escalation, L3 internal super-users, with defined response and resolution SLAs
- 05Publish simple job-aids and SOPs at each site/control room in local language where relevant, laminated at operator desks
- 06Run a 90-day hypercare period with weekly adoption reviews, login/usage analytics, and rapid-fix backlog for early usability issues
- 07Hand over a sustainment plan — refresher training cadence, new-joiner onboarding kit, and KPI dashboard the client team owns going forward
What we need from you
- Final user list and org chart with roles for all system users across HQ and site locations
- Site access and calendar availability for on-site training sessions (control room + field O&M crews)
- IT helpdesk / ticketing tool access if an existing system is to be integrated
- Sign-off from client sponsor on support SLA tiers and escalation matrix
- List of any regional language requirements for job-aids and training material
- Availability of 2-3 internal 'super-users' per site to be trained as first-line champions
Worked example (anonymised, illustrative)
Digital O&M Command Centre rollout · 850 MW solar + 300 MW wind fleet · Pan-India, multi-state O&M sites
Following platform deployment for real-time generation monitoring and predictive maintenance, adoption across 14 sites needed structured training and support to replace manual logbooks and ad-hoc calls.
Sample deliverables from this step
Every sample below is analyst-written and anonymised for illustration — structure and depth mirror our real deliverables; figures and names are not from any client engagement.
Illustrative · Growthifye-preparedRole-Based Training & Certification Plan
Structured training calendar mapping each user role to modules, delivery mode, and a competency sign-off before system go-live at each site.
Sample excerpt · Training Schedule Extract — Site Cluster 3 (Rajasthan) — illustrative figures
| Role | Module | Mode | Duration | Sign-off Owner |
| Control Room Operator | Real-time SCADA dashboard & alarms | Classroom + live shadow | 2 days | Ops Manager |
| Site O&M Technician | Mobile fault-logging app | On-site hands-on | 0.5 day | Site Lead |
| Asset Manager | Performance & availability reports | Remote webinar | 3 hrs | Portfolio Head |
| Finance/Billing | Energy settlement export module | Remote webinar | 2 hrs | Finance Lead |
| Super-user (per site) | Advanced diagnostics & escalation | Classroom | 1 day | IT Consultant |
- Sign-off checklist required before individual user access is activated
- Refresher sessions scheduled at 45 and 90 days post go-live
Illustrative · Growthifye-preparedChange Management & Adoption Playbook
Documents resistance points, communication plan, incentive alignment and a stakeholder map to drive genuine day-to-day usage rather than parallel manual processes.
Sample excerpt · Adoption Risk Register — Sample Entries — illustrative figures
| Risk | Site/Group | Likely Cause | Mitigation | Owner |
| Reversion to manual logbooks | Site Cluster 1 | Poor mobile connectivity | Offline-sync mode enabled in app | IT Consultant |
| Operator distrust of auto-alarms | Control Room HQ | Past false-positive alerts | Alarm tuning workshop + trust-building period | Platform Vendor |
| Low usage by senior asset managers | Portfolio Office | Dashboard seen as ops-only tool | Custom executive KPI view added | IT Consultant |
| Data entry fatigue | All field sites | Duplicate entry across systems | Single-entry API integration with legacy ERP | IT Consultant |
- Playbook reviewed jointly with client HR/Ops leadership before rollout
- Updated at 30/60/90-day adoption checkpoints
Support Model & SLA Framework
Defines the tiered support structure — helpdesk, vendor escalation, internal super-users — with response/resolution SLAs and after-hypercare handover terms.
Sample excerpt · Support Tier & SLA Summary — illustrative figures
| Tier | Handles | Response SLA | Resolution SLA | Channel |
| L1 Helpdesk | Login issues, basic usage queries | 30 min | 4 hrs | Phone/chat |
| L2 Platform Vendor | Software bugs, integration faults | 2 hrs | 24 hrs | Ticketing portal |
| L3 Internal Super-user | Site-specific config, training gaps | 4 hrs | 48 hrs | On-site/remote |
| Post-hypercare (Day 91+) | All tiers, client-owned | As per internal SLA | As per internal SLA | Client helpdesk |
- SLA tiers agreed with client sponsor before hypercare start
- Escalation matrix reviewed monthly during first quarter
Adoption Analytics Dashboard
Tracks login frequency, feature usage, ticket volumes and training completion by site during the 90-day hypercare period to flag sites needing extra support.
Sample excerpt · Adoption KPI Extract — Week 6 of Hypercare — illustrative figures
| Site | Login Rate (7-day) | Fault Logs via App (%) | Training Completion | Open Tickets |
| Site Cluster 1 (Rajasthan) | 92% | 78% | 100% | 2 |
| Site Cluster 2 (Gujarat) | 65% | 41% | 85% | 6 |
| Site Cluster 3 (Tamil Nadu) | 88% | 83% | 100% | 1 |
| Control Room HQ | 97% | N/A | 100% | 0 |
- Low-scoring sites flagged for targeted re-training in week 7
- Dashboard handed to client Ops team with editable thresholds
Outcomes
- System usage sustained above 85% of active users past the 90-day hypercare window, verified through login and feature-use analytics
- Manual/parallel processes (logbooks, spreadsheets) formally retired at all rollout sites
- Support tickets resolved within agreed SLA in over 90% of cases during hypercare
- Client team fully equipped with an internal training and support playbook to onboard new sites or staff without external help
Questions clients ask
What if some sites have poor connectivity for training or app usage?
We build offline-first workflows into the rollout plan and run on-site (not remote-only) training at low-connectivity locations, with a sync mechanism once connectivity is restored.
Who owns the support desk after your engagement ends?
The support model is designed for a phased handover — we run L1/L2 support during hypercare, then transition ownership to the client's internal team or IT partner, with documented SOPs and escalation contacts.
How do you measure whether adoption has actually succeeded?
We track hard usage metrics (login frequency, feature use, ticket trends) rather than relying on self-reported satisfaction, and report these weekly during hypercare with clear thresholds for intervention.
