December 16th (12pm EST) Ali Hanyaloglu, Head of Global Product Marketing at Akeneo, will be answering any questions on building a marchitecture. It's the last AMA of 2020 - ask away.

Hey Marcelina!

Thanks for your question. A perfect one to get started with!

I have seen a few different definitions for "marchitecture" or "marketecture" depending on who you ask. Frankly, I don't agree with many of them. It's not the abstract, marketing-friendly of an architecture - that's both over-simplified and somewhat patronizing.

My definition of a marchitecture is that it's a visual representation that can both explain what you do, how you do it and for whom, and inspire the viewer with WHY you are doing it.

Why is it gaining importance? Decision-makers are totally overwhelmed with information and marketing blurbs and sales pitches. And each one is beginning to sound like the other. And those decision-makers have less time on their schedules to have to sit down through a long presentation with slide after slide of text and numbers. A marchitecture is a great tool to be able to quickly, or in length, be able to explain who you are that is easier to digest and remember for the decision-maker.

Hope that helps!

Ali H.

Hey Paul!

Thanks for your questions. Ouch! I would never describe things that way, and if someone was using a marchitecture for that purpose they have other problems!

A great example of a widely-used marchitecture is from Salesforce. I will put a link to it below. You have probably seen it before. In one beautifully designed image you see the platform architecture, the applications built on it, and the use cases it was created for. It includes key parts of their technical architecture (i.e. CRM Data, Lightning), lots of things that aren't products per se but concepts (i.e. Einstein), products (Sales Cloud) and use cases (service, etc). It is used in many different places and versions in order to explain what Salesforce do and why they are an ecosystem unto themselves. It's super powerful, indispensable to Salesforce, their partners and customers, and clearly much more than a marketing exercise, as it's used in a technical architecture context.

https://trailhead.salesforce.com/en/content/learn/modules/starting_force_com/starting_understanding_arch

Hope that helps you overcome any objections.

Ali H.

Hey Sa!

GREAT question! Been there, done that, got the t-shirt.

Firstly, this is something that you ABSOLUTELY DEFINITLY POSITIVELY MUST get your company leadership behind. A marchitecture is essentially a visualization of how they talk about their company, their products and their vision, and how everyone else should be talking about it too. I am very proud of the work a group of us at Criteo did on a marchitecture and where it was used. But when the top leadership changed, the idea died very quickly when they weren't really supportive of the story behind it.

Secondly, get all your key stakeholders to be an input into it. Product marketing is said to sit at the nexus of product, sales, customers, and marketing. So leaders from each should have a say. And each one has a pain point with how the company offerings and story is told - whether that's sellers getting stuck explaining what makes your company unique, or marketers stuck on only wanting to market features. Start with that and how the marchitecture can be a way to address all those in a consistent and compelling way.

Ping me if you're still getting pushback!

Cheers,

Ali H.

1. Good ole pen and paper! Seriously!
2. Mind map
3. Some kind of digital whiteboarding tool that has some sharing or collaboration features, like Miro or Microsoft Whiteboard.
4. And test it over and over again!

Hey Robert!

Thanks for that! I actually had to look that one up: turns out it's "technical architecture". Someone just wanted their old technical architecture diagrams to have a cool name like the marketing people got to use! :D

To me a tarchitecture is what we typically think of a technical diagram used and loved by developers, architects and IT folks. You've seen them before: the classic stack diagram used by every IBM and Oracle rep for decades, or maybe the left-right data flow diagram. It's intention is to show how your product or solution works behind the scenes and what pieces make up that solution. Very hard to build, but easy to diagram.

A marchitecture is more of a story-telling device. In addition to some things from the tarchitecture, it can also explain WHY you do something and for whom. I am currently working on a marchitecture, and without giving too much away, it also captures the people and process involved in addition to the technology. This is much harder to visualize than a tarchitecture.

Hope that clears it up a little!

Cheers!

Ali H.

Hi Martha!

Thanks for your question. Lots to think about here, but a couple of pointers for you:

1. You need to make sure your differentiators are TRULY unique: is it something that only you can claim, could a 3rd-party verify that, and is it of value to the customer? Check all three and you have something that - for now - will be relevant.
2. With respect to demonstrating them, your goal should be to get an existing customer to validate those differentiators. We all want the customer testimonial that says "we had this problem before, and company x's product y was the only way to solve it." No-one buys bold claims from vendors anymore unless there is solid proof.

Good luck!

Ali H.

Hi Nick!

Fantastic question. I think my biggest challenge has been to avoid trying to capture everything in a marchitecture. It is very tempting to react to "well what about this offering, or what about this use case?" A marchitecture needs to beautifully simple but all-encompassing, if that makes sense? Or, it needs to be just enough to tell your story, help you stand out, and trigger responses where the viewer wants you to double-click down into details.

Another challenge? Try not to make it just about you and your company. But that's what we product marketers are here for, amiright? :)

Hope that helps.

Ali H.

Hi Jeremy!

Thanks for your question. Developing a marchitecture must be an inclusive and iterative process. Everyone from the CEO on down should feel like they are a part of this, and probably more than once. Don't land on a marchitecture based on consensus - it will be diluted, never finished, or both! Just bring in leaders from each of the key stakeholder groups - and that includes external parties like partners, analysts and customers. And each time you meet with them, paint a picture of how they could use and benefit from the marchitecture: a customer success manager can use it to help bring awareness to an existing customer of what else you do in context of what they have today, for example.

Hope that's helpful.

Ali H.

Hey Philip!

Great question! A couple of starting points:

1. Identify what challenges customer-facing teams, including marketing, have with describing your company's offerings and positioning. For example, maybe they can talk about your main product just fine, but struggle with explaining how you are part of a broader ecosystem.
2. Try giving an elevator pitch on your company using nothing more than a pen and paper/whiteboard. You will quickly realize where things can be simplified or filled in.

Good luck!

Ali H.

Hey Lisa!

Thanks for your questions.

1. As mentioned in another reply, I have been blown away by Salesforce's marchitecture. Not necessarily in terms of it's design, but the number of places and ways it has been used, and its longevity as well. It suits both the techie and business types. It acknowledges that there are gaps that can be filled as part of their vision.
2. Speaking of Salesforce, have you seen the "napkin marchitecture" drawn by Marc Benioff when he met then-CEO of Burberry Angela Ahrendts? There's a great story behind this, but Marc drew this vision for Burberry's digital transformation, and it included parts from his competitors at the time as he didnt have the products to address those gaps. What I took away from this is that a marchitecture can be bigger than your company's parts, and it should be used as a tool to paint a vision. It's said that Angela has that napkin framed in her office. https://www.slideshare.net/Helixa/burberry-the-digital-enterprise

Hope that helps!

Ali H.

Hey Alana!

Ah yes, the techie product manager. Ignore them. Just kidding!

What I find is if you bring in the people and process into the architecture, then it's not just a simple tech diagram. They aren't building tech for the sake of building tech: there are people involved, there are workflows and processes, not all of which your company's products are even a part of but still matter.

And bring in business needs and impact into that marchitecture too. In fact, I suggest starting your marchitecture right there, in the center of the visualization.

They will quickly realize the difference of a marchitecture vs a tarchitecture, why it's needed, and why product marketing is best suited to build these. But do include them still.

Hope that helps!

Ali "The Shopper is at the Center" H.

Hey Lukas!

Thanks for your question. So, I don't consider a marchitecture a strategy. Remember, it is a tool. A powerful one at that, if done and adopted well.

But to your question about strategies to take when embarking on a marchitecture project, I suggest the following:

1. Start with a specific business need in mind. For example, will this be used as a tool to enable sellers to be able to give more compelling and relevant pitches to higher levels in the target customer accounts? Or will it be used as a visual to describe new offerings that will be launched for analyst briefings. This way you aren't trying to boil the ocean, nor will it be just seen as a pointless marketing exercise!
2. Don't go in to with a specific layout or design in mind. I have been working on a new marchitecture and I started out with the classic stack diagram. I got stuck very quickly! Instead, I started just putting key points and concepts in a notepad and on sticky notes. From that I could organize and rearrange concepts until I had a connection between them that made story-telling sense. All I will say is that the new marchitecture I am working on is far from a typical stack diagram!

Good luck!

Ali H.

Hi Lauren!

Awesome question. Thanks!

Having been through this a few times now I have to say that building a marchitecture is something that should be done at the highest levels of the organization as possible, especially if your marchitecture is something that is going to represent your company, its offerings and beyond. This is something that you should be confident that your CEO could present to the board, key investors or your biggest customers. Having too many people involved risks diluting your story or delaying its release.

Having said that, your team should be part of this. Each product marketer should be able to take the marchitecture and tell the story with it in entirety, or how it relates to their areas of coverage. The marchitecture should also incorporate things like people and process, and your PMM team will know aspects and nuances that could be a part of the story.

Otherwise, see my previous answers about who should be involved, and treat the marchitecture as something that will be used by each of our direct stakeholders.

Hope that's helpful!

Ali H.