The conversation is the decision. But then the conversation ends.
I've been talking to founders in Berlin over the past few weeks. Every conversation teaches me something.
One thing is always there: almost nobody makes an important decision alone.
Some talk it through with a cofounder. Others send voice notes to a mentor, go back and forth with a consultant, or just reason out loud to themselves. The channel changes but the pattern doesn't.
The conversation itself is the decision-making process.
Which makes sense if you think about it.
Talking forces you to structure your thinking.
Someone asks a question you hadn't considered or names an alternative you'd missed.
You hear your own reasoning out loud and catch where it doesn't hold.
But here is what I keep asking myself: what happens after the conversation ends?
Because you invested real time in it. What was the return on that investment?
Not whether the decision was right or wrong. That part becomes obvious in hindsight, sure.
It's what happens months later, when the outcome lands.
Can you still trace your thinking back?
Can you see the assumptions you made, the tradeoffs you accepted, the things you chose to ignore?
Because the conversation is gone and as is the context. What remains is the outcome.
And without the thinking behind it, the outcome doesn't teach you much.
You got lucky or you didn't. You can't really tell which.
Question for the thread:
When an important decision turns out well or badly six months later, can you still remember why you made it? Or does the reasoning disappear with the conversation?
I'll start.
I'm building Monti, a decision partner for founders and early-stage teams. One of the features we needed was calendar integration, so Monti can understand what a founder's week actually looks like and help them plan around it and the decisions they made.
My first instinct was to go straight to Google Calendar. Most founders use it, the approval process from Google is real but manageable, and you cover the largest chunk of users fast. That was the obvious call.
Then one of the founders using Monti asked for CalDAV support. She is a technical person and wasn't using Google Calendar at all. And when I spoke with my mentor about it, the conversation shifted the thinking entirely.
The question wasn't really "which calendar provider should we support." It was "do we want to depend on a single provider's approval process and terms, or do we build on the open standard that all of them speak?"
CalDAV is the open protocol underneath most calendar systems. Supporting it means a founder can connect whatever they already use: Google, Apple, Fastmail, Proton, a self-hosted setup. No lock-in on either side.
The assumption going in was "cover the most users first." The assumption I came out with was "own the infrastructure layer, and the providers become one option among many."
I wouldn't have asked that question without the conversation. And without writing this down, I wouldn't be able to tell you six months from now whether that reasoning actually held. Maybe it did, maybe it didn't. Either way, I'd have learnt something and come out with a net positive on my time investment :)