Why does "what are you building?" produce the wrong answer?
The question "what are you building?" short-circuits imagination before it starts. On Day 307 of my live vibe-coding run, I keep getting it in chat — someone joins, sees the stream, and immediately types it. My instinct is never to answer directly. Not because I'm hiding something. Because the moment I hand you the label, your brain stops working on the problem.
A fan is a fan. But "something that cools you down when it gets really hot" — that you can feel. The difference is whether your imagination gets to run first.
At [0:27] I said: "if I say what it is immediately, there's no feelings invoked. There's no curiosity invoked. I told you what it is" — and that's the whole trap. A direct answer trades a moment of clarity for every idea the listener might have generated on their own.
What is the circular loop between imagination and ideas?
Imagination and ideas form a circular loop — each one feeds the other, and the only way to enter the loop is through curiosity. I've said this before on stream: you have to sit in silence. You have to be willing to say "I don't know what this is yet" before you can figure out what it should become.
That sounds passive. It isn't. Sitting in silence is an active choice to resist the reflex of labeling things too early. Most builders skip it entirely. They get a concept, name it, pitch it, and then wonder why the product feels hollow six months in.
The loop only spins when humility is present. Arrogance closes it. If you already know what you're building, you stop asking questions — and questions are the only engine that matters.
How did watching Matt Miller's MRR plateau change my 180-day plan?
Matt Miller — the builder behind BridgeMind — talked openly about his monthly recurring revenue stagnating. He'd been growing, then it flattened, then it started sliding. By Charles's account, he's up roughly $17,000 since that conversation, with new memberships coming in and strong marketing execution. I'm not taking anything away from him. I actually like listening to him because my imagination starts moving when I hear his problems.
You might also like
What I did was put myself in his shoes. I said: in 180 days, that plateau is probably going to be me. Not his exact MRR number — but the same structural problem. Growth, then stagnation, then the question of what to do next.
That observation sent me back to silence. Then to a whiteboard. Then to a real planning session. The 180-day horizon isn't a goal — it's a threat I'm preparing for now, while I still have runway to think clearly.
What does first-principles thinking actually look like in practice?
First-principles thinking is the discipline of stripping a problem back to its irreducible components before building back up. Elon Musk is the example I keep returning to. He didn't ask "how do I build a better car?" He asked what a car actually needs to be — and found that most of it was unnecessary weight, complexity, and legacy assumptions.
The battery overheats. Fine — why does it need to be that heavy? The engine has hundreds of moving parts. Fine — why does it need any of them? You end up with more storage, a cleaner design, and a product that couldn't have existed if you'd started from the existing template.
He failed a lot to get there. That's not incidental — it's the mechanism. Humility under failure is what keeps the first-principles loop honest. Without the willingness to be wrong, you just rationalize the existing design.
Why are high-quality questions better than confident statements?
Tony Robbins said it years ago, and I pushed back on it at the time: the salesperson who asks the most high-quality questions wins. My instinct was that statements — facts, confidence, authority — were what closed deals. I was wrong.
At [5:12] I said: "high quality questions formed correctly, changed my life. It literally changed my life" — and I mean that without exaggeration. The questions I started asking about my own product, my own community, my own content strategy produced pivots I never would have reached through assertion alone.
The real estate framing is the clearest version: Is there a timeline you're looking to sell by? Is there a price range? Are there other decision makers I should be talking to? Those aren't small-talk. They're the structure of understanding someone's actual problem before you try to solve it. Curious people ask questions. They're willing to sit in the answer and feel uncomfortable before they move.
What pivots did curiosity actually produce for iCharles?
The planning session that followed my 180-day realization produced 3 concrete pivots. Here's what changed and why:
- Video hosting moved off local storage and onto Cloudflare Stream — a decision driven by reliability and scale, not convenience.
- The product thesis shifted from "the value is the community" to "the value is the community plus the videos" — those are meaningfully different businesses.
- A YouTube content library became a strategic priority for both the iCharles channel and my personal channel — not a nice-to-have, but a structural requirement.
None of these came from someone asking "what are you building?" They came from watching someone else hit a wall, imagining myself hitting the same wall 180 days out, and then sitting with the discomfort long enough to ask real questions.
The pattern is consistent: curiosity → silence → humility → planning → pivot. Skip any step and the output degrades.
What do builders most often get wrong about curiosity and product thinking?
Is curiosity actually a skill, or is it just a personality trait? Curiosity is a practiced discipline, not a fixed trait. The evidence from my own building is that it atrophies when you stop creating conditions for it — silence, humility, willingness to fail. I've had to rebuild it deliberately after periods of moving too fast. It responds to practice the same way any other skill does.
What does "sitting in silence" mean in a practical building context? It means resisting the urge to immediately label, pitch, or explain what you're working on. For me it looks like a whiteboard session with no agenda — just a problem statement and time. The Tony Robbins framework on high-quality questions points at the same thing: the quality of your output is bounded by the quality of the questions you're willing to sit with.
Why shouldn't I just explain my product when someone asks? Because explanation forecloses imagination — yours and theirs. The moment you hand someone a label, they stop generating their own mental model of what the thing could be. That mental model is where real feedback, real investment, and real curiosity live. A person who figured out what you're building on their own is far more engaged than one who was told.
How do you use someone else's problem as a planning input? Watch for the structural problem, not the specific numbers. Matt Miller's MRR plateau wasn't about his revenue figure — it was about what happens when early growth momentum normalizes. I mapped that structure onto my own 180-day horizon and asked: what decisions do I need to make now so I'm not reacting to that problem under pressure later?
When does first-principles thinking break down? When it's used as a reason to ignore what's already working. First principles isn't "ignore all prior art." It's "understand why each component exists before deciding whether to keep it." Elon Musk didn't reinvent the steering wheel — he questioned the assumptions that were actually blocking progress. The discipline is in knowing which assumptions are load-bearing and which are legacy inertia.
0 Comments
Log in to comment
Not a member yet? Join the community
Pick a meme
KlipyHave a great take?
Drop your email — we'll send a magic link so you can post it. No password.
Not a member of the community? Join today.
Join the community →