… same discipline there as you do when you set a plan to launch a new feature or ship a new version. For us, we stepped back and “architected” our overall “product.” What language are we building in? What’s our system architecture? Who is designing the front end? Back end? Have we researched the best payments APIs? Swap out those words with sales/marketing terms and you’ve got it. Great product people architect the product first — then they build it.
But here’s the thing: it’s not enough. Editorial standards, metadata strategies, customer journeys, voice and tone guidelines, key messages, workflows and governance charts and audit criteria—they aren’t just one corner of a bigger puzzle. They are the puzzle. They’re what define how a business communicates—and communication is everything.