Boundaries
Separate content when audience, owner, lifecycle, or risk is meaningfully different.
Home / Workspace design
Information architectureGive every connection an intuitive home.
We design the vault, folder, entry, naming, and ownership system that makes RDM predictable as teams and infrastructure change.
The shape of the work comes first.
We observe how operators search: by customer, environment, location, platform, service, responsibility, or task. The design uses the most stable distinctions and avoids deep trees based on temporary org charts.
Vocabulary
Define names, tags, fields, and descriptions that match operator language.
Maintenance
Give creation, review, correction, and retirement to known roles.
What the blueprint includes
Decisions are recorded with examples and the reason behind them, so future administrators can evolve the system without starting over.
- Vault and top-level folder map
- Entry naming grammar and required context
- Template families for repeated connection types
- Ownership and lifecycle responsibilities
- Pilot migration and validation sequence
Findability test
| Task | Design question |
|---|---|
| Find a known server | Can operators recognize its name and likely location? |
| Find any tool for a service | Do tags and descriptions support exploratory search? |
| Choose between similar entries | Is authority, environment, and owner visible? |
| Retire a system | Can maintainers locate dependencies and accountable owners? |
Design FAQ
How deep should folders be?
Only as deep as users can predict. Search, tags, and well-formed names often outperform an elaborate hierarchy.
Should we import everything?
No. Pilot representative, owned, current entries first. Importing obsolete or ambiguous inventory makes a new workspace feel old immediately.
Sketch one representative vault.
Bring 30–50 entries and the people who use them.