June-August, 2020CONSTRUCTIONBUSINESSREVIEW.COM9It is extremely exciting to see the proliferation of software solutions in the construction industryAt Lithko, to navigate the complexity of this environment, we strive to follow these five principles on every initiative: 1. Put yourself in the User's shoes ­ For us it all starts with the operational pain points. Our IT department does not generate revenue by building buildings, so we must ensure that the money we invest in technology generates the maximum return on investment (ROI) for the business. Thus, we spend significant amounts of time understanding the pain points of coworkers that plan our jobs, manage our jobs, and pour concrete. We then prioritize those pain points and determine how we can alleviate them by applying technology. At Lithko, we do not adopt technology solutions and then find the problem to apply them to; instead, we identify the problem and then find the technology to resolve the problem. 2. Process always wins ­ Once we choose what pain point to address, we focus on the process by seeking to understand the interactions between different stakeholders, the information that needs to be exchanged, the metrics that need to be reviewed, and the best way for our stakeholders to review those metrics. With all of this in front of us, we then overlay the timing of how the process, data, metrics, and reports come together. Then, and only then, do we begin to look at technology solutions. This mindset ensures we don't get awestruck by the flashiest user interface or slickest dashboard, and it keeps the user requirements in front of us. It also ensures our Technology team becomes subject matter experts on the topic and can adequately support the users in the future.3.Look for a strategic partnership ­ To us technology is not a quick fix to a solution, it is a long-term commitment between us and our vendor. Thus, we have conversations with all levels of the vendor's management team to ensure we understand their vision and roadmap and they understand ours. If we get the feeling they are not willing to grow with us or have our best interests in mind, then we stay on the hunt for the right vendor, even if that means delaying the project.4. Integrate the data flow between systems ­ Technology solutions are great until you need a staff of individuals to move data from one point solution to another, or worse yet, when reporting from one does not match the other. Whenever we look to add a new technology solution to our best-of-breed portfolio, it must integrate with our other systems so that the data flow can be scheduled and seamless. At our size and scale, we cannot afford to hire a team of people to push and pull data by hand.5. Always implement with 2-in-the-box ­ As mentioned, the business need should lead the way; therefore, a technology solution should never be implemented by just IT. Every technology solution we implement is co-led with one person from the Technology team and one person from the Business. This approach not only ensures that the technology implemented meets the business need, but that user adoption becomes easier when a trusted expert of the business is on-board.There is no doubt that it is extremely exciting to see the proliferation of software solutions in the construction industry ­ not only are these solutions long overdue, but they could dramatically change the competitive environment for those that are first adopters. With that said, it can also be difficult to determine which ones to adopt, how many to adopt, and how to implement them so that they drive maximum business value and impact. For us, creating and standing by our list of key principles provides the bell-weather so that we donot lose our way in the rapidly changing environment.
< Page 8 | Page 10 >