Avoid These 3 Common Airtable Mistakes

This morning, I met with a local business owner to discuss having a sprinkler system installed. Actually, I was hoping our existing (defunct) system could be repaired – but I didn’t think it was likely.

So, the local Sprinker Guy, named Scott, showed up – took one look at the existing system – and started laughing. Apparently, our broken system is older than I am, so it’s just easier to replace the whole thing.

The reality is – I have NO IDEA what I’m doing when it comes to installing, repairing, or maintaining sprinklers.

And that’s totally fine with me – I have no intention of becoming a sprinkler master. But, if I did have allusions of sprinkler-master-grandeur, I imagine I’d make a whole host of mistakes when I attempted to perform an installation on my own.

How is this relevant to Airtable?

Well, as I’ve continued to work with clients in Airtable, I’ve started noticing patterns. I get asked the same questions, from clients with similar concerns. I also start to see similar ways of thinking that leads to pitfalls and “misuses” of Airtable.

So, I documented the three most common misuses that I see, along with the best way to solve them. Check out that video, here.

In this video, I cover the following top three Airtable errors:

How to best communicate with your team in Airtable (hint: it’s not by creating a “notes” field). How to properly lock-down views so that they can be used for Zapier integrations (to build automated workflows in your base).

  1. How to properly architect tables (if it’s the same record, you don’t need a second table).
  2. If you’re looking to build your Airtable skills, or perhaps self-diagnose your own Airtable base, I hope this puts you on the right path.

___________________________________

Need help with Airtable? Schedule a no-obligations call here.

New to Airtable? Get a free trial here (affiliate link).

Want to learn more about Airtable? Check out my blog here.