The Fallacy of Being Irreplaceable

Imagine if one person held the only keys to a vital system, and then went on sudden sick leave. How long would it take before things ground to a halt?

There is a persistent fallacy in some workplaces, the belief that if you keep your knowledge to yourself, you become indispensable. That by becoming the only person who knows how to do a task, run a process, or fix a problem, you’re creating job security. In reality, this mindset introduces fragility, not strength. It’s a short-term tactic that fails the long game of career growth, leadership, and organisational resilience.

In a previous article, Winning the lottery or failing the bus test (8th June 2015), I explored a simple resilience thought experiment: What happens if a key person wins the lottery or gets hit by a bus? Whether someone leaves for joyful reasons or tragic ones, the point remains. Businesses must be prepared to continue functioning without any one individual.

That article focused on assessing the risk, whereas this one focuses more on one of its root causes; knowledge hoarding.

The Hidden Cost of Knowledge Hoarding

The idea that hoarding knowledge makes you valuable is deeply flawed. It’s understandable that people want to feel needed, but locking knowledge inside our heads doesn’t protect our position. In practice, it limits our growth, introduces single points of failure or single points of success into the business, situations where one person’s absence could derail critical operations or progress. These points of fragility are the antithesis of good governance, risk management, and succession planning.

I have experienced many situations over the years where we have discussed specific topics and issues, identified information that we needed to proceed, assigned tasks in the meeting, and scheduled a follow-up meeting, only to discover a week later that someone already had all the information but didn’t share it, allowing us to waste valuable time.

Understanding the Motives

People hoard knowledge for many different reasons. Sometimes fear-based, other times it’s due to past experiences or organisational dynamics. Here are some of the most common causes:

  • Fear of being replaced
  • Belief that knowledge equals power
  • Job insecurity
  • Ego or status-driven behaviour
  • Lack of trust in colleagues or leadership
  • Past experiences of being overlooked or unrewarded after sharing
  • Competitive or toxic workplace culture
  • Unclear job boundaries or expectations
  • Lack of recognition for knowledge-sharing efforts
  • High workloads and time pressure
  • Absence of easy-to-use documentation tools or systems

These are based on a fallacy, that being the only one who knows something creates job security. In truth, this behaviour can backfire spectacularly. The real value comes from empowerment, not from exclusivity.

Sharing knowledge also depends on trust. In organisations where people feel safe to ask questions, admit what they don’t know, and share openly, knowledge flows more naturally. This psychological safety underpins a learning culture and strengthens resilience.

I once had a conversation with someone who told me that, because I’d gone to university and earned a degree at great personal expense, my knowledge was my property, something to sell, not share. I’ve never fully agreed with this mindset. I’ve always felt that knowledge becomes more valuable when it helps others. It is one of the reasons I continue to write and publish articles here on Integritum; not because I have all the answers, but because collective thinking helps us all improve.

In resilient teams:

  • Knowledge flows through cross training
  • Processes are documented, shared, and improved collaboratively.
  • Team members cover each other’s workload during sickness and annual leave
  • If someone receives a promotion, resigns, or retires, they can do so without the business suffering.

The Path to Growth

If someone else can do what you do, it doesn’t make you replaceable, it makes you promotable. Consequently, the objective is not to cling to tasks, but to enable others so we can move on to higher-value work. It is not about guarding secrets, but creating capacity in others.

For succession planning, every role should have a shadow, a backup, or at least a process manual. This also supports onboarding new staff, covering holidays or sickness, or responding to emergencies. Shared knowledge builds resilience.

When we share knowledge, the benefits are wide-reaching. It builds trust, supports professional development, and improves operational continuity. For example:

  • We build trust with colleagues
  • We support a culture of learning
  • We position ourselves as leaders
  • We reduce organisational risk
  • We create the conditions for personal growth and advancement

The idea that ‘if no one else knows how we do this, they’ll always need us’ may feel like control, but in reality it only serves to trap us where we are. True job security doesn’t come from being irreplaceable, it comes from being so effective, helpful, and growth-oriented that people want us to succeed, and want to give us responsibility, not less. The more people that can do what we do, the more space we will have to do something greater.

Standards such as ISO 27001, ISO 9001, and ISO 42001 define management system frameworks that reinforce the importance of documented processes and knowledge continuity as core aspects of resilience and risk management.

As AI continues to automate routine work, the value of human roles will shift even more toward strategic thinking, mentorship, and collaboration, all of which depend on shared knowledge.

Reflections on Client Confidentiality

In 2017 and 2018, I wrote a four-part series titled “How Much Info Is Too Much?” to challenge an uncomfortable norm: professionals, especially in IT and information security, are routinely expected to share confidential client details as proof of credibility. Whether in procurement discussions or during recruitment, the pressure to disclose private information to secure the next opportunity became standard practice.

Seven years later, this article recaps the original series, ties in a follow-up article on recruitment ethics, and considers whether we have changed our professional culture or whether client confidentiality is still treated as expendable when careers or contracts are on the line.

The Ethics of Disclosure

The series began with a direct comparison that exposed the double standards applied to confidentiality in IT and other professions.

“Imagine asking a solicitor about their past divorces to prove they can handle yours. It would never happen.”

Part 1 (4th December 2017) challenged the assumption that sharing previous client information demonstrates trustworthiness. It used everyday examples like taxi drivers, alarm installers, and lawyers to make a key point. In nearly every other industry, discussing former clients would be considered unprofessional, if not a breach of duty. Why should IT and information security be any different?

Even now, procurement teams and hiring managers sometimes equate name-dropping past clients with credibility. Sharing details about past clients to win future work may signal cooperation, but it also demonstrates a lack of discretion and professionalism.

During my years running a small business, I often found myself pressured to list previous clients. This expectation not only contradicted the NDAs I had signed, but also reflected a fundamental misunderstanding of professional discretion. This isn’t to say that referencing clients is always wrong, but it must be:

  • Done with clear consent
  • Aligned with contractual terms
  • Handled with the client’s reputation and privacy in mind.

Anything less risks crossing the line from credibility to compromise. In my case, I relied on client-provided testimonials, which offered a transparent and ethical way to demonstrate value without breaching confidentiality.

  • An obvious red flag during procurement is the request for client names during early-stage discussions. Referencing industries served, or challenges solved is usually sufficient; naming clients is rarely necessary.
  • While IT lacks formal licensing, many adjacent fields, including law, healthcare, and finance, would consider such disclosure a breach of conduct. Expectations in tech are starting to catch up.
  • Professional trust is earned through process, integrity, and insight, not by exposing others’ confidential work.
  • Clients who ask you to sign a Non-Disclosure Agreement (NDA) while requesting information about your past clients fail to see the contradiction.
  • Professionalism includes protecting client reputations long after the contract ends, reinforcing trust and encouraging future referrals.

Spotting Red Flags in Early Conversations

The second article shifted from theory to practice, warning about misleading early-stage discussions.

“A 15-minute call that’s all about your past clients and nothing about current needs? This is not a sales lead; it is a red flag.”

Part 2 (12th December 2017) moved from principle to practice, focusing on identifying conversations that veer into information mining rather than genuine engagement. If a potential client spends more time asking about previous engagements than outlining their own needs, it’s likely not a real opportunity.

With AI-powered phishing, voice impersonation, deepfakes, spoofed job interviews, fake procurement opportunities, and corporate espionage now part of the landscape, the original advice has only grown in relevance.

  • If the caller avoids basic discovery questions like “What are your current pain points?” or “What do you need?”, it’s likely not a real opportunity.
  • Attackers use believable personas (recruiters, clients, journalists) to harvest sensitive business information.
  • Ethical conversations involve reciprocal openness, so we shouldn’t share anything confidential if the other party is unwilling to share anything about their needs.
  • Professionals don’t always know how to identify social engineering.
  • Having a clear discovery script or process can help deflect and detect bad actors while remaining professional.

When Disclosure Becomes Expected

Part three took a more candid tone, acknowledging that indiscretion is sometimes rewarded, even incentivised, in the workplace.

“Those who break confidentiality are often rewarded with a contract opportunity, not because they are professional, but because they cooperate in breaching confidentiality.”

Part 3 (18th December 2017) took a sharper tone, acknowledging the grim reality that disclosing confidential information helps people win work. This behaviour has become normalised in sectors like IT and information security, where no professional licence to revoke and no external body enforcing ethical standards.

We still see this today, especially in competitive bids where clients and employers reward name-dropping and logo slides. ISO standards, frameworks, and organisational codes of conduct are slowly shifting this culture by embedding expectations of privacy, discretion, and ethical information handling.

  • Selection teams often reward evidence of previous client activities, and from personal experience, I know how not being short-listed for an opportunity by refusing to disclose confidential information feels demoralising. This perpetuates indiscretion as a competitive advantage.
  • I’ve seen contracts where the NDA was so vague that confidentiality was open to interpretation.
  • It feels like people and businesses are gradually reframing discretion as a strength rather than treating it as an obstruction. I’ve lost count of the opportunities I missed because I chose to uphold confidentiality. Today, especially in regulated sectors, disclosing client details without authorisation now carries legal risk as well as reputational damage.

A Professional Alternative

To counter the trend of oversharing, the fourth article offered a proactive solution: shifting the focus to structured, client-first engagement.

“Credibility should come from solving real problems, not showcasing someone else’s private history.”

Part 4 (4th January 2018), and the final article in this series, offered a way forward: a professional five-step process for engaging with clients. It helps avoid off-topic digressions about past work and puts the focus where it belongs, on solving the client’s current problems through a structured, ethical dialogue.

As procurement and supplier due diligence processes become more rigorous, driven by regulatory scrutiny, AI governance, and Environmental, Social, and Governance (ESG), structured professional processes are no longer a luxury. They’re essential for resilience, trust, and legal protection.

  • A professional engagement process builds more trust than any client list ever could.
  • Clients need insights into their problems, not a retrospective view on someone else’s problems.
  • When done well, structured onboarding protects both sides and guards against phishing and reputational damage to  both parties. Clients are increasingly judged by what they ask and how they conduct vendor selection.
  • I found that having repeatable processes helps maintain credibility through moments of pressure, ambiguity, or inconsistency. I don’t recall who, but someone once told me that “How people behave some of the time reflects how people behave all of the time”. I heard a similar quote recently “How you do anything is how you do everything”. This applies to confidentiality, as if I am will to tell a potential client what I did for previous clients, it is reasonable for them to assume I would do the same in the future with their confidential information.

Recruitment: A Parallel Problem

The follow-up article expanded the issue into recruitment, highlighting the ethical risks of sharing confidential information when changing jobs.

“If you’re willing to use your current employer’s clients now to get a new job, you’ll likely do the same to your next employer.”

In this follow-up article, Avoid Revealing Employer’s Clients (12th April 2018), I explored how the same confidentiality breaches play out during recruitment. Candidates sometimes list their employer’s clients on public profiles and CVs or refer to them in interviews, thinking it shows breadth of experience. However, the ethical problem is the same: those clients aren’t theirs to share.

Today, these disclosures can end careers before they start. Many firms now treat unauthorised disclosure of client identities as a breach of NDA, contract, or even data protection law, and rightly so. Confidentiality applies just as much when leaving a company as when engaging with a new one.

  • Listing employer clients without authorisation can violate contracts and raise character concerns before the interview stage.
  • Employers increasingly filter out candidates who appear to treat sensitive data as a personal asset.
  • I recall refusing to give client names because of confidentiality, then declaring that I had passed their confidentiality test, and that we can move on to discussing their requirements. They refused to do that. I saw this as a big red flag.
  • Some roles now include applicant-level risk profiling where client name-dropping is seen as a security weakness.
  • NDAs, employment contracts, and professional ethics don’t expire when you change jobs.
  • The best candidates increasingly demonstrate judgement, not just experience.
  • Organisations with strong governance cultures actively avoid hiring people who treat discretion as optional.
  • Some recruitment agents still encourage “name-dropping” for profile strength, but this can backfire for both candidates and the agency.

Additional Thoughts

Whether in recruitment or procurement, the heart of this matter remains unchanged. Professionalism in this context is about discretion, not disclosure. We can’t gain trust and establish credibility by revealing what we did for others; we can only demonstrate what we can do for future clients or employers.

That said, one fact remains the same. Suppose people and businesses are forced to choose between disclosing client names (along with what was done and when) or risking the conversation about future work ending abruptly. In that case, they often choose the opportunity first.

Unfortunately, many professional cultures still reward indiscretion while overlooking integrity, especially when disclosure offers a short-term advantage. This isn’t just a question of professionalism; it’s a systemic problem.

It reminds me of the UK smoking ban in pubs. Many landlords wanted to implement a smoke-free policy years before it became law, not just for the health benefits but also to create a better environment for their customers and staff. They couldn’t because if one pub acted alone, the smokers would go next door, taking away a significant portion of their revenue. There were a few exceptions, but it wasn’t until the ban became a legal standard that everyone could act without fear of competitive loss.

Confidentiality suffers from a similar imbalance. Clients, employers, and recruiters are legally entitled to ask questions. Employees, consultants, and small business owners often feel compelled to respond, as not answering might mean losing the opportunity.

Change will remain slow until our professional culture matures to reward discretion and due process rather than indiscretion and shortcut credibility. It will remain impossible to lead alone, and the cycle will continue.

Understanding the New Control Structure in ISO 27002:2022

Here are the changes to ISO27001 and ISO27002:

  • ISO 27002:2013 contains 114 controls spread across 14 domains. The 2022 version includes 93 controls spread across four control domains. The new version has all the existing controls, but many merged to reduce the quantity.
  • The following four control domains replace the 14 in ISO 27002:2013:
    • Organisational (37)
    • People (8)
    • Physical (14)
    • Technology (34)
  • ISO 27002:2022 includes 11 new controls:
    • Threat Intelligence
    • Information Security for Cloud Services
    • ICT readiness for business continuity
    • Physical security monitoring
    • Configuration Management
    • Information Deletion
    • Data Masking
    • Data Leakage Prevention
    • Monitoring Activities
    • Web Filtering
    • Secure Coding
  • Due to the control changes in ISO 27002 and the controls listed in Annexe A within ISO 27001, this section will need updating to fully align ISO 27001 with ISO 27002. There may be additional changes to ISO 27001, so it will require a careful review when formulating a transition plan.

These changes simplify the control set and remove significant overlaps between controls across multiple domains.

Post-Brexit VAT Due Diligence

As a result of Brexit and the expiry of the transition period, the European Commission Taxation and Customs VAT Information Exchange System (VIES) system (http://ec.europa.eu/taxation_customs/vies/) is no longer available to GB registered businesses.

The new system for UK-registered businesses is here – https://www.tax.service.gov.uk/check-vat-number/enter-vat-details

Although many businesses still ask for a copy of the VAT registration certificate as part of their supplier due diligence process, it is essential to remember that the certificate only shows that a VAT registration existed at a single point in time. Please consider the following alternatives:

  • Verify the VAT registration online as part of your invoice processing
  • Verify the VAT registration at periodic intervals throughout the relationship with the supplier
  • Use the online process while onboarding your supplier

The new HMRC service allows UK VAT-registered businesses to prove they have performed checks. However, this is not guaranteed to absolve companies of financial liability for any VAT paid and subsequently claimed, strengthening the need for increased vigilance. Businesses knowingly or recklessly participating in fraudulent VAT transactions can become jointly liable for the unpaid VAT.

You can report suspected VAT fraud here – https://www.gov.uk/report-vat-fraud