Rapid Health Check Report· Northwind · RHC-0482 · Operational (3pp)
← Back
Mantis QAExecutive Summary
RHC-0482 · Northwind01 / 03
PRODUCT QUALITY AUDIT FOR NORTHWIND

Rapid Health Check Report

ClientNorthwind
Date14 May 2026
PlatformsWeb · iOS
RunRHC-0482

Executive Summary

PREPARED BY MANTIS
Audit scope01
  • Core flows — Checkout, Billing, Onboarding, Dashboard empty states
  • Methods — Exploratory testing, UX review, regression gap analysis
What we found02
Critical02
High07
Medium09
Low05
23 issues+ 11 UX observations
Overall release risk03
MediumHighest risk concentrated in checkout, billing, and onboarding recovery flows.
Top concerns04
  • Two release-critical issues in checkout and billing
  • Weak error and recovery states in onboarding
  • Regression blind spots around billing & trust-sensitive flows
Recommended next step
  • Fix critical checkout and billing issues first
  • Improve onboarding recovery states
  • Add lightweight regression protection for the most sensitive flows
Mantis QAFindings & Risk
RHC-0482 · Northwind02 / 03
SECTION 02

Findings, risk & gaps

Key findings

04 OF 23
01
CriticalPayments / Checkout
Checkout fails on retried 3DS challengeWhy it mattersA broken retry state can block purchase completion in a revenue-critical flow.
02
CriticalAccount / Billing
Account deletion leaves orphaned billing recordsWhy it mattersCreates billing integrity risk and should be resolved before broader account lifecycle changes.
03
HighOnboarding
Onboarding step 3 has no error recovery pathWhy it mattersUsers are not clearly guided when they hit invalid or incomplete input, increasing drop-off risk.
04
HighDashboard
Empty-state copy implies misleading data lossWhy it mattersCurrent messaging can create unnecessary alarm and reduce trust in dashboard behavior.

Where risk is concentrated

A
FlowCheckout
FlowBilling
FlowOnboarding recovery

UX & trust observations

B
  • 01Checkout confirmation lacks enough reassurance after sensitive payment actions.
  • 02Onboarding recovery states are too weak in moments where users expect explicit guidance.
  • 03Dashboard empty-state language can be interpreted as destructive or alarming.

Regression gaps

C
  • 01Billing flow lacks reliable repeatable regression protection.HIGH
  • 02Checkout retry states are under-protected.HIGH
  • 03Onboarding error paths are not consistently validated before release.MED
  • 04Dashboard edge states appear under-reviewed.MED
SUMMARYThe product currently depends too heavily on ad hoc manual validation for several trust-sensitive flows. That creates false confidence and increases release risk.
Mantis QARecommended Next Steps
RHC-0482 · Northwind03 / 03
SECTION 03

Recommended next steps

Fix now01
THIS WEEK · CRITICAL
  • Resolve checkout 3DS retry issue
  • Fix billing & account deletion integrity issue
  • Improve onboarding recovery and error messaging
Next sprint02
2 — 3 WEEKS
  • Re-test checkout, billing, and onboarding after fixes
  • Define a small smoke layer for the highest-risk user journeys
  • Tighten validation around empty / error states
Recommended pathA focused follow-up sprint to fix the most important issues and establish lightweight regression protection around checkout, billing, and onboarding.
Optional Mantis follow-up
ARetest after fixes
BFocused follow-up sprint
COngoing QA support
SHARED ISSUE TRACKERDetailed issues & evidence
Detailed bug reports, reproduction steps, screenshots, and supporting evidence are available separately in the shared issue tracker. The PDF is the executive layer — the tracker is the operational layer.Open Trello board
END OF REPORTRHC-0482 · Northwind · 14 May 2026
Book a Fit Call
Rapid Health Check Sample Report | Mantis QA