How Allan Myers IT Empowers Heroes in Hard Hats: A Construction Tech Success Story

In the demanding world of heavy civil construction, where every minute counts, our heroes wear hard hats and manage million-dollar projects. But even heroes need help, especially when it comes to navigating technology and change.

With over 20 years of experience at Allan Myers, Eugene Eshbach understands these challenges intimately. As the Director of Information Technology, he’s not just a tech guru; he’s a former Project Engineer, Superintendent, and Project Manager. Eugene and his team don’t just implement software; they partner with the men and women in the field and their technology vendors to ensure the technology enhances rather than hinders their business. By equipping these construction champions with the tools they need to overcome their daily challenges, they are planning for success.

Imagine being responsible for a massive construction project, juggling crews, heavy machinery, material deliveries, safety protocols, timelines, and budgets. Now, add the pressure of learning new software systems crucial to your job. It’s a daunting task that could overwhelm even the most seasoned professional. Luck aside, there is a plan in place that can carry the burden.

Eugene’s team has developed a strategy to empower the business and move with purpose.

To ensure something can last, everything gets a project plan. Not only does a solid project plan provide proof of progress, but it also sets up the best opportunity to convert a goal into reality. “No matter how big or small, we document the objectives, the purpose, who is the executive sponsor, the administrative process, the business process, and what the architecture looks like,” says Eugene. “This preparation is important because you are asking us to take and spend money, and we have to be able to answer what the business wants out of the application.”

Working relationships with software vendors, like that between HCSS and Allan Myers, can be a great asset. With round-the-clock support that can answer the most basic or complex questions, combined with an online self-help library that contains answers to every support call that HCSS Support has taken, creating documentation and supplementing project documents can be a breeze.

For example, if Eugene and his team want to walk through best practices when there is something on the project plan that needs to be documented, like an installation how to report quantities on a time card, the answer can be found on the HCSS Academy, the support help, or by calling or chatting HCSS Support any time of day.

The Business Must Define the Need

“If we want Dispatcher, for example, we have to understand what you are going to do with it to make our business better,” says Eugene. “When we bring something onboard, we define the objective, and that is all we are required to support.”

Defining the use case for software helps Allan Myers stay sharp on all aspects of how the business will use a program and helps them create clear steps for performing each user’s task. There may be several ways to do one thing, but there is one documented way Allan Myers will train and support their users to follow. This helps them avoid situations like: I’m not sure how I got this result, maybe we just start from scratch when it happens again? What happens when we lose the only person who has all the passwords? What if the person who submits payroll is sick on payroll day, and no one else knows how to do it?

“I don’t want anyone to say, ‘I don’t know how to do it because there is no guide for it,’ says Eugene. “There is a guide, a video, a document, and it has the policy in it. If there is a very specific way the business wants you to do something for Allan Myers, we will make you a guide. If there is a general thing that you want to do with the software, we will send you to the vendor’s site.”

Step-by-step project plan

1. Understand the battlefield: Regular IT visits to foremen and project sites ensure a deep understanding of real-world needs.
2. Create a blueprint for success: Every software implementation, big or small, gets a comprehensive project plan.
3. Provide clear instructions: Custom guides, videos, and documents are created for every Allan Myers-specific process.
4. Test before deployment: A rigorous testing environment ensures all updates are vetted before reaching the field.
5. Continuous improvement: Following the company motto of “Better, Faster, Safe,” the IT team learns and adapts with every interaction.

“Beginning everything with a project plan, no matter how big or small, prepares us,” says Eugene. “If we ask the right questions up front, then our implementation works on time and on schedule. If people ask us questions, we can actually answer them. By the time we go live, there is a fully-baked solution that is sustainable outside of implementation (and into the hands of our support and users) within 2-4 weeks.”

Make technology work for you, not against you.

By following this plan, Allan Myers has created a culture where changes in technology don’t have to be feared. Their people in the field can focus on what they do best – building amazing projects – while having the confidence that their IT support system has their back.

“Our success is based on culture, structure, and expectations,” Eugene explains. “When we understand the business and the day in the life of the people in the field, we can move faster and stronger.”

In summary:

1. Start with a clear project plan for every tech implementation.
2. Define specific objectives and use cases for each software solution.
3. Create detailed, accessible documentation for all processes.
4. Rigorously test updates before deployment.
5. Continuously improve based on real-world feedback.

Remember: HCSS is here to support your projects and your teams every day, all day. Taking a step towards technology is better with a path laid out and the right tools that fit your business needs. It’s time to build a better, faster, and safer future—one project at a time.