<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Arnadi Mulyadi (Arry) on Medium]]></title>
        <description><![CDATA[Stories by Arnadi Mulyadi (Arry) on Medium]]></description>
        <link>https://medium.com/@arrnadi?source=rss-60df4a8cb0f2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*z1Z7KNPU-B91TYGn2VtA-Q.jpeg</url>
            <title>Stories by Arnadi Mulyadi (Arry) on Medium</title>
            <link>https://medium.com/@arrnadi?source=rss-60df4a8cb0f2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:23:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arrnadi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Incompetence: The Cancer of Meritocracy]]></title>
            <link>https://arrnadi.medium.com/incompetence-the-cancer-of-meritocracy-5539b8398a9f?source=rss-60df4a8cb0f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/5539b8398a9f</guid>
            <category><![CDATA[work]]></category>
            <category><![CDATA[toxic-workplaces]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[meritocracy]]></category>
            <dc:creator><![CDATA[Arnadi Mulyadi (Arry)]]></dc:creator>
            <pubDate>Mon, 20 Jul 2026 10:46:54 GMT</pubDate>
            <atom:updated>2026-07-20T10:46:54.396Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qdSsdVwCx3fzp_lAh4KzcQ.png" /></figure><blockquote>You know, I’ve been working in a professional environment for more than eleven years now. During that time, I’ve met all kinds of leaders. The friendly ones. The killer ones. Even the ones who simply didn’t care. Honestly, none of them really got under my skin.</blockquote><blockquote>Except one.</blockquote><blockquote>The incompetent one.</blockquote><p>This is a story from my close friend, Steve. I’ve known him for 10 years since we’re in the college. He’s now working in a sales department in a Multi National Company. He already have years of career experiences. But I never saw him this much frustrated before. He’s always been a calm, cold tempered, and one of the most patient person I’ve ever known.</p><p>Why am I bother to telling you his story (which I already obtained his promise to share this to all of you) and writing this long-ass article? Because I don’t think people realize how dangerous an incompetent leader can be, especially one who doesn’t even realize how incompetent he is. It doesn’t destroy a team overnight. It’s more like cancer. It spreads slowly, quietly, eating away at the meritocracy that once made the team successful until one day you look around and barely recognize the place anymore.</p><p>Before I tell you what happened to him, let me explain to you what I mean by incompetent. At least what me and Steve already agreed on.</p><h3>What Does Incompetent Mean?</h3><p>Imagine this. Let’s say I’m a husband with two kids. I work full-time while my wife stays home and takes care of the children. One day, she gets seriously sick and can’t look after them anymore, so I take a few days off work to take over.</p><p>Naturally, everything becomes a mess. The kids keep fighting, and I can’t calm them down. They miss their homework. They don’t eat on time. I arrive late to pick them up from school because I’m still trying to figure out how to wash, dry, and fold their clothes before leaving the house. Eventually, despite having a high fever, my wife has to get out of bed just to help me because I’m completely overwhelmed.</p><p>Now let me ask you something. Does that make me an incompetent father?</p><p>Well… it depends.</p><p>If I admit that I’m terrible at managing the household, listen carefully when my wife points out what I did wrong, accept her advice, and make an effort to improve, then the next time this happens I’ll be much better prepared. In that case, I wouldn’t call myself incompetent. I simply lacked experience, and I was willing to learn.</p><p>But imagine the opposite.</p><p>Instead of admitting my mistakes, I refuse to acknowledge that I did anything wrong. Worse, I blame my wife for getting sick in the first place. I accuse her of not fulfilling her responsibilities and complain that, because she’s ill, the so-called “provider of the family” has to do work that “shouldn’t be done by men.” (It’s a disgusting mindset, I know. But believe it or not, people like that still exist.).</p><p>See the difference? Competence isn’t about already knowing everything. It’s about being willing to grow. A competent person is someone who can:</p><ol><li>Acknowledge their own mistakes and weaknesses.</li><li>Stay as objective as possible.</li><li>Listen to feedback, especially from the people closest to them.</li><li>Constantly strive to become a better version of themselves.</li></ol><p>The moment someone refuses to do those things, that’s when we can start calling them <strong>incompetent</strong>.</p><h3>How The Cancer Began</h3><p>According to Steve, it hadn’t always been like that.</p><p>Back then, his team was led by someone much better. Her name is <strong>Juliet</strong>, and by every account, she was exactly the kind of leader people hoped to work for. Despite leading a department of more than a hundred people, she knew everyone by name. It didn’t matter whether someone was a senior manager or the most junior employee on the team — she made the effort to understand their concerns, listen to their ideas, and stand up for them whenever necessary.</p><p>Steve admitted that the job itself wasn’t always enjoyable. There were difficult targets, demanding clients, and stressful days like any other workplace. But Juliet made sure that no matter what challenges the team faced, everyone’s opinions, feedback, and concerns were heard. People genuinely felt that someone was looking out for them.</p><p>Then, as Steve jokingly put it:</p><blockquote>Everything changed when the Fire Nation attacked.</blockquote><p>While Juliet was deeply respected by her team, she wasn’t particularly popular with upper management. From their perspective, she was more of an obstacle than an asset. Whenever management introduced policies that benefited the company at the expense of the employees, Juliet often pushed back. Steve believed that management saw her as someone who constantly got in the way of their plans.</p><p>Eventually, they removed her from the position and replaced her with a manager from another department. He’s a much older man called <strong>Jacob</strong>.</p><p>Steve’s first impression of Jacob was neither positive nor negative.</p><p>“There wasn’t much to read from him,” he told me. “His face was always expressionless. You couldn’t tell whether he was happy, angry, disappointed, or excited. It was always the same.”</p><p>As time went on, Steve learned that Jacob was an introvert — the complete opposite of Juliet. He rarely interacted with his colleagues or subordinates unless absolutely necessary. He seldom joined the team for lunch, preferring to eat alone in an empty room. Even casual conversations or lighthearted jokes with the team were almost nonexistent.</p><p>At first, Steve wasn’t too concerned. He figured the team already had a solid culture and a well-established system. Surely one person couldn’t undo years of good leadership. Right? RIGHT?</p><p>Unfortunately, Stevee quickly realized how wrong he was.</p><p>The first warning sign appeared when Jacob began replacing several key people with individuals from his own circle. These weren’t just ordinary staff members. They were influential positions that shaped the direction of the team. What troubled Steve however, wasn’t merely the replacements themselves, but the stark difference in qualifications.</p><p>As he put it, “How do you justify replacing someone with ten years of experience and a master’s degree with someone who has only three years of experience and a bachelor’s degree from an university located in a random underdeveloped city?”</p><p>To Steve, there was only one explanation. Jacob wasn’t looking for the most capable people. He was looking for <strong>the most obedient ones</strong>. People who wouldn’t question his decisions. People who would simply do whatever pleased the boss. You know, in Indonesia we call that “Asal Bapak Senang” (ABS), essesentially doing whatever it takes to keep the boss happy, regardless of whether it’s actually the right thing to do.</p><p>That single decision was enough to change the team’s trajectory.</p><p>One incompetent employee rarely has the power to ruin an organization. But place several incompetent yet loyal people in positions of influence, and the damage spreads rapidly. A team that had once been known throughout the company for its high morale, strong collaboration, and outstanding performance slowly became one of the least desirable teams to work in.</p><h3><strong>Covering The Incompetence, Enhancing The Damage</strong></h3><p>Alright, based on Steve’s story, we know that he’s incompetent and refused to acknowledge it. But the main question to us will be like, how do we know he’s incompetent at the first place? How can we be sure this is not just about someone’s bad personality.</p><p>Alright I’m gonna tell you everything, there are several signs. But to sums up in one sentence: <strong>He spends his time to do anything other than his most important responsibility, to do his job.</strong></p><h4>Tong Kosong Nyaring Bunyinya</h4><p>Have you ever heard about this well-known proverb? Sure you do. It (literally) means “Empty Vessels Make The Most Sound”. That’s exactly what Jacob’s been doing all this time.</p><p>You see, genuinely competent people rarely needed to prove themselves by talking endlessly. They communicated efficiently, got straight to the point, and respected other people’s time. A capable leader, he argued, didn’t need to dominate every conversation with hours of unnecessary discussion.</p><p>To put things into perspective, Steve reminded me that they worked in a sales team.</p><p>“The most important part of our job is selling,” he said. “Everything else should support that objective.”</p><p>Yet every meeting under Jacob seemed to revolve around anything but selling.</p><p>Instead of discussing market opportunities or helping the team close more deals, Jacob would suddenly start a quiz for everyone on product knowledge or sales strategies. He would ask each salesperson to explain their current progress, why certain clients hadn’t been visited yet, or why particular tasks were still pending. In Steve’s eyes, every meeting eventually became another exercise in micromanagement.</p><p>Then Steve pointed out something I hadn’t considered before.</p><blockquote>“Notice what all those meetings have in common?” he asked.</blockquote><blockquote>“The questions?”, I replied.</blockquote><blockquote>“Exactly.”</blockquote><p>According to Steve, Jacob was always the one asking questions. Unfortunately, the conversation almost never flowed in the opposite direction. He would bombard the team with question after question, leaving little room for anyone else to speak.</p><p>At first, Steve assumed it was simply a matter of time. Maybe the meetings were already running long. Maybe there just wasn’t enough time left for employees to raise their own concerns.</p><p>But over time, he noticed a clear pattern. Whenever Steve tried to ask a follow-up question, even a brief one, Jacob would immediately dismiss it. Instead of providing an answer, he would respond with another question, effectively steering the conversation away from the original topic.</p><p>That wasn’t the only thing Steve found frustrating, unfortunately. Jacob also had a habit of interrupting discussions with stories from his own past, even when they had little to do with the subject being discussed. He would talk about how hard he worked when he was younger, how little he earned at the beginning of his career, or how he once spent half of his salary just commuting to work.</p><p>Steve didn’t necessarily dislike hearing personal stories from leaders. His issue was that these stories often replaced meaningful discussion instead of adding value to it.</p><p>After hearing Steve describe these meetings, one thing became increasingly clear to me. A leader who consistently avoids answering legitimate questions makes it difficult for the team to trust his judgment.</p><p>As Steve put it, “How are we supposed to believe he’ll help us grow or achieve our targets if he won’t even answer simple questions? And how can we feel confident about where the team is heading when our meetings are filled with irrelevant stories instead of real guidance?”</p><p>To Steve, Jacob’s constant storytelling wasn’t simply an annoying habit. It was a way of filling the silence where genuine leadership should have been.</p><h4>Micromanaging</h4><p>When Steve described Jacob’s leadership style, I couldn’t help but bring up an idea from Simon Sinek’s infamous book, <em>Start with Why</em>. Sinek argues that effective leaders begin with <strong>why</strong>, which is the purpose behind what they do. Those who lack that sense of purpose tends to fixate on what and how instead. They obsess over procedures, checklists, and strategies, yet struggle to answer the most fundamental question: <strong>Why are we doing this in the first place?</strong></p><p>Based on Steve’s story, I believe Jacob perfectly embodied that mindset.</p><p>Given Jacob’s years of experience in sales, Steve had expected someone capable of thinking strategically. Someone who could align the team’s work with the broader objectives of both the department and the company. Instead, what he encountered was the most micromanaging leader he had worked under throughout his entire career.</p><p>According to Steve, the changes began almost immediately after Jacob had replaced several key positions with people loyal to him.</p><p>When Juliet was still in charge, the team operated with a relatively simple but effective system. At the beginning of every quarter, they established goals that aligned with the company’s overall vision. Each salesperson was trusted to manage client relationships using approaches that suited their own strengths and territories. Every month, the team gathered to evaluate their progress, exchange ideas, discuss challenges, and share successful strategies. If someone struggled to meet their targets, the team worked together to identify what had gone wrong and adopted methods that had proven successful for their highest-performing colleagues.</p><p>It was really a culture of continuous learning one where results mattered more than rigid procedures.</p><p>Then, Jacob dismantled that culture.</p><p>Although quarterly targets still existed, Steve felt they gradually became secondary. Instead, Jacob introduced an elaborate monitoring system that tracked nearly every activity performed by the sales team. Every client visits, phone calls, or meetings had to be reported immediately. Employees were expected to upload photographs, selfies with clients, and even GPS locations as proof that the meetings had actually taken place.</p><p>That wasn’t all. Jacob insisted that everyone follow his preferred sales pitch almost word for word. Deviating from his script was strongly prohibited, regardless of an employee’s experience or track record.</p><p>Whenever sales numbers fell short, Jacob rarely discussed market conditions or broader business challenges. Instead, he scrutinized each client interaction, analyzing how every salesperson delivered their presentation. If someone’s approach differed from his prescribed method, he would publicly criticize or humiliate them during meetings.</p><p>Ironically, Steve noticed something that troubled him even more. As long as an employee followed Jacob’s prescribed process, poor sales results were often excused. Jacob would simply say,</p><blockquote>You’ve already followed the fundamentals I taught you. Whether you achieve your target isn’t entirely within your control.</blockquote><p>To Steve, that statement revealed everything. Juliet had measured success by <strong>outcomes</strong>. Jacob measured success by <strong>compliance</strong>.</p><p>Steve believed that this subtle shift slowly eliminated creativity and independent thinking from the team. Employees stopped experimenting with new ideas because there was little incentive to do so. Instead, they focused on following instructions as closely as possible, knowing that obedience mattered more than effectiveness.</p><p>The micromanagement didn’t stop with sales activities, however. Steve recalled how Jacob personally rearranged seating assignments throughout the office. Employees whom Jacob considered less productive, often those he believed spent too much time chatting with colleagues, were deliberately seated close to his desk so he could constantly observe their computer screens. Jacob frequently walked around the office floor, checking whether anyone was playing games, browsing social media, or using TikTok during working hours.</p><p>Steve story reminded me of my elementary school days. It felt less like a professional workplace and more like being back in school under the watchful eye of a strict teacher.</p><p>He also remembered how Jacob relocated many of the senior team members, including Steve himself, into a separate section divided by cubicle partitions. Steve believed the move had little to do with improving collaboration and everything to do with reinforcing the hierarchy Jacob wanted to establish.</p><p>That realization naturally led Steve to another conclusion about Jacob’s leadership.</p><h4>Classism, Arrogance, and a Lack of Empathy</h4><p>Whenever Steve compared Jacob to Juliet, the contrast couldn’t have been more striking.</p><p>Juliet knew everyone by name, from senior managers to interns, despite overseeing a department of more than one hundred people. She made an effort to build genuine relationships with her team. She frequently invited employees to dinners at restaurants or even to her own home, often paying for everyone herself. She organized activities outside the office, accompanied employees to difficult client meetings, and made herself approachable even outside working hours. She even followed every member of the team on Instagram, a small gesture that, to Steve, reflected her humility and willingness to connect with people regardless of their position.</p><p>Jacob, on the other hand, behaved very differently.</p><p>According to Steve, Jacob rarely interacted with anyone below the level of senior manager. Even simple greetings were often ignored. Steve remembered seeing interns greet Jacob in the hallway or restroom, only to receive no acknowledgment whatsoever. He even sanitized his hand with his hand sanitizer every time he had to shake hands with them.</p><p>The separation wasn’t merely social, it became physical. Jacob designated an exclusive area on the office floor for himself and the senior managers. Junior employees were discouraged from entering unless absolutely necessary.</p><p>Then Steve told me one incident that he said he won’t forget until he died, or even until his ashes scattered on the sea.</p><p>A junior associate needed Jacob’s feedback on an important document. She had already obtained her manager’s approval before approaching him.</p><p>Instead of listening, Jacob immediately reprimanded her.</p><p>Steve remembered his words almost verbatim.</p><blockquote>Why are you talking to me? You’re an associate. You have a manager. If I need something from your team, I’ll speak to your manager. There are hierarchies here. You’re being disrespectful. I don’t deal directly with junior employees. GET OUT.</blockquote><p>When I heard that story, I frozed a moment. It reflected more than simple rudeness. It demonstrated a deeply hierarchical mindset that viewed rank as more important than people. Jacob could have politely redirected the associate to her manager or simply explained the proper communication channel. Instead, he chose public humiliation.</p><p>Steve believed incidents like that weren’t isolated. They revealed how Jacob genuinely viewed the people beneath him. Another example came during a discussion about declining client visit numbers among the junior sales team. After investigating the issue, the team concluded that rising fuel prices had forced many junior employees to reduce the number of client visits they could afford. The company didn’t provide transportation allowances, meaning those employees paid travel expenses entirely out of their own pockets.</p><p>Steve expected Jacob to at least acknowledge the challenge and will try to figure out a better solution for everyone. Instead, Jacob dismissed it.</p><p>Jacob argued that public transportation was far more accessible than when he was younger. If employees couldn’t afford fuel, they should simply <strong>walk more and “be healthier.”</strong></p><p>Steve was already stunned by that response (well so did when he retold that story). Then Jacob continued saying more horrible things. He argued that increasing salaries or introducing transportation allowances would reduce the company’s return on investment, which is so high in Indonesia compared to other countries. He won’t push the company to reduce the company’s just to satisfy some employees.</p><p>You know what I think after I heard that story? Maximizing profitability mattered more for Jacob than addressing legitimate concerns raised by employees struggling with rising living costs.</p><p>Listening to Steve describe those moments, I understood why he often compared Juliet and Jacob as complete opposites. In his eyes, the team hadn’t simply exchanged one manager for another. It had gone from a leader who invested in people to one who viewed people primarily as resources to control. And to Steve, that represented the most troubling consequence of Jacob’s incompetence.</p><h3>When Meritocracy Falls, Favouritism Rises</h3><p>Steve often joked that Jacob reminded him of Emperor Palpatine from Star Wars. He would even quote the infamous line:</p><blockquote>“In order to ensure the security and continuing stability, the Republic will be reorganized into the first Galactic Empire! For a safe and secure society!”</blockquote><p>To Steve, Jacob had done something remarkably similar.</p><p>A system that had once rewarded competence and performance was gradually replaced by one built on loyalty and favouritism. All under the guise of creating a more “organized” and “effective” workplace.</p><p>What is the clearest sign that meritocracy had collapsed? Simple, the wrong people began receiving the rewards.</p><p>Promotions no longer reflected achievement or capability. Instead, they increasingly depended on whether Jacob viewed someone favorably. Even then, Steve insisted, earning Jacob’s approval was far more complicated than simply performing well.</p><p>Before explaining why, Steve always made one thing clear.</p><p>“In Jacob’s system,” he once told me, “your performance barely matters.”</p><p>He wasn’t saying that performance had no value whatsoever. Good numbers could still earn someone incentives or bonuses. But when it came to career progression, Steve believed performance had become only a small piece of the puzzle.</p><h4>Nothing Matters If You Are Not “Seen”</h4><p>According to Steve, the first requirement for advancing under Jacob wasn’t delivering outstanding results. It was becoming visible.</p><p>By “visible,” Steve didn’t mean arriving early or being physically present in the office every day. He believed there were only two reliable ways to attract Jacob’s attention:</p><ul><li>Working directly on projects that involved Jacob.</li><li>Creating a highly visible “breakthrough” that impressed him personally.</li></ul><p>Steve explained that the first option often had little to do with an employee’s actual responsibilities. The project could belong to another department or even be something Jacob had initiated himself. What mattered wasn’t whether it fit someone’s job description. It was whether the project created opportunities to work directly alongside Jacob.</p><p>For junior employees, even that wasn’t enough. Steve observed that they usually needed their reporting managers to introduce them and remain involved throughout the project because Jacob rarely interacted directly with employees at lower levels of the organizational hierarchy.</p><p>The second path involved what Steve called creating a “breakthrough.” He remembered one colleague who eventually became Jacob’s second-in-command as Vice Director of Sales. Interestingly, the promotion wasn’t the result of exceptional sales performance. Instead, the employee developed a simplified smartphone-based system for tracking client meetings, replacing an older process that relied primarily on desktop computers.</p><p>Jacob was impressed. Shortly afterward, the employee received the promotion.</p><p>From Steve’s POV, I can see why is this become an even larger problem. Employees spent enormous amounts of time trying to make themselves visible to Jacob instead of focusing on the work they had originally been hired to do.</p><p>I mean, I asked him, why even that burden of being visible fell on employees in the first place. A good leader should actively engage with the entire team, recognize people’s contributions regardless of rank, and understand their strengths without requiring them to compete for attention. Steve just simply replied, “I asked myself that all the time”.</p><p>It was not always like this, Steve said. Because how Juliet led his team before, was the complete opposite of that. But again, Juliet’s days are already over.</p><p>Even then, however, visibility offered no guarantees. Steve believed that gaining Jacob’s attention was merely the beginning of a much longer process. Whether someone eventually earned Jacob’s trust or his approval remained entirely unpredictable.</p><h4>Making Favouritism Look Legitimate</h4><p>Steve believed Jacob understood one important weakness of his favouritism. If promotions or dismissals appeared to be based purely on personal preference, they would be difficult to justify within the company. So instead of making arbitrary decisions, Jacob designed systems that gave those decisions an appearance of objectivity.</p><p>He gave me a bit more context on his team. At the time, only ten of the roughly fifty remaining team members were permanent employees. The rest worked under renewable contracts. That arrangement had existed long before Jacob arrived, or even before Steve himself joined the company.</p><p>Under Juliet’s leadership, contract employees generally progressed as expected. Strong performers were often converted into permanent employees, while those struggling received additional coaching, mentoring, and performance improvement programs. Juliet believed in rewarding excellence without abandoning employees who needed more support. As a result, contract non-renewals due solely to poor performance were relatively uncommon.</p><p>However, Steve believed that changed dramatically after Jacob took over.</p><p>As team performance declined, the number of underperforming employees increased. Yet instead of strengthening coaching programs, Jacob discontinued many of them, reportedly saying they were “not worth his time.”</p><p>Over the following years, Steve watched the department shrink from more than one hundred employees to roughly fifty.</p><p>Then came what Steve considered Jacob’s most effective tool. A new performance assessment system. For contract employees, the evaluation consisted of three components, each has its own weights:</p><ul><li><strong>KPI / Performance (20%)</strong></li><li><strong>Productivity (30%)</strong></li><li><strong>Values (50%)</strong></li></ul><p>Measuring performance is of course justifiable and Steve won’t object it. That portion reflected actual business results.</p><p>Then the productivity category, which focused heavily on compliance. Employees were evaluated based on how closely they followed Jacob’s sales procedures, how many client visits they conducted, how many products they pitched, and whether they adhered to his preferred methods.</p><p>Steve found it telling that productivity carried more weight than actual business outcomes. It perfectly reflected Jacob’s philosophy of valuing process over results.</p><p>But the category that concerned Steve the most was the final one. Values.</p><p>Every company has its own set of corporate values, Steve acknowledged.</p><p>The problem, as he saw it, was that measuring someone’s alignment with those values was inherently subjective. And because <strong>Values accounted for half of the total evaluation</strong>, Steve believed it became an ideal mechanism for rewarding favored employees while penalizing those Jacob disliked.</p><p>Even exceptional performers weren’t immune. If someone achieved excellent sales results and maintained strong productivity scores, Steve believed Jacob could simply assign a lower rating in the Values category and significantly reduce that employee’s overall evaluation.</p><p>To Steve, the system gave favouritism a veneer of legitimacy.</p><p>On paper, every decision appeared justified. In reality, even I can tell that it gave Jacob enormous discretion over who stayed, who advanced, and who quietly disappeared from the team.</p><p>Many employees whom Steve considered outspoken or critical of Jacob eventually got kicked out of the department. Surely it wasn’t a coincidence.</p><h4>Challenges After Challenges</h4><p>Even then, Steve told me that Jacob had another strategy.</p><p>Occasionally, an employee’s performance and productivity scores were simply too strong to offset with lower subjective ratings. In those cases, Steve said Jacob rarely admitted defeat. Instead, he introduced delays.</p><p>Employees would first receive praise for their strong evaluations. Then came the explanation.</p><p>Because of the so-called “company restrictions,” permanent positions supposedly weren’t available. Instead of receiving the standard one-year contract extension or permanent employment, they were offered only a short extension. Six months if Jacob think’s they’re a jerk, or three months if he thinks they’re an even more jerk.</p><p>Steve remained skeptical of that explanation because, according to him, other departments continued converting contract employees into permanent staff without similar difficulties.</p><p>After those short months, another hurdle appeared. Jacob introduced what he called <strong>Career Development Challenges</strong>.</p><p>According to Steve, these challenges often had little connection to the employee’s previous performance evaluation. Success supposedly led to permanent employment. Failure meant the contract would not be renewed.</p><p>But even passing didn’t necessarily guarantee anything.</p><p>Employees who achieved merely “good” rather than “excellent” results often received yet another short three to six months extension, followed by another challenge. And then another.</p><p>The pattern was unmistakable. Each new requirement created another opportunity to delay promotions, extend uncertainty, or justify terminating someone Jacob no longer wanted on the team. By constantly introducing new criteria, Steve believed Jacob could maintain the appearance of fairness while preserving complete discretion over who advanced and who didn’t.</p><p>Knowing Jacob, Steve often joked that if these methods ever stopped working, he wouldn’t be surprised if Jacob simply invented a hundred new ones.</p><h3>Is Meritocracy Beyond Saving?</h3><p>As Steve reached the end of his story, I will return to the analogy that had inspired the title of the article. Everything he had described reminded me of cancer.</p><p>Not because the damage happened all at once, but because it spread slowly and quietly. Like cancer gradually destroys healthy cells and organs, Jacob’s leadership had slowly eroded the culture that once made the team successful. By the time most people realized how serious the situation had become, much of the damage had already been done.</p><p>I’m no doctor, but let me explain this analogy the way I understood it.</p><p>When someone is diagnosed with cancer, one of the first things doctors determine is its stage. The earlier the disease is detected, the more treatment options are usually available. In the early stages, surgery alone may be enough to remove the affected tissue. As the disease progresses, more aggressive treatments such as chemotherapy may become necessary. Those treatments can save a person’s life, but they often come with significant costs and side effects because they affect healthy cells as well.</p><p>By the time cancer reaches its most advanced stages, the options become far more limited. Treatment may still be possible, but it often requires far more drastic measures than would have been necessary earlier.</p><p>Steve story on his work weren’t all that different.</p><p>If the damage to a team was still in its early stages, perhaps meaningful reform was still possible. It would require people within the organization to challenge the existing culture, rebuild broken systems, and accept that meaningful change would likely come with discomfort and resistance.</p><p>But Steve himself also wondered whether his own team had already passed that point.</p><p>In his view, Jacob had spent years surrounding himself with loyal supporters while gradually removing or sidelining people who challenged his decisions. Many of those who had once defended the team’s culture had already left, either by choice or through circumstances that were far from coincidental.</p><p>If that was true, organizing meaningful reform would be extraordinarily difficult. Speaking up carried risks. Building opposition seemed almost impossible and changing the culture from within felt increasingly unrealistic.</p><p>That brought Steve back to the question he had been asking himself (and to me) throughout the entire story.</p><p>Was the team’s meritocracy already beyond saving? Had Jacob’s leadership permanently replaced a culture of competence with one built on loyalty and favoritism? Steve didn’t claim to know the answer. When he finished telling me his story, he simply shrugged and said that maybe there was still hope. Or maybe there wasn’t. Only time would tell whether the damage could still be reversed or whether the team would continue living with the consequences of decisions made years earlier.</p><p>How about my take on this? Sadly, I believe that we can find stories like this everywhere. Finding jobs nowadays are already hard. Finding a good job with a good leader is even harder. I’m lucky enough to have a great leader in my office. But my dear friend Steve and most of the others aren’t so lucky.</p><p>I can only wish him good luck, and may he find the solutions to his problem. But whether to fight the cancer, or to abandon the fight and succumbing to it, it’s purely his choice, whether he can control it or not. One thing for sure tho, if he chose to give up the fight, I’ll do anything I can help him to get a better opportunity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5539b8398a9f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>