Investor UX Redesign

Carta

InvestorUXRedesign

Redesigning Carta's investor experience into a clear fund-to-company information architecture

EnterpriseFinTechB2B

Role

Product Designer

Duration

2018 – 2020

Platform

Web · Enterprise SaaS

Team

2 PMs, 6 Engineers, Design System partners

Users

LPs, GPs, Investor Relations, Fund Ops

I led the Investor UX redesign across information architecture, navigation model, and high-density reporting surfaces spanning Funds, Companies, and detail workflows.

Overview

Outcome Snapshot

What shipped, why it mattered, and how impact was measured.

I redesigned Carta's investor experience around a strict hierarchy: account context, entity context (fund vs company), and task-specific detail views. The redesign connected conceptual IA work and production UI redesign so investors could scan fund health quickly, then drill into exact supporting data without losing context.

Investor users could access critical data, but the product had grown into disconnected surfaces. Navigation depth, entity switching, and inconsistent page structures made it hard to move from portfolio summary to decision-level details.

3-level

Navigation model

Fund→Company

Connected drill-down path

10+

Investor surfaces redesigned

Challenge

Powerful Data, Fragmented Investor Experience

Funds, investments, capital calls, and statements were all present, but not stitched into one coherent experience. Investors could see numbers, yet each area used different navigation and interaction conventions.

The core failure was context continuity. Moving from fund-level summaries to company-level detail required repeated navigation resets, slowing review workflows and increasing support dependency.

  • Fragmented IA: Similar investor tasks lived behind unrelated nav structures
  • Entity Switching Cost: Jumping from Funds to Companies broke user orientation
  • Inconsistent Drill-Down: Top-line metrics lacked predictable paths to source details
  • Operational Overhead: Teams relied on repeated manual checks to validate state
Investor service journey and operating model map
Service map used to align investor workflows across sourcing, performance tracking, and LP reporting

Architecture

Define IA Before Redrawing Screens

I treated navigation as core product logic, not visual chrome. The redesign established explicit navigation levels and standardized transitions between fund and company contexts.

Before UI polish, we mapped the entity hierarchy and defined drill paths so every key metric had a stable route from summary to evidence.

  • Level 1: Global account navigation (Home, Companies, Requests, Account settings)
  • Level 2: Entity-specific sub navigation (Fund tabs, Company tabs)
  • Level 3: Task details (capital call details, scenario modeling details)
  • Hierarchy Model: Firm -> Funds -> Investments with clear cross-links
Three-level navigation architecture diagram
Navigation architecture defining global, entity, and detail levels
Firm to fund family and investment hierarchy diagram
Entity hierarchy model connecting firm, fund families, and company investments

Redesign

Production UX Across Fund Overview, Performance, and Investments

Fund Overview was rebuilt into a summary-first page with critical fund health metrics, then direct pathways into performance and statements.

Fund Performance and Investments were redesigned with table-first, metric-dense layouts that matched investor mental models and reduced interpretation overhead.

Portfolio views introduced persistent side navigation for funds and companies so users could switch entities without losing overall context.

  • Summary-first modules for vintage, fund size, contributed capital, and invested amount
  • Consistent tabs for performance metrics and investment breakdowns
  • Persistent side rail for fast pivoting across funds and investments
  • Shared interaction patterns across overview, capital calls, and investment tables
Fund overview and performance redesign
Fund overview redesigned around summary cards and readable performance trends
Capital calls page redesign
Capital calls surface aligned to the same information hierarchy and status model
Investments summary and detailed table redesign
Investments summary and deal-level tables integrated under one consistent pattern
All funds view with side navigation and performance chart
All-funds portfolio view with persistent side rail and cross-fund performance comparison

UI System

Cross-Surface Consistency For High-Density Enterprise UI

The redesign also normalized top navigation, contextual tabs, and table controls across company-level and fund-level pages. This reduced relearning when users moved between workflows.

I introduced repeatable patterns for filters, tab stacks, and dense data modules so teams could scale new investor pages without reinventing layout logic.

  • Unified global nav + entity filter scaffolding
  • Shared tab architecture for portfolio and company pages
  • Table + chart coexistence patterns for decision workflows
  • Reusable interaction rules for search, date filters, and exports
Modular redesign concept mapping fund modules to overview page
Early modular concept mapping overview, performance, statements, capital calls, and investments
Annotated company page showing navigation and table system
Annotated UI audit used to standardize global nav, local tabs, and data table controls

Impact

A Navigation Model Investors Could Operate At Speed

After the redesign, investor workflows felt like one connected product rather than a set of disconnected tools. Users could start from account context, move through funds or companies, and reach detail tasks through predictable patterns.

The biggest gain was operational confidence: less orientation overhead, clearer status visibility, and faster movement from portfolio review to action.

3-level IA

Navigation standard adopted

Fund->Company

Drill continuity improved

Shared patterns

Cross-page consistency improved

Lower friction

Faster investor task completion

Reflection

Key Learnings

01

IA Is A Product Decision

In enterprise fintech products, information architecture is not a documentation artifact. It is the operating model users depend on to make high-stakes decisions quickly.

02

Context Continuity Beats Visual Novelty

The highest-value UX improvement came from preserving user context while changing depth and entity type, not from adding more visual treatment.

03

Dense UI Needs System Rules

Financial power users accept information density when interaction rules are consistent. Standardized nav, tabs, and table mechanics are what make dense interfaces usable.

Next Project

Carta - Capital Call Workflow

View next case study