Concentra’s John de Lorimier on the Hidden Complexities of Improving Business Functions with Technology
In many of my positions and in the initiatives I’ve led in my career, there’s been someone who says “It’s easy” or “That would be simple” or “We can get that done relatively quickly.”
Upon self-reflection, I might have said those things in my past as well. That said, I always added that “It’s a lot easier when I don’t have to do it,” and that it’s simpler when I could delegate it to someone else.
But after migrating from business into IT, I’m here to announce: Nothing’s easy.
Whether you are upgrading an application, moving an application from an on-prem to the cloud, doing both of those things at the same time (don’t do it!), or improving business functionality through technology, it will come with a level of complexity and effort that mere mortals don’t really understand. So again, from my experience in the business and sitting on the sidelines (sometimes in the good — let’s say “box seats”), I’d always wonder why IT initiatives took so long yet there was always a date being pushed out.
Now that I’m involved in all those things, I understand the reasons that determine why something won’t make the due date. I understand why a system went down, whether it was an application, a networking issue, a server, or all of the above. Sometimes these things are in our control, and sometimes they’re not.
I do think, from a technology standpoint, that many times we promise too much and deliver too little. We don’t push back enough when the business wants a technology solution to a business problem. That is, we don’t always ask enough questions to really understand the business problem, which leads us to starting building without a true understanding of the requirements and level of effort. As a result, as we start a project (and then get into multiple sprints), we find out that we didn’t understand what was needed or the business didn’t know what it really wants.
Unraveling that takes a considerable amount of time. Most of the time, we must restart, with wasted time in between. From a technology perspective, it’s key that we make sure that our requirements document is totally buttoned up, the level of effort is understood and the resources that will be needed are aligned.
As I stated earlier, it will not be easy, but by being more thorough up front, it certainly will make it easier. &