The Board Wants an App
A regional retailer with 22 stores and 8% online sales has seen footfall fall 4% year over year; three stores are loss-making. A competitor has just opened two automated dark stores in your catchment. The board has directed IT to build a mobile app and asked you to lead strategy analysis. Constraints: a 15-month budget cycle, an aging point-of-sale platform, only four IT staff, and customer satisfaction scores that are strongest for in-store service. Online orders currently require staff to phone customers back to confirm stock, and nobody can say how often an order is cancelled for that reason. The CEO wants a recommendation at the next board meeting.
1. What current-state analysis do you need, and how do you treat the board's direction to build an app?
Read the worked answer
The app is a proposed solution, not a business need, and strategy analysis begins by testing the need behind it.
Current state to establish:
- Internal: store-level profitability, POS capability and integration limits, inventory visibility across stores, fulfilment capacity, staff skills, IT capacity (four people is a hard constraint).
- External: competitor dark-store model, customer expectations on delivery and collection, local demographics driving the footfall decline.
- Assumptions and constraints, stated explicitly, including the unknown stock-confirmation cancellation rate.
Treat the app as a hypothesis. Reframe the question: what problem is the board responding to, and would an app address the cause? The unknown cancellation rate is a measurable gap that should be closed before committing budget, because if stock visibility is the real constraint, an app without it will simply move the phone call.
Present current-state findings before options so the board can judge the recommendation against evidence, not enthusiasm.
2. How do you define the future state and assess options and risks?
Read the worked answer
Future state should be expressed as measurable goals and required capabilities, not as a product. For example: raise online share from 8% to a stated target within 18 months, reduce stock-confirmation cancellations to a stated level, decide the future of the three loss-making stores, and build cross-store inventory visibility and a defined fulfilment model.
Options to assess, including the option of doing nothing:
- mobile app only;
- click-and-collect from existing stores using current inventory;
- partnership with an existing dark-store or delivery operator;
- in-store experience investment only.
Assess each on value, cost, feasibility against four IT staff and an aging POS, and risk. Risks worth explicit likelihood and impact ratings: integration failure with the POS, unfulfillable online demand, cannibalisation of store sales, loss of the in-store service advantage, and delivery economics.
Recommend rather than merely list. A shortlist with a reasoned recommendation and stated assumptions is what the CEO can act on.
3. What belongs in the change strategy?
Read the worked answer
The change strategy is how the organisation moves from current to future state; it is broader than the delivery project and much broader than the app.
Include:
- Scope of change: process, technology, organisation and skills, not just software.
- Transition states and sequencing: for example, pilot click-and-collect in a defined set of stores, measure cancellation and conversion, then scale. This also buys time within the 15-month budget cycle.
- Investment envelope and funding route, with what is explicitly not funded.
- Who leads the change and how decisions are made, given that IT has only four staff and the business must own the operating model.
- Capability and readiness: store staff performing fulfilment is a new role, and satisfaction scores suggest in-store service is an asset to protect.
- Benefit measures and review points, so the board can judge the strategy on outcomes.
Say plainly that the app is one component of the strategy, and that the strategy can succeed without it or fail with it.