u/chirag-ink

Tim Urban writes about how the human brain is still running ancient social survival software.

The part that's terrified of being rejected by the tribe. The part that reads criticism as physical danger. The part that will do almost anything to avoid social discomfort, even when the discomfort is completely harmless.

I read it on a flight, thinking about nothing work-related.

Landed and immediately thought about our customer calls.

Specifically, why customers never told us the real reason for their unhappiness.

They'd say "we're going in a different direction" when they meant "this stopped solving our problem 3 months ago."

They'd say "budget reasons" when they meant "we couldn't justify the cost because the value wasn't clear enough."

They'd say "we might come back later" when they meant "we're not coming back."

The mammoth brain was doing its thing.

Avoiding the discomfort of telling a founder his product wasn't working. Softening the blow. Protecting the social relationship at the cost of honest information.

Which meant I was making product decisions based on polite exit stories instead of real ones.

Changed the offboarding completely after that.

Stopped asking why they were leaving.

Started asking what they were going to do instead and how they were going to solve the problem now.

Different question. No social threat in it. Just curiosity.

The answers were completely honest.

And completely different from everything the polite exit stories had been telling me.

Tim Urban was explaining ancient human psychology.

He accidentally fixed our churn analysis.

What's the most useful thing you learned about your customers from a completely unexpected source?

I have a journal that's just mental models.

First-principles thinking. Inversion. Second-order consequences. Hanlon's razor. The map is not the territory. 200-something of them have now been collected over 3 years.

I read them. I understand them. I can explain most of them clearly.

Almost none of them changed anything I actually do.

3 did.

Just 3 out of 200-something actually landed in a way that changed real decisions in the real world.

The first: "Don't ask people what they want, watch what they do." Changed how I interpret customer feedback entirely.

The second: "Every system is perfectly designed to get the results it gets." Changed how I diagnose problems. Stopped asking what went wrong. Started asking what in our system made this outcome inevitable.

The third: "The map is not the territory." Changed how I hold my own beliefs about the product. My understanding of what we've built is just a map. The customer's experience is the territory. They're never the same.

Here's what that taught me about advice, frameworks, and mental models.

Understanding something and being changed by it are completely different things.

You can collect frameworks indefinitely. Read every book. Fill every journal. Understand every concept perfectly.

None of it matters until something lands at the exact moment you're ready for it. When the right idea meets the right experience, it becomes permanent. Before that, it's just information.

The job isn't to collect more models.

It's to stay curious enough and present enough that when the right one arrives at the right moment, you actually catch it.

What's the one mental model that actually changed how you make decisions?

both spent years experimenting with mysterious systems, hoping to discover some hidden formula that transforms uncertainty into gold.

You can seek attention pretty easily now.

With:

- controversy
- ai images
- rage bait
- hooks

But trust compounds painfully slowly.

Usually through:
- consistency
- specificity
- taste

Small interactions repeated over time.

Most people optimize for reach because it's visible.

Very few optimize for remembered reputation.

So many founders I know, including past me, will stay in a sales call, a customer conversation, a networking chat, or a meeting that's going nowhere for far longer than it needs to go. Because leaving feels impolite. Because maybe something useful will happen. Because saying "I think we've covered what we needed to" feels like a confrontation.

The cost: hours a week, real hours, in conversations that stopped being useful 20 minutes ago.

The skill: knowing when a conversation has peaked and ending it gracefully while it's still good. This has been really useful; I'm going to let you go. I'll follow up on X. Done.

Nobody is offended by an efficient conversation. Most people are relieved.

And the conversations you do stay in become better because you're actually choosing to be there.

Takes practice. Worth it. Probably saved me 6+ hours a week once I got decent at it.

They expected a system.

Morning routine. Meditation. Journaling. Something optimized.

I said I just talk to my team.

They looked at me like I'd said something strange.

But that's genuinely it.

Something feels heavy; I just say it out loud to the people building this with me.

Not for advice always. Sometimes just to say it.

The problem doesn't always get solved in that conversation.

But it stops being something I'm carrying alone.

Carrying things alone is where founder burnout actually starts.

Not in the workload. In the silence around the workload.

How do you actually handle the hard weeks? 

She runs a small coaching business. Friend of a friend. We were just talking.

I asked how she collects feedback from her clients. She described this whole manual process: WhatsApp messages, screenshots, and a folder on her desktop called "nice things people said."

I asked why she doesn't use a tool for it. She said she didn't know tools like that existed.

I asked what she'd want it to do if it did exist. She talked for 25 minutes. No filter. No technical assumptions. No awareness of what was "hard to build" or "already been tried."

Just a real person describing exactly what would make her life easier in completely plain language.

I wrote down 11 things. Six of them I'd never thought about. Three of them I'd thought about and dismissed as "too simple to bother with."

The most useful product conversations I have are never with other founders or tech people. They're with people who use things without caring how they work.

Everyone in startups is talking to other people in startups. All the same vocabulary. All the same assumptions. All the same blind spots are reinforcing each other.

Talk to someone who calls it "the cloud thing." Genuinely. You'll come back with a notebook full of stuff.

Products people love: "it finds the testimonials for me." "It just sends the follow-up." "It builds the wall automatically."

Products people tolerate: "it's a testimonial management platform." "It's a workflow tool." "It's a customer feedback system."

The verb "products" feels like they do something. The noun "products" feels like a place where you go to do something yourself.

This isn't just a marketing observation. It's a product, one.

When users describe your product with a verb, it means the product has genuine agency. It takes something off their plate. They don't have to manage it; they just benefit from it.

When they use a noun, it means they're the ones doing the work and the product is the environment they're doing it in. Which is fine, but it's a much easier thing to replace.

The most defensible SaaS products are the ones where the software is doing something real, not just the ones where the software provides a place for the user to do something.

Look at how your happiest customers describe the product. Are they using verbs or nouns? The answer tells you a lot about how hard it would be to leave.

How do your best customers describe what your product does?

The problem isn't that you're undisciplined

It's that you're running someone else's system on your hardware

Copy this prompt into Claude and build one that's actually yours

SITUATION: I want to build a personal system for how I run my life, not borrow from someone else's morning routine.

CONTEXT:
How my brain actually works: [when you're sharpest, when you crash, how you make decisions, what drains you, what you need to do good work]
What I've tried that didn't stick: [productivity systems, habits, routines, be specific about why they failed]
What my life actually needs to contain: [work, relationships, health, things I want to do, and things I should not do]
The one thing I keep failing to protect: [the thing that always gets sacrificed first]

WHAT I NEED FROM YOU:

1. Based on how I described my brain, tell me what kind of operating system would actually work for me. Not GTD. Not Atomic Habits. Something specific to what I've described.
2. Build me a weekly structure, not a schedule, a structure that works with my energy, not against it.
3. Give me 3 rules for my week that are non-negotiable, simple enough that I'd actually follow them.
4. Tell me the one metric I should actually track to know if the week was good. Not tasks completed. Something that reflects how I want to feel.
5. Tell me what to do when the system breaks down, because it will, so I don't throw the whole thing away.

IMPORTANT:
This should sound nothing like advice I could have googled. Make it specific to exactly what I described.

He said, "Just be someone people can count on."

Not being smart. Not the best. Not disrupt anything.

Just be someone people can count on.

I've been building for years. Talked to hundreds of customers. Read all the books.

Still comes back to that one sentence.

The customers who stayed the longest stayed because they could count on us. Not because we had the best features or the lowest price.

Because when something went wrong, we showed up.

That's it. Be countable. Everything else follows.

What's the best business advice you got from someone?

Hard months make sense to people.

Things are bad. You're stressed; that's absolutely normal.

Good months are harder to explain.

Numbers are up. Customers are happy. The team is good.

And there's still this quiet thing in the background that doesn't have a name.

Not anxiety exactly, and not fear exactly.

Just the knowledge that you can see further ahead than anyone around you, and what you can see isn't guaranteed.

You can't say this at dinner without sounding ungrateful.

You can't post it without sounding dramatic.

So most founders just carry it quietly during the good months and wait for the bad months when it finally makes sense to people.

I'm posting it because I think more founders feel this than admit it.

Does anyone else find the good months quietly harder than the bad ones?

I read everything before I started building.

Zero to One. The Lean Startup. Every Paul Graham essay. Every founder interview I could find at 2 am. I had notebooks full of frameworks. I thought I was ready.

I was ready for the business part. The metrics. The growth loops. The fundraising language. I could talk about product market fit like I'd found it before I'd even built anything.

Nobody prepared me for the other part. The part where building something real holds a mirror up to your face at the worst possible moments.

That part wasn't in any book. I had to learn it the slow, expensive way. Three years of it.

So here's everything I actually learned:

1. You will build the wrong thing for longer than you think is possible.

Six months ago, I built from assumptions. Features I thought were clever. Problems I thought existed. Solutions to things nobody had actually complained about out loud.

People would see demos and say, "Wow, this is cool." I'd walk away feeling like I was onto something. I wasn't onto anything. "Cool" and "useful" are completely different things, and I kept confusing them.

The moment everything changed was when I stopped showing people what I built and just asked them one question: walk me through what your Tuesday actually looks like.

What to do differently: Before writing a single line of code, talk to 10 real potential customers about their actual day. Not about your idea. About their life. The product that comes out of those conversations will be completely different from the product in your head. And it will be better. Every single time.

2. Asking for help will feel like weakness until the day it saves everything.

I had this idea that figuring things out alone was the right thing to do. That asking for help meant I wasn't ready for this. So I'd sit with problems for days. Going in circles. Getting slower. Getting quieter about it.

In one particularly bad month, I finally said the actual problem out loud in a team call. Not a polished version of it. The real messy version.

We solved it in 25 minutes.

What to do differently: Make a rule for yourself. If you've been stuck on something for more than two hours, you say it out loud to someone. Not because they'll always have the answer. Because the act of saying a problem clearly to another human being changes how you see it. Every time.

3. Money will change rooms before it changes your life.

When the business started making real money, the first thing I noticed wasn't happiness or relief or any of the things I'd expected.

It was how differently people talked to me. Same people. Same conversations. But more agreement suddenly. More laughing at things that weren't that funny. More "you're so right" from people who used to push back on me regularly.

I hadn't changed. The number had. And the number was doing something invisible to every room I walked into.

The dangerous part was that the agreement felt good. Validation feels good. A room full of nodding feels like confidence. So I almost didn't notice it happening. Almost let it go on too long.

What to do differently: Build your honest feedback systems before you need them. Advisors who have no reason to be nice to you. Churned customers who'll tell you what broke. A co-founder with a genuine standing invitation to tell you when you're wrong. Because money quietly turns down the volume on the uncomfortable truths, and you won't always notice it happening.

4. Miscommunication is the most expensive thing in a small company. Not competition. Not a bad product. This.

We almost lost three months of work once because two people on the team were working from the same message thread and building completely different things. Both were smart. Both were confident. Both were working hard every day.

Just on different things.

When I finally got them in a room together, it took eight minutes to fix. Eight minutes versus three months. That gap is the real cost of assumed alignment in a small team.

What to do differently: Make talking out loud non-negotiable. No important decision lives only in a text thread. You say it out loud. You confirm that the other person heard the same thing. You write down what was decided. Simple. Obvious. Almost nobody does it consistently until something breaks badly enough to make them.

5. The ambition you start with is rarely the ambition you need.

I had a very specific idea of what building a company was supposed to look like. Big numbers. Fast growth. A story impressive enough to tell at a dinner table without people's eyes glazing over.

Then I had an honest coffee with a founder who had everything that looked like success from the outside. Big team. Real funding. Impressive trajectory.

He hadn't slept properly in months. His co-founder's relationship was quietly breaking. Every decision had six opinions attached from people who'd written checks.

He looked at my situation and said he was jealous. I was looking at him, thinking the same thing. Neither of us had the right version. We just had different ones with completely different costs attached.

What to do differently: Write down early what you actually want the company to feel like in three years. Not the numbers. The actual feeling of it. What kind of customers? What kind of team? What kind of decisions do you want to be making? Then check your progress against that instead of against someone else's journey. Comparing your chapter three to someone else's chapter seven is the fastest way to lose the thread of what you were actually building.

After 10+ years, the thing that surprised me most wasn't anything about business.

It was how thoroughly building something real dismantles the version of yourself you thought you were before you started.

You find out you avoid difficult conversations. You fix it or it costs you something real. You find out you celebrate too early and get complacent. You fix it, or it costs you again. 

The company doesn't care about the story. It just shows you the gap.

That's the part no book prepared me for. And honestly, it's the most valuable part of all of it.

I'm a genuinely different person than I was three years ago. Not because I read better books or followed better frameworks.

Because the company kept putting me in rooms I couldn't perform my way out of.

If you're early in this journey, just know that the business is almost the secondary thing happening.

The primary thing is you figuring out who you actually are when it counts.

That process is uncomfortable and slow and occasionally genuinely painful.

It's also the best thing that's ever happened to me.

What's the thing building taught you about yourself that no book could have?

Every option on your list sounds important

That's the problem

This prompt cuts it down to one and tells you why the rest can wait.

When everything feels like a priority, nothing actually moves forward.

If you’re heading into a new quarter (or even just feeling stuck choosing what to focus on next), this prompt forces clarity. It helps you stop overthinking and commit to the one direction that will actually create momentum.

 
PROMPT

SITUATION:
I have too many directions I could go next quarter, and I need to commit to one that actually drives meaningful progress.

CONTEXT (read carefully before answering):

•  I tend to overthink and keep options open instead of committing 
•  I value long-term growth and momentum over short-term wins. 
•  I am okay with slow progress if it compounds over time. 
•  I don’t want validation or safe answers. I want honest, strategic judgment. 
•  Assume my time, energy, and focus are limited, so prioritization matters more than ambition

 

MY CURRENT STATE:

•  What I'm building/running: [brief description] 
•  Stage (idea / early traction / scaling): [choose one] 
•  Key constraint right now (time / money / skills / distribution): [be honest]

 

OPTIONS I’M CONSIDERING:
[List everything — even messy or half-formed ideas]

REFLECTION:

•  What worked this quarter: [specific, real signals only] 
•  What didn’t: [specific, real signals only] 
•  What I actually want (not what sounds impressive): [be brutally honest]

 

WHAT I NEED FROM YOU:

1. Look at my options and tell me which one has the highest chance of creating real momentum, not the most exciting one, the one that compounds.
2. Tell me which options I'm considering because of fear of missing out, fear of being wrong, and fear of committing.
3. Give me a simple filter I can run every option through to cut the list in half immediately.
4. Pick one. Tell me why. Tell me what the first 2 weeks of actually committing to it look like.
5. Tell me the thing I'll be most tempted to do to avoid fully committing and how to catch myself doing it.

THE RULE:
One direction. Real commitment. Everything else gets parked, not killed.
Help me feel okay about that.

I've seen it a handful of times. Someone goes from the idea to the thing being real.

The process is never clean. There's always a moment where they almost stop. usually around week 3 when the initial energy dies, and the thing is 40% done and looks bad, and the gap between what's in their head and what's on the screen feels uncrossable.

The ones who make it through that week: I genuinely don't know what distinguishes them. It's not obviously talent. It's not resources. It's something more like stubbornness mixed with genuine curiosity about whether it'll work.

The ones who don't make it through that week are often smarter. Often, it's more aware of all the reasons it could fail.

Awareness of failure modes is not the same as the ability to ship. Sometimes it's the opposite.

We've hired 4 people recently. One hire was a mistake. I think I know why now.

Before the final offer, I ask, "What's a project or thing you've built or done not for work that you're actually proud of?"

Not "where do you see yourself in 5 years?" Not "what's your greatest weakness." This.

The answers sort people fast.

Some people have an immediate answer. They light up a bit. Talk about a side project, something they fixed at home, a community they helped run, or a tool they made for themselves. They've made things. They know what it feels like.

Some people pause and then describe a work project. Which is fine, but it's a different kind of person.

For a bootstrapped startup, I need people who make things because they can't make things. Not because they were told to.

The hire, which turned out to be a mistake, gave a technically perfect answer about a work project. Great execution. Just needed more structure and direction than we could provide at our stage.

It's not a definitive test. But it's been the most useful 2 minutes of every hiring process for us.

What's your go-to hiring question?

The email was three paragraphs.

First paragraph: genuinely kind intro, said they'd enjoyed using the product.

Second paragraph: explained why it wasn't the right fit for them right now: specific, reasonable, no drama.

Third paragraph: They wished us luck, said they'd probably be back when their business was bigger, and asked politely for a refund.

I processed it in 3 minutes and replied, "Done. And thank you for the nicest refund request we've ever received."

They replied with, "Haha, I hope that's a compliment."

It was purely a compliment.

I think about this email when I'm writing emails to cancel subscriptions or give feedback. It costs nothing to be specific and kind. The person on the other end is a human who built something.

Also, they came back 4 months later and upgraded.