ProductsMapPodCoverHow it worksAboutCareers

Products

Map, Pod and Cover

Cover is the destination: named business journeys, checked as the system changes. There are three ways to reach it, and the shortest is for the client who is already ready.

01The three products

What each one is for

The test manager is usually where this starts. Who signs differs: a sponsor above them for Map, a programme director or PMO for Pod, a platform or business owner for Cover.

02The routes

Three routes to the same recurring service

Three routes, all ending at Cover: direct to Cover; Map, then Cover; Map, then Pod, then Cover. Cover Direct to Cover Platform already live Map, then Cover Map Map, then Pod, then Cover Map Pod

Direct to Cover. The platform is live and you know which journeys matter. Cover’s onboarding builds the checks; no assessment first.

Map, then Cover. You need the business case before you commit. Map names the journeys and the order, and Cover picks them up.

Map, then Pod, then Cover. The platform is a new programme and the pre-production capability does not exist yet. Pod builds it; Cover maintains it once the journeys are live.

03Where to start

Which one is yours

The harness is never bought on its own. A Pod builds it during a programme; Cover’s onboarding builds it for a platform that is already live. Either way it is built in your test environment or CI — never in production.

Which business journey would create the greatest impact if it failed after the next release?