06 - QA Consultation

An honest look at your QA process.

A 2-week paid diagnostic of how your QA is actually running - not how it is supposed to run. You get a written report with findings and a prioritised action list. No upsell.

Request a consultation
Overview

A diagnostic, not a sales call. We review what you have and tell you what is actually wrong.

Most QA problems are not caused by a lack of testers. They are caused by unclear scope, inconsistent process, poor bug filing standards, or coverage that does not match actual risk. This engagement is a 2-week diagnostic of your current QA setup.

We review your existing process documentation, sit in on a test cycle, interview your leads, and read your recent bug reports. Then we write up what we found and hand it to you with a prioritised list of what to fix and in what order.

This is a fixed-fee engagement. There is no discovery call designed to sell you a larger retainer. If the findings point to us being the right team to help, we will say so - but the report stands on its own regardless.

We have run this diagnostic for studios about to hire a full internal QA team, for publishers who felt their vendor was not performing, and for developers who had cert failures they could not explain. In each case the problem was visible in the first week.
Deliverables

What you receive at the end of the two weeks

  • Written diagnostic report: findings, root causes, severity
  • Prioritised action list - what to fix first and why
  • Coverage gap analysis against your current title and stage
  • Bug filing audit with specific examples and recommended standards
  • Process notes from the observed test cycle
  • 30-minute readout call to walk through the report
Process

How the two-week diagnostic runs

01

Brief & kickoff

You send us what you have: process docs, test plans, recent reports, cert history if relevant. We read it before we speak to anyone. Kickoff call is a structured interview, no slides.

02

Review & interviews

We go through existing documentation and conduct short async interviews with your QA lead and, if applicable, the dev-side PM. We are looking at the gap between stated process and actual practice.

03

Observe a cycle

We observe one active test cycle in real time - attending your standups or reading your session logs, depending on how your team works. We note what the process looks like in practice, not on paper.

04

Report & readout

You receive the written report before the readout call. The call is for questions, not for us to read the document to you. Everything is in writing. You keep it and can act on it without us.

Ready for an honest assessment of your QA process?

Request a consultation All services