Skip to Content
Author's profile photo Juergen Jakowski

The difference between a product UX strategy and an enterprise UX strategy

When you read the title of this blog, you might wonder what the difference is between product UX strategy and an enterprise UX strategy. It is quite likely that you have never even heard of this distinction, though I believe it is important to talk about it.

The thing which inspired me most to write this blog was a great article by Jaime Levy posted in Linkedin, called “What is UX strategy?”. In this article, Jaime talks about how a good UX strategy can help to build a product. In her example, it is a consumer-facing website with a DB back end and a valuable information structure applied. The article also reflects on how important it is to not just know the users, but to really know what they want and what they need.

I fully agreed with what she said. At the same time though I had to admit that when I talk and blog about UX strategies, I’m talking about a completely different animal. Why is this?

It’s quite simple because there are two different parties out there talking about the topic of “UX strategy” from completely different perspectives. When I talk about UX strategy, I mean the strategy that an enterprise has to come up with in order to improve the user experience for their users in the company. When others like Jaime talk about UX strategy, they talk about creating consumable (software) products.

I think this motivates many discussions and complaints about user experience in enterprises, because these two worlds are often mixed up.

Another thing that ultimately convinced me to write this blog was when I met Dan Barton and Gilson Teixeira from the SAP partner “BluestoneX”. They have put together some really good material about user experience strategies and often use the term enterprise UX. In the beginning, I was not sure about how introducing an additional name to the UX environment would make a difference. But in this post, I would like to show you that it actually does.


What is a product UX strategy?


Please let me quote what Jaime said, because this really hits the nail on the head:

“UX strategy is the process that should be started first, before the design or development of a digital product begins. It’s the vision of a solution that needs to be validated with real potential customers to prove that it’s desired in the marketplace. Although UX design encompasses numerous details such as visual design, content messaging, and how easy it is for a user to accomplish a task, UX strategy is the “Big Picture.” It is the high-level plan to achieve one or more business goals under conditions of uncertainty.”
Jaime Levy

The major goal of a UX strategy made for the development of a product is to have a product with the best possible user experience. This user experience is required in order to increase both the adoption of the product and the happiness of the users.

Before we move onto discussing what an enterprise UX is, I would like to underline a very important point. In the case of a (consumer) product, it is the consumer, in other words the end user, who buys and/or adopts the product. As a result, the user selects a product that correlates with most of his/her needs. It is obvious that this user will be much happier based on this fact.

As we all know, SAP also develops products. To do this, SAP has its own SAP UX Strategy.


What is an enterprise UX strategy?


A key fact of users in an enterprise is that they usually don’t buy and adopt the software themselves. Instead, the choice of which software to use, and how to customize it, is made by others. In the worst possible case, the people who make this choice don’t consult in any way with the real end users.

But there are more facts to consider:

  • IT operation is based on an IT strategy, which ultimately serves a business strategy
    In each enterprise, there is (hopefully) an IT strategy in place. This strategy defines the enterprise-specific rules, regulations and goals, and sets the boundaries for the IT operation. I think the most obvious aspect of this is security. As an end user, you are normally not the best person to judge how a given software solution will impact the security of your enterprise’s IT environment.
  • IT operates a lot of products
    Usually, a set of software solutions is used in an enterprise in order to support the business in running its processes. Ideally (from my perspective as an SAP employee), this software is provided by SAP.  We can, however, assume that there is a larger set of SAP and non-SAP products being used together in a harmonious mix. Some of them might be integrated with each other. Some of them are on old versions that might not support the most recent enhancements. Others might be modern, but are connected with older systems that need to be updated first. I have to admit that the CIO of an enterprise has a huge task keeping track of all the dependencies in the enterprise’s IT landscape.
  • The CIO’s target is to support the business
    Another highly important point to consider when talking about enterprises is this: The ultimate target of almost every business is to make money. In an enterprise, the question of whether or not to make user experience a priority is a business decision. If you develop a product, user experience is without question a major driver of your success. Depending on the enterprise strategy, it is the business that decides the value of any investment. As people with an interest in UX, we will of course try hard day in day out to make the values of a good UX crystal clear. Ultimately though, neither we nor the end-users in the enterprise get to decide where investments are made.

An enterprise UX strategy has to consider the best possible user experience under specific conditions and boundaries related to the specific enterprise, its business strategy and its IT landscape.


Is a great user experience unimportant in enterprises?


Of course not. We know that there are a great many arguments for why UX improvements are of value for an enterprise.

With this in mind, I warmly recommend all CIOs to take a closer look into UX. If you are wondering why the software products you have adopted are not well accepted by your users, you probably have an UX issue.

So let me repeat my point once more: “User experience is important to every single enterprise”.


Creating a product versus extending a product


I trust that most readers are familiar with the general options for improving the user experience in an enterprise as illustrated in the graphic below:


We can assume that the majority of customers have chosen SAP because they were looking for standard software that helps them to make their business more efficient and profitable. Obviously, these customers are looking for SAP software that they can directly adopt. To customize the SAP software to specific business needs, they also accept to adapt it accordingly. Developing their own applications based on the given SAP platforms might not be an option for many.

As a result, it is fair to say that in most cases an enterprise UX strategy will focus pretty much on the improvement options “adopt” and “adapt”. The fact that SAP has won the Red Dot Award for its next generation SAP Fiori UX design concept demonstrates that adopting SAP software is a valuable and trustworthy path to improve user experience. There are also a number of tools, in particular SAP Web IDE and SAP Screen Personas, that easily support the adaptation of SAP software where required.

Of course, there are also customers who will agree to “developing” their own applications. In cases like this, the main driver will be that a suitable standard SAP application is not available to meet the customer’s needs. As this blog deals with the difference between enterprise and product UX strategy, it could be argued that developing an application in an enterprise is also a kind of software product development. While this is basically correct, I would add that this development also has to consider the boundaries of the enterprise and does not have the goal of creating a product as such (it will not be put on the market and be sold for example). It has the same purpose as all other investments in the enterprise: to improve the business.

I think it is fair to describe development in an enterprise as being an “extension”, as illustrated in the graphic below.



Why is it so important for us to grasp this distinction?


I believe it is important to understand that a UX strategy has two different flavors, driven by different business goals, visions and environments. This explains why product designers (and not just software product designers) sometimes don’t understand why a user environment for a business user is actually different. It also explains why (enterprise) users might think their SAP user interface is substandard and that we always need to consider the restrictions of a software solution before judging on the quality of a user experience.

I created the table below as a quick guide to the difference between the enterprise UX strategy and the product UX strategy. There are of course more aspects that could be added, but I think that I have covered all of the most relevant ones. Please let me know if you have a different view. Maybe we can use the comment section to discuss and improve this.



Does that mean that Design Thinking is not relevant for me in an enterprise?


I noticed in talks with customers that some of them are not particularly interested in design thinking. And I assume that some of you have noticed this too. But what does that mean for us? Is the bottom line of this that Design Thinking is not relevant?

In addition to this question, there is one statement that holds true in all cases: “You need to know your users in order to provide the maximum valuable environment for their work”.

As mentioned above however, most customers will look into their options to adopt a product or functionality first. In this case, I can understand that people are not greatly interested in working through a fully-fledged design thinking process. There are aspects of design thinking that make a lot of sense in this case however, example being building “personas” or performing “user research“. But again, whether to invest time and effort in this is a business/management decision.

In fact, it is clear in a product UX strategy that decision makers put as much effort as possible into understanding the user base. It is obviously ideal to involve end users in the process of designing the visuals and interactions, building prototypes and do lots of validations. Design thinking provides exactly this process.




When talking about UX strategies, it makes sense to make clear right from the start what the focus of the strategy is. Is the focus to develop a product or to improve the user experience in an enterprise?

In the context of SAP, you will find both aspects.

  • SAP develops products and therefore has its own product UX strategy, known as the SAP UX Strategy
  • Customers want to improve the way their end users experience the software and their whole working environment. In this case, an enterprise UX strategy is needed, also known as a Customer UX Strategy.

The separation into two aspects avoids miscommunication and misinterpretation, especially when people with a focus on a product UX strategy talk with people with a focus on an enterprise UX strategy. Both have different boundaries that define their vision and goals, and drive their decisions.


As always, I’m very keen to find out what you think. Let me know in the comments section!

All the best,

JJ (@JJComment)

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Alexandre Costa
      Alexandre Costa

      Nice article !

      Author's profile photo Jocelyn Dart
      Jocelyn Dart

      Hi Juergen

      In general I like how you have expressed this. 

      My one concern would be the notion that an Enterprise Strategy can somehow skip end user research and validation. 

      The sad reality at many companies is that their own organization often has far less understanding of their own end users than they think. Without doing at least some end user observation the risk is that organisations either:

      * solve the wrong UX problem, or

      * solve edge cases - failing to identify the UX that will deliver on promised business outcomes.

      This is especially true when with limited IT budgets CIOs need to decide WHICH UX should be adopted, adapted or extended first.

      We have tragically seen this too often at our customers where they prioritise

      adopting/adapting UX solutions that have limited business or end user impact over identifying UX solutions that actually deliver on promise to business, enterprise and end users.  Or worse where UX is overweighted with one-size-fits-all options that don't apply to the targeted role or task.

      There is a middle ground here between the extremes giving end users free reign and not talking to them at all. 

      Unless there are some attempts to cut through assumptions and preconceptions, my observation is that achieving promised business and IT outcomes is highly unlikely. 

      Likewise unless there is some form of end user representation or engagement, the opportunity to set expectations is missed, leading to lower than expected adoption and maverick behaviour.

      Your thoughts?



      Author's profile photo Juergen Jakowski
      Juergen Jakowski
      Blog Post Author

      Hi Jocelyn,

      I thought I do cover this in the section "Does that mean that Design Thinking is not relevant for me in an enterprise?".

      Also my statement "There are aspects of design thinking that make a lot of sense in this case however, example being building “personas” or performing "user research". But again, whether to invest time and effort in this is a business/management decision." is from my perspective a clear direction.


      Author's profile photo Juergen Jakowski
      Juergen Jakowski
      Blog Post Author

      I would like to add some additional view. 🙂

      I agree, if one wants to improve user experience, it is essential to know what the user needs and wants. I sometimes provide the example about a birthday present for my loved ones. Of course, I can buy my son just something and he might be happy because he just got something. But only if do listen to my son and if I do understand what he likes and wants the most, I'm able to provide the present with most positive happiness impact.

      Actually, what is important in the case of UX is already natural and very common to all of us in our private life environment.

      I also agree, that there are still many people out there who believe that UX is just a fancy topic of some designers. And yes, especially these people should be convinced to look deeper into the values of improving UX.

      And I do agree that many of the activities of an design thinking process and in particular user research make a lot of sense. Actually, I'm talking about that all the time. 🙂

      On the other hand, I don't want to preach this in each and every blog. Many of my followers went through these arguments already in my previous blogs.

      Another view I want to raise here. At least I also know customers who are aware of UX and its advantages, but still have to drive their business decisions differently. And this is for good reasons. Like with many things in life, there is rarely one answer that is right for all. 

      Again, please don't get me wrong. It remains that improving UX makes a lot of sense and the related activities do obviously provide a lot of value from my perspective. However, I want to keep realistic. UX is not the only important parameter for business and IT decisions. I'll keep convincing decision makers to invest into user centered improvement activities. Though I do accept if people decide differently at the end.



      Author's profile photo Jocelyn Dart
      Jocelyn Dart

      That's fair enough Juergen.  And agree that there are sometimes good reasons for making those sorts of compromises.  Especially in the early stages of a UX journey when negotiating between stakeholders.

      So long as when people make those compromises they are making an informed decision - i.e. they understand the risks associated with not involving end users. Especially the risks that the very business outcomes they are aiming for may not be achievable if the UX is misaligned to the user's context or motivations.   

      Which is what to me is the essence of your blog: it doesn't have to necessarily be consumer-grade UX, but the UX does need to support the business process and the business outcomes.  And you can only do that if the UX is effective for the end user too.

      I find as more people understand this they work to correct this regardless of their own corporate culture and politics. 

      For instance, I met with a consumer products customer yesterday who is an organization with no design thinking or UX culture.  He deliberately takes part in monthly factory induction training just to have an excuse to walk around the factory floor and observe what's happening with his users. He might spend 20 minutes chatting about fishing with one of the men, and then they might show him a problem they are having.  Often that problem is fixed with some simple adjustments, or it might bring to light a new use case.  In this way he keeps in touch with his end users and has a much clearer picture of what they need without having to explicitly ask what they want.

      It's these sorts of stories I'd really like to see more of - the pragmatic side of how do you actually make that enterprise UX strategy a reality - even when there are barriers to overcome.

      I really like your blogs and I think these are important discussions to have - there are so many SAP customers now trying to work through their UX journey. So please keep blogging.