The problem
Designing and delivering curated learning for many customers was spread across spreadsheets, decks, and separate trackers. Strategy work started from a blank page each time, project status was hard to see across customers, and there was no single view of what was delivered and what was pending.
What was built
One workspace, organized around three jobs. It grew out of working prototypes, and each area maps to a phase of the learning lifecycle.
Strategy: from data to a plan
- Data and signals. Users upload pathway reports and optional supporting files, so the analysis is grounded in real content, not a blank form.
- Business value. The customer, learning maturity, team structure, business priorities, and the measures under pressure.
- Roles and people. Who the strategy develops and where the gaps are.
- Alignment and design. Anchoring the strategy to initiatives, signals, and research, with the option to include Open Library pathways alongside the customer's own content.
Command: running the work
Catalogs are organized by customer, each with its projects, plus a queue of upcoming projects, reusable templates, and notifications. Team members work under their own profile, so tasks and mentions are personal.
Insights: seeing the portfolio
A roll-up across every catalog shows what has been delivered and what is pending, a weekly roadmap of tasks due across projects, and drill-downs into each catalog's team, projects, and people.
Product decisions
- Start from the customer's data. Uploading real pathway reports replaces guesswork and makes recommendations specific, including existing content to activate and gaps to fill.
- One workspace, one lifecycle. Strategy, delivery, and measurement share the same catalogs and projects, so nothing is re-entered.
- Templates for repeatability. Curation work that repeats becomes a template instead of a one-off.
- Portfolio view for leaders, task view for teams. The same data serves both, with a "due this week" list that keeps daily work visible.
- Prototype first. Each area began as a prototype, was used with real work, and only then became part of the product.
Skills shown
Product ownership from prototype to live product, workflow and information design, AI-assisted analysis, portfolio and status reporting, and designing for the people who run curation at scale.
Customer names and figures are intentionally left out of this case study.