The question is simple: what role does feedback play in shaping your marketing strategy? The answer from this founder is equally simple and unequivocal. Not a lot. Not quite a bit. Everything.

That single word reframes how to think about every launch decision. It means no amount of internal planning, polishing, or team alignment replaces the signal you get when a real customer touches your product. The rest of this walkthrough unpacks exactly what acting on that belief looks like in practice.

This team has given their philosophy an official name: Just Get Embarrassed. It is not a casual attitude. It is a documented, named approach they apply consistently to every new program, tool, or feature in their marketing platform and learning management system.

The operating procedure is direct. When something new is ready to ship, they ship it. No extended QA cycles aimed at perfection. No waiting for a clean, polished experience. The discomfort of a rough launch is treated as an acceptable and expected cost, not a problem to be engineered away before anyone sees the product.

This matters because the alternative, waiting until you feel proud of what you are releasing, systematically delays the only feedback loop that can tell you whether the thing works at all.

The practical execution of Just Get Embarrassed includes a specific communication move: tell the audience upfront that it might break. The speaker's phrasing is exact: launch it with a whole new class and tell them, it might break, we're sorry, we're trying this.

When something does go wrong, and they assume it will, the response is not defensive. It is: thank you for your feedback, followed by a fix. That sequence, transparency before launch plus gratitude after breakage, converts what would be a bad customer experience into a productive feedback exchange.

This approach works because it sets the correct expectation. Customers who know they are in an early version of something are far more forgiving and far more specific in their complaints than customers who expected a finished product and got a broken one.

The speaker states this as an explicit instruction, not a suggestion: we don't try to avoid getting embarrassed, we don't try to avoid someone having something go wrong or break. The double statement is deliberate. Both avoiding personal embarrassment and avoiding customer-side failures are named as things they actively choose not to pursue.

The mechanism they use instead is transparency. Being open about the fact that something is new and imperfect means the team does not need to spend energy managing appearances. That energy goes into fixing what breaks instead of preventing anyone from seeing it break.

The underlying logic: the attempt to avoid embarrassment is what creates the delay. Every extra sprint of polish before launch is, in effect, a vote against getting real data faster.

The speaker frames transparency not as a PR strategy but as a response to a fundamental reality: you really have no idea what's going to work until it touches a customer. This is the reason behind everything else in this update. Every decision to delay, polish, or refine before launch assumes you already know what needs fixing. You do not.

Customer contact is not a final step in the launch process. It is the primary research method. What you build in isolation is a hypothesis. What you learn when a customer uses it is data. Those two things are categorically different, and no amount of internal testing converts one into the other.

The speaker uses a specific hypothetical to make the principle concrete. Imagine you are going to sell glasses. Your plan is to sell red glasses. The moment you can get those glasses made in red, your job is to try to sell them. Not to perfect them. Not to add more options. To try to sell the version that exists right now.

Then a customer responds: they're great glasses, but they're made of plastic. You now know something you did not know before. You do not like plastic red glasses. Move to glass. That feedback loop, launch the red plastic version, hear the plastic objection, pivot to glass, is faster and more accurate than any market research that tries to predict what customers will say before they have held the product.

The speaker's phrasing captures the cadence: as soon as I can get these glasses red, I'm going to try to sell them. The word as soon as is doing the real work. Not eventually. Not once they are perfect. As soon as.

The instruction here is stated plainly: do not sit back and wait to get your product right. The alternative the speaker prescribes is to want to be in front of customers and to want to be trying to sell all the time. Not sometimes. Not when the product is ready. All the time.

Selling continuously is the mechanism. Every attempt to sell a rough product either succeeds, which proves the product works, or surfaces an objection, which tells you exactly what to fix next. Both outcomes are useful. Sitting back and refining produces neither.

The speaker puts a number on the problem: most entrepreneurs and marketers, by most I mean 90 percent or more, or startups, they spend far too long trying to get something right before they get in front of a customer. The qualifier matters. This is not a vague majority. It is 90 percent or more, drawn from the speaker's direct observation across their career.

The timeline they describe is also specific: days, weeks, years too long. The fact that they list all three is the point. For some people this delay is a few days of unnecessary polish. For others it is a years-long refinement cycle that ends with a product built entirely on assumptions, delivered to customers who were never consulted at any stage.

Both extremes are the same mistake at different scales. The fix is identical regardless of scale: shorten the distance between your current state and a real customer interaction, then shorten it again.