The Client Conversation That Made Me Cringe

Last Wednesday, client Boss Zhang asked me how SaaS data isolation works. I answered "industry standard solution" while my heart was pounding — what even is that?

I've gotten stuck like this before. Every time something came up I didn't understand, I'd nod along and pretend it didn't happen when I got home. This time I didn't want to fake it anymore.

Who Actually Uses "Write What You Don't Know"

The method is dead simple: when you hit something you don't get, don't skip it — open a doc and write it down. The writing forces you to research it properly and organize your logic. Engineer blogger Julia Evans cracked through Linux kernel and other hard topics this way; Simon Willison writes a "version of what I understand so far" post before trying any new tool. They didn't become experts first and then write — they became experts by writing.

I tried this last month — wrote "What is data isolation, really?" Next day in a meeting with Boss Zhang, I actually caught his references.

Replication Cost: Money, Time, Barrier, First Step

Money: $0. Time: First post takes 2-3 hours (research + organize thoughts); after that, 30 minutes a week is enough. Technical barrier: Zero coding needed — pick Yuque, WeChat Official Account, or Notion, sign up, start writing. First step: Today, open a new doc and write down the concept you were recently asked about but couldn't answer. Title it "My Current Understanding of X" and write 500 words.

I've made this mistake before — always wanting to write a "perfect" piece before publishing, which means I never publish. Ship it first, iterate later.

Pick a Starting Approach by Your Stage

Just starting out (no clients yet): Don't wait for business to come — write first. Pick a domain you know you don't understand, like "What is an API" or "How does SaaS billing work," write 500 words, and publish. Nobody reads it? Fine — next time you talk to someone, you won't freeze up.

Got 1-2 stable clients: Before each new project kicks off, write a primer post: "For this project, I need to understand X." Clients see it and think you're serious. You also pre-learn the basics.

Scaling up (3-5 person team): Have each teammate write one post a week about something they got stuck on. Stack them into an internal wiki plus external content. Low-cost content production and knowledge capture in one go.

This method isn't for everyone. If you're swamped right now, bookmark this — try it next week. Lighter than you think.