{"version":"1.0","type":"rich","provider_name":"Acast","provider_url":"https://acast.com","height":250,"width":700,"html":"<iframe src=\"https://embed.acast.com/$/68357ec21b846c88bdcd7480/68e3e847d17b81f346e7b927?\" frameBorder=\"0\" width=\"700\" height=\"250\"></iframe>","title":"123: Unpacking the Go-To-Market Sprint","description":"<p>You've got a brilliant idea. Everyone agrees it could work. So why has it become the project nobody wants to hear about anymore?</p><p><br></p><p>We dissect our Pitch Provocations method and package it up as a Go To Market Sprint that compresses 12 months of market learning into 3 weeks. </p><p><br></p><p>We use a real agency case study to work out how to explain what we do (and realise we forgot to check how the story ended). This is strategy consulting behind the scenes: the wrestling match between method names and outcomes, the challenge of writing your own testimonials, and the uncomfortable question of whether \"go-to-market\" really means anything much to anyone.</p><p><br></p><p>Plus: an unexpected musical interlude courtesy of a mobility scooter with a sound system.</p><p><br></p><p>Some of the stuff we talk about:</p><p><br></p><ul><li>How good ideas turn into millstones and what can break the cycle</li><li>Why traditional market research creates reports nobody acts on (and what works instead)</li><li>The 12-month learning compression: how Pitch Provocations actually delivers on this promise</li><li>Micro-projects vs. mega-builds: throwaway experiments that people actually want to do</li><li>Customer interviews as enjoyable therapy sessions (both sides enjoy them)</li><li>Why Go To Market means different things to a startup founder vs. a corporate messaging lead</li><li>The estate agent's gambit: give away an 80-page instruction manual and see who still hires you</li><li>How to get teams generating their own ideas instead of nodding politely at yours</li><li>You can't write the ending of a case study if you don't know how it actually turned out</li><li>Common sense thresholds: when does a micro-project stop being micro in your context?</li></ul><p><br></p><p>The bit about us being bad at this:</p><p><br></p><p>We struggle in real-time with packaging our own work, forget to follow up on crucial details, and can't quite nail whether we're selling a method or a result. It's real, it's rambling, and if you've ever tried to explain what you do for a living, you'll recognise the feeling.</p><p><br></p><p>For consultants packaging expertise, product teams sick of \"build first, ask later,\" and anyone who suspects their next big project might quietly become the thing everyone dreads discussing.</p><p><br></p><p>References:</p><p><br></p><ul><li>Pitch Provocations (Crown &amp; Reach) - intro in episodes 007-009: https://shows.acast.com/triggerstrategy</li><li>Multiverse Mapping - https://multiversemapping.com</li><li>The \"4U\" framework: Unpack, Undergo &amp; Unfold Uncertainty</li><li>Ritual Dissent (Dave Snowden) - https://cynefin.io/wiki/Ritual_dissent</li><li>Innovation Tactics deck (Pip Decks) - https://pipdecks.com/products/innovation-tactics</li></ul><p><br></p><p>Contact:</p><p>tentacles@crownandreach.com</p>","author_name":"Tom Kerwin"}