The relationship between three things
WHY our clients take on eCommerce projects - increase revenue, decrease cost, improve customer loyalty) and...
...WHAT we deliver on our projects (Omnichannel eCommerce [e.g. buy-online-pick-up-instore], eCommerce site, Mobile experience, Launch a site in new geographies, sell to new types of customers, sell more to existing customers, allow customers to look up their orders [customer self-service, myaccount], Sales Rep mobile application, eCatalog, Configure-Price-Quoting experience) and...
HOW to make that happen (HOW to make WHAT they want happen so they can achieve their WHY)...
-business requirements definition
-business process design
-product catalog taxonomy & migration
-user story creation
-user experience design
-infrastructure readiness and deployment
-mobile development/responsive design
-Agile implementation methodology
We want people to look at the graphic and see the relationship clearly between these three things. We also want them to understand that they may not want, care, or even need to know about all the "HOW" items but they are critical to them achieving what they want. i'd like to represent when items on the "HOW" list are not included in a project, they can't get from What to Why. I'd like to show risk of crossing that bridge or divide.