By John Kenney, Cotney Consulting Group.  

Learn about roofing's silent occupational hazard.

Ask a group of veteran roofers about the biggest safety risks they face, and you'll probably hear the same answers. Falls. Weather. Heavy lifting. Power tools. Traffic. Electricity. Rarely does someone mention the one hazard they've been exposed to almost every day of their career — the sun. 

Unlike most jobsite hazards, excessive ultraviolet (UV) exposure doesn't cause an immediate injury. There is no loud noise, no flashing warning light and no incident report at the end of the day. Instead, the damage builds slowly, year after year, often without anyone realizing it until decades later. 

For roofing professionals, the effects of long-term sun exposure deserve far more attention than they typically receive. Protecting crews isn't just about preventing today's accidents. It's also about protecting their health twenty and thirty years from now. 

The roof is one of the most demanding work environments

Anyone who has spent time on a roof during the summer understands the difference between the weather forecast and actual working conditions. An air temperature of 90 degrees can quickly become much hotter on the roof surface. White membranes reflect ultraviolet radiation upward. Metal roofs amplify glare. Dark roofing materials absorb heat while continuously radiating it back toward workers. 

Roofers aren't simply standing in the sun. They're surrounded by it. 

The combination of direct sunlight, reflected UV radiation and elevated surface temperatures creates one of the harshest outdoor work environments in construction. Most crews accept those conditions as simply part of the job. That acceptance, however, shouldn't prevent us from reducing unnecessary exposure. 

The damage happens slowly 

One of the biggest challenges with UV exposure is that the effects aren't immediately obvious. Unlike a fall or a laceration, excessive sun exposure doesn't usually stop production. Workers often think of sunburn as little more than an inconvenience. In reality, repeated UV exposure contributes to premature skin aging, eye damage andsignificantly increases the risk of skin cancer over the course of a career.  

Most roofers don't develop these problems after one summer. They develop them after forty summers. That's why this issue deserves the same level of attention as any other occupational hazard. 

Experience doesn't provide protection 

I've often heard experienced roofers say they no longer burn because they've "gotten used to the sun."  Unfortunately, that's not how ultraviolet radiation works. The absence of a severe sunburn doesn't mean the skin isn't being damaged. Every day of excessive exposure adds to the cumulative effect. In many ways, veteran roofers may actually face greater long-term risk simply because they've accumulated decades of exposure. Safety programs should recognize that occupational health isn't only about preventing today's injuries. It's also about protecting careers that may span forty or fifty years. 

Protection should become routine 

Fortunately, reducing UV exposure doesn't require complicated procedures. Like many safety improvements, consistency matters more than complexity. Lightweight long-sleeved performance shirts, wide-brim attachments designed for hard hats, quality UV-blocking safety glasses, neck protection and regular sunscreen application all reduce cumulative exposure. 

These shouldn't be viewed as optional comfort items. They should become standard components of personal protective equipment during outdoor work. The same companies that invest in fall protection equipment should also invest in protecting employees from occupational hazards that develop over decades instead of seconds. 

Planning makes a difference 

Operational planning can also reduce unnecessary exposure. During periods of extreme heat and intense UV conditions, project managers should evaluate work sequencing whenever practical. Tasks requiring prolonged exposure in open areas can often be scheduled earlier in the day while shaded work, staging activities, equipment preparation or interior tasks are completed during peak afternoon conditions. 

No roofing contractor can eliminate sun exposure. Every contractor can manage it more intelligently. These decisions protect workers while often improving productivity by reducing heat-related fatigue. 

Leadership sets the standard 

One of the greatest influences on safety culture is what supervisors choose to emphasize. If foremen consistently wear neck protection, sunglasses and sunscreen while encouraging crews to do the same, employees quickly recognize these practices as normal. If leadership ignores long-term health risks, crews will usually do so as well.  

Safety culture isn't built through written policies alone. It's built by the daily example set by field leadership. The message should be simple. Protecting yourself from the sun isn't about comfort. It's about making sure today's work doesn't create tomorrow's medical problems. 

Don't forget your eyes 

Skin isn't the only concern. Years of ultraviolet exposure can also contribute to cataracts and other vision problems. Roofers spend countless hours looking across highly reflective roof surfaces where sunlight bounces directly into their eyes. Quality safety glasses that provide UV protection should be considered essential PPE, not merely impact protection. Clear vision isn't only important for long-term health. It's critical for safely navigating roof edges, recognizing hazards and performing quality workmanship every day. 

Looking beyond today's job 

One of the signs of a mature safety program is its willingness to think beyond immediate injuries. The best companies understand that protecting employees means considering both today's hazards and tomorrow's health. 

Just as we encourage hearing protection before hearing loss develops, we should encourage sun protection before skin damage becomes permanent. The goal isn't simply getting through another project safely. The goal is helping employees enjoy long, healthy careers after decades in the roofing industry. 

Final thoughts 

The most dangerous occupational hazards aren't always the ones that cause immediate injuries. Sometimes they're the ones we become so accustomed to that we stop noticing them altogether. 

For roofers, ultraviolet exposure is a hazard. Every day spent on a roof leaves an impression. Most of the time we can't see it happening, but the effects accumulate throughout an entire career. The best roofing companies understand that safety isn't measured only by the accidents that didn't happen today. It's also measured by the long-term health of the people who helped build the company's success over the last forty years. 

By Emma Peterson.

We’re counting down the 10 most-read stories from The Coffee Shops® to help you stay on top of the latest industry conversations.

Though it may be hard to believe, October is already coming to a close. And if your month has been anything like ours here at The Coffee Shops®, it’s been busy and hard to keep up with!

To make it a bit easier for our readers to catch up on the biggest industry news and stories from October 2026, we’ve collected our top ten articles published this past month.

As our readers move into the off-season, we’ve seen an uptick of interest in training and business development articles! On the training side, our top ten list includes an article about John Kenney of Cotney Consulting Group's upcoming two-day live classroom training workshop (November 17-18, 2026) and an article based on a conversation with Rick Johnson of Tremco CPG about partnering with manufacturers that back their products up with training.

On the business development side, Emma Peterson wrote three articles for The Coffee Shops® highlighting different ways contractors can set their businesses up for success. The first, which comes in at number 6 on our list, talks about four takeaways from a decade of RoofersCoffeeShop® Trends Reports. The other articles, which take spots 3 and 2, take a look at the state of the economy going into the last quarter of the year and at the National Roofing Contractors Association (NRCA)'s live LEGALCon event, respectively.

As for our top article of the month, it was all about "the certifications, technologies and best practices that help roofing professionals build more fire-resilient structures.”

Our top ten articles from October

10 - The business case for smarter construction recycling

9 - Extending building life starts with education and training

8 - Advocacy remains a roofing priority

7 - Building smarter roofers with expert training

6 - A decade of roofing trends

5 - Good project managers think three weeks ahead

4 - NWIR scholarship opens doors for future roofing leaders

3 - Going into the last quarter of 2026

2 - Set yourself apart from the competition at LEGALCon 2026

1 - Creating a more fire-safe future

By John Kenney, Cotney Consulting Group.  

The question isn't whether learning is taking place. The question is whether your organization is teaching the lessons that will make it stronger tomorrow than it is today.

One of the biggest misconceptions in business is that training only happens when people gather in a conference room, attend a seminar or complete an online course. In reality, training starts the moment someone walks through the door. Every conversation. Every decision. Every project meeting. Every jobsite. Every interaction between a foreman and a new crew member. Every response from a project manager. Every expectation an owner reinforces — or overlooks. 

Whether a company realizes it or not, it's teaching people how the business operates every single day. The only question is whether those lessons are intentional. I've spent much of my career helping roofing contractors improve operations, and one observation has stayed with me through every company I've worked with. People usually don't perform the way leadership expects. They perform the way leadership consistently demonstrates. That's an important distinction. 

I've walked into companies that proudly told me they had excellent procedures, detailed manuals and well-developed systems. Yet when I spent time with their teams, I found something entirely different. Employees weren't following the documented process because they had learned another one. 

They had learned how the company actually operated. Those lessons didn't come from a training manual. They came from:  

• Watching experienced employees 
• Seeing which standards leadership enforced and which ones quietly disappeared when business became busy. 
• Observing what happened when mistakes occurred, deadlines slipped or communication broke down. 

People pay far more attention to behavior than they do to policy. 

One lesson I've learned over the years is that culture isn't created by what a company says. It's created by what the company consistently accepts. If incomplete job documentation is tolerated, new employees learn documentation isn't really important. If project handoff meetings are frequently skipped, new project managers quickly conclude they're optional. If change orders are delayed until the end of the project, that becomes the accepted way of doing business. Nobody needs to explain those expectations. People learn them simply by working there. 

I've also noticed that new employees become remarkably good observers. Before they're confident enough to make decisions on their own, they're watching everyone around them. 

• How does the superintendent handle pressure? 
• How does the project manager communicate with the customer? 
• How does the estimator respond when production questions arise? 
• How does the owner react when problems develop? 

Those observations become the foundation of their professional habits. Long before they're officially trained, they're already learning. That's why experienced leaders understand they're always setting an example, even when they don't realize it. 

A foreman who begins every morning with a clear plan is teaching preparation. A project manager who follows through on commitments is teaching accountability. An estimator who takes the time to explain production assumptions is teaching collaboration. An owner who remains calm during difficult situations is teaching confidence. Those lessons become part of the company's culture because people naturally repeat what they experience most often. 

Unfortunately, the opposite is equally true. I've seen organizations unintentionally train employees to accept constant firefighting as normal. They learned that planning could wait because someone would eventually solve the problem. They learned that communication wasn't necessary until something went wrong. They learned that documentation could always be completed later. Over time, those habits became the company's operating system. No one designed it that way. It simply developed through repetition.  

One observation that has stayed with me throughout my career is that companies don't drift toward excellence. They drift toward whatever behaviors leadership reinforces most consistently. That's why culture requires far more than good intentions. It requires consistency. 

One thing I admire about exceptional roofing companies is that they recognize teaching doesn't stop after orientation. Every project becomes an opportunity to develop people. Job reviews aren't simply discussions about profit and loss. They're learning sessions. Project meetings aren't just about schedules. They're opportunities to improve communication and decision-making. 

Even mistakes become valuable if leadership takes the time to explain what happened and how similar situations can be avoided in the future. That approach creates something every contractor wants, but very few intentionally build. Institutional knowledge. Knowledge that doesn't exist in one person's head. Knowledge that's shared, reinforced and passed from one generation of employees to the next. 

I've often said that one of the greatest risks facing any roofing company isn't losing a customer. It's losing decades of experience because no one took the time to pass it on. Strong companies don't allow that to happen. They create environments where experienced people teach naturally because leadership values learning as much as production. 

Another lesson I've carried with me over the years is that training isn't measured by how many classes employees attend. It's measured by how they perform when no one is watching. That's when habits reveal themselves. That's when culture becomes visible. 

Technology has created tremendous opportunities to improve learning. Online training, digital resources and mobile access have made education more available than ever before. Those tools are valuable, and they should absolutely be part of a company's development strategy. 

But technology doesn't replace leadership. People still learn most effectively by watching experienced professionals make decisions, solve problems and demonstrate the standards expected throughout the organization. That's how confidence is built. That's how judgment develops. That's how future leaders emerge. 

The strongest roofing companies I've worked with understand that every day is a training day. Every conversation either strengthens the culture or weakens it. Every decision either reinforces expectations or quietly changes them. Every leader is teaching something. Whether they intended to or not. Because your roofing company is always training someone. 

By John Kenney.  

Roofing companies don't improve simply because people work harder. They improve because leadership helps people focus on what matters most. 

Walk into almost any roofing company during the busy season, and you'll see the same thing. Phones are ringing. Estimators are turning around bids. Project managers are juggling multiple jobs. Crews are moving from one project to the next. Owners are answering questions before finishing the last conversation. From the outside, it looks productive. Everyone is busy. The problem is that being busy has never guaranteed that the business is moving in the right direction. 

Over the years, I've noticed that some of the hardest-working roofing companies I've encountered weren't necessarily the most profitable. They had talented people, good reputations and plenty of work. Yet they constantly felt like they were trying to catch up. At the same time, I've worked with companies that seemed noticeably calmer. They weren't working less. They weren't less committed. In many cases, they were actually growing faster. The difference wasn't effort. It was focus.  

One lesson this industry has reinforced throughout my career is that efficiency and effectiveness are not the same thing. Efficiency is about doing work quickly. Effectiveness is about making sure you're doing the right work in the first place. Those two ideas often get confused. 

A project manager can answer fifty emails in a day and still avoid the one conversation that would have prevented next week's scheduling problem. An estimator can produce more bids than anyone else in the office but spend valuable time pursuing projects that never fit the company's strengths. An owner can attend meetings from morning until evening without making a single decision that moves the company forward.Everyone was efficient. Very little was effective. 

I've learned that roofing companies don't usually become overwhelmed because people are lazy. They become overwhelmed because everyone is busy responding to work instead of intentionally directing it. That distinction changes everything. Think about how often interruptions shape the day. A customer calls with an urgent question. A supplier needs clarification. A foreman encounters an unexpected condition. Accounting needs information. Another opportunity to bid arrives. Every one of those situations deserves attention. But not every one deserves immediate attention. 

One of the characteristics I've consistently seen in exceptional leaders is their ability to distinguish between activity and priority. They don't simply ask, "What needs to be done?" They ask, "What matters most right now?" That question sounds simple. In practice, it's incredibly difficult. Especially in roofing. 

Construction has a way of making everything feel urgent. Weather changes. Deliveries move. Customers call. Crews need answers. Without discipline, the loudest issue quickly becomes the most important one — even when it shouldn't.  

I've walked enough jobs to know that some of the biggest operational problems started because leadership became consumed by the urgent while quietly neglecting the important. Planning meetings were postponed.Project reviews were delayed. Training was pushed to another week. Communication became shorter. Documentation waited until tomorrow. No one intended for those things to happen. Everyone was trying to survive the day. Eventually, the day started running the business instead of leadership running the day. 

Another observation that's stayed with me is that effective leaders become very comfortable saying no. Not because they don't care. Because they understand that every yes carries a cost. Every unnecessary meeting consumes time that could have been spent coaching a project manager. Every project accepted without available management capacity affects every existing customer. Every interruption accepted without question steals attention from something more important.  

Time is one of the few resources a roofing company cannot purchase more of. The strongest leaders protect it carefully. I've often told owners that one of the most valuable exercises they can perform is reviewing how leadership spent the previous week. Not what was accomplished. How time was invested. Did most decisions move the business forward? Or did leadership spend another week reacting to whatever appeared next? The answer usually explains a great deal about the company's operational performance. 

Technology has certainly improved efficiency. Estimating software is faster. Project management platforms organize information better. Artificial intelligence is helping contractors complete tasks that once requiredsignificant manual effort. Those are meaningful advancements.  

But technology doesn't determine effectiveness. It simply allows companies to perform existing processes more quickly. If the wrong priorities are driving the work, faster technology helps organizations become more efficient at heading in the wrong direction. That's an uncomfortable thought. It's also an important one. 

The companies I've admired most throughout my career weren't the busiest. They weren't the loudest. They weren't constantly celebrating how much work they had under contract. What impressed me was something much simpler. They seemed to know exactly where leadership belonged. Owners focused on leading. Project managers focused on managing. Foremen focused on execution.  

Everyone understood their priorities. Because priorities were clear, decisions became clearer. Because decisions became clearer, operations became more predictable. And because operations became more predictable, profitability usually followed. 

One lesson I've never forgotten is that roofing companies don't improve simply because people work harder. They improve because leadership helps people focus on what matters most. That's effectiveness. Efficiency makes companies faster. Effectiveness makes them better. The strongest roofing companies understand they need both. But if forced to choose between the two, they'll always prioritize effectiveness. Because moving quickly in the wrong direction has never been a winning strategy. 

By John Kenney, Cotney Consulting Group.  

In roofing, companies rarely lose their edge overnight. More often...they slowly drift away from it. 

One of the biggest challenges facing successful roofing companies isn't a lack of opportunity. It isn't finding work, investing in technology or even attracting good people. It's maintaining the operational discipline that made them successful in the first place. 

I've watched companies grow from a handful of employees into organizations with multiple crews, several project managers and an impressive backlog of work. From the outside, they looked like success stories. Revenue was increasing. New customers were coming in. The business appeared healthy. 

Then, almost without anyone noticing, things started to change. Project reviews became less consistent. Communication between departments became more informal. Jobsite visits happened a little less often. Purchasing decisions became rushed. Documentation slipped. Follow-up conversations that once happened automatically were postponed because everyone was busy. 

None of those changes seemed significant at the time. Together, they changed the company. 

I've come to believe that roofing companies rarely lose operational control because of one major event. They lose it through operational drift. Operational drift doesn't announce itself. It doesn't send an email or show up during a management meeting. It happens quietly. Processes that were once followed every time become "most of the time." Meetings that were once considered essential become optional. Once non-negotiable standards slowly become suggestions. The company continues moving forward, but the discipline that built its reputation begins fading in small, almost invisible ways.  

That's what makes operational drift so dangerous. It feels harmless. One thing I've learned over the years is that people rarely wake up and decide to lower their standards. Good people don't intentionally create average companies. Operational drift happens because everyone is trying to solve today's problem. When the phones are ringing, projects are behind schedule and customers need answers, it's easy to convince yourself that you'll get back to the process later. The problem is that "later" tends to become permanent. 

I've seen estimating reviews disappear because everyone was focused on bidding more work. I've seen project handoff meetings shortened until they eventually disappeared altogether. I've watched job cost reviews become quarterly discussions instead of the conversations that used to happen after every project. None of those decisions were made because leadership stopped caring. They were made because everyone believed they were saving time. In reality, they were borrowing problems from the future. 

One observation has stayed with me throughout my career. Strong operations aren't built on extraordinary decisions. They're built on ordinary disciplines repeated consistently. 

The daily habits that don't seem exciting are usually the ones protecting profitability. A project manager who follows up when they said they would. A superintendent who completes documentation before leaving the jobsite. An estimator who communicates assumptions instead of expecting others to figure them out. An owner who insists on reviewing projects even when the company is busy. 

Those aren't extraordinary actions. They're operational disciplines. The strongest companies protect them because they understand something many organizations overlook. Consistency compounds. So does inconsistency. 

Another mistake I see is assuming growth automatically means improvement. Growth creates opportunity, but it also magnifies weaknesses. A process that worked with two project managers may begin breaking down with six. Communication that felt natural in a twenty-person company becomes much more difficult when the organization reaches one hundred employees. Responsibilities become less clear. Decisions take longer.Information travels through more people. Without intentional structure, operational drift accelerates. That's why I often tell contractors that growth doesn't create operational problems. It exposes the ones that were already there. 

I've also noticed that operational drift usually appears long before financial reports reveal it. Margins slowly become less predictable. Projects require more management attention. Crews spend more time waiting for decisions. Customers begin asking more questions. Leadership feels busier than ever but struggles to explain why. Those are operational warning signs. The financial results arrive later. 

The companies that avoid operational drift have something in common. They periodically stop and ask themselves difficult questions: 

• Are we still following the processes that made us successful?  
• Have our standards changed without us realizing it? 
• Are we solving problems — or simply becoming better at living with them? 

Those conversations require honesty. They also require leadership. 

One lesson I've carried with me over the years is that companies don't stay excellent by accident. Operational excellence has to be protected. Every process. Every expectation. Every standard. Not because people can'tbe trusted. Because organizations naturally drift toward whatever leadership consistently reinforces. 

That's why culture matters. Culture isn't built by mission statements hanging on a wall. It's built by what leadership chooses to inspect, discuss and expect every single day. If leadership stops paying attention to the details, eventually everyone else will too.  

The encouraging news is that operational drift is completely reversible. It doesn't require rebuilding the company. It requires reconnecting the organization with the disciplines that made it successful in the first place.Sometimes that means slowing down long enough to evaluate how work is actually being performed. Sometimes it means having conversations that should have happened months earlier. Sometimes it means simply refusing to accept "good enough" where excellence once existed. 

The longer I've worked in this industry, the more convinced I've become that successful roofing companies don't outperform their competitors because they're constantly changing. They outperform them because they protect the habits, standards and operational disciplines that continue to produce predictable results year after year. 

Because in roofing, companies rarely lose their edge overnight. More often...they slowly drift away from it. 

By John Kenney, Cotney Consulting Group. 

An effective job-cost review turns a financial result into useful operating information. 

A roofing contractor can complete a project, issue the final application for payment and close the file without ever fully understanding what the work actually taught the business. That is a missed opportunity. Every completed project contains information that can improve the next tender. It shows how labour performed, whether material quantities were accurate, how long plant remained on hire, where access affected productivity and which assumptions proved realistic. 

The problem is that many businesses review project cost only to determine whether the job made or lost money. That matters, but it is not enough. A final margin tells the contractor the result. It does not always explain why the result occurred.  

A proper job-cost review should connect the financial outcome to the way the project was estimated, planned and delivered. When that connection is made consistently, completed projects begin improving future tenders. Without it, the estimating team may continue using the same rates and assumptions even when actual performance has changed. 

The final margin is only the starting point 

The first question in a project review is often simple.  

Did the project achieve the expected margin? 

That question is important, but the answer should lead to a much deeper discussion. A project may have achieved its target overall while performing poorly in several areas. A profitable variation may have hidden a labour overrun, a favourable material purchase may have covered extended plant hire or a strong final account settlement may have made the project appear operationally better than it was. 

The opposite can also happen. A well-managed project may produce a disappointing result because the original tender was too low, the programme changed or the contractor accepted a commercial condition that created additional cost. 

Looking only at the final percentage can therefore give the business the wrong lesson. The review should separate the result into its main parts and examine how labour, materials, plant, subcontract costs, supervision, delays and variations compared with the original allowance. This turns a financial result into useful operating information. 

Labour needs to be reviewed in detail 

Labour is usually one of the highest controllable costs on a roofing project, but it is often reviewed too broadly. The report may show that the project used 1,200 labour hours against an allowance of 1,000. That identifies an overrun, but it does not explain it.  

The business must understand where the additional 200 hours were used. Were production rates lower than expected? Did the team spend more time distributing materials? Was access restricted? Did the project require additional visits? Were operatives waiting for other trades? Did the client change the sequence? Was more preparation required than the tender allowed? Did quality issues create remedial work? 

The answer matters because each cause requires a different response. If the original production rate was unrealistic, future estimates should change. If the overrun was caused by site disruption, the tender process should identify and qualify that risk more clearly. If the team lacked experience with the system, training or supervision may need improvement. If additional work was completed without recovery, the variation process needs attention. 

The business should never adjust a labour rate simply because one project exceeded the estimate. It should adjust the rate when the evidence shows that the underlying assumption no longer reflects actual performance. 

Production rates should come from real work 

Many estimating systems rely on standard production rates built over time. Those rates are useful, but they should not become permanent simply because they are familiar. Roofing work changes. Materials change, installation methods improve, packaging and delivery arrangements evolve, site restrictions increase and the workforce changes. A rate that was realistic five years ago may no longer reflect the way projects are delivered today. Job-cost reviews provide the evidence needed to keep those rates current. 

If a particular system repeatedly takes longer than the estimating allowance, the contractor should investigate why. The issue may be the rate itself, but it may also be that the rate does not account for details, access or project type. Installing a large uninterrupted area is different from working around numerous rooflights, penetrations and changes in level. A new-build project with planned access is different from a refurbishment project on an occupied building. A continuous workface is different from several small phased areas. 

The estimating database should reflect those differences where practical. The goal is not to create a separate rate for every possible condition. It is to prevent the business from applying one general assumption where the work consistently behaves differently. 

Material review should include quantity, price and waste 

Material cost is another area where the final invoice total does not tell the whole story. The contractor should compare estimated quantities with actual usage and consider whether the measured quantities, packaging assumptions and waste allowances were realistic. 

Did the project require more laps, cuts or detailing than expected? Was material damaged? Were partial packs or rolls left unused? Did changes in sequence create additional waste? Were split orders or urgent purchases required? 

The review should also consider purchase price. The estimate may have used a supplier quotation that expired before the order was placed. A substitute product may have been required. Additional carriage may have been paid, or smaller orders may have reduced purchasing leverage. 

These differences should not automatically be treated as estimating errors. The purpose is to understand whether the original allowance remains realistic and whether procurement decisions affected the result. Waste deserves particular attention because it is often hidden inside total material usage. A project may appear to have consumed the expected quantity overall while one detail or roof area generated considerably more waste than planned. That lesson should return to estimating. 

Plant duration should be compared with the programme 

Plant costs are usually linked closely to project duration. If the programme extends, plant hire often extends with it. A job-cost review should compare the planned duration of cranes, hoists, telehandlers, scaffolding, mobile elevating work platforms and other access equipment with the actual duration. 

If the equipment remained on site longer, the business should understand why. Was the original programme too short? Did access begin later than expected? Was the work resequenced? Did another trade delay release of the roof area? Was the equipment hired too early? Could it have been released sooner? Did the contractor need to return later because the work was completed in phases? 

These questions improve both estimating and project planning. The review should also consider associated costs such as delivery, collection, fuel, operators, permits and repeated mobilisation. The weekly hire rate is rarely the complete financial effect. 

Supervision and management time should not disappear into overhead 

Project management and supervision are often underestimated because some of the cost is carried within company overhead. That does not mean the project did not consume the resource. A contracts manager may spend additional weeks coordinating a delayed project. A site supervisor may remain in place longer than planned. Senior management may become involved in commercial disputes, client communication or recovery planning. 

Those hours have value. If one project demands far more management time than expected, the business should understand why. Was the project inherently complex? Was the tender allowance too low? Did poor information create repeated questions? Did weak site reporting require more office involvement? Did the client’s management structure increase meeting and reporting demands? Did commercial problems require senior intervention? 

Not every hour needs to be charged directly to the project for the review to be useful. The contractor should still recognise which projects consume disproportionate management attention. That information can influence future pricing, staffing and project selection. 

Variations can distort the lesson 

Variations are an important part of the final project result, but they can make the underlying operating performance harder to see. A project may finish above its original margin because additional work was priced favourably. That does not necessarily mean the base contract performed well.  

The contractor should separate original-scope performance from variation performance where possible. Did the tendered work achieve the expected margin? Did variations recover their full labour, material, plant and management cost? Were any changes completed but not valued? Did the business carry the cost for too long? Was additional work recorded clearly enough to support recovery? 

This distinction prevents profitable changes from hiding weaknesses in the original delivery plan. It also shows whether the variation process itself is working. A variation that creates revenue but disrupts the base programme may still reduce overall project efficiency, so both the commercial value and operational effect should be reviewed. 

Interim review and final review serve different purposes 

A detailed final review is valuable, but contractors should not wait until completion to look at cost performance. If labour is already exceeding the allowance halfway through the project, the business needs to know then. If material usage is higher than expected, the team should investigate before placing the final orders. If plant is likely to remain on site longer, management should understand the reason while options still exist. 

Interim reviews help protect the current project. Final reviews improve the next one. A monthly or milestone-based review can provide enough information to identify trends without creating an excessive administrative burden. The frequency should reflect the size, duration and risk of the project. The important point is that cost information must reach the people who can influence the outcome. A report that arrives after every decision has been made is accounting history. Useful job costing supports current management and future estimating. 

The review must include the people who know what happened 

Financial reports alone cannot explain project performance. The estimator understands how the allowance was built. The project manager knows which conditions changed. The site supervisor understands what affected labour and sequence. Procurement knows what happened with suppliers and lead times. The commercial team understands variation recovery and payment. 

A useful job-cost review brings those perspectives together. This does not require a large meeting or an elaborate presentation. It requires the right people to compare what was planned with what occurred and agree on the lesson. 

If labour exceeded the estimate, the site team should explain the operating conditions. If material cost increased, procurement should explain whether the cause was price, quantity, timing or delivery. If the programme extended, the project manager should identify the events that drove the delay. If recovery was weak, the commercial team should explain whether the issue was records, notice, valuation or entitlement. Without that discussion, the business risks changing the wrong thing. 

Lessons must reach the estimating system 

A project review has limited value if the conclusions remain in meeting notes. The lesson must change something. A production rate may need to be revised, a waste factor adjusted, a plant allowance increased for a particular type of project or a tender checklist expanded to address access, phasing or occupied premises. A supplier lead time may need updating, a recurring detail may need a separate labour allowance or a qualification may need to be strengthened. 

The change should be specific and assigned to someone. Otherwise, the same lesson will appear again on the next project. This is where many contractors lose the benefit of job costing. They identify the problem but do not update the estimating tools, procedures or assumptions that created it. The meeting ends, the project is archived and the next tender begins from the same information as before. That is not continuous improvement. 

Not every result should change the rate 

Job-cost reviews must also be used carefully. One unusual project should not automatically rewrite the estimating system. A severe access restriction, client-driven delay or unexpected condition may make the project unrepresentative of normal work.  

The contractor should look for patterns. If the same issue appears across several projects, the evidence is stronger. If one system repeatedly uses more labour, one detail regularly creates excess waste or one project type consistently requires more supervision, the estimating model should reflect that experience. 

The review should distinguish between a one-off event, a project-specific condition, a repeated operating problem and an estimating assumption that is no longer accurate. That distinction prevents overreaction and keeps the estimating system grounded in reliable information. 

Good data supports better project selection 

Job-cost reviews can also help the contractor understand where the business performs best. A particular type of project may appear attractive by contract value but consistently demand excessive management time. Another may generate strong margins but create heavy cash-flow pressure. Some clients may provide repeat work with predictable conditions, while others create frequent change and delayed recovery. 

The business should understand which systems, project sizes and client relationships fit its workforce and management structure. Not every available project is the right project. A contractor that understands its actual performance can pursue work where its experience and operating system create an advantage. 

Job costing should create a learning cycle 

The most valuable job-cost system is not the one with the most reports. It is the one that changes future decisions. The tender establishes the expected cost and operating plan. The project produces actual results. Interim reviews help protect the work while it is still in progress. The final review explains the differences and converts them into better estimating assumptions. 

That cycle should continue throughout the life of the business.  

• Estimating informs delivery. 
• Delivery creates evidence. 
• Evidence improves estimating. 

When that connection is strong, the contractor becomes more accurate over time. Labour allowances become more realistic, procurement risks become easier to identify, and project teams begin with better information. When that connection is weak, the business repeats the same assumptions and hopes for a different result. A job-cost review should do more than confirm whether the project made money. It should make the next tender better. 

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 MIoR designation 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. 

By Emma Peterson. 

Woodchuck.ai rethinking how jobsite waste is handled in order to support sustainability goals while creating measurable financial benefits. 

Sustainability has become a key talking point for contractors. As John Kenney, the CEO of Cotney Consulting Group put it, “Not that long ago, sustainability discussions were limited to a handful of projects...Today, that conversation has become much more mainstream. Building owners are asking about energy efficiency, architects are exploring sustainable design options and municipalities are increasingly adopting standards that encourage greener building practices.” And as this demand for more sustainable practices rises, it is crucial that contractors not only consider the sustainability of the products they are installing, but also the sustainability of their building practices. 

This idea, of building more sustainable practices in addition to products, is what Todd Thomas and the team at Woodchuck.ai focuses on. We got the chance to learn more about their work and its benefits on an episode of Contractor Outlook™ we recorded with Todd. 

What Woodchuck.ai does is bring dumpsters to jobsites. But rather than your typical, throw everything and the kitchen sink into the same place, these dumpsters are designed to be used for material sorting. In fact, they utilize cameras and artificial intelligence software to help ensure that materials are separated properly. Then, when a dumpster is full, the Woodchuck.ai team can collect it, and take that sorted material, whether that’s asphalt products or wood products, and recycle it easily because it’s already sorted. 

Todd described how this separating and recycling of materials is such a good thing for sustainability, sharing, “We have a finite number of landfills across the United States and if you look at these landfills, they're often 30-40% wood by volume. And that wood is coming from things like construction site mixed dumpsters.” He went on, “So if we can get crews to sort their materials, we can keep that wood out of the landfill, extend the life of that landfill and get additional value out of that wood all at the same time.”  

And the best part of this whole set up? Not only can contractors feel good about their impact on the environment, it also can give them financial benefits. Todd explained:  

It might seem like a big change to start sorting materials, but it’s something that actually is pretty easy after you do it once and comes with benefits beyond sustainability. For example, we just partnered with a contractor who worked on Ford’s EV battery factory in Marshall, Michigan. Over the course of that project, we diverted 10,000 tons of wood from the landfills and instead were able to turn it into 10,000 megawatts of clean electricity. In addition to being an incredible win for sustainability, that diversion also returned a savings to the contractor of $1.6 million!  

With that kind of savings, it’s hard to deny the positive impact the Woodchuck.ai team is providing for both the environment and contractors in the field. As Todd put it, “If we can extend the life of our existing landfills by making sure that valuable materials don't get buried there, it's a win for everybody. It's a win for the contractor, it's a win for the community and it's a win for whoever was going to have the next landfill next to them.” 

Listen to the whole episode or Watch the recorded episode to learn more about Woodchuck.ai. 

By Emma Peterson. 

From field installation and project management to executive leadership, John Kenney brings a unique perspective to roofing education. 

This November, right before the holiday season begins, John Kenney, the CEO of Cotney Consulting Group, will be hosting a two-day live classroom training workshop. This workshop, which runs Nov 17-18, 2026, promises to provide attendees with high-level skills related to project takeoffs, estimating and unit pricing. To learn more about how this training and others hosted by John help professionals improve their expertise and boost their businesses, we brought John onto an episode of Roofing Road Trips®. 

All of John’s trainings are based off of his own 45+ years of experience in the roofing industry. He shared a bit about his experience with us, saying, “I started in the field and worked my way through estimating project management, operations, leadership and eventually up to the executive roles. All that experience has allowed me to see the industry from a wide variety of angles.”   

And that wide perspective gave John a clear understanding of where companies often struggle and what they need to change in order to find success. He went into more detail: 

One of the biggest challenges that I've seen is that estimators are taught how to measure roofs and how to price materials, but not how to manage the most important items, which are their assumptions, communicate scope and protect the margins of a company. This is because people see estimating as just a math problem, and not the risk management it actually is.  

In his courses, John helps attendees overcome misconceptions like this. He explained, “I work with my classes to help them recalibrate the way they think about sales and estimating... I reframe estimating as a decision-making role, not a takeoff role and from there we dive into things like scope clarity, assumptions, production planning and communication.” And at the end of the course, John’s students leave with clear, actionable ways to build better estimates and better workflows in their businesses. 

Want to learn more about John’s training offerings? Listen to the whole episode or visit the Cotney Consulting Group training page.  

By John Kenney, Cotney Consulting Group.  

Retention does not begin when an employee submits a resignation. It begins with the way the business is managed every day. 

Roofing contractors often discuss workforce retention in terms of pay, benefits and recruitment. Those factors matter, but retention is also shaped by how consistently the business is managed every day.  People notice whether projects are planned properly, expectations are clear, materials arrive when needed and supervisors communicate with respect. They notice whether good work is recognised, poor performance is addressed fairly and development opportunities are available. They also notice when every day feels like another emergency. 

A skilled roofer may accept difficult work, changing weather and the physical demands of the trade. What becomes harder to accept is repeated disruption caused by preventable management problems. Incomplete information, constant changes in direction, unclear responsibility, inconsistent supervision and repeated corrections create frustration even in companies with good intentions. For that reason, retention should not be viewed only as a recruitment or human-resources issue. It is also an operational responsibility. 

Good people become tired of preventable problems 

Roofing will always involve pressure. Programmes change, weather affects production, materials are delayed and site conditions do not always match the tender information. Experienced people understand that. The frustration begins when avoidable problems become normal. Operatives arrive without the correct materials. The planned work area is unavailable. Instructions change several times. Drawings are incomplete. A supervisor gives one direction in the morning and another later in the day. The team is then blamed when productivity falls. 

One difficult day will not usually cause a good employee to leave. A pattern of disorganisation can. People want to feel that their effort is being used productively. When they spend too much time waiting, remobilising, searching for information or correcting preventable mistakes, they begin questioning whether the business respects their time and skill. 

Retention improves when the company removes unnecessary frustration from the working day. That does not mean eliminating every problem. It means managing the problems the business can control. 

Planning affects the employee experience 

Operational planning is usually discussed in terms of programme, cost and productivity. It also affects morale. A well-planned project gives the site team a clear understanding of what needs to be completed, what materials are available and how the work should progress. A poorly planned project creates uncertainty. People may not know where they will be working next week, whether the required equipment will be available or whether the company expects them to complete a task under conditions that do not support the planned output. That uncertainty wears people down. 

Good planning creates confidence. It tells the workforce that the company understands the work and is making a serious effort to support the people expected to deliver it. Even when conditions change, a well-managed response makes a difference. If a site cannot proceed, the team should receive clear information about the revised plan. If materials are delayed, the supervisor should explain what work can continue and what is being done to resolve the issue. If labour must move between projects, people should understand why and for how long. Communication does not remove inconvenience, but it prevents inconvenience from feeling like disregard. 

Supervisors have a major influence on retention 

Employees often experience the company through their immediate supervisor. Senior leadership may establish the culture, but supervisors apply it on site. A good supervisor creates clear expectations, treats people consistently and addresses problems before they grow. They recognise effort, provide useful direction and maintain standards without creating unnecessary conflict. A poor supervisor can undermine an otherwise strong business. They may communicate through anger, apply different standards to different people or fail to plan the work. They may tolerate poor performance from some employees while expecting stronger people to carry the additional load. That creates resentment. 

Good operatives notice when accountability is uneven. They notice when reliable people are repeatedly given the most difficult tasks because management knows they will handle them. They also notice when poor attendance, low productivity or careless workmanship is allowed to continue without action. 

Retention is not improved by avoiding difficult conversations. It is improved by creating a fair environment in which expectations apply consistently. Supervisors therefore need more than technical ability. They need training in communication, planning, coaching and accountability. The way they lead will influence whether people want to remain part of the team. 

Respect is demonstrated through actions 

Most companies would say they respect their workforce. Employees judge that statement through daily experience. Respect is demonstrated when the company provides the correct information and equipment, pays accurately and on time, responds to legitimate concerns and avoids making promises it cannot keep. It is also demonstrated when management listens to people who understand the work. Site teams often recognise risks, inefficiencies and quality concerns before the office sees them. When those observations are routinely ignored, people stop offering them. That is a loss for both the employee and the business.  

Listening does not mean accepting every suggestion. It means taking the concern seriously, asking questions and explaining the decision. People are more likely to support a decision they understand, even when it is not the outcome they preferred.  

Respect is also demonstrated in how mistakes are handled. If every error leads to public criticism, employees will hide problems. If mistakes are ignored completely, standards decline. Strong leaders separate honest mistakes from carelessness, address the issue directly and use the experience to improve performance. That creates accountability without humiliation. 

Recognition should be specific 

Employees want to know that good work is noticed. Recognition does not need to be elaborate. A clear and specific acknowledgement from a supervisor or director often has more value than a generic company message. Telling a team that they did a good job is positive. Explaining that they maintained quality while adapting to difficult access, protected the client’s property or completed a challenging detail correctly is more meaningful. 

Specific recognition tells people that leadership understands what the work required and reinforces the behaviour the company wants repeated. The strongest employees are often the least demanding. They arrive, complete the work and solve problems without drawing attention to themselves. That reliability can make them easy to overlook.Contractors should make sure consistent performance is recognised, not only the most visible success. 

Development creates a reason to stay 

People are more likely to remain with a company when they can see a future within it. That future does not need to mean promotion into management. Some employees want to become supervisors or project leaders. Others want to develop greater technical skill, learn additional roofing systems, become trainers or take greater responsibility for quality. 

The company should provide more than one development path. Treating supervision as the only form of advancement can push excellent operatives into roles they do not want while leaving technically skilled employees believing there is nowhere for them to progress. Development can include manufacturer training, recognised qualifications, mentoring, cross-training, commercial awareness, leadership preparation and opportunities to support less experienced operatives. 

The most important element is clarity. Employees should understand what opportunities exist, what skills are required and what steps they can take. A vague promise of future advancement is not a development plan. People are more likely to invest in the company when they can see that the company is willing to invest in them. 

New employees need a structured beginning 

Retention begins before the first day on site. A new employee’s early experience tells them a great deal about the business. Were they given clear information about the role? Did someone explain the company’s expectations? Were the necessary equipment, clothing and documentation ready? Did they understand who they report to? Were they introduced to the team properly? Was there a plan for their first week? 

When a new employee arrives and no one appears prepared, the message is immediate. The company needed labour but did not plan for the person. A structured induction does not need to be complicated. It should cover company standards, health and safety, reporting, working hours, attendance, quality expectations, communication and the practical details of the role. 

The new employee should also know who can answer questions. Throwing someone into the work and hoping they learn by watching may appear efficient, but it often creates inconsistent performance and early frustration. A strong beginning improves confidence and helps the person become productive more quickly. 

Training should connect to real work 

Training is most valuable when employees can see how it applies to their daily responsibilities. A course may introduce an important principle, but the learning must continue on site. Supervisors should reinforce the standard, provide feedback and give employees opportunities to practise the skill. This is especially important for people moving into leadership roles. 

A newly promoted supervisor may understand the theory of planning or communication but still need help applying it during a difficult project. The contractor should not assume that one training session completes the development process. Coaching, review and repetition are necessary. Training should also reflect the individual. 

An experienced roofer learning a new system requires a different approach from a new entrant learning basic site expectations. A future supervisor needs different development from someone pursuing a technical specialist role. The best training programmes create progression rather than isolated events. 

Poor performers affect the retention of good people 

Retention discussions often focus entirely on keeping employees. The company must also recognise that retaining the wrong people can drive the right people away. Strong employees become frustrated when poor attendance, unsafe behaviour, weak workmanship or disruptive conduct is repeatedly tolerated. They may be asked to correct someone else’s work, carry more of the production load or manage avoidable conflict. Over time, they may conclude that performance does not matter. 

A fair workplace requires accountability. Employees should understand the standard, receive appropriate guidance and have a reasonable opportunity to improve. When improvement does not occur, leadership must act.  

This is not inconsistent with a positive culture. A strong culture supports people, but it also protects the team from repeated behaviour that damages quality, safety or morale. Good employees are more likely to stay when they believe the company values their effort enough to address poor performance. 

Compensation matters, but fairness matters as well 

Pay is an important part of retention. Skilled people know their value, and roofing contractors must remain aware of the market. However, dissatisfaction may also be caused by inconsistency, uncertainty or a lack of transparency. Employees may question why people with similar responsibilities are treated differently or why additional duties are assigned without recognition. They may become frustrated when overtime, travel or incentive arrangements are unclear. 

The company should have a fair and understandable approach. People should know what performance is expected and whether additional responsibility creates an opportunity for progression. Promises should also be handled carefully. A commitment made during a busy period may be remembered long after management has forgotten it. If the business cannot fulfil the promise, trust is damaged. It is better to communicate honestly than to offer reassurance the company cannot support. 

Communication during change is critical 

Roofing businesses change as they grow. Roles are adjusted, reporting lines move, technology is introduced and new procedures are added. Change may be necessary, but poor communication can make employees feel that decisions are being imposed without explanation.  

People usually want to know why the change is happening, how it will affect their work and what will be expected from them. Leadership should answer those questions directly. Not every employee will agree with every decision, but uncertainty often creates more resistance than the change itself. 

Communication should also happen early enough to matter. Telling people after a new process has already been introduced makes them feel excluded and unprepared.When possible, involve the people who will use the process. Site teams can identify practical concerns that may not be visible from the office. Their input can improve the final approach and increase acceptance. A company does not lose authority by listening. It gains better information. 

Exit conversations should become operating feedback 

When a good employee leaves, the business should try to understand why. The answer may be straightforward. They may have accepted a different opportunity, relocated, changed industries or made a personal decision that the contractor could not reasonably influence. Not every departure is a management failure. The distinction is between unavoidable turnover and preventable turnover. 

Preventable turnover may reveal an operating problem. Was the supervisor difficult to work with? Did the employee see no development path? Was the workload consistently disorganised? Were expectations unclear? Did the person feel unrecognised? Was poor performance tolerated around them? 

One exit conversation should not lead to an immediate change in policy. Patterns matter. If several people raise the same concern, leadership should take it seriously. 

Departing employees may also be more willing to discuss issues they were hesitant to raise while employed. That feedback can be uncomfortable, but it may be valuable.The purpose is not to argue with the person’s decision. It is to determine whether the business can improve the experience for those who remain. 

Retention should be measured before people resign 

Employee turnover is a late indicator. By the time someone resigns, the decision may have been developing for months. Contractors should pay attention to earlier signs. Attendance changes, participation declines, reliable employees stop offering suggestions, supervisors report growing frustration or people who once volunteered for responsibility begin doing only what is required. None of these signs proves that an employee intends to leave, but they may indicate disengagement. 

Regular conversations can help. Supervisors and managers should ask how the work is going, what is causing frustration and what support is needed. These should not be limited to formal annual discussions. Short, honest conversations throughout the year provide better information. People are more likely to raise a problem when they believe something may be done about it. Asking for feedback and then ignoring it can make the situation worse. 

A well-managed business is easier to stay with 

Roofing contractors cannot retain every employee. People leave for many reasons, and some departures are unavoidable. The goal is not to eliminate turnover. The goal is to avoid losing good people because the business made their work unnecessarily difficult. A well-managed company creates clearer expectations, stronger planning, fair accountability and visible opportunities for development. It equips supervisors to lead, listens to site knowledge and addresses poor performance before it damages the team. It also communicates honestly. 

These practices improve productivity and project performance, but they also create a more professional workplace. People are more likely to remain where they feel their effort matters, their skill is respected and their future is taken seriously.  

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. 

Por John Kenney, Cotney Consulting Group. 

En el roofing, las empresas rara vez pierden su ventaja de la noche a la mañana. Más a menudo... se van alejando poco a poco de ella. 

Uno de los mayores desafíos que enfrentan las empresas exitosas de roofing no es la falta de oportunidades. No es encontrar trabajo, invertir en tecnología o incluso atraer buenos trabajadores. Es mantener la disciplina operativa que las hizo exitosas desde el principio. 

He visto empresas crecer de un pequeño grupo de empleados a organizaciones con múltiples cuadrillas, varios project managers y una impresionante cantidad de trabajo pendiente. Desde afuera, parecían historias de éxito. Los ingresos aumentaban. Llegaban nuevos clientes. El negocio parecía saludable. 

Entonces, casi sin que nadie lo notara, las cosas comenzaron a cambiar. Las revisiones de proyectos se volvieron menos constantes. La comunicación entre departamentos se hizo más informal. Las visitas a los sitios de trabajo comenzaron a realizarse con un poco menos de frecuencia. Las decisiones de compras se tomaban con prisa. La documentación comenzó a descuidarse. Las conversaciones de seguimiento que antes ocurrían automáticamente se posponían porque todos estaban ocupados. 

Ninguno de esos cambios parecía importante en ese momento. Juntos, cambiaron a la empresa. 

Con el paso de los años, he llegado a creer que las empresas de roofing rara vez pierden el control operativo debido a un solo acontecimiento importante. Lo pierden a través de una pérdida gradual de disciplina operativa. 

Esta pérdida gradual no se anuncia. No envía un correo electrónico ni aparece durante una reunión de administración. Ocurre en silencio. Los procesos que antes se seguían siempre pasan a seguirse “la mayoría de las veces”. Las reuniones que antes se consideraban esenciales se vuelven opcionales. Los estándares que antes eran innegociables poco a poco se convierten en sugerencias. La empresa continúa avanzando, pero la disciplina que construyó su reputación comienza a desaparecer de pequeñas maneras, casi invisibles. 

Eso es lo que hace que la pérdida gradual de disciplina operativa sea tan peligrosa. Parece inofensiva. 

Algo que he aprendido a lo largo de los años es que las personas rara vez se despiertan y deciden bajar sus estándares. Las buenas personas no crean intencionalmente empresas promedio. La pérdida gradual de disciplina operativa ocurre porque todos están tratando de resolver el problema del día. Cuando los teléfonos no dejan de sonar, los proyectos están retrasados y los clientes necesitan respuestas, es fácil convencerse de que uno retomará el proceso después. 

El problema es que ese “después” tiende a convertirse en algo permanente. 

He visto desaparecer las revisiones de estimaciones porque todos estaban concentrados en presentar más propuestas. He visto cómo las reuniones de entrega de proyectos se fueron acortando hasta que finalmente desaparecieron por completo. He visto cómo las revisiones de costos de los proyectos se convirtieron en conversaciones trimestrales, en lugar de las conversaciones que antes ocurrían después de cada proyecto. 

Ninguna de esas decisiones se tomó porque el liderazgo hubiera dejado de preocuparse. Se tomaron porque todos creían que estaban ahorrando tiempo. En realidad, estaban tomando problemas prestados del futuro. 

Hay una observación que me ha acompañado a lo largo de mi carrera. Las operaciones sólidas no se construyen a partir de decisiones extraordinarias. Se construyen a partir de disciplinas comunes que se repiten de manera constante. 

Los hábitos diarios que no parecen emocionantes suelen ser los que protegen la rentabilidad. Un project manager que da seguimiento cuando dijo que lo haría. Un superintendente que completa la documentación antes de salir del sitio de trabajo. Un estimador que comunica sus supuestos en lugar de esperar que los demás los descubran. Un propietario que insiste en revisar los proyectos incluso cuando la empresa está ocupada. 

Esas no son acciones extraordinarias. Son disciplinas operativas. 

Las empresas más sólidas las protegen porque entienden algo que muchas organizaciones pasan por alto. La constancia se acumula. La falta de constancia también. 

Otro error que veo es asumir que el crecimiento automáticamente significa una mejora. El crecimiento crea oportunidades, pero también amplifica las debilidades. Un proceso que funcionaba con dos project managers puede comenzar a fallar con seis. La comunicación que parecía natural en una empresa de 20 personas se vuelve mucho más difícil cuando la organización llega a 100 empleados. Las responsabilidades se vuelven menos claras. Las decisiones toman más tiempo. La información pasa por más personas. 

Sin una estructura intencional, la pérdida gradual de disciplina operativa se acelera. 

Por eso, a menudo les digo a los contratistas que el crecimiento no crea problemas operativos. Expone los que ya estaban ahí. 

También he notado que la pérdida gradual de disciplina operativa suele aparecer mucho antes de que los reportes financieros la revelen. Los márgenes poco a poco se vuelven menos predecibles. Los proyectos requieren más atención de la administración. Las cuadrillas pasan más tiempo esperando decisiones. Los clientes comienzan a hacer más preguntas. El liderazgo se siente más ocupado que nunca, pero tiene dificultades para explicar por qué. 

Esas son señales de advertencia operativas. Los resultados financieros llegan después. 

Las empresas que evitan la pérdida gradual de disciplina operativa tienen algo en común. Periódicamente se detienen y se hacen preguntas difíciles: 

• ¿Seguimos aplicando los procesos que nos hicieron exitosos? 
• ¿Nuestros estándares han cambiado sin que nos demos cuenta? 
• ¿Estamos resolviendo problemas o simplemente nos estamos volviendo mejores para vivir con ellos? 

Esas conversaciones requieren honestidad. También requieren liderazgo. 

Una lección que he llevado conmigo a lo largo de los años es que las empresas no se mantienen excelentes por accidente. La excelencia operativa tiene que protegerse. Cada proceso. Cada expectativa. Cada estándar. 

No porque no se pueda confiar en las personas. Sino porque las organizaciones naturalmente se adaptan a aquello que el liderazgo refuerza de manera constante. 

Por eso la cultura importa. La cultura no se construye con declaraciones de misión colgadas en una pared. Se construye a través de lo que el liderazgo decide revisar, discutir y exigir todos los días. Si el liderazgo deja de prestar atención a los detalles, con el tiempo todos los demás también lo harán. 

La buena noticia es que la pérdida gradual de disciplina operativa se puede revertir por completo. No requiere reconstruir la empresa. Requiere volver a conectar a la organización con las disciplinas que la hicieron exitosa desde el principio. 

A veces eso significa detenerse el tiempo suficiente para evaluar cómo se está realizando realmente el trabajo. A veces significa tener conversaciones que debieron haber ocurrido meses atrás. A veces simplemente significa negarse a aceptar un “es suficientemente bueno” donde antes existía excelencia. 

Mientras más tiempo llevo trabajando en esta industria, más convencido estoy de que las empresas exitosas de roofing no superan a sus competidores porque están cambiando constantemente. Lo hacen porque protegen los hábitos, estándares y disciplinas operativas que continúan produciendo resultados predecibles año tras año. 

Porque en el roofing, las empresas rara vez pierden su ventaja de la noche a la mañana. Más a menudo... se van alejando poco a poco de ella.