NorthBridge Coverage Workspace
A public-safe reconstruction of a private-capital coverage portal, rebuilt from archival wireframes, meeting notes, specs, and prototype artifacts. The prototype shows how a deal professional moves from signal triage to company context, from meeting note to follow-up task, without losing the thread.
The design challenge was not to make enterprise work feel simpler than it is. It was to give fast bearings inside a dense workflow so the next action is defensible, traceable, and captured in context.
The original program redesigned an internal portal used to track companies, activities, tasks, notes, and relationship context across a private-capital workflow. The problem was not a lack of data. It was that the existing tooling made deal work slower: too much hunting, weak orientation, and too little connection between the thing a user just learned and the next action they needed to capture.
The archival record is unusually strong. The wireframes show a full five-module system, a reusable component vocabulary, and dated iteration across multiple rounds of refinement. That makes this reconstruction useful for a portfolio in a very specific way: it can demonstrate real enterprise product structure without relying on confidential UI or unsupported claims about shipped outcomes.
This is not a speculative redesign. The original wireframes already proved the module architecture. The reconstruction proves that the workflow still stands up when it is staged as a live, guided operator session.
One Critical Path, Not A Feature Tour
The archive is broad enough to support dozens of entry points, but a portfolio prototype only earns attention if it makes one business case quickly. Here the guided path starts on My Coverage, drills into a live company record, opens the latest meeting note, converts that note into a follow-up task, and returns to the dashboard with the system visibly updated.
That path matters because it proves the product is connected. The dashboard is not decoration, the company page is not a dead profile, the note is not a text blob, and the task is not a detached to-do. Each surface hands context to the next one.
1. See The Signal
My Coverage surfaces a meaningful update tied to investment-committee preparation, so the user starts from urgency rather than from generic navigation.
2. Enter Company Context
The company workspace acts as the organizing object: overview, activity, note, and task context all stay attached to the same entity instead of scattering across pages.
3. Work Inside The Note
The note tabs show structured working memory: summary, details, fund interest, and linked tasks. The note is where diligence context becomes operational follow-through.
4. Close The Loop
A follow-up task is created in context, then reflected back in the dashboard queue and activity stream. That visible state change is the proof that the workflow has memory.
The SAP Fiori direction is deliberate. It provides a current enterprise grammar for dense work: shell bar, dynamic header, object page structure, calm surfaces, and explicit hierarchy. The guided tour carries the explanatory layer so the interface itself can stay terse, operational, and closer to how real internal tools behave.
Guided tour available · SAP Fiori reconstruction · simulated data
The prototype is intentionally narrow. It does not try to recreate every archival screen. It proves one believable working session in under 90 seconds: notice something important, open the relevant company context, capture the next step where the evidence lives, and confirm that the system now reflects the decision.
That is the right scope for a portfolio insertion. The archive carries the breadth. The live prototype carries the behavioral proof. Together they show how historical enterprise design work can be reconstructed honestly: preserve the information architecture, modernize the visual semantics, and keep every public claim tied back to evidence.
Technical Details
- Single-file HTML prototype built for static hosting and WordPress iframe embedding
- SAP Fiori-inspired shell bar, dynamic page header, object-page structure, and guided-tour overlay
- Critical path modeled on the original workflow: coverage review → company context → note to task → workflow confirmation
- Notes workspace includes summary, details, fund interest, and tasks tabs based on archival module behavior
- Simulated company, activity, note, and task data with obfuscated institutional framing
- Source hierarchy grounded in wireframes, meeting notes, specs, and prototype artifacts from the original engagement
- Iframe resize messaging added so the prototype behaves cleanly inside the portfolio page shell
- No backend, auth, API, or confidential production data required for the demo
This showcase is a portfolio reconstruction based on archival design evidence from a private-capital enterprise portal. Company names, activity details, and records are simulated or obfuscated. The workflow structure and design logic are authentic to the original engagement, but no confidential client interface is reproduced verbatim.
What This Demonstrates
Enterprise UX is not about reducing complexity until the work becomes generic. It is about structuring dense operational context so a user can move faster without losing the argument behind the decision. This piece demonstrates how dashboards, object pages, notes, and tasks can behave as one workflow instrument rather than as disconnected modules.
It also demonstrates a second skill that matters for senior portfolio work: reconstruction discipline. Historical work can be made legible in the present without fictionalizing it. The archive provides the proof, the prototype provides the behavior, and the case study makes the reasoning visible.
Volatility Surface
A linked options-trading workspace that turns a 3D volatility field into slice, grid, spread, and strategy decisions.
View case study →
HR as DJ
A workforce planning interface that makes staffing uncertainty visible as a capacity distribution.
View case study →