DeepStation

Building operational clarity for a fast-scaling global organization

TL:DR

• Role: Head of Operations / Product Designer

• Context: Rapid growth, global expansion, volunteer-led execution

• Work: Designed and implemented a centralized operational system

• Impact: Improved onboarding, leadership visibility, KPI tracking, and decision-making—creating a foundation for scale

Deepstation Website

Overview

In 2024, DeepStation entered a critical growth phase focused on brand expansion, consulting services, and global reach. While momentum was strong, the organization lacked the internal structure required to support that pace.

I identified operational fragmentation as a core risk and led the creation of a centralized system to bring visibility, accountability, and shared understanding across teams.

The Challenge

As the organization expanded:

• Information was inconsistently documented or siloed

• The founder carried too much operational load, limiting effective delegation

• Volunteers had little onboarding context or system access

• Leadership lacked reliable insight into events, pipeline, and performance

This created unnecessary stress during planning cycles and made it difficult to evaluate what was working or where to invest next.

My Role & Leadership

Head of Operations / Product Designer

I took full ownership of defining and implementing an operational framework that could scale with the organization.

This included:

• Identifying system-level gaps impacting execution

• Selecting and deeply leveraging existing tools

• Designing a structure that balanced flexibility with control

• Driving adoption through live onboarding, documentation, and iteration

Rather than introducing new software, I focused on making the organization operationally legible to itself.

Operating Model

The system was designed around a few core principles:

• One source of truth for events, tasks, and metrics

• Clear separation of visibility between volunteers, leadership, and revenue teams

• Consistency without rigidity, allowing teams to adapt without breaking structure

Event planning, volunteer coordination, and performance tracking were unified into a single operational view, enabling teams to move faster with fewer handoffs.

Experience & Adoption

Onboarding was treated as a strategic component, not an afterthought.

• New volunteers were guided through a clear, role-appropriate entry point

• Leadership gained immediate visibility into upcoming work and capacity

• Teams could collaborate directly within the context of events and tasks

Early usage patterns revealed a key insight:Too much information reduced engagement, while fragmented views caused critical details to be missed.The system was refined to surface only what was relevant—without losing accountability.

Impact

The system:

• Enabled KPI tracking across all events for the first time

• Improved leadership understanding of pipeline and operational load

• Reduced planning friction and last-minute coordination issues

• Surfaced repeatable workflows that later informed automation efforts

Most importantly, it shifted the organization from reactive execution to intentional, informed decision-making.

Constraints & Judgment

Working within Notion required tradeoffs:

• Limited visual customization

• Risk of accidental data loss

• Manual data entry during early adoption

These constraints reinforced a deliberate choice to prioritize durability, clarity, and organizational buy-in over polish.

Why This Matters

This work demonstrates my ability to:

• Identify and resolve structural bottlenecks

• Lead through ambiguity during periods of growth

• Design systems that support people, not just processes

• Translate operational complexity into clarity at scale

It also reflects how I approach product design: by focusing on leverage, alignment, and long-term impact.