Why we're writing this
A short, honest note about what this space is for, and what it isn't. Notes from the work, in public, written by the person doing it.
Most blog posts on company sites are sales documents in a costume. You can usually tell within two paragraphs.
This isn't that.
What this is, instead: notes from the work. The discovery calls I'm having with hardware teams. The technical decisions we're making and why we're making them. The thing a customer said in passing last week that changed how I think about the product. Half of it will be useful to you, half of it will only be useful to me, and I'm honestly not always going to know which half is which when I hit publish.
I'm writing in public for two reasons.
The first is selfish. Every founder knows that the act of writing forces you to actually understand what you think you understand. There's no faking it on a page. If a sentence doesn't make sense, the underlying idea probably doesn't either. Writing this stuff down is the cheapest discovery tool I have.
The second is generative. The Mom Test (the book that's been on my desk for two months) keeps making the same point in different ways: the only way to find out what people actually need is to talk to them, and the only way to talk to them is to give them a reason to start the conversation. A blog is one of the cheapest ways to start a conversation with someone you'd otherwise never meet. If something I write here lands for you, the win isn't that you read it. The win is that you reply.
The only way to find out what people actually need is to talk to them.
So that's the deal. Notes from the work. No keyword bait, no pretending I know more than I do, no advice on things I haven't done myself. Just what I'm seeing and learning, written down while it's fresh.
If something here makes you nod, or argue, or remember a problem your team is dealing with right now, write back. The reply email is at the bottom of the page.
I'd like to hear from you.