Illustration generated with AI
9 Bold HR Decisions That Succeeded Despite Pushback
Some of the best HR decisions face resistance before they deliver results. From improving patient care to using AI responsibly, these nine bold choices show how teams can turn pushback into progress. Insights from experts in the field explain why these decisions worked and what leaders can learn from them.
§ How this was made
The perspectives in this article were written by the named contributors and submitted through Connectively. Connectively's automated system selected them and used AI to write the headline, introduction, section headings, summary sections, and illustration, and to make minor edits for clarity. Articles are assembled and published automatically. Report errors to corrections@connectively.us. How we make our content
What the experts said
- Bruce TasiosEmpower Employees to Improve Patient Care
- Lilach BullockAudit Outputs Before Team Restructures
- Ace ZhuoEnd Solo Overnight On-Call Shifts
- Christopher PappasMeasure Outcomes Instead of Online Hours
- Kristie TseChampion Strengths-Based Care
- Corina ThamTie Metrics to Renewals
- Omer MalikPromote Demonstrated Ability, Not Tenure
- Daniel GohAutomate Drudgery, Redeploy Staff to Video
- Conor SmartMandate Human Checks for AI Changes
Empower Employees to Improve Patient Care
I made a notable change regarding how we handled our employees at Tasios Orthodontics. Most people who work in healthcare, including me, are frequently preoccupied with making appointments, improving office flow, and boosting employee and office productivity. Of course, these are important, and I am not dismissing them. What I learned and realized is that if the employees are stressed and lack confidence in their jobs, patients will also be stressed and may not be able to identify the reason for their stress.
Rather than creating additional work regulations, I created opportunities for the employees to make important decisions about their jobs and to take charge of their responsibilities. The major challenge I had is comparing and affirming my decision with others in the same field. There are fears about order and discipline in the workplace.
The greatest reassurance I had and the most important lesson I learned was to appreciate employees as individuals and to understand what each needed to thrive.
Most importantly, the lesson I learned is to disregard and ignore analyses and reports that focus on regulating, improving and boosting productivity and other numbers that are vital in healthcare, and to concentrate on employees and what they need to be happy, motivated and satisfied. When employees experience this, patients are also happy and satisfied.
Audit Outputs Before Team Restructures

Restructuring a team that's already running feels risky, and I've done it as fractional CMO for a US non-profit, where I report to the COO and the board. Start by listing every role, agency and contractor against what each one produced. Where you can't point to the output, the change risks very little. That check is where the confidence comes from, because you're deciding on evidence. Then take the list to the board before you act, so nobody is surprised by the decision.
End Solo Overnight On-Call Shifts

I banned single-person on-call at TradingFXVPS. Now every overnight window is covered by 2 people in different timezones (one in Asia, one in Europe) so no one gets woken up at 3am to fix a broker's MT5 server half-asleep. People said it was a luxury for a company of our size and would add pure overhead to our existing technically working setup.
It worked until it didn't. I pulled the incident history for our self-inflicted problems, and most of them occurred between 1am and 5am local time of the person on call (a wrong config pushed, a wrong node restarted, a rollback not done, etc.). Tired people, not failing hardware, are the weakness in execution-critical hosting. A 10-minute mistake during the London open can cost more than a year of an extra engineer's salary.
I know how badly I was going to screw up at 3am. My confidence comes from being able to show you the logs from those incidents and from having personally worked those 3am shifts for years. After the switch, human-error incidents plummeted and soon all ops team member turnover ceased. Nobody quits when they get to sleep at night.
Burnout is an infrastructure risk. Track the data, build the redundancy, and the cost argument to staff adequately will likely fall apart.
Measure Outcomes Instead of Online Hours

The decision was made to stop measuring commitment by time spent online and shift the team toward outcome-based planning. Some advisors worried that less direct oversight would weaken accountability, especially across a distributed workforce. To address this concern, the team agreed on clear weekly priorities, assigned owners, and shared progress openly. This created a better way to track results without constant supervision.
The decision was supported by clear evidence from within the team. Strong contributors were producing thoughtful work independently, while frequent check-ins were slowing decisions. Greater freedom was balanced with regular reviews and clear standards. The change improved follow-through and helped problems surface earlier, making it a careful experiment guided by regular reviews rather than a blind leap.
Champion Strengths-Based Care

Taking an unconventional path can feel daunting, especially when it goes against common opinion. Early in my career, I prioritized implementing a strengths-based approach with clients, even when this was often sidelined for more structured methods. The shift wasn't easy; it required persistence, thorough research, and evidence-backed reasoning with supervisors who were hesitant about its long-term effectiveness. What solidified my confidence was the progress I saw in clients who thrived when their innate capabilities were acknowledged rather than focusing exclusively on fixing deficits. Watching measurable improvements in their mental well-being served as proof where skepticism previously thrived.
I leaned heavily on continuous learning, attending specialized trainings, and staying informed about emerging studies supporting this approach to ensure it wasn't just intuition guiding me. Small tangible results snowballed into ongoing success, which reinforced that following my professional instinct, while navigating resistance respectfully, was the right choice. True growth often comes from balancing courage with careful preparation, not from following prescribed norms blindly.
Tie Metrics to Renewals

The boldest people decision I have made to date is to remove speed-based scorecards from our customer-facing team at CheapForexVPS and move to a client retention/sales-based model around client renewals. Colleagues were adamant that without a target such as tickets closed per hour, productivity would fall dramatically and costs would escalate. However, the opposite has been true, and our client chattiness has seen a dramatic upswing as people take an extra 5 minutes to solve a problem rather than just to move a ticket. Churn has dramatically fallen and referrals have increased dramatically as the team now behaves as relationship managers rather than queue clearers.
I based my confidence on two things. Firstly, from my time leading the agents at Huttons I knew that the salesperson who treats the customer by rushing them round to try and make a sale will never get a referral. People behave in the way that you measure. Secondly, the numbers worked. From my finance work at TradingFXVPS I had modelled out what a small increase in customer retention would be worth against the cost of slightly longer response times to customers. It looked good on paper before I asked people to trust me on this, and it was a 3-month pilot with one team, so I couldn't have made it more reversible if I had tried. Being bold is not about being reckless; it's about trusting your knowledge of people and then providing evidence to the doubters.
Promote Demonstrated Ability, Not Tenure

One of the boldest workforce decisions a business leader can make is promoting employees based on demonstrated capability instead of tenure or traditional credentials. This approach can challenge established expectations, particularly when seniority has historically influenced advancement. However, experience alone does not guarantee leadership effectiveness. I would evaluate candidates through practical problem-solving exercises, communication skills, and their ability to make sound decisions under pressure. The goal is to identify people who can handle greater responsibility, regardless of how long they have held their current position.
The key to making such a decision confidently is replacing subjective judgments with measurable evidence. I recommend a 60-to-90-day leadership pilot where selected employees take responsibility for defined projects, coordinate cross-functional work, and demonstrate accountability for outcomes. Performance should be assessed against clear criteria, including decision quality, team coordination, and project delivery. This gives leadership a structured way to evaluate potential while reducing concerns about favouritism or premature promotion.
I would also establish regular feedback sessions and clear escalation procedures throughout the pilot. If an employee demonstrates strong technical ability but struggles with delegation, targeted coaching can address that gap before a permanent promotion decision. The confidence to challenge conventional hiring or promotion practices should come from a transparent evaluation process, not personal conviction alone.
Bold leadership decisions become defensible when evidence replaces assumptions and employees receive a fair opportunity to prove their potential.
Automate Drudgery, Redeploy Staff to Video

This call was one of the boldest "people calls" I made. As the team was overloaded with repetitive work, the natural reaction of most people would be to hire another admin. But I was hell bent to get my colleague to move to video and content. To make that happen I had to automate the repetitive work first.
A lot of the pushback was valid too. Many people felt that automation would lead to staff feeling replaced by computers, and that the new tools would fail and make things worse. So before I ever wrote a line of Python code, I had a chat with the person that I expected to transfer the most to short form video, and I asked him to make a list of all the things he currently did that he hated. That list became the build plan.
In the end it worked well. Instead of spending hours on repetitive tasks the colleague can now edit short-form videos for our channels. Work that he actually wants to do instead of copying data from one spreadsheet to another.
To build my confidence I measured everything before making any changes. We tracked the tasks of repetitive work for two weeks and measured how long it took to complete each task. That gave me a set of numbers that I could use as a baseline for what we currently did and which no one could try to argue with.
One team at one company is not a large data set to draw from for examples. My advice would be to identify tasks that people would be happy to stop doing. Write them down. Start there.
Mandate Human Checks for AI Changes

I'd encourage other HR leaders to remember this: your real life examples will carry far more weight than anything else. I've been able to point to my mistake and the weeks it took to remedy and that's given me strength in advocating for my position when others have questioned why we're being 'too careful'. Counter to what seems to be happening in the world right now with AI and automation, 'the more we can get AI to do without human intervention the better', I actually made the decision recently to put humans back in charge of all changes made with AI at our company. As Founder and Managing Director of a company (we make custom team uniforms and branded workwear) this means that although I have HR support, people decisions ultimately come down to me. For us this has meant introducing a policy that any changes made with AI (we use Claude and AI agents for various tasks from production to marketing and content) must be checked by a human before implementing and anything irreversible must have human sign off. While on the surface this may seem like a step backwards and against progress, for us it's actually given our team greater confidence in using AI as they know there's someone ultimately responsible for checking its work and any mistakes will (hopefully) be identified before our customers do. The impetus for this policy change came about when I allowed AI to make a series of changes relating to updating products a little quicker than I should have done and the changes weren't made correctly. It took us weeks to manually check and correct all changes made. After this event I was determined to never allow AI to make changes at our company without human intervention again.
