Tool
UX Resource Compass: Who on the Team Has Room?
Used inside Salesforce, so there is no public demo. The notes below explain how it works.
The problem
Planning design work across releases lived in spreadsheets and status threads. A simple question, "who can take this project next release?", meant adding up weeks by hand and hoping the sheet was current.
System architecture & prompting
The first version was prompted into shape with Lovable, an AI app builder, then refined by hand in React and TypeScript.
- Load. Assignments come in as a JSON export, uploaded or pasted. They stay in the browser and are never sent to a server.
- Capacity. Each designer has about 13 weeks in a release window. Assigned weeks are added up, and a designer counts as full at 95% of that time or at five projects, whichever comes first.
- A written summary. Instead of one more chart, the top of the page says it in words, for example: "Team is balanced: 6 designers carrying 18 projects, no one over capacity", with chips for the next milestone and the busiest phase.
- Views. A schedule by designer, cards per person, and a timeline. Backlog improvements sit in their own tab.
Failure modes / edge cases
- Weeks hide switching costs. Five small projects cost more than their weeks suggest, which is why the project count caps capacity too.
- Data goes stale. The board is only as fresh as the last export, so every summary says when its numbers are from.
- Work with no release. Backlog improvements have no release, so they ignore the release filter and only follow the designer filter.
- The default view. Opening on every release at once buries the present, so the filter starts on the current release.
It runs on real team data, so it stays internal: no public demo and no screenshots.