In-Role Platform Case Study
Capacity Planning Platform
A web-based operational platform built to help leaders visualize project capacity, forecast overload,
and rebalance work before assignment issues became urgent.
From scattered planning data to an operational platform
Leaders needed a clearer way to see capacity across teams, compare project load, and make assignment decisions
before workload issues became urgent. Existing planning details were spread across multiple spaces, which made it
harder to see overload risk, handoffs, and rebalancing opportunities in one place.
I built a web-based capacity planning platform that connected project planning data, manager views,
capacity forecasting, and rebalancing signals into one usable operating tool.
4manager orgs
5solution paths evaluated
2 weeksto functional prototype
Org-widescope expansion
What I owned
This project shows in-role ownership across stakeholder discovery, product thinking, workflow design,
data architecture, front-end development, API integration, visual design, and scope management.
Role
Discovery lead, product/workflow designer, prototype builder, integration partner, and scope manager.
Scope
Capacity model, monthly heat map, project sync, manager views, utilization rollups, overload alerts, and intake decision support.
Status
Functional prototype built in under two weeks, with scope expanded from a single-team tool to an org-wide initiative.
Capacity Planning
Operational Platform
Stakeholder Discovery
REST APIs
GitHub Enterprise
GenAI (Claude)
The problem to solve
Leaders needed better visibility.
Monthly planning required a clearer view of who was loaded, who had room, and where work could be rebalanced.
Capacity needed to be forecasted, not discovered too late.
The goal was to surface overload before it became urgent, not simply report on workload after the fact.
Different managers needed different levels of detail.
The platform needed progressive disclosure so leaders could start with a clear view, then expand into deeper planning detail when needed.
The workflow needed to connect back to project data.
The tool needed to support planning decisions without becoming another disconnected place to manually update project information.
How the work moved forward
I approached the work as an operational product build: clarify the need, test the solution path,
design the model, build the prototype, connect the data, and support broader adoption.
1
Led discovery
Worked with stakeholders across four manager organizations to define the capacity problem, planning needs, required views, and decision points.
2
Evaluated solution paths
Compared five possible approaches before selecting and building the path that best balanced speed, usability, integration needs, and future scale.
3
Designed the operating model
Created the interaction model, data architecture, and visual design system so the platform could support real planning decisions, not just display data.
4
Built the prototype
Built and deployed a functional prototype in under two weeks using HTML, CSS, JavaScript, REST APIs, GitHub Enterprise, internal enterprise hosting, and GenAI as an engineering partner.
5
Connected the workflow
Created an API integration with the team’s project management platform to support project sync and tie the capacity platform back to the operating hub.
What the platform included
The feature set focused on helping leaders see capacity, understand risk, and make better assignment decisions faster.
Monthly heat map
A 7-tier capacity color scale made load, overload, and expected utilization easier to scan and compare.
Portfolio rollups
Portfolio-level utilization views helped leaders understand load across teams instead of only one person or one project at a time.
Forward-looking alerts
Overload alerts and cross-team availability suggestions surfaced rebalancing opportunities before assignment problems became urgent.
Manager-specific views
Per-manager configurable views used progressive disclosure so leaders could see the right level of detail without one-size-fits-all clutter.
Allocation tracking
Multi-assignee support allowed independent allocation tracking so shared work could be represented more accurately.
Intake support
A priority scoring engine and contractor offload opportunity detection helped support better intake and assignment decisions.
A practical operating tool for better decisions
The result was a functional platform that helped leaders see project load, forecast overload, identify rebalancing opportunities,
and connect capacity planning back to the team’s project management workflow.
What changed
The work moved from scattered planning inputs toward a clearer operating model for resource allocation, capacity visibility, and assignment decisions.
What it demonstrates
This case study shows how I approach ambiguous operational problems: listen first, map the real workflow, test solution paths, build practical structure, and create tools that help leaders make better decisions faster.