RFI 269888
Engage with all recommendations on one page
Every Start, Continue, and Stop recommendation with its bottom line. Vote with a single tap, or open the comment bubble to read and join the discussion.
Sign in to vote, comment, or build your own response.
- START 1Start: Classifying work with a horizons model, and creating a new CMS support capability for Horizon 3 (actual ecosystem transformation)
The bottom line
Transformation work needs its own home at CMS.
- START 2Start: Focusing intently on reducing the lead time to learn
The bottom line
States wait too long to learn what works.
- START 3Start: Pushing decision authority to the people closest to the work
The bottom line
The people doing the work should decide how it gets done.
- START 4Start: Preparing for AI-built software as a transformation driver
The bottom line
AI will soon build what states buy today.
- START 5Start: Making procurement reform a first-class element of the standards program
The bottom line
Procurement may be the long pole
- START 6Start: Filtering vendors on demonstrated performance, not proposals
The bottom line
Judge vendors on what they do, not what they say
- START 7Start: Making production-like testability a definition of done
The bottom line
Nothing is done until others can test against it.
- START 8Start: Funding small and deciding often
The bottom line
Learning what doesn't work, quickly, is the best way to get it right
- START 9Start: Providing the central infrastructure only the federal government can provide
The bottom line
Only the federal government can solve identity.
- START 10Start: Running end-to-end slices in protected environments, and letting standards emerge from what they teach
The bottom line
Protect horizon 3 work and prove the future through end-to-end slices
- START 11Start: Putting policy change on the table as part of Horizon 3 transformation
The bottom line
Modernizing systems without touching policy only automates yesterday's rules.
- START 12Start: Treating security as a machine-speed problem
The bottom line
Security can no longer be a point-in-time test. It has to be a way we operate.
- CONTINUE 1Continue: Supporting outcome-based certification, extended further
The bottom line
Certify against outcomes people actually feel.
- CONTINUE 2Continue: Supporting state flexibility and novel approaches
The bottom line
State flexibility works, so make it safe to use.
- CONTINUE 3Continue: Enforcing the CMS intellectual property model
The bottom line
Build trust and ownership in government by working in the open
- STOP 1Stop: Forcing solution and execution decisions to come from people far from the work
The bottom line
Stop deciding delivery far from the work.
- STOP 2Stop: Calling systems products
The bottom line
The product is the service, not the system.
- STOP 3Stop: Using enterprise architecture frameworks and MITA as the definitional frame for transformation work
The bottom line
MITA can map the present, not chart the future
- STOP 4Stop: Misusing modularity
The bottom line
Modules that cannot be swapped are not modular.
- STOP 5Stop: Building procurement on the assumption of upfront correctness
The bottom line
Procure for learning, not prediction
- STOP 6Stop: Treating standardization and COTS adoption as the transformation lever
The bottom line
Buying COTS is not transformation.
- STOP 7Stop: Using standards compliance as a barrier to entry
The bottom line
Compliance gates keep capable builders out.
- STOP 8Stop: Mandating adoption. Build something worth adopting instead.
The bottom line
Build things states would choose
- STOP 9Stop: Fighting Conway’s Law
The bottom line
IF THE ORGANIZATION DOESN'T CHANGE, NEITHER WILL THE ARCHITECTURE, NO MATTER WHAT THE STANDARD SAYS.