12 Ways to Handle Unpopular Operational Decisions that Benefit Your Company
Making tough operational decisions is a critical aspect of business leadership. This article explores expert-backed strategies for implementing unpopular yet beneficial changes within your company. From standardizing workflows to restructuring vendor contracts, discover practical approaches to drive long-term growth and efficiency.
- Standardize Workflows for Long-Term Company Growth
- Implement Structured Revision Policy for Project Profitability
- Prioritize Emergency Calls During Peak Heating Season
- Enforce Digital Documentation for Job Closure Efficiency
- Redirect Resources Toward Sustainable Growth Initiatives
- Transition to Performance-Based Pay for Crew Loyalty
- Restructure Schedules to Improve Work-Life Balance
- Reduce Publishing Frequency to Enhance Content Quality
- Eliminate Underperforming Product Line for Revenue Growth
- Automate Reporting Process to Increase Operational Efficiency
- Restructure Vendor Contracts to Reduce Operational Costs
- Streamline Client Onboarding for Improved Collaboration
Standardize Workflows for Long-Term Company Growth
One of the most unpopular operational decisions I had to make was standardizing workflows across multiple teams that had historically enjoyed complete autonomy. Each team had developed its own way of doing things, and while that worked in the early stages, it became chaotic as the company grew. Duplicate work, inconsistent data, and delayed handoffs were costing us both money and customer trust.
The decision was to consolidate processes into a unified system with shared tools and clear checkpoints. On paper, it made sense. In practice, it felt like I was stripping away team independence, and the pushback was immediate. Managers worried it would slow them down, employees felt micromanaged, and there was no shortage of vocal resistance.
The way I handled it was by over-communicating the why. I made it clear that the change wasn't about control—it was about creating consistency so we could scale without constant friction. I also involved team leads in shaping the standardized process, so they had ownership instead of feeling dictated to. It wasn't an overnight fix, but slowly, people started to see the benefits.
The turning point came a few months later, when customer response times improved dramatically and cross-team projects ran more smoothly. What had once been viewed as restrictive turned into a relief—people no longer had to reinvent the wheel every time, and performance metrics visibly improved. In fact, many of the same employees who had resisted the most became advocates once they saw how much easier their work became.
The lesson I took away is that unpopular decisions are part of leadership, but how you handle the pushback determines whether they stick. If you ground the decision in clear benefits, bring people into the process, and give it time to prove itself, even the toughest changes can earn buy-in. Sometimes leadership means being willing to bear the short-term heat in service of the long-term gain.
Implement Structured Revision Policy for Project Profitability
I eliminated our popular "unlimited revision" policy for client projects, replacing it with a structured revision framework that charged for changes beyond three rounds. The team was furious because they believed this would damage client relationships and reduce our competitive advantage.
The decision came after analyzing 18 months of project data showing that unlimited revisions were destroying profitability on 34% of our engagements. Clients with unlimited revision policies averaged 8.7 revision rounds compared to 2.1 rounds for structured agreements, but weren't measurably more satisfied with final outcomes. We were essentially subsidizing indecisiveness rather than delivering superior value.
The pushback was immediate and emotional. The sales team argued we'd lose competitive bids, project managers worried about difficult client conversations, and account managers feared relationship damage. The resistance felt personal because the team took pride in our "client-first" reputation.
My approach focused on reframing the decision around client success rather than cost control. I shared data showing that projects with endless revisions actually produced lower-quality outcomes because clients never committed to clear objectives. The revision limit would force better upfront requirements gathering and more focused feedback, ultimately improving results.
The implementation was gradual and transparent. We piloted the policy with new clients first, then transitioned existing relationships during contract renewals with detailed explanations of how structured revisions would accelerate their project timelines and improve outcomes.
Results validated the decision within six months: project profitability increased 23%, average project completion time decreased 31%, and client satisfaction scores improved 12% because projects stayed focused on original objectives rather than scope creep.
The key insight was that popular policies aren't always effective policies. True client service sometimes requires boundaries that protect both parties from inefficient processes that feel collaborative but actually waste time and resources.

Prioritize Emergency Calls During Peak Heating Season
Certainly! One instance that comes to mind was last winter when we faced a significant challenge with our response times during peak heating season. As a family-owned business, ALP Heating Ltd. has always prided itself on delivering prompt service and maintaining strong relationships with our clients. However, we found ourselves stretched thin due to an unexpected surge in emergency calls, particularly during a brutal cold snap that left many homes without heat.
To address this issue, I made the difficult decision to temporarily suspend our non-emergency service calls. This meant postponing routine maintenance for some of our loyal clients to prioritize urgent repairs for those without heat. I anticipated that this decision might not be well-received, especially by clients who had been with us for years and valued our regular maintenance services.
To handle the pushback, I took a proactive approach. I reached out personally to our affected clients, explaining the reasoning behind the decision. I emphasized our commitment to safety and comfort, letting them know that by prioritizing emergency needs, we could ensure that those in urgent situations received the help they required swiftly. I also offered them priority scheduling for their maintenance once we regained our capacity.
In addition to this communication, I assured our clients that we were actively working to expand our technician team and investing in training to better manage peak times in the future. I shared our vision for a more resilient operation that could adapt to the seasonal demands we face in the Greater Toronto Area, including the ice storms and extreme temperature fluctuations that are all too common.
Ultimately, while some clients were initially disappointed, many appreciated the transparency and the rationale behind the decision. Our focus on clear communication helped to maintain trust, and as a result, we saw a significant increase in positive feedback regarding our emergency response. This experience taught us the importance of prioritizing safety and responsiveness, reinforcing our commitment to provide tailored solutions that consider the unique needs of our community.
At ALP Heating, we believe that sometimes tough decisions are necessary for the greater good, and our dedication to customer care and community welfare remains at the forefront of everything we do.

Enforce Digital Documentation for Job Closure Efficiency
It takes courage to enforce a change that's good for the business, even when your team is comfortable with the old way. My experience with an "unpopular operational decision" was all about cleaning up our paperwork. The "radical approach" was a simple, human one.
The process I had to completely reimagine was how we closed out a job. The unpopular decision was making mandatory digital photo and checklist documentation of every job before the crew could leave the site. The pushback was strong—the team felt like I didn't trust them and it added time to their day.
I handled the pushback by showing them the financial numbers. I calculated the precise amount of money and time they lost when we had to return to a site because a payment was disputed due to poor documentation. I proved the extra five minutes of digital logging saved them hours of unpaid hassle and secured their payment instantly.
The ultimate benefit was fantastic. We eliminated client payment disputes entirely, and our job efficiency increased because materials were tracked perfectly. It proved that discipline directly protects our bottom line.
My advice for others is to prove the benefit with numbers. A job done right is a job you don't have to revisit. Show them how the new process protects their money. That's the most effective way to "make a difficult decision" and build a business that will last.

Redirect Resources Toward Sustainable Growth Initiatives
I remember one moment in particular when I decided to cut back on a project that had real momentum within the company. The initiative was focused on scaling quickly, but it relied on processes that were inefficient, created unnecessary waste, and lacked a path toward sustainable growth. At the time, pulling resources from it was unpopular because people had already invested energy and believed we needed speed over structure. I had to sit with the teams, explain that building something scalable required more than short-term wins, and show how tech-driven efficiencies and recycling models would create a stronger foundation.
There was pushback, of course, because nobody likes to hear that the effort they've poured into might shift direction. What worked was being transparent, showing how the decision tied into long-term value, and listening to their concerns while still holding firm. Six months later, the company was healthier, and we had a platform that attracted the right partners. It wasn't easy in the moment, but I've learned that guiding people through change is part of the job, and if you stay focused on sustainable growth, the results speak for themselves.

Transition to Performance-Based Pay for Crew Loyalty
There are times when one must make a tough choice for the long-term health of a business. The most unpopular operational decision I made was transitioning the entire crew from a flexible hourly wage to a performance-based pay system tied to zero callbacks. The crew resisted immediately because they feared losing the guaranteed hourly rate during slow weather periods.
The old system rewarded slowness and complacency. When the crew pushed back, I didn't argue about loyalty or fairness. Instead, I sat them down and clearly outlined the simple financial reality of the new system. I showed them the numbers: I had set the performance rate high enough that any good, dedicated craftsman would earn 20% more than their previous hourly rate.
The strategy for handling the pushback was total transparency and fairness. I guaranteed that if their work was flawless and resulted in zero callbacks, the massive increase in income would be theirs. The slow, average workers left, but the dedicated craftsmen stayed, knowing they would finally be paid exactly what their high-quality work was truly worth.
The positive outcome was immense profitability and loyalty. My advice is that people will always resist change until they see the direct benefit for themselves. The way to handle pushback is to eliminate emotion and prove the change with a clear, direct, and attractive financial reality. It benefited the company by giving us a high-performing team that earned more money.
Restructure Schedules to Improve Work-Life Balance
A few years ago, one tough decision I made was ending overtime for routine pest control routes and instead restructuring schedules to balance workloads. It wasn't a popular decision—many technicians relied on that extra pay. However, we were seeing burnout, rushed jobs, and an increase in callbacks, which indicated to me that the long hours were doing more harm than good.
When the change was implemented, I made sure to explain the reasoning face-to-face. We reviewed the numbers together so everyone could see how the new system would help them maintain steady hours and earn better performance bonuses. Within a few months, morale improved, customer satisfaction increased, and our turnover rate dropped. It wasn't an easy transition, but it proved that setting limits can actually protect both the team and the business.

Reduce Publishing Frequency to Enhance Content Quality
At "What Kind of Bug Is This," one tough call I made was cutting back on publishing frequency so we could invest more time in quality control. We went from pushing out three blog posts a week to just one — which, on the surface, looked like we were slowing down. The team's concern was that we'd lose traffic or fall behind our competitors. However, in reality, we were spending too much time revising mediocre drafts, which was burning people out.
Instead of pushing through the resistance, I shared the actual data: which articles were performing, how long editing was taking, and how Google was rewarding depth over volume. Once the team saw that fewer, stronger posts would get us further — and give them more pride in their work — the energy shifted. Traffic didn't drop. It went up. And the team had more breathing room to do better work.
Eliminate Underperforming Product Line for Revenue Growth
When I had to make the difficult decision to eliminate an underperforming product line, I faced significant internal resistance from teams who had invested years in its development. I approached this challenge by gathering comprehensive performance data, consulting with key stakeholders across departments, and clearly communicating the financial rationale behind the decision. This transparent approach helped manage the pushback, and ultimately the decision proved beneficial as we saw a 25% increase in overall revenue by reallocating resources to our more promising product lines.

Automate Reporting Process to Increase Operational Efficiency
A time I had to make an unpopular operational decision was when I eliminated a long-standing manual reporting process and replaced it with an automated system. Many employees were comfortable with the old method because they had used it for years, and the new system required training and a shift in habits. At first, there was significant pushback, with concerns about job security and fears that automation would make their roles less important. I handled the resistance by being transparent about the reasoning, showing how the change would free them from repetitive work and give them more time for analysis and higher-value tasks. I also involved them in testing and refining the system so they felt ownership in the transition. Within a few months, reporting times dropped dramatically and accuracy improved. The lesson I learned is that unpopular decisions can succeed if you combine clear communication with empathy and involvement.
Restructure Vendor Contracts to Reduce Operational Costs
Early in my career as a COO, I had to restructure vendor contracts to curb rising operational costs. The decision included terminating long-established relationships with a few suppliers who had ceased to be cost-effective, despite the strong relationships they had developed with internal teams over time. The decision was the cause of an immediate backlash since many employees cherished the knowledge, partnerships, and comfort that came with those older vendors. However, after detailed analysis of the data, it became evident that the new vendors were more competitively priced, had faster turnarounds, and offered better quality—the three elements that in combination constituted greater efficiency. There was a lot of resistance to this, so I shared transparently how much of the cost-savings went into investment for growth initiatives and employee training. I also organized open forums where team members could express their concerns and be heard during this process.

Streamline Client Onboarding for Improved Collaboration
A small process change can unlock big opportunities. Efficiency, collaboration, and client trust often grow in ways you can't fully predict.
There was a moment when we decided to slightly streamline our client onboarding process, essentially reducing redundant approval steps and adding a clearer communication touchpoint. It seemed like a small operational tweak at the time, but it ended up transforming the way teams collaborated across departments. Not only did client satisfaction improve noticeably, but internal efficiency surged, deadlines became more predictable, and employees felt more empowered taking ownership of their work. It reinforced that even minor adjustments, when thoughtfully applied, can generate a ripple effect that strengthens culture, performance, and client trust all at once.