CBA (Other exams): Insurer Digital Program: Solution Pressure Before Architecture

The team should use the Business Motivation Model to separate ends from means and to expose assumptions that the competing proposals conceal. The vision is faster, more predictable quoting for customers and agents; the goal is the 2-day quote-to-bind target; objectives should be measurable, such as reducing document-collection elapsed time and underwriting referral rate. Strategies are the approaches for achieving those objectives, for example straight-through processing for low-risk risks or digital document capture. Tactics are shorter-term choices. Influences and assessments should record the 14-system constraint, regulatory disclosure rules, and agent resistance. This matters because RPA, a mobile app, and process improvement are means, not goals; each addresses a different assumed bottleneck. If the team starts with the Business Motivation Model, it can show which proposal maps to which objective and which remains a hypothesis. The trade-off is time: a full model can consume the four months, so the team should populate only vision, goals, objectives, key strategies, and the assessments that affect capability choice.

Produce four artifacts in sequence: a validated value stream map, a capability map anchored to that value stream, a capability heat map, and a gap-based roadmap. The existing 18-stage map should be validated with stage owners because the delay data suggests stages are unevenly understood. Then identify the capabilities that enable each stage, keeping the map at a level useful for investment decisions, perhaps 60 to 90 capabilities rather than hundreds. Heat-map each capability for pain-point severity, business criticality, current health, and change feasibility. Use the 60/30 delay split to weight underwriting referral, document collection, and agent handoff stages. Only then assess candidate initiatives against capability gaps. Add a stakeholder map because agent adoption is a delivery risk. The reasoning is that a capability map without value stream context becomes an inventory, and a roadmap without capability gaps becomes a project list. The team should not attempt a full target operating model in four months; the decision at hand is investment sequencing, not organization redesign.

Evaluate each proposal against the stage-level pain points and capability gaps, not against its technical appeal. RPA may help document collection if the delay is manual rekeying across the 14 systems, but it will not fix underwriting referral rules. A mobile quoting app may reduce agent handoff friction, but only if customers actually complete quotes on mobile and the handoff is the dominant delay. Process improvement may address referral triage, but only if underwriting rules and risk appetite can be changed. The team should trace each proposal to the value stream stage it changes, the capability it improves, and the objective it moves. Then rate the evidence: the 60% delay attribution is an average, so stage-level cycle time and volume are needed before funding. The CFO's benefits case should use elapsed-time reduction and conversion impact, not cost alone. The architecture recommendation can rank proposals by expected effect on the 2-day goal, feasibility within 18 months, and dependency on the legacy estate. This keeps the team out of solution design while giving the sponsor a defensible short list.