You already know that speed is important for OSS users. They / we don’t want to wait for minutes for the OSS to respond to a simple query. That’s obvious right? The bleeding obvious.
But that’s not what today’s post is about. So then, what is it about?
Actually, it follows on from yesterday’s post about re-framing of OSS transformation. If a parallel pilot OSS can be stood up in weeks then it helps persuasion. If the OSS is also fast for operators to learn, then it helps persuasion. Why is that important? How can speed help with persuasion?
- It takes x months of uncertainty out of the evaluators’ lives
- It takes x months of parallel processing out of the evaluators’ lives
- It also takes x months of task-switching out of the evaluators’ lives
- Given x months of their lives back, customers will be more easily persuaded
It also helps with the parallel bake-off if your pilot OSS shows a speed improvement.
Whether we’re the buyer or seller in an OSS pilot, it’s incumbent upon us to increase speed.
You may ask how. Many ways, but I’d start with a mass-simplification exercise.