Why High Performers Who Hold Your Business Hostage Are Not Assets

By Tomáš Cina, CEO at Discury · AI-assisted research, human-edited

Editor's Take — Tomáš Cina, CEO at Discury

What strikes me reading these threads is how often founders mistake "veteran status" for "high performance." I have seen this pattern repeat across the threads we monitor at Discury — a founder keeps a legacy employee because they are "the face of the business," even when that employee actively sabotages the systems needed to scale. It is a classic trap: we fear the short-term drop in service quality so much that we accept long-term stagnation.

The second trap is the "reassurance" fallacy. In one r/smallbusiness thread, a founder struggled with a receptionist who resisted new workflows after a business partner introduced efficiency changes. The founder tried to reassure her with benefits and job security, but the resistance deepened. Security does not cure a lack of alignment; it often validates it. When an employee feels they are untouchable, they stop seeing themselves as part of a team and start seeing themselves as the owner of their specific domain.

If I were managing this today, I would stop the "reassurance" cycle immediately. It is a waste of energy. Instead, I would define the new workflow as the only way to operate, provide the training, and measure the output. If they cannot or will not adapt, they are not high performers anymore; they are bottlenecks. The most successful founders are those who prioritize the system over the individual, knowing that a business held hostage by one person is not a business — it is a dependency.

Managing High Performing Teams When Process Meets Resistance

Founders often struggle when a long-term, high-output employee rejects new operational efficiencies. In one r/smallbusiness thread, a business owner described a receptionist who was essential to the daily workflow but refused to implement new digital systems that would have streamlined patient intake. The owner’s attempt to provide stability did nothing to alleviate the employee's resistance to the new business partner's methods. This behavior suggests that the employee is not just protecting their job, but their status as the sole gatekeeper of the business's "old way" of doing things.

When processes change, the "high performer" who resists is often protecting a manual workflow that makes them irreplaceable. As noted in this r/smallbusiness discussion, simply utilizing technology to allow doctor assistants to issue refills and lab requests increased the income of the doctors, yet the staff resisted because it forced a change in their established habits.

"She likes the old ways and is very resistant to change. We suspect she may have paranoia about her losing her job." — u/Sad_Ad_12, r/smallbusiness thread

The 80% Mental Energy Tax of Managing High Performers

Managing high performers who are "checked out" creates a hidden tax on the founder's focus. A founder in one r/SaaS thread shared the realization that they were spending 80% of their mental energy managing a single developer who had lost their drive, while ignoring the consistent, quiet performers who were actually holding the fort. This "slow fade" is often more dangerous than overt toxicity because it drains the team's morale and the founder's bandwidth without providing a clear trigger for termination.

The founder stops looking for new opportunities and instead spends their day "managing the mood" of the unmotivated dev. When a developer starts taking longer than three months to ship features that previously took weeks, the founder often tries to "fix" the person rather than the output. As u/Due-Bet115 reported in this r/SaaS teardown, the mistake was letting the performance slip slide for far too long, which eventually created a culture where mediocrity was tolerated because the developer was a "good guy."

"It made me realize we were spending 80% of our mental energy worrying about the one who was slipping, and forgetting to acknowledge the one quietly holding the fort." — u/Due-Bet115, r/SaaS thread

Why Managing High Performers Requires Hard Thresholds

High performers often use their value as a shield against necessary changes. In the context of business acquisition, a buyer found that a stand with $400k/year in net sales was priced at $320k, despite relying entirely on the owners working 80 hours a week combined to net $100k/year. As discussed in one r/smallbusiness thread, the owners' inability to add wholesale or catering — despite claiming it would increase profits — highlights the danger of relying on "hypothetical upside" rather than the reality of the current operational bottleneck.

When a small business has been run by the same people for 20 years, the "high performance" is often just a result of sweat equity rather than efficient systems. The buyer in this case correctly identified that the owners were not actually high performers, but were instead "trapped" in their own business model. The lack of documented processes meant that any new owner would have to start from scratch, effectively paying $320k for a job rather than a business.

"If they could add 50% in profits, they would have. They've been doing this for 20 years and haven't done it.. it's either very difficult or not realistic." — u/MtNeverest, r/smallbusiness thread

Managing for High Performance Through Structured Reflection

Entrepreneurs often prioritize trivial tasks like landing page tweaks over the interpersonal conflicts that bleed their focus. One r/Entrepreneur thread notes that founders will spend 6 hours on minor design changes but avoid a 30-minute conversation to untangle a personnel bottleneck. The consensus among experienced founders is that high performance is not about avoiding conflict, but about focusing attention where it is most impactful for the business's longevity.

High performers in the startup space often have a high success rate in their own minds, but they fail to realize that the anxiety of managing others is a skill that must be learned, not white-knuckled. As u/rogue_psych points out in this r/Entrepreneur discussion, founders often white-knuckle through these issues until the next "win" makes the anxiety quiet down. However, the real work of scaling is not in the wins, but in the untangling of the "30-minute problems" that prevent the business from growing.

"Entrepreneurs will spend 6 hours tweaking a landing page but won’t spend 30 minutes untangling the thing that's quietly bleeding their focus." — u/rogue_psych, r/Entrepreneur thread

Managing High Performing Teams by Prioritizing Reliability

Many business owners are terrified to hire young, inexperienced talent, yet the threads suggest that reliability is a more valuable trait than raw technical skill. In one r/smallbusiness thread, the discussion centered on whether high schoolers could be trusted with small tasks. The consensus was that age is irrelevant; the real issue is the ability to show up on time, communicate when a mistake is made, and not disappear mid-project. A high performer who is unreliable is essentially a net-negative for the business.

When a business owner is managing high-risk environments, they need employees who follow the process. As u/Virekto noted in this r/smallbusiness thread, the biggest red flag is not a lack of knowledge, but a lack of accountability. A "high performer" who is technically gifted but requires constant hand-holding is a drain on the founder's time.

"Don't be lazy. Don't call out. Do the right thing, not the easy way. Keep your word. Trust will be there." — u/MentallyAut, r/smallbusiness thread

Audit Your High-Performer Dependencies

If your business relies on a single person who refuses to adopt new systems, your business is a dependency, not an asset. Use this audit to determine if you are being held hostage by a "high performer."

1. Map the bottleneck: List the top three business processes that only this person can perform. If they left tomorrow, would the business stop?
2. Define the threshold: If the employee refuses to adopt a new workflow that saves ≥ 20% of their time, document the refusal as a performance issue.
3. The "Quiet Search" step: If you answer "Yes" to the bottleneck question, begin a search for a replacement or a freelancer who can handle the specific tasks. Do not fire the current employee yet, but remove the fear of "what if they leave" by having a backup candidate ready.
4. The final conversation: Present the new workflow as a requirement, not an option. If they refuse, you have your answer.

Managing High Performing Teams: Source Methodology

This analysis draws on six r/SaaS and r/smallbusiness threads cited inline above. Threads were surfaced via Discury's cross-subreddit monitoring.

discury.io