MVP Field Notes: You built it. Now what happens if you leave?

A few weeks ago, ​@Mirek_Walton posed a question to other Airtable MVPs that hit close to home for many: what do you do when your organization has become so dependent on you and your Airtable build that you genuinely can't step away?

Thirty-two replies and 165 views later, it's clear this is one of the defining challenges of being an Airtable power user! 

Whether you're in a 12-person startup or a 700-person enterprise, the pattern is the same: you champion the tool, build something that works, and suddenly everything runs through you.

So here's what our MVPs had to say on the subject.

The single-point-of-failure problem is real — and documentation alone won't fix it

@Helen_Fletcher put it plainly: great docs require someone who can both understand them immediately and have the drive to follow through. ​@elijahcg went further, noting that in most orgs there simply isn't a bench of technical people who could pick up the work even if it were documented perfectly. Writing docs under pressure can feel like effort that will almost certainly never be read.

"Surface-level handover is not the same as operational resilience." — ​@Matthew_Williams, who was mid-transition to a new role (congratulations on the new role, Matthew!)

Documentation is still worth doing, but clearly it's just not a solution on its own and the end goal needs to be distributed ownership in the organization.

So what actually works?

Here are the strategies that surfaced in the thread:

1. Cultivate an internal apprentice: ​@Willy_Deslandes spent five years gradually mentoring one team member with natural curiosity about the "how." The result: two power users instead of one, and a huge reduction in the single-person risk. It's not the fastest solution, but it's the most durable one!
2. Run a power user forum: ​@joshchilds nominates one curious person from each team and runs monthly themed sessions on topics like capacity views, automations, interfaces, etc. They also send a monthly email showcasing how builds have benefited specific teams, which drives adoption and builds appetite to learn. Love this one!
3. Onboard on interfaces, not raw data: ​@AcDemas brought up a good point: new users should get comfortable with the front end before they ever touch the backend. It reduces the learning curve, and it prevents people from accidentally breaking things.
4. Use screen recordings over text docs: Multiple members like ​@DisraeliGears01, ​@Olena Baych, and​@Diederick Vos shared how they have shifted to Loom, Scribe, or AI-assisted recordings over writing things down over and over. Video is more approachable for most people, and these are easier to keep updated than written SOPs but “I usually attach SOP directly on relevant pages for easy retrieval to address the problem of people who do not know or remember where to search the SOP,” says @Olena Baych.
5. Simplify your bases continuously: Complexity is a handoff risk. ​@AcDemas shared that he regularly goes back to streamline structures — fewer fields, fewer lookups — so there's less to explain AND less to break!
6. Make it your manager's problem: ​@Mirek_Walton’s pragmatic move? Escalate the dependency risk to leadership so they're invested in solving it, including potentially hiring freelance backup support.

A framework worth knowing: the Center for Enablement Excellence

People seemed most excited by this hot tip that came from ​@Jan_Sassmannshausen, Airtable’s Field CTO: build a Center for Enablement Excellence (CEE). Jan lived this exact situation that MVPs were commiserating on before he joined Airtable. He scaled the tool from a small pilot to nearly 500 seats across a global enterprise, and becoming the go-to for everything.

Creating the CEE framework became a huge unlock for Jan and his organization:

A small core team owning governance and standards, a Champions Network of power users in each department handling 80% of questions, and a community where builders share and learn from each other. It takes about 90 days to stand up.

The key insight: the people who govern the platform should be the people who believe in it. External experts treat the symptom, while internal champions solve the root cause!

The mindset shift that matters

​@doooneeez framed it well too: the friction isn't just knowledge, it's mindset.

Some colleagues are just more open to learning new tools than others. Microlearning (short recordings of how something was done, posted in a channel where requests land) has helped shift that in their org and, after a year, they’re seeing some progress. 2 of 15 people creating interfaces independently and 3 doing routine maintenance confidently. It might not be a lot a lot, but it’s enough to keep them going!

Add your own perspective by leaving a reply on this thread 👇🏻

Interested in joining the Airtable MVPs program? Learn more and apply here.