Get a fact-based answer to what is working, what is blocked, and the shortest credible path to release.

In seven days, I assess one launch-critical web-app journey and deliver: • Current-state evidence and a blocker map • UX, accessibility, loading, error, and retry review • Completed-versus-unfinished work inventory • Prioritized release plan with acceptance criteria • Final walkthrough and go/no-go recommendation

Where relevant to the agreed journey, I also review API responses, authentication and owner-access boundaries, data relationships, and failure/retry behavior using authorized read-only evidence or staging tests with synthetic data. Findings distinguish verified behavior from untested areas. We select the relevant checks within the one-journey scope and confirm inputs, access, price and timing before starting.

Scope: one product and one core journey. I work with read-only, staging, sandbox, synthetic, or redacted data. Do not send production credentials or regulated customer data in chat.

Not included: implementation, a full rebuild, penetration testing, compliance certification, or production data migration. If the diagnostic confirms a bounded fix, I can propose a separate five-day rescue sprint.

The linked example is an original fictional engineering study, not a client engagement.