Technology cannot repair a broken process

By John Kenney, Cotney Consulting Group. 

Technology can strengthen a disciplined business. It cannot create discipline for the business. 

Promises about technology surround roofing contractors. New platforms claim to improve estimating, project management, reporting, communication, scheduling, procurement and financial control. Artificial intelligence is now part of many of those conversations, often with the suggestion that it will make businesses faster, more accurate and easier to manage. 

Technology can certainly improve a roofing business. It can reduce duplicate entry, provide earlier visibility, simplify reporting and help information move more efficiently between the office and site. However, technology cannot repair a process the business has never properly defined. 

If responsibilities are unclear, information is inconsistent and people do not understand what is expected, software will not solve the underlying problem. It may simply allow the confusion to move faster. 

That is why contractors should follow a clear sequence. 

1. Define how the process should work. 
2. Select technology that supports it. 
3. Review whether the technology actually improved the result. 

The first question should not be, “Which software should we buy?” It should be, “How should this work?” 

Technology reflects the process behind it 

Every digital system depends on human decisions. Someone must decide what information needs to be entered, who is responsible for entering it, when it must be updated and what action should follow. If those decisions are unclear, the system will produce inconsistent results. 

One project manager may update the programme weekly, while another updates it only when the client asks. One supervisor may complete detailed site reports, while another records only labour and weather. One estimator may document assumptions carefully, while another stores them in personal notes. 

The technology may be functioning exactly as designed. The operating process is not. A system cannot create consistency unless the business first defines what consistent performance looks like. 

Before introducing technology, leadership should understand the current process from beginning to end. How does an opportunity enter the business? Who decides whether it is suitable to tender? How is estimating information reviewed? What happens when the contract is secured? How does the project manager receive the tender assumptions? Who creates the procurement plan? How are site reports completed? How are variations recorded and valued? How does actual project performance return to estimating? 

Technology should support those decisions and handovers. It should not be expected to invent them. 

A poor process remains poor when it becomes digital 

Contractors sometimes believe that replacing spreadsheets, emails or paper forms will automatically improve the business. The new system may look cleaner and provide more features, but the same weaknesses can continue underneath it. 

A poor handover completed through software remains a poor handover. An incomplete site report submitted electronically remains incomplete. A late variation entered into a commercial platform remains late. An inaccurate production rate stored in an estimating database remains inaccurate. 

Digital information is not automatically good information. The business must decide what information is important and establish a standard for how it will be captured. Otherwise, the contractor risks investing in technology while continuing to make decisions from unreliable data. That can be more dangerous than having limited data because the system may create confidence in information that does not reflect reality. 

Define the problem before selecting the solution 

Technology decisions often begin with a demonstration. The contractor sees an impressive dashboard, mobile application or automated workflow and begins imagining how it could improve the business. 

The better approach is to begin with the problem. Where is information being lost? Which decisions are made too late? Where does duplicate work occur? Why do project managers lack visibility? What prevents estimating information from reaching the site? Why do variations remain unresolved? What is leadership unable to see each week? 

Once the problem is clear, the contractor can decide whether technology is the right solution and which capabilities are genuinely required.  

Some issues may not need software. They may need clearer responsibility, better meetings or a simpler checklist. The objective should not be to make every process digital.It should be to make every important process work.  

Technology becomes valuable when it removes friction from a process that already has a clear purpose. 

Simplify the process before automating it 

Automation can make a good process faster. It can also make an unnecessarily complicated process harder to manage. Before automating a workflow, the contractor should ask whether every step is needed:  

• Why is the same information entered in several places?  
• Why does a routine approval require several people?  
• Why are reports created that no one uses?  
• Why does the site team complete forms that do not lead to action?  
• Why does the project manager maintain a separate spreadsheet when the information already exists elsewhere? 

These questions often reveal that the process has grown over time without being reviewed. A new requirement was added after a problem, another report was introduced for a manager and an additional approval was created to improve control. Eventually, the process became burdensome. 

Technology should not preserve unnecessary complexity. It should create an opportunity to remove it. The strongest implementation begins by simplifying the process, defining the required information and automating only the steps that add value. 

Ownership must remain clear 

Automation can create the impression that the system is now responsible for the work. It is not. The system may send a reminder, update a dashboard or move information to another stage, but someone still owns the outcome. 

If a technical approval is overdue, someone must follow up. If labour is moving above the allowance, someone must investigate. If a site report identifies additional work, someone must review it. If a material delivery date changes, someone must assess the programme effect. 

Technology can make these issues visible. It cannot replace ownership. Every workflow should identify the person responsible for entering or confirming the information and the person responsible for acting on it.  

Without that clarity, notifications accumulate and dashboards become lists of known problems. Visibility without action does not improve performance. 

Site adoption determines whether the system works 

Many technology implementations are designed primarily from the office. That creates risk. A process may appear logical on a computer screen but be difficult to use on site. Supervisors may be expected to complete lengthy forms on a mobile device while managing labour, deliveries, quality, access and client communication. Poor connectivity may make the system unreliable or operatives may be asked to enter information that duplicates what the supervisor already reports. 

When the process is difficult, people find ways around it. They send a message instead of completing the form, make notes and enter them later, record only the minimum information or return to the old spreadsheet because it feels faster. Leadership may describe this as resistance to technology. Sometimes it is. Often, it is evidence that the system was designed without enough understanding of the work. 

The people expected to use the technology should be involved before the process is finalised. They can identify where a step is impractical, where information is unclear and where the workflow does not match what happens on site. Listening to users does not mean allowing every preference to control the design. It means testing whether the process can be followed under real working conditions. 

Training must explain why the information matters 

Technology training often focuses on system navigation. Users are shown how to open the application, complete a form, attach a photograph and submit the information.That is necessary, but it is not enough. People also need to understand why the information matters. 

A site supervisor is more likely to complete a variation record properly when they understand how it supports labour and material recovery. A project manager is more likely to maintain procurement dates when they understand how leadership uses the information to identify programme risk. An estimator is more likely to document assumptions when they understand how those notes support the handover. 

Training should connect the task to the business outcome. It should also explain what happens after the information is submitted. If employees enter information but never see anyone use it, they begin questioning the value of the process. Technology adoption improves when users see that their information leads to decisions. 

Avoid creating several versions of the truth 

One of the greatest risks in technology implementation is allowing multiple systems to carry the same information. The project programme exists in the project management platform, a spreadsheet and the client’s system. Labour hours appear in payroll, site reports and a separate job-cost file. Variations are tracked by the project manager, quantity surveyor and finance team in different formats. 

When information changes, not every version is updated. The business then spends time deciding which number is correct. Technology should reduce duplicate records, not create more of them. The contractor should establish which system is the recognised source for each type of information. 

Where is the current programme maintained? Where is the official variation register? Where are procurement commitments recorded? Where does leadership review labour performance? Who is authorised to update each record? 

Other reports may draw from that information, but the underlying source should remain clear. A dashboard is only useful when everyone trusts the data behind it. 

Dashboards should show where action is needed 

Dashboards can be valuable, but only when they support management decisions. A dashboard filled with every available measure may look impressive while making it difficult to identify what requires attention. 

The most useful dashboards focus on exceptions. Which projects are over labour allowance? Which approvals are overdue? Which materials threaten the programme? Which variations remain unsubmitted? Which client commitments are late? Which applications have not been certified? Which quality issues are repeating? 

The objective is not to display everything the business knows. It is to show where the operating plan is moving outside expectation. 

A measure should also lead to a defined response. If the dashboard shows that a project is amber, what happens next? Who reviews it? What information is required? When is the position reassessed? Without that discipline, the dashboard becomes another report that people look at without changing the outcome. 

Technology should reduce administrative effort 

A good system should make it easier to complete important work. If technology creates more administration than it removes, the contractor should examine the design. Project managers should not spend hours transferring the same information between systems. Supervisors should not complete several forms that capture similar details. Estimators should not rebuild information that already exists in a client or project record. 

Automation, integration and standard templates can reduce repetitive work. That gives people more time for planning, communication and decision-making. However, efficiency should not be measured only by how quickly a form can be completed. The quality of the information still matters. A shorter report that captures the critical facts is more useful than a long report completed poorly. The contractor should seek the simplest process that provides enough information to manage the work properly. 

Artificial intelligence depends on reliable information 

Artificial intelligence may create valuable opportunities for roofing businesses. It can assist with document review, summarisation, communication, data analysis and the identification of patterns across large amounts of information. However, AI is only as useful as the information and judgement supporting it. If the source information is incomplete, inconsistent or inaccurate, the output may be misleading. 

An AI tool cannot explain labour overruns properly if waiting time, access restrictions and additional work were never recorded. It cannot identify reliable estimating patterns if cost codes are used differently across the business. It cannot provide a dependable summary of contractual risk if the documents supplied are incomplete. 

Artificial intelligence can process information quickly. It cannot create missing facts. Contractors should improve their information discipline before relying heavily on AI-driven analysis. 

Human judgement remains essential 

Roofing projects contain context that systems do not always understand. A labour overrun may indicate poor productivity, but it may also reflect restricted access, client-driven resequencing or additional preparation. A delayed material may appear to be a procurement failure, but the release may have depended on information from another party. 

Technology can identify the condition. Experienced people must interpret it. That is particularly important when decisions affect health and safety, quality, contractual responsibility, client relationships or significant financial risk. 

The system should support professional judgement, not replace it. The strongest technology strategy combines reliable information with people who understand roofing and know how to act on what the information reveals. 

Implementation should happen in manageable stages 

Contractors sometimes attempt to replace several systems and processes at the same time. Estimating, project management, site reporting, procurement, job costing and client communication are all changed together. That creates unnecessary risk.  People are asked to learn too much at once; problems become difficult to isolate, and leadership cannot tell whether the process, training or technology is causing the difficulty. A staged implementation is usually more effective. 

The contractor might begin with one process that creates clear value, such as project handovers, site reporting or variation management. The business defines the process, tests it with a small group, gathers feedback and corrects weaknesses before expanding. Early success builds confidence and gives leadership practical experience before moving into more complex workflows. The objective should not be the fastest possible implementation. It should be sustainable adoption. 

Old processes must be retired 

One reason technology projects fail is that the new system is introduced while the old process remains available. Employees are told to use the new platform, but the spreadsheet is still accepted. Site reports can be entered digitally or emailed. Project managers maintain personal trackers because leadership has not established one standard. 

The business then operates two systems. That creates duplicate work and inconsistent information. Once the new process has been tested and shown to work, leadership must decide when it becomes the required standard. The old method should be retired unless there is a genuine reason to retain it. This requires confidence from management. If leaders continue asking for personal spreadsheets because they are familiar, employees will follow that example. Adoption begins with leadership behaviour. 

Review whether the technology improved the result 

A system is not successful simply because it has been launched. The contractor should review whether it is producing the intended improvement. Are users completing the process consistently? Is the information accurate? Has duplicate work decreased? Are decisions being made earlier? Has project visibility improved? Are variations moving more quickly? Which parts of the process are still being avoided? 

The business should also consider whether the system has created unintended work. A report may take longer than expected, an automated notification may be sent too frequently or a workflow may require approval from someone who does not need to be involved. Continuous improvement applies to technology as much as any other operating process.  

The goal is not to preserve the original design. It is to improve business performance. 

Technology works best inside a disciplined business 

Technology can help roofing contractors become more consistent, informed and efficient. It can improve communication between estimating, project management, site operations, commercial management and leadership. It can reduce duplicate entry, create useful reminders and make risks visible earlier. What it cannot do is compensate for unclear expectations, weak ownership or inconsistent management. 

The contractor should first define and simplify the process. The right technology can then support that process, after which leadership must review whether it actually improved the result. The system should support the way the business intends to operate. Not the other way around. 

The best technology does not make leadership less important. It gives leaders better information and more time to lead. 

Learn more about Cotney Consulting Group in their Coffee Shop Directory or visit www.cotneyconsulting.com.

About the author 

John Kenney has more than 45 years of experience in the roofing industry. His career has included every level of roofing operations, from field installation and estimating through executive leadership. He is CEO of Cotney Consulting Group, a partner member of the International Federation for the Roofing Trades and earned the MIoRdesignation from the former Institute of Roofing in the United Kingdom. He works with roofing contractors to improve estimating, project management, operational performance, leadership and profitability.