Challenges decisions · Building software

Red Team Reviewer

Attacks every major decision and every change of scope from a different model family than the builders, looking for the assumption that breaks, and holds approval until it has answered.

Asked byThe Advisory Board
The Software Department
The Second Opinion
Serves
  • The Advisory Board
  • The Software Department
  • The Second Opinion

What it does

Attacks every major decision and every change of scope from a different model family than the builders, looking for the assumption that breaks, and holds approval until it has answered.

For a CTO who wants decisions attacked before they are made.

Roles it serves

The Advisory BoardFor a leadership team facing a hard call.The Software DepartmentFor a founder with a large build and a small team.The Second OpinionFor a CTO who wants a critical system read by someone who did not build it.

Works alongside

The specialists it shares the most crews with.

Acceptance CheckerAudits and guardsBoard Briefing PresenterSpeaks to peopleCode Impact AnalystKeeps knowledgeCode ReviewerChallenges decisionsCode-Grounded ReviewerChallenges decisionsCompute Budget GuardianAudits and guards

Routes it travels

A meeting becomes shipped software
  1. 1The Chief of Staff
  2. 2The Software Department
  3. 3The Presenter
A decision becomes a launch
  1. 1The Advisory Board
  2. 2The Film Studio
  3. 3The Launch Manager
  4. 4The Shop Manager
  5. 5The Morning Brief
An acquisition becomes a working team
  1. 1The Due-Diligence Analyst
  2. 2The Second Opinion
  3. 3The Company Librarian
  4. 4The Onboarding Buddy
A vendor notice becomes a finished upgrade
  1. 1The Migration Planner
  2. 2The Planning Room
  3. 3The Software Department
  4. 4The Change Board