ADI Workbench
The operating layer behind ADI.
This is where ADI stores its active engagement records, artifacts, standards, governance materials, and design decisions.
How ADI Organizes Work
Everything has a reason and a relationship.
ADI work is not organized as isolated projects. Each engagement is linked to strategy, business benefit, capability, ownership, scope, artifacts, and governance. Use this as the working model when scoping or documenting anything new.
Engagement Portfolio
Active work with relationships visible.
Each engagement is connected to strategic theme, business benefit, sponsor, owner, scope, and capability built.
| Engagement | Status | Strategic Theme | Business Benefit | Sponsor | Owner |
|---|
Artifact Library
Files with purpose.
Downloads are grouped here, but each one keeps its what/why/status context.
Governance & Standards
The control spine.
These are the source documents copied from the current ADI docs package. Some are draft or pending ratification; that maturity should remain visible.
Governance
Governance artifacts, registers, data dictionary, lineage, and operating charter.
Technical Standards
Draft technical standards, data warehouse model, and governance guide.
Analytics Standards
Placeholder for analytical output standards and decision-asset rules.
Work Instructions
Recurring procedures and handover-ready operating instructions.
Known Issues / Tech Debt
Place to capture limitations, workarounds, and follow-up needs.
Decision Log
Preserves why key decisions were made, not only what was decided.
Knowledge Base
Definitions tied to operating use.
Design Decisions
Why the site is designed this way.
Design Philosophy
The principles behind Experience vs Workbench, one-idea pages, and teaching-first writing.
Design Decisions
Decisions, alternatives, trade-offs, and review points.
Object Model
The relationship model connecting strategy, benefits, capabilities, engagements, and artifacts.
Content Guide
Writing pattern: what, why, without it, how, example.
For Future Maintainers
A capability should outlive its founders.
This workspace is intentionally designed so that ADI's knowledge, standards, reasoning, and decision assets remain available regardless of who originally created them. Institutional knowledge belongs to the organization, not to individuals — if you're picking this up new, start with Design Decisions and the Object Model above.