A short talk arguing that the largest driver of long time-to-value for software implementations is not the technology but inconsistent implementation approaches and user indecision. The speaker emphasizes standardizing methodologies and providing guidance (in-app guides, community support, best-practice methodologies) to reduce back-and-forth and accelerate value delivery.
How should we implement your software? And we would say, I don't know, what would you suggest we do? And the customer would say, well, what would you suggest we do? And we had no idea because we're this little startup. But the problem is we went too long with that, like letting everyone implement in totally different ways. Some of you might have done this, right? Customer A wants to implement a certain way. Customer B randomly wants to do a different way, right? Here's the problems over time. The back and forth is where long time to value comes from. People always talked about time to value. I'd argue the biggest part of time to value is not your technology, it's how people implement it. Because people spend a lot of time on indecision. How should I use this? You know, you've all used products where you're like, okay, what do I do first? Right? And sometimes an in app guide can help. Sometimes your community can help. Sometimes just a methodology and best practice can help.
