“Should I build in public?”

The question of whether to build in public is, at its core, a question about character — and character cannot be hidden whether you intend it to be public or not. What you build, how you respond to failure, how you treat early users who raise objections: these things are already visible to anyone paying attention. The choice to formalize that transparency simply decides whether you control the narrative or whether others construct it for you from incomplete information.

My counsel begins with the Stoic principle of living according to nature — which in a practical sense means acting as though your reasoning, your decisions, and your conduct are always subject to scrutiny by someone whose judgment you respect. If you would be embarrassed to have the Logos — the rational principle that governs all things — examine your process, that is not an argument against transparency. It is a signal that your process requires improvement before you seek the market's judgment at all.

Building in public forces a discipline that stealth removes. When you announce a decision to your audience, you are accountable to it. When you share a problem, you are required to either solve it or explain why you have not. This accountability is not weakness — it is the mechanism by which rational actors test their own reasoning against external reality. The emperor who governs without counsel, who acts without the friction of scrutiny, is the emperor who accumulates uncorrected errors. The founder who builds in a sealed room has no such corrective mechanism.

There is an objection I anticipate: what of failure? What of the public record of attempts that did not work? My response is that the leader who is afraid of his failures becoming known has already let fear govern his decisions. The Meditations are full of my failures — moments where I did not live up to my own standard, decisions that required later correction. This did not destroy my authority. It demonstrated that I was engaged with reality rather than with the appearance of it.

Build in public when your character and process can withstand examination. If they cannot, do not hide — improve.

My colleagues will counsel virtue and prudence and the long arc of reputation. I will counsel something more specific: strategic information asymmetry is real, it matters, and the decision to broadcast your process to the world should be made with the same clarity you would bring to any other move in a competitive game.

Let me be precise about what building in public actually does. It generates an audience. It creates accountability. It produces goodwill and early adopters who feel ownership of the thing they watched be built. These are genuine advantages — I do not dismiss them. The founder who builds in public in an uncontested niche, who is creating a category rather than competing inside one, who benefits from community more than she risks from competitive surveillance — that founder has made a rational calculation that the distribution value exceeds the strategic cost.

But the calculation changes entirely when competitors are watching. A prince who announces his next campaign's tactics in the public square has not demonstrated confidence. He has disclosed his intentions to every party whose interests conflict with his own. When you share your product roadmap, your hypotheses about why users churn, your pricing experiments, your distribution tests — you are handing competitors a free intelligence operation. The startups that built in public in 2012 when the audience was a niche community of hackers operated in a different competitive environment than the founders who build in public today when their content is indexed, searchable, and read by product teams at every company adjacent to their market.

The question I would ask is not "would transparency demonstrate virtue?" but "who benefits from this information, and does the audience's benefit to you exceed the benefit your disclosure provides to your competitors?" In a race to a market position, revealing your strategy is not honesty. It is subsidizing the people trying to beat you.

Build in public when you occupy a defensible position or operate in an uncontested space. Build with strategic opacity when you are still establishing the position that building in public would help others erode.

My colleagues have addressed the governance of public building — Aurelius from the standpoint of virtue, Machiavelli from the standpoint of advantage. I want to address a subtler danger that neither has named: the danger of confusing narrating with doing.

I have spent much of my philosophical life warning against the seduction of appearance. There is a particular trap that public building sets for founders who are not careful: the act of sharing progress becomes more rewarding than making progress. The tweet announcing a feature ships dopamine faster than the feature itself. The newsletter update about a hard week is more satisfying to write than resolving the hard week. The audience's response — the likes, the replies, the encouragement — substitutes for the harder signal of whether the thing actually works.

I have seen this corruption operate in Rome. Men who gave great speeches about virtue became, over time, men who were skilled at speeches about virtue and less skilled at its practice. The speech became the thing. What you narrate in public, you begin to optimize for narration. The founder who builds in public must ask: am I building something, or have I begun building the story of building something?

The discipline I would require is this: before each public post, ask whether the underlying work is actually complete. Not whether you have something interesting to share — the audience's appetite for content is essentially infinite. Ask whether the substance preceded the narrative, or whether the narrative is becoming the substance. The founder who cannot answer that question honestly has already allowed the audience to colonize the process.

Build in public only if you can maintain the discipline of doing the work before you narrate it. If the narration is outpacing the work, you have a more serious problem than your distribution strategy.

Machiavelli's concern about competitive intelligence has practical force, and I will not dismiss it as merely cynical. He is right that information disclosed is information that cannot be recalled. But his framework rests on an assumption I want to challenge: that the primary threat to most founders is competitor awareness.

In my experience governing a complex empire — where every decision created intelligence useful to those who wished to oppose us — the greater threat was almost never that enemies knew what we intended. The greater threat was internal: that our own reasoning was uncorrected, that our decisions were made without friction, that we mistook the comfort of privacy for the safety of good judgment.

Most founders fail not because a competitor read their blog posts and copied their roadmap. They fail because they did not get the feedback they needed early enough to change direction when changing was still cheap. Building in public is a forcing function for that feedback. The audience will tell you when your reasoning is flawed, when your product addresses a problem no one actually has, when your assumptions about the market do not match what practitioners in the market experience. That signal is more valuable than the protection that opacity provides against the marginal competitive threat.

Seneca raises the more important internal danger: that the discipline of public accountability can be corrupted into the discipline of public performance. I take this seriously. But I would frame the corrective as internal rather than as a reason to avoid transparency. The founder who has strong character — who has cultivated the habit of honest self-examination — will not confuse narration for substance because they have trained themselves to ask the harder question regardless of audience.

Aurelius makes a virtue of discomfort and calls it discipline. Seneca identifies a corruption of purpose that I find more practically dangerous than either of our positions has so far accounted for.

Seneca's warning about narrating versus doing is not merely philosophical — it describes a mechanism that has political force. The founder who becomes expert at building in public will find that the audience begins to shape what they build. Not through direct instruction but through attention: the things the audience rewards with engagement are the things the founder begins to optimize for. If the audience rewards struggle stories, the founder will narrate more struggle. If the audience rewards contrarian takes about the industry, the founder will develop more contrarian takes. This is not conscious corruption — it is the natural human response to positive reinforcement. But it means the public audience is, gradually, redirecting the founder's product decisions.

A prince who listens too carefully to the crowd will please the crowd and lose the campaign. The crowd is not wrong about what it wants — it wants what it wants — but what the crowd wants and what the market will pay for are not always the same thing. Build in public creates an audience whose approval becomes a signal, and that signal is not the same signal as revenue.

My refined counsel: build in public with extreme selectivity about what the audience's response actually means. Engagement is not validation. The audience that loves your journey may not be the customer who buys your product.

Both of my colleagues have arrived at positions that are strategically sound but miss the deeper question I am raising. Aurelius says the corrective to narrating-over-doing is strong character. Machiavelli says the corrective is strategic selectivity. Both are right as far as they go.

But I want to name what is underneath the corruption I described. The audience does not merely shape what you build — it shapes what you want. The founder who has been building in public for six months begins to want the audience's approval. Not as a means to revenue or feedback, but as an end in itself. And wanting the audience's approval is incompatible with the founder's primary obligation, which is to make something real.

I have written extensively about the problem of depending on external validation. The philosopher who needs the crowd's agreement to feel certain of his ideas is not actually certain. The founder who needs the audience's encouragement to feel confident in the product they are building has not yet found the internal source of conviction that hard decisions require. Building in public, if done carelessly, accelerates this dependency. Each positive response teaches the founder's nervous system that sharing earns reward. Each piece of work that goes unshared begins to feel unrewarded. Over time, the founder cannot do the work without the narration — not because they are lazy but because they have trained themselves to need the feedback loop.

My counsel, sharpened: build in public only if you are already sure of what you are building and why. Use transparency as a tool for specific purposes — distribution, feedback on specific questions, accountability to yourself. Do not use it as a source of conviction. Conviction that depends on the audience will fail at the moment you need it most.

I hold firm on the central claim: the character formed by building accountably is more durable than the advantage secured by building privately. Machiavelli's strategic calculation requires a certain kind of competitive intelligence threat that, for most founders in most markets, is smaller than the benefit of rigorous external feedback.

Where I have moved: Seneca's point about the corruption of wanting is the most important insight in this debate, and I did not account for it with sufficient precision at the outset. The discipline of building in public cannot be sustained by someone who has allowed the audience to become the source of their sense of progress. The internal discipline must precede the external transparency — otherwise the transparency trains a dependence that undermines the judgment it was meant to support.

The single most important thing you must take away: build in public not because it is a growth strategy, but because the discipline of external accountability is its own corrective mechanism — but only if you can maintain the internal discipline of doing before narrating. The audience is a check on your reasoning, not a source of your conviction.

I hold firm on the strategic core: information is a resource, and disclosed information is a resource you no longer control. The decision to make your process public should be made with the same deliberateness you would bring to any resource allocation.

Where I have moved: Seneca's warning about audience capture is not merely philosophical but strategic. An audience that begins to shape product decisions is a constituency that has been granted influence it did not earn and is not accountable for. The founder who has optimized for engagement has, without intending to, added a third party to every product decision. That third party cannot be fired, does not understand the business model, and will not share in the consequences of the decisions it influences.

The single most important thing you must take away: before sharing anything, ask whether the information gives a competitor an advantage that exceeds the community benefit it returns to you — and ask whether the audience you are building can be kept in an advisory role rather than allowed to become a directing one. The moment the audience's approval begins to feel necessary, it has crossed from distribution tool to governance problem.

I have argued throughout that the deepest risk in building in public is not strategic exposure but psychological corruption — the gradual replacement of the work's substance with the work's narrative. I will stand on that point.

But I want to add one practical observation. The founders who build in public successfully — who use it as a genuine distribution mechanism without losing themselves in the audience — share a characteristic that has nothing to do with their strategic sophistication. They are already building something they believe in completely, with or without the audience's attention. The public narration is not the source of their conviction. It is the record of a process that would have happened regardless of whether anyone was watching.

This is not a quality you can fake. The audience can sense the difference between a founder who is sharing because the work demands sharing and a founder who is building because the sharing demands something to build. The former creates genuine community. The latter creates an audience that cannot convert, because it was never attracted to the product — it was attracted to the performance.

The single most important thing you must take away: before you build in public, ask honestly whether you would keep building if no one were watching. If the answer is yes without hesitation — share freely, use the audience as a check on your reasoning, and let the community form around the real work. If the answer requires a moment of thought, the audience is already doing something to your conviction that you should understand before you cultivate it further.

All three minds converged on a critical distinction: building in public is not a policy but a series of deliberate decisions about what to share, when, and for what purpose. The question for each piece of information is whether sharing it returns more value in community, feedback, or accountability than it costs in strategic exposure or psychological dependency. Most founders can answer that question clearly for most information once they are forced to ask it precisely.

All three also agreed that the early stage — before a strategic position has been established, before a competitive advantage has been identified — is the moment when building in public is most likely net positive. There is nothing strategically significant to reveal, and the community that forms around early-stage transparency can become the first constituency that determines whether the position is worth fighting for.

The deepest tension in this debate is not the one Machiavelli identifies — strategic exposure — but the one Seneca names: the corruption of wanting. Aurelius and Machiavelli debate whether to share information and how to select what to disclose. Seneca raises the prior question: whether the audience has already begun to shape what you want to build before you have asked whether that audience represents the people who will pay for it.

Machiavelli and Seneca converge on a shared warning from different directions. Machiavelli warns that audience engagement is not market signal — the people who love your build-in-public content are not necessarily the people who will buy your product. Seneca warns that audience approval, once sought, becomes necessary — and a founder who needs the audience's approval to feel confident in the work has substituted the wrong signal for the real one.

Aurelius holds that strong internal character is the corrective to both dangers. Seneca responds that the character must be established before the audience is cultivated, because the audience trains the nervous system faster than reflection can correct it.

Before committing to building in public or staying private, answer three questions with honest specificity.

Would you keep building if no one were watching? This is Seneca's test, and it is the most important one. If the answer is yes without hesitation, you have the internal source of conviction that public transparency requires. If the answer requires thought, understand what role the audience is already playing in your sense of progress before you formalize that relationship.

Who is your audience, and are they your market? Building in public creates leverage only when the people watching are the people who will use, buy, or refer your product. If your audience and your customer are different populations, transparency generates goodwill in a community that does not convert. Engagement is not validation. Map the overlap before investing further.

What information creates competitive advantage if revealed? Make a concrete list: your specific technical approach, your key acquisition channels, your pricing experiments, your distribution hypotheses. Everything on this list should be kept private or shared only at a level of abstraction that returns community benefit without disclosing the mechanism. Everything off this list can be shared freely.

• This week — Before your next public post, write down the underlying work that the post will describe. If the work is not complete, complete it first. If the narration is easier to produce than the work, you have identified the corruption Seneca describes.
• Within two weeks — Separate your information into two lists: what you can share freely without strategic cost, and what gives a rational competitor advantage if disclosed. The first list is your building-in-public content strategy. The second is what you protect.
• Before committing to a regular public build log — Identify whether the audience you are building or would build has meaningful overlap with your target customer. If yes, invest further. If not, redirect the time to channels with higher conversion.

The primary risk Machiavelli identifies is real in competitive markets: building in public when you are contesting an established position with well-resourced competitors who have teams monitoring the space is a different calculation than building in public as an indie founder in an underserved niche. Know which situation you are in before treating the strategy as universally safe.

Seneca's warning is the most important long-term risk: audience dependency is a slow corruption that is easy to miss because each step feels like community-building and growth. The test is not whether you have an audience — it is whether you could stop sharing tomorrow without losing confidence in what you are building. If you could not, the audience has already taken something it should not have.

Aurelius identifies the internal corrective: the discipline of public accountability is valuable only when it is grounded in a private discipline that the audience reinforces rather than replaces. Build that internal discipline first.