Consulting

On-Time Digital Transformations for COOs and CIOs

Independent analysis by Starro. Not client work.

Cubes moving along a track through four lit checkpoints

Objective

Why Large Transformations Overrun

Large IT projects often run over budget, run late and deliver less than promised. Hardware programs face the same risk and control it with four habits.

Our transformation is behind schedule and over budget. What would a hardware program do differently, and where would it save the most?

Findings

Four GAO Factors Built In, Five Checked at Gates

Each step maps to a documented systems engineering practice, and each gate resembles a NASA life-cycle review. Against GAO's nine success factors for major IT programs, the method builds in four directly: engaged stakeholders, users who help write requirements, users who test before acceptance, and ranked requirements. It checks the other five at the gates.

The paper ends with a ten-question health check for a program that is already running.

Matrix of GAO’s nine success factors for major IT programs against the four steps. Four factors are built in directly; the other five are checked at the gates.

Approach

Hardware-Program Practices Mapped to a Four-Step Method

We took four practices from the NASA Systems Engineering Handbook: testable requirements traced to design and test, a drawing of the system before build, reviews with entry and exit criteria, and verification evidence. We built them into four steps (Assess, Design, Build and Migrate, Verify and Hand Off) and walked a generic order-to-cash process through them.

Generic order-to-cash system drawing: CRM, ERP, warehouse, bank feed and reporting, with five numbered interfaces traced to requirements and tests. Illustrative, no client data.

Validation

Traced to NASA Practice and GAO Success Factors

How we checked the method:

  • Each step traced to the NASA Systems Engineering Handbook (NASA/SP-2016-6105 Rev 2).

  • Each GAO success factor (GAO-12-7) mapped to the steps that build it in or check it.

  • Every cited figure checked against its primary source by an independent reviewer.

  • Not tested on a client program for this paper; the order-to-cash example is generic.

Recommendations

Run the Health Check Before Adding Scope

The four habits add modest effort at the start and protect the late phases, where mistakes cost the most. If your program is already running, use the health check and fix the first "no" before you add scope or staff.

Tools used:

Process mapping; target-system architecture; requirements traceability