Untangling the Tech: organizing our digital infrastructure with Obsidian
One of the key challenges I've encountered is organizing our technology portfolio. Initially, it was likened to a plate of cooked spaghetti. However, I prefer to envision it as either a large pile of yarn or a collection of assorted threads:
To address this, I've collaborated across our organization to enhance the structure of our infrastructure. Figuratively, I want to arrive at something like this:
We're utilizing Obsidian to compile a dynamic and comprehensive technology portfolio. Currently, it enables me to trace any thread and understand its connections across our ecosystem, which includes people, platforms/software, servers, and various themes.
Moreover, I can examine specific groupings (such as archives, access services, data services) or themes (like transcription services or video platforms) to outline their scope. We're also using actionable labels such as things "we_host," "missing_info," or "decommission."
For instance, here is our initial archives footprint along with the corresponding technology stack. Each item on this list is linked to a detailed record:
We are in the midst of verifying the details for the various (100+) software projects/platforms we support. Once we've confirmed the basic information, we'll delve deeper into upgrades, integrations, APIs, and potential improvements for each item.
This overview will then be integrated into a roadmap using the Kanban plug-in within Obsidian, facilitating the creation of a multi-year, scalable, and shareable technology plan.
Visually, our goal is to transition into something like this:
I view this portfolio as a interactive communication and planning tool for our digital infrastructure.