Custom software and internal tools: the code ships, user adoption still has to be built.
In-house software comes with no vendor, no tutorials and no user community. Everything your users will ever know about it, you have to teach them yourself.
How do you drive user adoption of custom software?
By producing yourself what a software vendor normally provides, at three points in the project.
Simulate the application
Train end users on a replica, with no training environment and no live data.
Guide users on screen
Contextual help you can change without a new release.
Measure real usage
See which screens and processes actually block users.
Custom software has no training ecosystem to fall back on.
For SAP or Salesforce, your teams find trainers, tutorials and forums. For Isilis or OMEGA, nothing exists outside the company: the knowledge lives in the heads of the project team.
The software moves at sprint speed. Its documentation doesn’t.
With legacy software, the original developers are gone and business rules survive by word of mouth.
More internal tools, built faster than ever.
Training environment, docs, video or in-app help: which works best?
Rated against the three constraints specific to custom software.
“For a few dozen experts, a good wiki is enough. Beyond a few hundred users, or as soon as there is staff turnover, the economics shift to simulation and in-app help.”
Our view, shaped by supporting business applications since 2001.Orange replaced the OMEGA training environment with a simulation.
The in-house ordering application serves 5,000 advisors and talks to billing and SIM systems. Running a full process in a training environment was impossible.
500 new users / year
Staff turnover made classroom training unsustainable.
30 simulated processes
All the way to the signed quote, replayable at will.

iYour turnSelect the plan the customer signed up for.!AlmostThat field is the device, not the plan.✓Well donePlan selected, the quote can be issued.Isilis, a new customer relationship tool
Simulations used in class and in self-paced e-learning, delivered as SCORM on the Ilias LMS.
Read the case study → OrangeK-NOW110+applications since 2001Help that doesn’t wait for the next release
Messages are edited without touching the code of the supported applications.
Read the case study → QuickMS · QrewK-NOW10,000+users, first help live in 2 monthsHelp content no longer goes through R&D
The support team writes and fixes help for the HR review software itself, with no development cycle.
Read the case study →See also:Orange, a simulated training environment for OMEGA ·VAL Software, in-app help built into Ammon
Four steps to roll out custom software.
Map
Pick the 10 to 30 frequent, risky or new processes, not every screen.
Simulate before go-live
Train end users on a replica with K-STUDIO, delivered as SCORM in your LMS.
Guide users on screen
K-NOW overlays guidance and alerts, with no development on your side.
Measure
K-VALUE shows real usage and feeds your product backlog.
Five questions to size your adoption plan.
Three building blocks, three project phases.
Practice on a replica before go-live.
Users repeat their real tasks as often as they need, without touching production.
Explore K-STUDIO→- Faithful replica of your application
- End-to-end, multi-system processes
- SCORM modules for your LMS
- No training environment to maintain
Get guided in the live tool after go-live.
Guidance and alerts shown inside your application, independent of its source code.
Explore K-NOW→- Contextual step-by-step guidance
- Alerts on business rules
- Updates without a new release
- One tool for your whole application portfolio
Measure real usage, continuously.
Adoption metrics that show which screens, fields and processes in your application cause trouble.
Explore K-VALUE→- Real-time adoption KPIs
- Completion of key processes and fields
- Works with in-house applications
- A product backlog driven by real usage
Custom software adoption: your questions.
Does a digital adoption platform work with custom software and internal tools?
Do we need to change the application’s code to add in-app guidance?
Can you train end users before go-live?
Can a simulation replace a training environment?
Do the modules work in our LMS?
How is custom software adoption different from SAP or Salesforce?
How do you train users on legacy software when the original developers are gone?
Show us one process. We’ll show you how to get it adopted.
Share a real process from your application and we’ll show you what its simulation and in-app guidance would look like.