Only recently, I gave a lecture about data quality and master data management/governance for a larger audience. It was a not the first time that I presented the topic, and I started my speech as usual with common business needs for adopting a master data strategy and then moved to the SAP software portfolio that is set to tackle the challenge.

I began with SAP Data Services and Information Steward being the appropriate weaponry for data quality improvement and control, and then came to SAP Master Data Governance bringing in the process component ensuring sustained master data quality by involving predefined validations and putting the relevant data stewards in the driver’s seat.

The session went well, there was a lot of interest in the audience, and after the official Q&A part I was approached by a listener who stated that he liked the session overall, but was a bit confused by the product variety outlined in my presentation.

Well, I took the feedback… and forgot about it on my way home. It was only yesterday that this came to my mind again, and I started thinking about what the listener wanted to tell me. From an outside SAP perspective, the world obviously looks a bit different:

As a business or IT specialist in a company, if you are faced with data quality related business issues you want to:

  1. Be in a position where you can easily analyze and visualize existing data issues
  2. Be able to dig into the root cause, and be able to cleanse defective data
  3. Avoid in the long-term that such issues occur again

Actually the outlined SAP solution portfolio perfectly matches these needs, but the way data managers think starts with their needs and ends with a solution, not vice versa. So If I had told the story straight from a solution-oriented perspective and had come up with the associated software only afterwards, I guess the message would have been clearer.

It was really revealing how important it is to take the customers’ perspective to get the message across and not just by telling how great our products are.

Best,

Markus

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Neelesh Thackeray

    Hi Markus

    You have made a very valid point.

    Infact, it’s always better to follow a “top-down” approach. In other words – Customer / Business perspective (Top)  going down to the “appropriate” Technologies (Bottom) that will address their requirements.

    Excellent !!

    Regards

    Neelesh

    (1) 
    1. Markus Ganser Post author

      Hi Kiran,

      this was specifically drawn for an event in Germany (with German slides only). So, unfortunately I can’t share this deck.

      Best,

      Markus

      (0) 

Leave a Reply