Unified Sustainability Platform

Designing the UX Foundation for a Unified Sustainability Platform

How I helped bring Carbon and Source together into one connected product experience by unifying architecture, workflows, and design patterns.

Role
Senior Product Designer
Context
Sole designer, initiative
Scope
Platform strategy, IA,
systems design, patterns
Team
PM, engineering,
ops, CS, program stakeholders
Executive Summary

Carbon and Source had been built as separate product experiences, creating a platform that felt fragmented for growers, partners, and the team building it. I helped define a unified direction — aligning architecture, workflows, relationship management, and design patterns into one shared platform model that could scale across programs over time.

One platform
Carbon and Source brought into a single coherent product experience for growers and partners
Reusable
Shared patterns and architecture reduced duplication across programs and new workstreams
Foundation
Became the platform base that subsequent work — including the biofuels compliance platform — was built on
Platform ecosystem diagram
01 — Product

The unified platform in practice.

Unified platform architecture

Platform architecture

Unified IA spanning programs, enrollment, partners, growers, and fields — one structure supporting both Carbon and Source.

Partner management dashboard

Partner oversight dashboard

Standardized management view giving partners visibility into grower participation, status, and next actions across programs.

Relationship management and invitations

Relationship management and invitations

Consolidated user types and invitation flows into a single framework — consistent behavior across programs and user types.

Reusable page structures

Reusable page structures

Shared layouts and interaction patterns applied consistently across product areas and programs, reducing duplication across the platform.

02 — The Challenge

Carbon and Source had grown separately — and it showed throughout the product.

Growers Partners Internal teams
Fragmented UX across programs
03 — The Insight
The problem wasn't inconsistent screens. It was inconsistent system logic underneath them.

Carbon and Source had grown through separate initiatives without a shared model for how programs, operations, relationships, and oversight should work together. That reframe shifted the work from optimizing isolated flows to defining the shared structure beneath the experience.

04 — The Solution

I focused on the structural decisions that would create the most leverage across the system.

Rather than fixing surface-level inconsistencies, the work focused on defining shared structure: unified platform architecture spanning programs, enrollment, partners, growers, and fields — with standardized relationship management, consistent oversight patterns, and reusable page structures shared across both Carbon and Source.

Unified product framework diagram
05 — My Contribution

What I owned.

Reframing fragmented UX issues as a broader platform challenge
Defining unified platform and information architecture across major domains
Connecting program, operational, and management workflows
Standardizing relationship management and invitation frameworks
Improving partner oversight and grower management patterns
Establishing reusable page structures and interaction models
Supporting implementation across evolving workstreams
Alignment with VPs and cross-functional leadership on platform direction