Dr. Russell Gomersall
While talking to customers preparing for their HANA journey, I often hear a commitment from the IT departments to involve the business. To a point, everyone agrees that it is inevitable. However, the question of when and how to involve the business is disputed. It is obvious that the business will have many questions, while the project management will not be ready to give answers, yet. Open points during the project inception will involve aspects such as brown vs. greenfield, budgets, duration, and approach.
This often leads to procrastinating to involve the business. Sometimes, there is a 'shadow project' for preparation. This neglect of open communication frequently results in duplicate efforts with business and IT initiating parallel investigations that are hard to merge later on.
I suggest involving the business as early as possible.
Open communication is key, and identifying and involving key stakeholders from both sides will work better the earlier you join forces with them.
It is advisable to set up your own 'business readiness' stream with clear objectives to gather relevant information on current strategic guidelines, operating models, and an inventory of related end-to-end scenarios and their business processes.
As the basis for decisions on brown vs. greenfield, an analysis of pain points and key requirements is essential to effectively challenge the status quo and identify value drivers for the HANA initiative.
Besides gathering crucial information as input for planning and early decisions, timely activation of the business will have a fundamental, positive impact on change management during your project.
So, if you haven't involved your business yet, I suggest you start tomorrow and set up your first alignment.
As bpExperts, this is what we focus on. Using Business Process Management as a true management methodology, we help introduce a process-centric approach, bridging the gap between business and IT, as well as between strategy and operations.
We care, we act, we deliver.