Hi all!
1. What are typical ERP Cases, like how would an examplary prompt look like?
2. When the case is about coming up with a target IT architecture (e.g., PMI), what is the expected answer? Do they expect how the data would flow, like application layer or is it more about decommissioning redundant systems etc.
Thx
BCG Platinion - ERP Case & Target IT Architecture
Hi,
You can find an example of a BCG Platinion case that I wrote here:
https://www.preplounge.com/en/management-consulting-cases/candidate-led/advanced/bcg-platinion-retailcore-legacy-integration-414
I am quite familiar with BCG Platinion interviews and cases, so if you have any more specific questions, feel free to reach out via DM.
Best,
Franco
hi!
For ERP cases, the prompts are usually very practical. A typical ERP case prompt sounds like: “A client is replacing its legacy ERP with SAP S/4HANA. What should they consider, how would you structure the migration, and what risks do you see?” They want you to think about modules, processes, data migration, timeline, and change management, not deep technical configuration.
For target IT architecture cases (e.g., PMI), they don’t expect you to draw data flows or application‑layer diagrams. They want a business‑driven architecture: which systems to keep, which to decommission, how to integrate the two companies, what the core platforms should be, and how to reduce redundancy. Think in terms of capabilities, system landscape, integration approach, and high‑level sequencing.
Alessa
ERP cases usually come in three flavours. ERP selection, like SAP vs Oracle vs MS Dynamics for a manufacturer. ERP transformation business case, building the case for replacing a legacy system.
ERP implementation strategy, like big bang vs phased rollout across geographies. They test business framing, quantitative impact, and practical implementation thinking.
For target IT architecture cases, especially PMI, don't worry about data flow diagrams or application layer specifics. They want business-driven decisions. Think six steps. Understand the business strategy, assess current state, define architecture principles, identify what to decommission, sequence the roadmap, build the business case with quantified synergies.
Anchor recommendations in business outcomes, not technical detail. And show awareness of PMI pitfalls like data migration complexity and change resistance.
Good luck.
A quick follow-up q: When you say
"ERP transformation business case, building the case for replacing a legacy system."
How would the approach to such case look like?
Something like:
1. first analyzing the as-is (pain-points, etc)
2. target - such as potential benefits of the transformation
3. roadmap?
Would appreciate any feedback on this.
Thank you! BR