Every solar company has someone like her, even if they’ve never thought to name it. She’s the one who simply knows. She knows which AHJ insists on a three-line diagram and which one waves it through. She knows that the city across the county line quietly changed its rule last spring. She knows the one utility that will kick your interconnection application back if a particular box isn’t filled out exactly so. You can ask her almost anything about how a project needs to be built, and she’ll answer off the top of her head, quickly, and almost always correctly.
It feels like a gift to have her. In a way, it is. But she is also the single largest point of failure in your entire operation, and most companies never see it until the day it costs them.
Tribal knowledge feels like an asset. It’s a liability.
When the rules that run your business live inside someone’s head, your operation is really running on a daily memory test. And the thing about memory tests is that they pass quietly for years and then fail at the worst imaginable moment.
She goes on vacation. She takes a better offer somewhere else. She’s out sick the exact week you’re trying to onboard three new designers who don’t know any of this yet. In an instant, the knowledge that made you fast and accurate either walks out the door or sits somewhere you can’t reach it, and everyone left behind starts guessing. Guessing is slower than knowing. It’s also more expensive, because guessing is how a required three-line diagram gets left off the one AHJ that demanded it, and the project stalls in review while your cash sits frozen and the clock keeps running.
What looked like an asset was a dependency all along. You didn’t build a process. You built a person-shaped hole that only one human can fill.
The fix isn’t a binder nobody reads
The standard response to all this is to write it down. Document the process. Stand up a wiki. Build the enormous master spreadsheet of which-AHJ-wants-what and tell everyone to consult it.
It’s a reasonable instinct. It also rarely works, because documentation lives off to the side of the actual work, and the work always wins. Picture a designer under deadline pressure with five projects open. They are not going to stop, dig out a reference document, and cross-check the requirements for AHJ number forty-three against a spreadsheet someone last touched who-knows-when. They’re going to do what they remember and keep moving. Which lands you right back where you started, leaning on human memory and hoping it holds for one more day.
The lesson buried in all those ignored binders is simple. A rule that sits next to the work will be skipped. A rule has to live inside the work itself.
Tune it once, then let the system carry it
So here’s the better move. Rather than trusting a person to remember that Denver needs a three-line diagram while the town next door doesn’t, you teach that rule to the system a single time. For each AHJ, you spell out what’s required and what’s optional: the three-line diagram, the roof inspection, that one peculiar form nobody else asks for, all of it. You do that work once, carefully, and then you stop doing it forever.
From that point on, the system carries the load. When a new project gets set up, the steps that apply to its jurisdiction appear on their own, and the steps that don’t simply aren’t there. The designer no longer has to remember that Charlie mentioned this city is fussy. The system already knows. The right task is waiting because the project sits in an AHJ that requires it, and somewhere else that same task stays out of the way because it isn’t needed. We call this tuning, and in SolarSuccess a single project template comes out the far side already shaped to the job in front of you. No two-hundred-line checklist to wade through. No guesswork. No quiet “wait, do we need that one here?”
Why this is the quiet efficiency win
This is the kind of improvement that never makes the highlight reel, and it absolutely should.
What you’re really doing is taking knowledge that used to be fragile and unbacked-up, trapped in a single person’s memory, and turning it into something the whole company owns and can’t lose. New hires get good on their first day, because the system quietly carries the rules they haven’t learned yet. Your resident expert stops being a bottleneck and a flight risk and gets to go back to doing real expert work, instead of answering the same routine question forty times a week. And the work moves faster across the board, because nobody is pausing to wonder, second-guess, or go hunting through a reference doc. The right tasks are simply present, and the wrong ones aren’t there to slow anyone down.
Tribal knowledge built your company, and that’s ok. It’s how nearly every growing business gets off the ground. But you cannot scale a memory test, and you should never have to bet a whole quarter on one particular person showing up to work on Monday. So get the rules out of their heads and put them into the system. Then, at last, everyone gets to be the one who knows.
