Documenting BlackSwan So It Outlived the Solo Designer

Being the only designer on BlackSwan created an obvious organizational risk: everything the platform knew about its own design could walk out with one person. Good documentation was how I de-risked that for the team. The Design System was the anchor — not just a component kit, but the record of the decisions behind it, so future designers and developers inherit reasoning, not just pixels. The surface that needed documentation most was the Risk Engine. When you turn PEP/sanctions thresholds, module weights, and geographic rules into an auditable decision system, the rationale behind each rule and drill-down matters as much as the UI; without it, the next person rebuilds blind or, worse, breaks the audit trail. So I documented the four-engine structure, its states, and the intent behind the configuration model. Across Explore, the Entity page, the Dashboard, and Horizon Scanning, I kept documentation consistent so onboarding a new contributor didn't mean spelunking through files. For a PMO, this is continuity insurance: the project's design knowledge lives in the organization, not in my head, and the next phase can start from where we left off instead of from scratch.