The Writing Founder Project

I had a revelation recently when I saw a popular online creator say that the goal of all his projects is actually to create books. Physical books. All the work he does, funnels into that ultimate format. It is the end product, and everything else he creates or publishes on the side is an ancillory activity.

“…the core purpose of this program (and all the work I do — the pop-ups, the videos, everything) is to produce books.“

– Craig Mod

I was really struck by this, and it’s the right message at the right time. As a writer myself, I’ve long felt a sense of guilt whenever I spent time doing it — “I could be working and making money instead!”

“Writing” felt like adultery, cheating on the endless to-do list that my life as an entrepreneur had become.

But writing and sharing what I’ve learned is what brings me the most joy. That’s what most of my writing is about — doing something I found interesting, and then sharing what I learned with others.

What drives me is creating stories.

I see myself mainly as an explorer or a scientist on this planet, and even entrepreneurship is simply a lifelong experiment in “what ifs” and “wouldn’t that be cool.”

So here goes another:

WHAT IF the final output of all my activities was to write about the experience?

From now on, my core purpose of building SANPRAM will be to write articles and essays.

Here are the formats this content will be in:

Written word

The core formats I’ve played with so far are books, long essays, and short posts.

Books (physical books) are the hardest, but also the ultimate form, because they are timeless and a great creative medium. And you can also make them very short. One drawback is that they cost money to read.

Essays and short posts would be the bulk of my writing. I’ve found that consistent high-quality essays are great for building a following.

Here’s the different kinds of posts I’ll be writing as an output:

1. Sunday Reports — not monthly, because a 7 days is a more tractable unit of time (it’s hard to mentally grasp how long a month really is and be conscious of it). Deadline: every Sunday.
2. Daily Work Logs — whatever I happens that day. Deadline: every day.
3. Rambles and reflections — these will be about whatever is on my plate at the moment. The core of my “documentation.”
   • Format: take a company goal, and as you go through the process, document the process in front of the whole world. Simple.
4. Periodic Tech essays — this is how I got my start in writing. I take a technical topic, and write a deep explainer essay.

The whole workflow should go like this, each step starting and ending with a piece of writing:

• Ramble: I set a goal for what I need to do at the moment, and a timeline for it.
• Ramble: I write my plan for how I intend to do it.
• Rambles and Reflections: I start working the plan, and write about each step.
• Weekly report: I share the results / progress being made.

Video
Video is a great form of documentation, and it has certain advantages over text (being able to SHOW things, and share live emotions)

I’ve decided that video will best be a companion to my writing, as opposed to its own medium. I will use video to enhance the meaning of my written essays, as a communication aid.

It would fit mostly in the rambles and weekly reports category.

For livestreaming, I’ll use StreamYard.

Audio

I host two podcasts, using them mainly as a networking tool for building more relationships with other founders. I intend to keep doing them, but further reduce the effort that goes into production. (Not that I was putting a lot of effort to begin with)

What to share, and what to keep private?

I just had a long conversation with Gemini about this one, because I neither want to be so secretive that nobody gets value, nor to overshare so much that I come across as a clown / it’s boring / I give away strategic secrets.

To figure out where I fall on the spectrum, I looked into the sharing habits of Warren Buffett / Charlie Munger, and for an outlier opinion, Elon Musk.

Here’s the edited consensus, which I also feel comfortable with:

What to share:

⁃   Visions of the future I want to build
⁃   Monumental challenges that apply to the whole industry (“manufacturing is hard”, “full self-driving is hard”, etc) — highlight the difficulty of the process.
⁃   Product announcements (often very early)
⁃   Positive Outcomes: deliveries, good customer feedback, things that are really cool
⁃   Negative Outcomes (after they've been overcome): what happened, how we overcame it, and how our creative process / intellectual method has been changed or reinforced because of it.
⁃   The intellectual process / beliefs and philosophy behind decisions, and insights gained.

What to delay or keep private:

⁃   Core IP / secret sauce / technical details of solutions we develop.
⁃   Fundamental / existential doubts about the viability of whatever I’m doing. (Hey, I'm human, they come up from time to time)
⁃   Real-time suspense of a process that is in motion.
⁃   Anything that affects other people / makes someone lose face / reveals others' secrets.

You can subscribe to my newsletters here.