I’m preparing for an interview at an IT-Strategy consultancy and read through some material on IT strategy.
When asked to draft an IT strategy I would basically work through the following steps:
- Examine Status Quo (Processes, Governance, Sourcing, Infrastructure, Applications, Business-IT- Alignment, financials, obvious problems etc.)
- Check corporate strategy for boundary conditions, mission, challenges … for IT department to derive vision/mission
- Come up with an application strategy (which applications should be kept, changed, replaced/abandoned)
- Come up with a sourcing strategy (what services should be out- / insourced and how)
- Draft new (or changes to) IT organization, Governance
- Put all necessary tasks on a roadmap (based on priorities, dependencies etc.)
- Establish an instrument to track progress and effectiveness of all changes
Would that be a suitable approach?
However, my actual question is if this approach can be used to cover lots of different cases in an IT-strategy interview like
- Sourcing, e.g. Company XYZ asks you to check if outsourcing can help them to reach their goals
- Shall company xyz move their applications to the cloud?
- How could company XYZ reduce their (fixed) IT-costs
- How could company XYZ benefit from digitalization opportunities
- IT-Strategy for post-merger integration/ BU carve out
In my opinion all the steps above are required for these cases, it’s just the focus that changes. Would you agree or rather use separate, more individual frameworks for each case type?