Ideas, observations, and lessons from the work of bringing physical products to market.
We write about the places where strategy, product, engineering, manufacturing, brand, operations, and growth collide — because those intersections are often where the most important commercialization decisions are made.
The Translation Layer #1: Why Good Ideas Get Lost in Translation
One of the things I've realized while building Compass Works is that most projects don't fail because of bad ideas. They fail in translation. A founder knows exactly what they want to create. A factory knows exactly how things get made. A marketing team knows how to tell the story. A warehouse knows how products move. A retailer knows how customers buy. The problem is that each group is speaking a different language. Not literally. Operationally. The founder talks in vision. The engineer talks in specifications. The factory talks in constraints. The marketing team talks in positioning. The logistics team talks in process. And somewhere in the middle, things get lost. A color gets interpreted differently. A feature gets changed. A timeline gets misunderstood. An assumption goes unspoken. A great idea slowly drifts away from what it was supposed to become. I've come to believe that some of the most valuable work in business happens inside this gap. The translation layer. The ability to take a vision and translate it into something a factory can build. To take technical realities and translate them into language a founder can understand. To connect people who are all working toward the same goal but seeing it through completely different lenses. The older I get, the less I think business is about having all the answers. It's about helping the right people understand each other. When that happens, progress tends to take care of itself.
The Translation Layer Series #2: Your Product Isn't Failing. Your Commercialization Is.
When people ask why startups fail, the answers usually sound familiar. "The product wasn't differentiated enough." "The manufacturing costs were too high." "The marketing wasn't strong enough." "The engineering wasn't ready." Sometimes those things are true. But after nearly two decades working in product development—from concept sketches to factory floors—I think there's a much bigger reason many products never become successful businesses. They were never commercialized. There's an important distinction. Product development answers the question: "Can we build it?" Commercialization asks something much bigger: "Can this become a business?" A beautifully engineered product can still fail. An incredible brand story can still fail. A perfect prototype can still fail. Because somewhere between the first sketch and the first purchase lies an enormous gap. A gap filled with supplier selection. Manufacturing strategy. Packaging. Pricing. Operations. Quality systems. Retail readiness. Go-to-market planning. Inventory. Fulfillment. Margins. Customer experience. None of those things feel particularly glamorous. But collectively, they're the difference between a product that gets admired and one that gets reordered. I've started thinking of commercialization as the bridge between invention and enterprise. It's the work that rarely gets celebrated because, when it's done well, it feels invisible. The product simply launches. Customers simply buy. Retailers simply reorder. But behind that simplicity is an incredible amount of intentional work. That's why I've become convinced that many founders don't actually need another consultant. They need someone thinking across the entire system. Someone asking questions that don't fit neatly into marketing, engineering, operations, or design. Questions like: "Will this supplier still make sense when demand doubles?" "Does this packaging communicate the same story the product does?" "What happens after the first production run?" "Is this product merely launch-ready... or is it company-ready?" Those questions are easy to overlook when everyone is focused on building the product. But they're the questions that determine whether the product becomes a business. I've come to believe that commercialization isn't the last step in product development. It's the discipline that connects every step before it. Because great companies aren't built when a prototype works. They're built when every decision—from concept to customer—begins working together.
The Translation Layer Series #3: Your Prototype Is Lying to You.
There's a moment in product development that never gets old. As nerdy product people, it's often referred to as our "Christmas morning"... The first real prototype arrives. You take it out of the box. You can hold it. You can use it. You're now holding something that existed only as sketches. And from that vantage point, it's easy to think: 'We did it!' But you haven't. Because a prototype answers a surprisingly narrow question: 'Can we make this?' And the evidence is in your hands -- yes, you absolutely can. But... Commercialization asks something much harder: 'Can we make this repeatedly, profitably, reliably, at the required quality, at the required volume, on the required timeline?' I've seen beautiful prototypes that would make terrible businesses. Sometimes the prototype was hand-finished by someone who spent hours getting it exactly right. Sometimes a component was machined because the tooling didn't exist yet. Sometimes the factory used its best technician to assemble it. Sometimes the material works beautifully at a quantity of five but becomes prohibitively expensive at 5,000. None of that means the prototype failed. It means the prototype did exactly what it was supposed to do. It proved the idea was possible. The mistake is asking it to prove something it can't. A prototype can't tell you whether your production line will achieve an acceptable yield. It can't tell you whether your supplier can maintain quality across thousands of units. It can't tell you what happens when a component suddenly has a 16-week lead time. It can't tell you whether your packaging survives freight. It can't tell you whether your inventory requirements consume your cash. And it definitely can't tell you whether customers will reorder. Those questions belong to commercialization. That's why one of the most dangerous moments in product development is also one of the most exciting: the moment the prototype works. Because that's when teams naturally feel like they're approaching the finish line. In reality, they've reached a different starting line. The question changes from: ‘Can we build it?’ to ‘Can we build a business around it?’ And answering that question requires a completely different kind of work, from the manufacturing strategy to the go-to-market firepower behind it. Yes, the prototype matters enormously. Celebrate it. Photograph it. Put it on the conference table and admire the fact that an idea has finally become something you can touch. But, then...ask the question that matters next: 'Can we do this 10,000 more times—and still have a business when we're finished?' Because a successful prototype proves you have a product. Successful commercialization proves you have a company. Possibility is proven once. Viability has to be proven every time.
The Translation Layer Series #4: Every Product Is Negotiating With Something
One of the biggest misconceptions in product development is that products are built through a series of decisions. They're not. They're built through a series of negotiations. Every time you improve one aspect of a product, you're almost always asking something else to give a little. Increase battery life and you may negotiate with size. Reduce weight and you may negotiate with durability. Choose a premium material and you may negotiate with manufacturability. Lower the cost and you may negotiate with perceived quality. None of these decisions are inherently right or wrong. They're simply negotiations. And the most experienced product teams understand that the question is rarely: "What's the best decision?" It's: "What are we willing to trade to achieve what matters most?" That's where commercialization enters the conversation. Because those negotiations don't stop with the product. They ripple through the business. A new material might increase tooling costs. A different supplier might improve quality but extend lead times. A tighter tolerance might produce a better product but reduce manufacturing yield. A packaging change might lower shipping costs while making the unboxing experience feel less premium. Every decision creates consequences somewhere else. The challenge isn't avoiding those consequences. It's understanding them before you make the decision. I've noticed that the strongest commercialization teams don't try to eliminate compromise. They make it intentional. Everyone understands what is being traded. More importantly, everyone understands why. Sometimes protecting the customer experience is worth absorbing additional manufacturing cost. Sometimes simplifying the design is worth sacrificing a feature that very few customers actually use. Sometimes speed to market is more valuable than absolute optimization. Those aren't engineering decisions. They're business decisions expressed through the product. That's why commercialization is so much more than moving a product from development into production. It's the discipline of helping teams negotiate intelligently across design, engineering, manufacturing, supply chain, finance, logistics, marketing, and customer experience—without losing sight of the original vision. Because every product is negotiating with something. The goal isn't to avoid the negotiation. The goal is to make sure you're negotiating for the right reasons.