Refresh a Decade of Tangled Architecture Documentation
Overview
What this challenge is about.
Refresh a Decade of Tangled Architecture Documentation. Intermediate challenge in design. Designing real products under real constraints, earn a blockchain-v...
The Brief
What you'll do, and what you'll demonstrate.
Ten years of accreted, untrustworthy architecture documentation must be consolidated into a coherent C4 + arc42 + decision-record set that lets a new hire ramp in one week, with a maintenance playbook that keeps it from rotting again.
This is not a design exercise. It is the work a product designer does between a brief and a shipped interface. That distinction matters to every hiring manager who has seen candidates redesign Spotify's homepage and none who have worked under real product constraints.
When you finish, you will have something most graduates do not: a real-world deliverable, verified by Ewance, that you can show to a hiring manager and say "I did this. Here is the proof."
Earning criteria — what you'll demonstrate
- Audit and triage legacy documentation against an accuracy standard rather than preserving everything
- Model a real system across C4 levels while keeping diagrams internally consistent
- Produce a complete arc42 overview that a newcomer can read end to end
- Capture load-bearing decisions as Architecture Decision Records and design an index that stays current
- Design ownership and cadence so technical documentation survives organizational drift
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Aligned coursework coming soon.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
- Architecture Documentation
Apply architecture documentation to solve real industry problems and demonstrate production-level capability.
- C4 Model
Apply c4 model to solve real industry problems and demonstrate production-level capability.
- Arc42
Apply arc42 to solve real industry problems and demonstrate production-level capability.
- Architecture Decision Records
Apply architecture decision records to solve real industry problems and demonstrate production-level capability.
- Diagramming
Apply diagramming to solve real industry problems and demonstrate production-level capability.
- Developer Experience
Apply developer experience to solve real industry problems and demonstrate production-level capability.
Careers
Career paths this challenge builds toward
Completing this challenge demonstrates skills that transfer directly to these roles:
Systems Architect
This challenge mirrors the core architect duty of making a complex system legible: you model it across C4 levels, write the canonical overview, and capture the decisions that shaped it, exactly as an architect joining a legacy platform must.
This challenge sharpens
- c4-model
- arc42
- architecture-documentation
Developer Experience Lead
By cutting new-hire ramp from six weeks to one, you practice the developer-experience craft of reducing onboarding friction through well-structured, maintained documentation and curated reading paths that scale across a growing engineering organization.
This challenge sharpens
- developer-experience
- architecture-documentation
- diagramming
Technical Documentation Architect
Designing a maintenance routine, ownership model, and decision index trains the documentation-architect skill of building systems that keep knowledge accurate over years rather than producing one-off documents that quietly rot.
This challenge sharpens
- architecture-documentation
- architecture-decision-records
- diagramming