Architecture Decision Records for a Modernization Program
Overview
What this challenge is about.
Read 18 weeks of architecture-channel Slack history and 6 architecture-review meeting notes to inventory decisions already made. Backfill 12 ADRs using Michael Nygard's template, each covering one decision (e.g., 'we chose Kafka over RabbitMQ', 'we adopted Helm not Kustomize'). Set up the ADR repo (in the platform's Git org) with a pull-request-based review workflow. Build a 90-minute training kit and run it with 5 staff engineers. Deliver the ADR repo with 12 ADRs, the workflow documentation, the training kit (deck + exercise + facilitator notes), and a 4-page program memo for the chief architect.
The Brief
What you'll do, and what you'll demonstrate.
Stop architecture-decision amnesia on a 3-year modernization program by introducing ADRs, backfilling 12, and scaling the practice to 5 staff engineers.
Earning criteria — what you'll demonstrate
- Write ADRs that capture context, decision, and consequences rigorously
- Backfill historical decisions without rewriting history dishonestly
- Design an ADR review workflow that scales across multiple teams
- Train senior engineers in a new documentation practice
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.