Brilliance Mining™

You cannot tell your team everything you know. That is fixable.

Neither can your best people. Brilliance Mining is a three-step method for surfacing what you and they do instinctively, and turning it into something your team can learn, use, and improve.

You do not write anything. You talk, and you check what comes back.

The two layers

Two kinds of knowledge rarely get documented

What is instinct, when it comes to expertise? It is what you have after you have done something a lot of times. It leaves you with a hidden set of rules you follow and patterns you recognize, and you do both without consciously thinking about it. That is why it is so hard to train someone else to work at the standard you work at. Brilliance Mining changes that. It unearths the expertise you cannot see in yourself.

This is the part almost nobody names clearly, and it explains why companies with libraries full of procedures still end up with bottlenecks at the same few overburdened people.

Layer one: the steps nobody notices anymore

When a task has been performed thousands of times, the separate actions fuse into one fluent motion. Describe what you do and your account will be honest and still leave things out, not because you are holding back, but because those actions stopped registering as steps.

Cognitive researchers call it the expert blind spot. Once someone masters a domain, they lose reliable access to their own reasoning, because the process has become automatic. A beginner still works deliberately and can describe each move. The expert’s version has compressed into something faster and largely invisible to the person running it.

A confession. I had been doing this work for most of my career before I realized it was something special that should have a name. Someone else had to point it out to me: what I do is pull wisdom out of people’s heads and lay it in front of them, then help them do more with it. Until then it was just how I thought and worked. Once we gave the process a name, I could see it really had three steps. That is how Brilliance Mining was born.

The encouraging part is that what looks like magic is still made of steps. They happen in the real world, so they can be watched, described, and made teachable by someone who knows how to look. We teach people to do that.

Layer two: the judgment that was never a step

The harder layer is not a hidden step at all. It is judgment, and no recording reaches it, because there is nothing to record. Point a camera at someone exercising judgment and you capture a pause.

Here is what that costs. A glazing company I worked with hired an estimator with fifteen years in the industry. He won three projects quickly, and all three lost roughly half a million dollars, because he had underpriced every one. That was why he was winning them.

His experience was real. It was experience with simpler work. A straight glass rail can be priced by the foot. A glass rail winding up a staircase cannot, because the geometry changes what the work is, and linear feet stops being a useful unit. He priced the second kind as though it were the first, and had no way of knowing he was doing it. The senior estimators knew the difference. Nobody had ever written it down.

Once you are on the contract, you are stuck with it. The error was locked in before anyone picked up a tool.

That is the lowest of four levels. It gets harder as you go up.

Four ascending blocks showing the judgment a written procedure cannot capture: in-process judgment, the unusual event, cross-process orchestration, and cross-domain integration.
  • 1. In-process judgment. Judgment calls inside a process or procedure. Example. In the quality control training for a bathtub refinishing company, one question drove everything: how does the QC person know the quality is there? What can the technician fix on the spot? What means coming back and redoing the whole job? An experienced technician decides fast. Ask how, and the first answer is “you just know.” Sit with him through enough real jobs and the hidden set of rules he operates on becomes visible.
  • 2. The unusual event. What to do when the situation does not match the procedure, which is the moment the procedure stops helping. Example. A microelectronics packaging client commits to delivering their die on a set date and wants a fast turnaround. Then their own fabrication slips. Now the packaging production line sits empty. What work can you pull forward to keep your people productive? Do you charge for the disruption, and if so, how much? There is no single right answer, and that is the point. An experienced manager has a set of moves and knows what each one costs. A newer one freezes, unless you have done something about it ahead of time. You cannot catalogue every unusual event, and nobody should try. Capture a few real ones with the reasoning behind each call, and the next manager has a way to think the next one through.
  • 3. Cross-process orchestration. Knowing how work in one area will land on others, and sequencing accordingly. Example. Estimating and sales. Estimating has to be rigorous enough to tell you your real cost. Sales then decides what happens to that number: whether a new client with years of work ahead justifies a lower price, and how far is too far. Each side can be done well, and the handoff can still go wrong, if the rules connecting them sit in someone’s head rather than being articulated and agreed on.
  • 4. Cross-domain integration. Holding expertise in several fields at once and reasoning across them. The combination produces value that no single field could produce alone, and it is usually where a founder’s real value sits, because the founder is the one most likely to hold several disciplines at depth. Example. A software company whose founder held three fields together: the technical architecture of the product, the operational reality of his clients’ industry, and the commercial question of what would actually sell at scale. Any one of them could have been taught by someone competent. What made him irreplaceable was that every meaningful decision needed all three, and nobody else in the building held more than two.

That founder’s team was not underperforming. They were structurally unable to make the call. That is a very different problem, and it needs a very different fix.

Here is the useful part. An unusual event is only unusual once. Someone makes the call under pressure, and if you capture how they made it and why, your team is ready the next time it comes up. The same goes for the small calls. At the bathtub company we watched enough real jobs to collect the answers, and they went into the quality control training. That training keeps growing, because every new situation can be added to it. This is how judgment moves out of one person’s head and into the company.

This was never a documentation problem. That is why better documentation software has not solved it.

More on what procedures capture and what they miss

The method

Map it. Surface it. Put it to work.

Brilliance Mining runs as a quick cycle, not a long project. You can run it on one expert or across an entire organization, and the more you run it, the more capability you unlock.

The three steps of Brilliance Mining shown left to right with arrows between them: Mapping, Extraction, and Replication.
Step 1 · Brilliance Mapping™

Find out where the value and the risk actually sit

We cannot surface what nobody knows is there. Mapping is the treasure map. It answers four questions:

  • Where does the critical knowledge live, and who holds it?
  • What breaks if that person is unavailable?
  • Which dependency is most urgent?
  • What would create a fast, visible win?

The output is a prioritized picture rather than a plan to document everything at once. Trying to document everything is how these efforts die.

Step 2 · Brilliance Extraction™

Draw the knowledge out, without anyone having to write

Two ways to do it, often combined.

Observe. Watch the work as it happens. Record the session. Catch the decisions and the actions in context, including the ones your expert would never have mentioned.

Converse. Sit with your expert and work through real cases that were actually solved. Keep asking why that call and not the other one, until the answer stops being “it depends” and starts being the conditions it depends on. Do that across several cases and patterns emerge that your expert has never put into words, because they never had reason to.

A simple outline first makes this far more efficient: the why and the context, the big picture, the steps with their tips and pitfalls, how it fits together, and a summary. That structure surfaces the context your expert would otherwise skip right past.

Step 3 · Brilliance Replication™

Turn what surfaced into something people actually use

Raw material from a working session is valuable but messy. Experts circle back, recall things out of order, and talk at length. Processing turns that into decision guides, checklists, flowcharts, short training videos, onboarding guides, and procedures that are finally complete.

This is the step most efforts skip, and skipping it is why so much captured knowledge decays. A well-documented insight sitting in a system nobody opens is worth about the same as knowledge that was never captured at all.

What it asks of you

Two things founders expect, and neither is true

You expect to have to write. You do not. You talk and you review. That is the whole ask. The Brilliance Miner™ does the heavy lifting, so the person with the expertise never has to become the documenter. This matters more than it sounds, because “go document your process” is the instruction that has failed in your company before.

You expect it to take months. It usually does not. Thirty to sixty minutes of narration or screen sharing often captures eighty percent of something useful. You test it by handing it to someone who has never done the task and watching where they get stuck. Then you improve it.

Work founders were certain would take years to hand off has come apart in a handful of focused hours, because the difficulty was never the complexity of the knowledge. It was that nobody had ever asked the right questions.

Start small. Start fast. A two-minute clip or a one-page checklist that makes one thing easier is already worth more than a perfect manual you never finish.

Brilliance Systems™

The tangible part

What Brilliance Mining produces is a set of Brilliance Systems™: the tools that make expertise shareable. Format matters far less than function.

  • Decision guides that carry the reasoning, not only the steps
  • Checklists and process flowcharts
  • Standard Operating Procedures that are finally complete
  • Short training videos and onboarding guides
  • Internal courses and searchable knowledge libraries

These are living assets. They improve as people use them, and they evolve as the company grows. Something useful shows up early in the process, not at the end of it.

There is a side benefit that surprises people. Once an expert’s thinking is visible, the team can see it too, and the conversation shifts from “how do we do this” to “how could we do this better.” Process improvement stops being a separate initiative.

The honest answer

AI multiplies a good human process. It does not replace one.

AI is genuinely good at the part that used to feel tedious. It turns ninety minutes of thinking out loud into an ordered draft. It reshapes that draft into a checklist or a training outline. It sits inside a knowledge base and answers “how do we usually handle this” at the moment someone would otherwise walk into your office. The blank page is the single most common reason founders never start, and AI removes it.

But notice what all of that has in common. Every bit of it operates on knowledge that has already left your head.

AI cannot know what you have never said. The judgment that makes you the one people wait on is unspoken by definition. It is why you can look at a proposal and sense something is off before you can explain why. No model reaches that until a person draws it out of you in a form that can be recorded.

The same goes for missing steps. Your expert skips what they do instinctively. If those steps never make it into what you hand the AI, the AI has no way to notice they are gone. And when it drafts your process, it fills the gaps with plausible-sounding steps, which only the expert can catch.

The practical answer: use a human-led method to make the knowledge visible, then use AI to organize and shape what has been captured. That order matters, and reversing it produces a well-organized library of your conscious knowledge while everything valuable stays exactly where it was.

What this has done

Knowledge that had never moved, finally moving

Staffing firm

For twelve years nobody could replicate the founder’s instinctive method for matching candidates. Brilliance Mining made it explicit, and he stopped being the only one who could handle high-value placements or train complex recruiting work.

Read the case study

Fortune 500 medical device

Knowledge from multiple specialists became eLearning courses and a clear instructions-for-use manual, supporting FDA approval.

Read the case study

Executive Medicine of Texas

Four hours of Brilliance Mining turned a task known only to a senior medical executive into a clear, repeatable process. Four hours returned every week, which is twenty-five workdays a year.

Read the case study

Common questions

Frequently asked

How long before we see anything useful?

Often within the first session. Thirty to sixty minutes of narration usually produces a strong first draft of something small and usable. Full transfer of a complex area takes longer, but you should not be waiting months for the first result.

Does my expert have to write anything?

No. They talk, they walk someone through the work, and they check what comes back for accuracy. The writing is somebody else’s job.

We already have SOPs. Is this replacing them?

No. Your procedure library is not wrong, it is partial. Brilliance Mining fills in the two layers that never reached the page, and some of what it produces will be better versions of procedures you already have.

Can our own people learn to do this?

Yes, and that is the goal. Brilliance Mining is a skill rather than a talent. We train and certify internal Brilliance Miners™ so you are not trading one dependency for another.

What if the knowledge is too complex to transfer?

Almost every founder believes this about their own expertise. Not every last piece transfers perfectly, and anyone promising otherwise is selling something. What consistently surprises people is how much does transfer, and how quickly.

Which knowledge should you capture first?

That is the question Brilliance Mapping answers, and the Founder Freedom Score gives you the first version of it in three minutes. It maps where dependency currently sits across four dimensions and shows you which one is carrying the most weight right now.

Get Your Founder Freedom Score

Or book a 20-minute Brilliance Activation Call
Scroll to Top