Shandin HarperSenior UX Designer
Home Portfolio Workflow Systems UX Process Resume Contact
Workflow Systems · Real Product Evidence

From fragmented operations to a connected decision system.

Portfolio Command demonstrates how I approach complex workflow design: model the operating system beneath the interface — entities, states, rules, exceptions, handoffs, and decisions — then turn that complexity into a product people can inspect, test, and improve. Built for KBP Investments LLC.

Client / Product Sponsor: KBP Investments LLC Affiliated company Active product initiative
Full Portfolio Command Case Study Launch Synthetic Demo ↗
The workflow problem was not “design a dashboard.” It was: how do I preserve context across property, tenancy, finance, capital, maintenance, and exceptions so the operator does not have to reconstruct the business every time a decision comes up?
01 · Current State → Product Model

The improvement starts before the interface.

The operating information existed, but it lived in different places and different mental models. The design move was to stop treating those records as separate screens and model the relationships between them.

Before · fragmented operating context

The operator has to assemble the answer.

Property records
Rent / lease data
PM statements
Repair & turnover work
Reserves / CapEx notes
Reporting & follow-up
Result: context switching, duplicate tracking, and manual reconstruction before a decision can be made.
After · one operating model

Portfolio Command connects the state.

Thirteen work areas are grouped around the decisions the operator is actually trying to make.

OverviewDashboard · Properties
FinanceLedger · Capital · Reports
OperationsTasks · Units · Ops · Vendors
TenancyTenants · Leases
IntelligenceAction Center · Scenario
02 · Design Decisions

What changed in the workflow.

Pressure point
Design move
Operational effect
Too many peer-level destinations
Group work by five operating domains.
Users navigate by intent instead of remembering where thirteen separate functions live.
Records become data islands
Share property, unit, tenant, lease, task, vendor, and financial identifiers.
Drill-down preserves context instead of forcing users to rebuild relationships manually.
Operating cash and capital blur together
Separate ledger activity from owner moves, reserves, and CapEx while keeping them connected.
NOI, liquidity, reserve movement, and project spend are easier to reason about.
Problems hide inside records
Create an Action Center for delinquency, renewals, overdue work, and exceptions.
The product shifts from recordkeeping to intervention.
What-if analysis happens outside the product
Add scenario modeling for vacancy, expense pressure, repairs, and reserve changes.
Assumptions become visible decision inputs with portfolio and property-level consequences.
03 · Visual Evidence

Follow the workflow through the actual public product.

These are live, non-interactive previews of the synthetic recruiter build — not conceptual mockups. Open the full demo at any point to inspect the working system.

SCREEN 01

Orient before drilling down.

The dashboard is the first decision surface: portfolio health, property context, financial performance, capital spend, recent ledger activity, and operations signals.

  • Reduces initial context reconstruction
  • Creates a single operating entry point
  • Supports drill-down without losing portfolio context
Portfolio Command · DashboardOpen ↗
SCREEN 02

Make financial history traceable.

The unified ledger brings income and expense history into one searchable surface with property, unit, transaction-type, and text filtering.

  • Replaces statement-by-statement reconstruction
  • Maintains property and unit context
  • Supports audit, investigation, and export
Portfolio Command · LedgerOpen ↗
SCREEN 03

Turn uncertainty into a testable scenario.

The scenario tool models vacancy and repair stress against scheduled rent, operating cost, reserves, and projected NOI, then ranks the assets under pressure.

  • Makes assumptions explicit
  • Shows second-order financial impact
  • Moves the workflow from reporting to decision support
Portfolio Command · ScenarioOpen ↗
04 · Repeatable Method

The screens are evidence of the method, not the method itself.

01Map the messCollect records, tasks, reports, pain points, exceptions, and decisions.
02Expose the modelIdentify entities, roles, states, dependencies, and handoffs.
03Find pressure pointsLocate ambiguity, duplicate effort, hidden rules, and fragile decisions.
04Prototype behaviorMake the future state executable enough to inspect instead of merely describe.
05Stress the systemTest exceptions, financial shocks, bad states, and recovery paths.
06Translate to buildConvert validated behavior into reusable patterns and implementation guidance.
Public proof

Portfolio Command shows the work.

Because I control the public build, recruiters can inspect the information architecture, state relationships, financial logic, exception handling, scenario design, and interaction behavior directly.

Read Full Case Study
Enterprise Experience

The same systems thinking scales to enterprise work.

Across enterprise roles, I’ve applied the same discipline to complex workflows, design systems, research, stakeholder alignment, and implementation. Portfolio Command makes that systems approach visible in a public product, while my enterprise experience shows how it operates in larger organizations and cross-functional environments.

Bottom line

Workflow architecture is easiest to trust when you can see the operating model working.

Portfolio Command is the anchor. The domain is real estate; the transferable skill is modeling complex work so users can see state, trace relationships, understand risk, and make the next decision without rebuilding context from scratch.

Launch Demo ↗ View Portfolio