Evidence-led recovery

Recovery scenarios

These scenarios show how a difficult technology situation can be investigated and what evidence should shape the next decision. They are explicitly illustrative and are not presented as completed client engagements or measured results.

How to use these

Start with evidence, not the proposed solution

Use the scenarios as a diagnostic starting point. Collect enough evidence to establish what is happening, where ownership sits and which decision is blocked before committing to a rebuild, supplier change, reorganisation or new delivery date.

Verified client case studies should only be published when the client context, Farhan Islam's exact role, actions taken and measurable outcomes are approved for public use. Until that evidence is available, ASKWHYWEB keeps illustrative material clearly separated from client proof.

Pre-engagement evidence checklist
  • What business outcome, customer journey or operational service is affected?
  • What evidence demonstrates the problem rather than merely describing it?
  • Which systems, teams and suppliers are on the critical path?
  • What has already been attempted and what changed afterwards?
  • Which decision is currently blocked, and who owns it?

Illustrative scenarios

Four common recovery situations

Illustrative Scenario

A software programme keeps slipping

Milestones move while teams report steady activity, and leadership cannot tell what is genuinely complete, releasable or still dependent on unresolved work.

Evidence to collect
  • Accepted scope compared with working software
  • Open defects and unresolved dependencies
  • Test, release and rollback evidence
  • Decision and supplier blockers
  • Recent delivery history against forecast
Method
  1. Build a current-state delivery baseline
  2. Separate completed work, work in progress and unknowns
  3. Identify the decisions that can change sequence or dates
  4. Reduce work in progress around the next usable outcome
  5. Agree an evidence-based recovery review rhythm
Potential deliverables
  • Current-state delivery view
  • Recovery scope and sequence
  • Named dependencies and decision owners
  • Release-readiness criteria
  • Leadership reporting view based on evidence
Software delivery recovery
Illustrative Scenario

Trading journeys fail across system boundaries

Checkout, payment, stock, order or fulfilment behaviour becomes inconsistent, particularly during change or higher trading volume.

Evidence to collect
  • One affected journey traced end to end
  • Payment and order reconciliation
  • Inventory or fulfilment exceptions
  • Relevant release and incident history
  • Supplier hand-offs and service ownership
Method
  1. Find the first incorrect or missing state
  2. Separate customer impact from downstream operational symptoms
  3. Map systems and suppliers on the failure path
  4. Clarify who can restore each critical stage
  5. Prioritise controls around trading-critical risk
Potential deliverables
  • Critical-journey risk view
  • System and ownership map
  • Stability priorities
  • Release and recovery checks
  • Peak-readiness actions where relevant
eCommerce technology leadership and recovery
Illustrative Scenario

Production responsibility is split

Development, infrastructure, QA and suppliers each own part of production, but recurring incidents expose gaps between those responsibilities.

Evidence to collect
  • Recent incident timeline
  • Release approval and rollback path
  • Monitoring and escalation signals
  • Service and dependency ownership
  • Prevention actions from previous incidents
Method
  1. Follow one release from approval to production
  2. Trace one incident from detection to recovery
  3. Identify decision-right gaps at hand-offs
  4. Define accountable service ownership
  5. Agree evidence required to release, escalate and recover
Potential deliverables
  • Service ownership model
  • Release-readiness criteria
  • Incident and escalation path
  • Observability priorities
  • Operational risk and follow-up actions
DevOps, reliability and production operations
Illustrative Scenario

A platform decision is blocked by conflicting advice

Internal teams or suppliers recommend different technical directions, while leadership cannot see which assumptions, constraints or trade-offs separate the options.

Evidence to collect
  • Business outcome the decision must support
  • Current system and integration dependencies
  • Operating and migration constraints
  • Cost, change and reliability implications
  • Evidence supporting each proposed option
Method
  1. Define decision criteria before comparing solutions
  2. Map dependencies and ownership boundaries
  3. Separate observed constraints from preferences
  4. Compare options against the same criteria
  5. Record residual uncertainty and what would change the recommendation
Potential deliverables
  • Decision options and trade-offs
  • Architecture or dependency map
  • Integration risk view
  • Phased change path
  • Decision record with remaining uncertainty
Architecture and integration advisory

Next step

Have evidence from a real situation?

Share the business impact, systems involved and the decision currently blocked. The first step is to establish what the available evidence actually supports.

Discuss a technology problem