Teams operating dozens of brand sites live across Google Analytics, PageSpeed, documentation wikis, changelogs, and ticket queues, one tab per question. Pandora’s Box asks: what if the portfolio had a home?
The challenge
Operating a large multi-brand portfolio fragments attention. Site status lives in one tool, analytics in another, performance audits in a third, design-system documentation in a fourth, and feature requests in chat threads that never reach the backlog. The cost is not just time, it is decisions made without the full picture.
- Site health, analytics, and performance data scattered across disconnected tools
- No portfolio-level view of which brands and markets a team operates
- Design-system documentation divorced from the sites that consume it
- Feature requests and feedback lost between chat, email, and tickets
How I approached it
I started from the questions operators actually ask each morning, “which sites are live, how are they doing, what changed, and what does the team need next?”, and structured the platform around them: My Sites as the entry point, Site Data per brand, Documentation and Release Notes for the system, and Ask Hermes for the feedback loop.
Mapped the daily operational questions and the tools currently answering each one
Designed the portfolio directory: every brand site with URL, operational status, market, and freshness
Brought Google Analytics, Lighthouse scores, and Core Web Vitals into one per-site data view
Embedded module documentation with code snippets and instructional video
Designed Ask Hermes, feature requests with votes, tags, and Jira IDs feeding future releases
Trade-offs
The hard part was scope discipline: a “single pane of glass” can swallow every feature ever wished for. The concept stays at pre-alpha scope on purpose, directory, data, docs, feedback, with templates and deeper automation marked as coming-soon rather than promised.
- Designing data density that stays scannable, vitals, scores, and trends without dashboard fatigue
- One mental model across very different content types: sites, metrics, docs, requests
- Role-aware views for admins and members without forking the interface
Final direction
A clean, light operations hub: a My Sites portfolio grid as the front door; per-site data combining Google Analytics, Lighthouse diagnostics, and Core Web Vitals assessments; documentation with live code snippets and video walkthroughs; release notes and changelogs; and Ask Hermes, where requests carry votes, tags, and Jira IDs so feedback lands in the backlog instead of a thread.
Outcomes
As a concept, Pandora’s Box demonstrates an operating model: portfolio teams get a shared source of truth for site health and system knowledge, and a feedback loop that closes. It is the operational companion to a multi-brand design system, the place where the system meets the sites that run on it.
A portfolio without a home page is a portfolio run from memory.
Internal tools earn adoption the same way products do: by answering the questions people actually have, in the order they ask them.