Product Thinking


I approach product design as systems design. Interfaces are one layer of the solution. The real work happens when you map dependencies, design for trust, and build ecosystems that accommodate complexity and constraint.

I approach product design as systems design. Interfaces are one layer of the solution. The real work happens when you map dependencies, design for trust, and build ecosystems that accommodate complexity and constraint.

These frameworks guide how I analyze problems, structure decisions, and collaborate across product, engineering, policy, and operations environments.

My background spans engineering operations, civic systems, and product design. Working in environments where failure has operational consequences shaped how I approach design: by mapping systems, clarifying constraints, and building structures that allow teams to move with confidence.
Seen in practice with Kindred, Civil Access, Texas Cannabis Collective

Products don’t exist in isolation. They live inside organizational structures, data flows, compliance requirements, and user ecosystems. Mapping these relationships helps teams surface constraints early, reduce downstream rework, and align product direction across disciplines.

Trust is structural, not cosmetic. It’s built through data transparency, predictable behavior, and systems that protect agency. In environments where users face institutional power or changing civic systems such as healthcare and defense infrastructure, trust design becomes foundational to adoption.

I visualize how product components interact with users, backend systems, third-party integrations, and operational workflows. Ecosystem maps clarify dependencies, surface edge cases, and help teams prioritize infrastructure decisions alongside feature work.

Design in high-constraint environments requires structured decision-making. I build frameworks that evaluate tradeoffs between user value, technical feasibility, regulatory compliance, and operational capacity so teams can move forward with clarity rather than stalled decision cycles.

Systems Thinking ->

Identify landscape

Ecosystem Mapping ->

Reveal dependencies

Trust Design ->

Shape interactions

Decision Frameworks

Guide priorities

In practice, these frameworks layer. Systems thinking identifies the landscape. Ecosystem mapping reveals dependencies. Trust design shapes interaction patterns. Decision frameworks guide prioritization. Together, they create a structured approach to designing products that integrate into real operational environments.

Social discovery platform designed for trust, agency, and relational intelligence. Applied systems thinking to map user journeys across safety, matching algorithms, and community norms.

Systems Thinking

Product Ecosys Mapping

Trust Design

Operational design for high-stakes engineering environments. Operational coordination for operations in high-reliability engineering environments where protocol compliance, safety constraints, and cognitive load must coexist.

Trust Design

Decision Frameworks

Infrastructure connecting residents to municipal services. Mapped cross-departmental workflows, regulatory constraints, and citizen touchpoints to design a system that translates complexity into clarity.

Systems Thinking

Product Ecosys Mapping

Decision Frameworks

Community platform and information infrastructure addressing regulatory complexity around cannabis policy in Texas. Applied systems thinking to connect legislative data, public education, and stakeholder coordination into a structured information ecosystem.

Systems Thinking

Product Ecosys Mapping

Decision Frameworks

My work focuses on designing product systems, not just interfaces. I bring frameworks that translate complexity into structure so teams can build products that work in real operational environments.

View Case Studies ->