Skip to content
Wealth Architecture

Information hygiene as a management discipline

My professional insights · Lyudmil Karaulanov · 6 min read

Published: 1 August 2026 · Version 1.0

Sharing uncomfortable information sometimes means entrusting something personal too. An employee wants to raise a warning about a problem, but does not know how much detail is necessary, who will read it or whether the conversation will reach people who have no reason to be involved.

A well-organised business offers a better choice than silence or complete disclosure. This requires clear rules: what is needed, by whom, when and with what protection. This is the sense in which I use “information hygiene”. It describes care both for the quality of the decision and for the person bringing the information.

What do we know, and what are we assuming?

A simple example. Three tasks are overdue. That may be an established fact. The explanation that the team is demotivated is still an assumption. There may be other causes that we have not checked.

This distinction is worth preserving throughout the conversation. A fact is verified, an opinion provides a personal assessment, an assumption guides enquiry, and a rumour is an unconfirmed claim with an unclear or indirect source. Each may matter, but they do not carry equal weight.

A rumour may justify careful investigation. On its own, it is not sufficient grounds for punishment. Repetition by many people does not turn it into an independently confirmed fact either. The important question is how many separate observations underpin the shared confidence.

Six questions that establish a process

Before information enters an important decision, I believe it helps to be clear about what we know, how we know it, who needs to receive it, when, in what form and what must remain protected.

The source matters for credibility and the ability to ask a further question. This does not mean that their identity must be available to everyone. The recipient depends on the subject, and the form may be a conversation, a written report or an established procedure.

Timing is also part of quality. Information received after a customer has been lost may provide a lesson, but no longer permits the same intervention. People should know when not to wait for the next regular report.

What exactly are we promising to protect?

Anonymity, pseudonymisation and confidentiality mean different things. With anonymisation, a person cannot be identified by means reasonably likely to be used. With pseudonymisation, the name is replaced, but the link can be restored. With confidentiality, the identity is known and access is restricted.

This distinction also has legal significance. Information is not anonymous merely because the name has been removed. Sometimes the job title, department and event described are enough to identify the person.

The most sensible approach, to me, is the least revealing form that still permits verification and a decision, combined with an honest explanation of the limits of the protection promised.

Confidentiality that does not exclude responsibility

There are legitimate reasons for a matter to remain within a small circle. But it helps to be clear about which interest is being protected, from whom, for how long and who still has the right to investigate.

Otherwise, sensitivity can become a convenient explanation for why no one takes action. Controlled access allows us to protect the person without leaving a material risk without someone responsible for addressing it.

How will we understand why we decided this way?

After an important decision, it is useful to retain the facts, unconfirmed circumstances, risks discussed, the person responsible and the point for a fresh review. This does not require a bulky file for every minor task.

The aim is to be able to reconstruct the judgement later without rewriting it in light of the outcome. A reasonable decision can end badly, while chance may temporarily favour a poorly prepared one. If we look only at the outcome, we risk learning the wrong lesson.

How much of someone's private life do we need?

A manager may need to know that a temporary difficulty is affecting work. That does not justify asking for every family or medical detail. A reasonable boundary is what is necessary for the specific decision, with clarity about who receives the information and how long it is retained.

Care for someone loses its meaning if they experience it as constant scrutiny. Trust also needs respected boundaries.

Where is the point of instability?

It appears when we have no reliable way to distinguish, verify and protect information. We can then collect too much while simultaneously failing to learn what we need in time.

For me, good organisation is shown by whether an important issue reaches a decision while exposing people to as little unnecessary disclosure as possible. This is a harder task than saying “tell us everything”, but far more useful for the relationships we want to preserve.

Sources and notes
  1. Availability Cascades and Risk Regulation
  2. Big Other: Surveillance Capitalism and the Prospects of an Information Civilization
Suggested citation

Lyudmil Karaulanov, “Information hygiene as a management discipline”, Wealth Architecture, version 1.0, 2026

This material is of a general analytical nature and does not constitute individual legal, tax, financial or investment advice.

Colophon
Published
1 August 2026
Version
1.0

Wealth Architecture · Publisher: Nautilex EOOD

Does this concern your business?

If this question also stands before you, you can request a conversation about your specific situation.

Discuss your situation →How we would work togetherTo all analyses