Counting The Cost Of One Person Holding All The Knowledge

There is one person on your team who knows which bank charges what, which card rule changed last quarter, and why a particular fee got waived. Everyone jokes about what happens if they get hit by a bus. Nobody has ever worked out what it would actually cost.

You can count it. Take the tasks only that person can do, estimate how many days each would take somebody else starting from nothing, multiply by what a day of your team's time costs you, and add the days of delay to the work that waits. The number is usually larger than people expect, and it tells you which piece of knowledge to write down first.

A small team as the worked example

Picture a five person finance or operations team in the UAE. Part of their job is keeping track of card and bank rules: which card earns what, what the annual fees are, which fee waivers exist, what changed when an issuer updated its terms.

Those rules move. They vary by issuer, by card tier and sometimes by how you got the card. Nothing here is a universal fact, which is exactly why the knowledge is expensive to hold and expensive to lose. One person ends up as the memory of it, because they are the one who read the terms.

If that person leaves, the team does not lose a document. It loses the ability to tell whether the current arrangement is still the right one, which is why a handover note built around open decisions is worth more than a folder of files.

The three columns you need

Make a table with one row per task that only one person can do. Three columns.

• Rebuild days. If that person vanished today, how many working days would somebody competent need to get to the same answer, including reading terms, calling banks and getting it wrong once. Be honest. This is usually five to fifteen times longer than people guess.
• Waiting days. How long the rest of the work sits still while that happens. A renewal that cannot be decided. A report that goes out without a recommendation.
• Risk of a wrong call. Not a number. A sentence about what a bad decision here costs. Paying an annual fee for a card that no longer fits how the team spends is the small version. Missing a change in terms is the larger one.

Then multiply the day counts by whatever a day of your team's time genuinely costs you. Use your own figures. Anyone quoting an industry average for this is guessing.

Ranking what to share first

Once you have the table, the order becomes obvious, and it is usually not what people assume.

Share first the knowledge with high rebuild days and low glamour. The boring stuff that took a long time to learn is the expensive stuff. Complicated work that is well documented elsewhere can wait. Rotating ownership does the same job from the other end, by making a second person learn it in public.

Second, share anything with a date attached. A renewal, a fee cycle, an annual review. These are the items where the waiting days column bites hardest, because the calendar does not care that you are still rebuilding.

Third, share the judgement, not the data. Which card suits which spending pattern is judgement. The list of cards is data, and data can be looked up. The same split decides what to transfer when you are handing a finished project to a client's own team.

Where a tool takes the load off a person

Some of this knowledge does not need to be in anyone's head at all.

Wealthwise is built for the UAE and works in dirhams. It reads a card statement on the person's own device, uploading nothing, and ranks 19 UAE cards from 8 banks against what that person actually spends on. It shows the annual cost of using the wrong card. It is advisory only: it never moves money and never places trades. It is launching in early 2026.

What that changes for a team is which part of the knowledge has to be a human's memory. Comparing cards against real spending becomes something you can run rather than something one person recalls. What stays human is the decision, the relationship with the bank, and the local context. Check anything specific with your own issuer, because terms differ and they change.

Do the count this quarter

Block ninety minutes. List the tasks with a single owner, fill in the three columns, and multiply by your own daily cost.

Then pick exactly one row and fix it. Not all of them. One. The rest will still be there next quarter, and a single row properly written down beats a full plan that never starts.