Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 

In practice, many businesses running SAP struggle with finding the optimal balance between systems adaptability with systems stability. Business wants changes fast. But also require stable systems to support executing their business processes. I’ve experienced the SAP department or CCoE is rarely perceived as a unit that propels business growth through swiftly adapting systems functionality to changed business circumstances. One to chew on?

Well, I believe some of the answers can be found in properly organizing for this.The challenge at hand thus is to design an organization capable of meeting the omnipresent business demand for both SAP agility and stability, while delivering best value for money and facilitating instant change. An SAP organizational unit capable of efficiently servicing, supporting, and maintaining SAP whilst also enhancing and further improving existing functionality and in parallel deliver projects. Now, how to design such an organization?

I've had the pleasure to be involved in answering this question on various occasions and here are 14 strategic design principles I believe to be essential in arriving at such a balanced SAP organizational unit or Competency Center, referred to by SAP nowadays as Customer Center of Expertise (CCoE):

• Consider the business as the customer with an IT demand, and IT as supplier

• Supply IT in an end-to-end business function oriented fashion

• Discriminate between a RUN, a CHANGE and a SERVICE function in IT

• Align between CHANGE and RUN through SERVICE

• Separate RUN from CHANGE on an operational level

• Keep accountability for RUN and CHANGE in one hand on a tactical level, through SERVICE

• Consider RUN and CHANGE to be delivery capabilities, fed by (strategic) portfolio’s

• Have well-defined operational and tactical touch points at the IT demand side for RUN, CHANGE as well as SERVICE

• SERVICE evaluates business value

• Organize for an overlapping hand-over between RUN and CHANGE – hit the floor running

• Operationalize SERVICE in customer-centric manner providing customers with the easiest possible access to the services

• Keep tooling assimple and intuitive as possible, but no simpler than that

• People are key, developing competences must have an explicit place in the organization

• Build in a continual improvement capability               

If you need to get better control over your SAP Solution Lifecycle, here's the key.

- Mendel

(published before on my personal blog)

Labels in this area