North Bridge

A connected coverage workspace for private-capital investment operations. A coverage signal opens company context, a meeting note becomes evidence, and a follow-up becomes a tracked commitment.

Coverage UX
Notes-to-task
Enterprise workflow
Private equity and private credit
Audit trail
Regtech-adjacent

The dropped thread

01 · Failure context

Coverage teams at this private-capital firm were losing deal windows to fragmented tooling. Bankers hunted across legacy ERP screens for portfolio-company context, lost orientation between research and action, and then could not turn what they had just learned into a captured next step. A dropped thread was a missed window.

In private-equity and private-credit deal flow that loss compounds. The context is rebuilt from scratch on the next call, and the same research is repeated next quarter.

The archival record for this engagement is unusually strong. The wireframes show a full 5-module system, a reusable component vocabulary, and dated iteration across multiple rounds of refinement. That makes the case useful in a specific way: it can show real enterprise product structure without leaning on unsupported claims about shipped outcomes.

Role: Principal product designer. I shaped the signal triage, company context, notes-to-task loop, and confirmation path with product, engineering, and domain partners.
Approach: Treat the wireframes as source evidence. Preserve the homepage, company, notes, and tasks architecture, then modernize the surface with enterprise semantic grammar and a guided tour that explains the business case step by step.
Provenance: Reconstructed from the archival wireframes as a single-file HTML prototype.
Measurement: We never shipped a measured before and after. The engagement closed before instrumentation. That is an honest scoping statement, not a claimed result.

Close the context gap between signal triage and captured follow-up. Awareness, company context, action, and confirmation stay in one workflow, so every follow-up has an owner, a timestamp, and a source.

The 5 questions the workspace answers

02 · Scope

The workspace is scoped by the questions a coverage banker has to answer, in the order the desk actually hits them.

Which signals need attention right now?
What do we already know about this company?
What evidence did the conversation produce?
What is the next defensible action, and who owns it?
Did the action reach the shared operating view?

Question 5 feeds back into question 1: dashboard confirmation re-enters signal triage, so the critical path is a closed loop.

The Deal Thread Replay

03 · The spine of the product

A 90-second trace of 1 coverage signal becoming a defended action. The thread moves through 5 connected stages, and every stage leaves a trust anchor behind: a record the next person can read.

The thread as a flow is signal, context, note, task, dashboard confirmation. Each stage passes named fields forward to the next one, which is what stops the thread from decaying into private memory.

Coverage signal
Asks: is this company worth immediate attention? North Bridge starts the path from the signal, so the banker does not search from scratch. The signal arrives with company, stage, latest note, and decision window already attached.

Carries forward: company · stage · latest note · decision window. Trust anchor: signal source, timestamp, company, owner.
Company context
Asks: what do we already know, and what changed? Context sits beside the action path so research and the next step stay connected. The note list item links back to the company record that produced it.

Carries forward: linked company record · prior interaction · source-cell citation. Trust anchor: linked company record, prior interaction, source-cell citation.
Meeting note
Asks: what was learned in the conversation? Evidence is captured at the moment of work, before it can decay into after-the-fact CRM cleanup.

Carries forward: author · date · company · cited excerpt. Trust anchor: note author, date, linked company, cited excerpt.
Follow-up task
Asks: what happens next, and who owns it? Evidence converts into a task while the context is still visible on screen.

Carries forward: owner · due date · originating note · linked company. Trust anchor: task owner, due date, originating note, linked company.
Dashboard confirmation
Asks: did the thread reach the shared operating view? The action enters the shared dashboard as a tracked item, so the team can see the state change.

Carries forward: tracked item · owner · due date, back into triage. Trust anchor: activity feed, task status, audit trail, dashboard timestamp.

Dashboard confirmation returns to signal triage, which is what makes the replay a closed loop rather than a straight line.

Enterprise semantic grammar

04 · Interface language

The enterprise semantic grammar direction is deliberate. It provides a current enterprise vocabulary 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.

Each operator term maps through its domain meaning to a specific component pattern, so the interface speaks the vocabulary the desk already uses. Fiori is the reference point, and the grammar is applied to a modern component vocabulary.

Commitment: A legally binding pledge, expressed as a data table with a commitment tracker.
Drawdown: Requesting a capital release, expressed as an action button with an amount selector.
Capital Call: Invoking funding from LPs, expressed as a workflow card with status and an approval chain.
Exception: A breach of covenant or terms, expressed as an alert banner with resolution actions.
NAV: Net asset value per unit, expressed as a sparkline trend with a period selector.

The audit constraint

05 · What the design had to satisfy

The governing constraint was that every captured action had to stay bound to its evidence for audit: MFA, TLS, and SR 11-7-adjacent expectations for investment decisions. That constraint is why the workspace is a continuous relationship workflow rather than a set of screens.

Security and privacy: MFA, TLS, and audit-trail requirements for investment decisions.
Accessibility as risk: Missing access patterns become legal liability, not just compliance theater. Target’s $6M alt-text settlement is the reminder.
Unstructured data: Complex Virtual Data Room documents, financial models, and meeting notes required rapid parsing and traceability back to source.
Behavioral friction: Partners and associates accustomed to dense Excel and legacy SAP GUI layouts were resistant to consumer-style simplification.

4 pattern calls

I made 4 pattern calls on this workspace. The one that mattered most was binding every captured action to its evidence.

Flexible multi-pane layout

Preserves pipeline visibility alongside deal context and relationship intelligence.

Global search with dynamic inline filters

Placed in the enterprise shell bar. Transaction history and contact lookup are high-frequency actions.

Traceability anchors

Calculated metrics and notes link back to the source documents that produced them.

Source-cell traceability

A split-screen pattern with the extracted value on the left and the exact source evidence highlighted on the right. The notes-to-task loop is structurally analogous: captured evidence becomes defensible action.

Private-capital coverage is the setting, and the accountability loop is what carries. Any regulated workflow where a professional turns a signal into a captured, defensible action is the same design problem: surface the signal, hold the context, capture the next step, and leave an audit-ready record. That is the loop behind 15 years of my work in capital markets and regulated data products, and it is the same shape in deal-flow CRM, portfolio monitoring, spend operations, fund operations, wealth-ops advisor desks, and regtech case management.

Who reads the record

06 · Audience of the trail

A trust anchor only pays off if someone downstream can read it. These are the roles the coverage workspace has to serve.

Coverage bankers: Need fast triage with full context for the next call.
Senior coverage leads: Need pipeline health and decision signals they can act on.
Operations and compliance: Need source-to-task traceability for audit.
Product and engineering: Need a component language and clear separation of concerns.
New joiners: Need a discoverable mental model of the coverage workflow.
Risk and audit: Need documented decision evidence.

Trade-offs

07 · What was given up

3 explicit trade-offs shaped the final workspace.

Density over speed: Traded a calmer first load for density that the desk treats as credible, with legibility bought back through the semantic-grammar hierarchy instead. We considered a consumer-style card grid, which was the product manager’s first instinct for fewer fields above the fold, and rejected it after the coverage lead said partners read SAP GUI-density screens daily and a sparse surface reads as not serious.
Familiar grammar over a custom UI: Traded a fully custom interface for enterprise semantic grammar applied to a modern component vocabulary that reduces retraining friction.
Human validation over extraction speed: Traded automated AI extraction speed for data trust and auditability. Financial transactions require absolute accuracy.

Correction from the desk

The early working assumption was that partners wanted a calmer, simpler surface. The coverage lead’s SAP-density feedback reversed it. On this desk, density reads as credibility, so the layout was matched to the desk’s information metabolism rather than restyled away from it.

What the prototype proves

08 · Scope of the artifact

The prototype is intentionally narrow. It does not try to recreate every archival screen. It proves 1 complete 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. A guided tour is available inside it.

Underneath the connected workspace, 5 domain areas converge on 1 hub, and the hub drives the signal-to-action path. An operator moves from positions, transactions, obligations, exceptions, and documents into 1 coverage session, then forward through company record, meeting note, follow-up task, and the shared activity stream. The company object page brings context and action into 1 place: overview, notes, tasks, and activity share a single linked record.

Before

Fragmented legacy portal

The banker hunts across multiple legacy ERP screens for company context.
Orientation is lost between research and the next action.
What you just learned about a company never becomes a captured step.
A dropped thread is a missed deal window, and the work is repeated next quarter.

After

Connected coverage workspace

1 company object holds overview, activity, notes, and tasks together.
A meeting note converts into a follow-up task in context.
The dashboard queue and activity stream reflect the change immediately.
Every captured action stays bound to the evidence that created it.

What happened

The 5-module thread was the artifact that product managers and the coverage lead kept referencing in later sprint reviews, and the notes-to-task link became the standing requirement that survived into the next-quarter backlog. We never shipped a measured before and after. The engagement closed before instrumentation.

Stack and craft

Single-file HTML prototype with vanilla CSS and JavaScript. No framework, no build pipeline, no secrets in code.
Embedded as an iframe with a postMessage resize protocol.
Responsive from enterprise desktop to tablet widths, tuned for dense, context-rich workspaces.
WCAG 2.1 AA target: keyboard focus states, semantic landmarks, and contrast-checked surfaces.
Motion respects prefers-reduced-motion. Not a VPAT-certified product, a portfolio prototype demonstrating awareness.
Public claims are tied to visible product screens, notes-to-task flows, and the interaction model shown in the prototype.

Fig. 01 Coverage workspace

The thread as one workspace: signal, company context, note, task, and activity share a single linked record.

Fig. 02 Company object page

Context and action in 1 place: overview, notes, tasks, and activity on a single linked record.

What I would ship differently

09 · Next build

If I were building this for production today, 5 changes would come first.

Native build: Replace the iframe tour with a native React and TypeScript implementation, and make the Deal Thread Replay the default lens, not a sub-mode.
Source-cell traceability: Add a traceability layer modeled on Chronograph and Lumonic, so every summarized field links to the exact source cell that produced it.
Audit as an object: Move the audit trail from a footer artifact to the same UX weight as the company record. Auditability should be a property of every object, visible everywhere the object is used.
Human-gated copilot: Draft the follow-up task from the meeting note with an AI copilot, but keep human-in-the-loop validation as a hard gate. The trust anchor stays on the human.
Usability study first: Run a 5-user qualitative study against the new build before any A/B test. Per Nielsen Norman Group, 5-user studies surface most core flaws, and complex B2B flows need more.