Post by Anding & Company

A tool chosen by IT alone rarely meets business needs. A tool chosen by business alone is rarely implementable at scale. Two cardinal mistakes happen at the start of most transformations. The first: programs launch without understanding the underlying business processes. Team and org changes get debated without the underlying change in delivery processes or capabilities. The second: IT is brought in only after target processes and operating model have been shaped, handed a "requirements list" with no chance to shape it. Both errors compound. By the time IT engages, the cheapest decisions have already been made – and the expensive rework has just begun. Start with the business process. Bring IT in early. Lay the foundation by understanding the business processes and how the transformation will reshape them. Where needed, spend two to four weeks documenting as-is processes pragmatically, with adjacent business and supporting functions, to diagnose pain points accurately. Then bring IT in early and actively to shape target processes. When IT co-owns the target state, implementation friction drops and costly rework is avoided. To build that shared ownership, we run Campus Mode: five to ten key stakeholders from different functions problem-solving together two to three full days per week. It feels like a stretch to dedicate that much capacity. It pays back: stakeholders who go through Campus Mode save up to 40% of the alignment and course-correction time later. Read full paper here: https://bit.ly/TrafoPE #PrivateEquity #Mittelstand #Transformation #ChangeManagement #OperationalExcellence #PostMergerIntegration