Built to scale
Flows, components, states, and interface patterns are designed as reusable systems so the product can evolve without creating unnecessary inconsistency.
Services
Product Design
I design digital products and tools that need to organize workflows, reduce friction, and make complex functionality easier to understand and use.
The work begins by understanding what people need to accomplish, how the product supports those tasks, and where business requirements, user needs, and technical constraints intersect.
Flows, information hierarchy, interaction patterns, states, components, accessibility, and implementation constraints are considered as one connected system rather than isolated screens.
Common scope
-
Product direction & flows
Clarifying product goals, user roles, tasks, requirements, workflows, edge cases, and technical constraints before committing to detailed interface decisions.
-
UX & interface design
Designing flows, wireframes, responsive interfaces, interaction patterns, states, components, and prototypes around real product scenarios.
-
Systems & handoff
Building reusable interface patterns, documenting behaviors, validating key flows, and preparing design decisions for development or continued product work.
Project types
- Digital products Interfaces for platforms and digital services where users need to complete recurring tasks, manage information, or move through connected workflows.
- Internal tools Operational interfaces designed around specific team processes, helping reduce friction, repetitive work, and unnecessary complexity.
- Dashboards & data interfaces Products where information, status, metrics, filters, and actions need to remain understandable even as the amount of data grows.
- Portals & self-service experiences Interfaces that allow customers, partners, or teams to access information, complete tasks, manage requests, or follow ongoing processes independently.
Built around
Human-led, AI-assisted
Product and design decisions remain driven by direct judgment and project context. AI is used selectively for exploration, repetitive production work, documentation, and analysis support.
Task-focused
Interfaces are organized around what users need to understand, decide, or accomplish rather than around isolated screens or feature lists.
Accessible
Hierarchy, contrast, interaction states, keyboard behavior, feedback, and component behavior are considered as part of the product system from the beginning.
Implementation-aware
Design decisions account for technical constraints, existing systems, reusable patterns, and the realities of building and maintaining the product.
Responsive by design
Layouts, components, behaviors, and information priorities are considered across relevant screen sizes instead of adapting a finished desktop interface afterward.
Work process
-
Discovery
Understanding product goals, users, existing workflows, business requirements, and technical constraints before defining the experience.
How I do itI look at what users are trying to accomplish, what information they need along the way, and where the current process creates friction, uncertainty, or unnecessary effort. Existing interfaces, documentation, workflows, and stakeholder knowledge help establish what the product needs to solve before interface decisions begin.
-
Strategy
Connecting product goals, user needs, operational requirements, and technical constraints into a focused direction.
How I do itOnce the context becomes clearer, I identify the tasks and decisions that matter most, what needs to be prioritized, and what can remain outside the current scope. This helps prevent unnecessary functionality from becoming interface complexity.
-
Information Architecture
Structuring features, information, navigation, states, and workflows before investing in polished interface systems.
How I do itFlows and low-fidelity wireframes help clarify how users move through the product, what information appears at each step, and how different actions and states relate to one another. This makes structural problems visible before visual detail makes them harder to change.
-
Interface Design
Turning validated workflows into clear interfaces, interaction patterns, reusable components, and scalable product systems.
How I do itI design around real scenarios, states, and content rather than idealized screens. Components need to account for loading, empty, error, success, permission, and edge-case conditions as well as the default experience. Interaction, feedback, and motion are used where they help users understand what changed, what happened, or what they can do next.
-
Validation & Testing
Reviewing workflows, interaction clarity, comprehension, and usability through focused scenarios and product testing.
How I do itInstead of treating validation as a final approval stage, I use focused flows and prototypes to identify hesitation, unclear behavior, missing states, and incorrect assumptions. Testing specific tasks usually produces more useful design decisions than asking whether an entire interface works.
Frequently questions
What kinds of products do you work on?
I work on digital products, platforms, dashboards, internal tools, portals, and interfaces where users need to complete tasks, manage information, or navigate connected workflows.
The product does not need to start from scratch. I can also work on an existing interface that needs clearer flows, a stronger system, or support for new functionality.
Can you help define the product before design begins?
Yes. Product work often begins with requirements that are still incomplete, overlapping, or expressed as feature requests.
I can help organize those requirements into clearer workflows, user needs, priorities, interface states, and an initial product scope before detailed design begins.
Do you work on existing products?
Yes. I can review an existing product, identify structural and interaction problems, redesign specific workflows, extend its component system, or help introduce new functionality without unnecessarily rebuilding the entire interface.
Do you create prototypes?
Yes. The level of fidelity depends on what needs to be validated.
Prototypes can be used to review navigation, workflows, interactions, component behavior, or specific product scenarios before development begins.
Do you create design systems?
When the scale of the product requires one, yes.
I can define reusable components, variants, interaction states, layout patterns, and interface rules that help maintain consistency as the product grows.
For smaller products, this may take the form of a focused component library rather than a large standalone design system.
Can you work with our development team?
Yes. Product design can be delivered as part of an existing development process.
I can work alongside designers, developers, product owners, or internal teams to clarify requirements, prepare designs for implementation, review production interfaces, and resolve design decisions as the product evolves.
Do you develop the product?
Front-end development can be included when it fits the project and technical requirements.
Products requiring backend architecture, infrastructure, or specialized engineering are normally developed in collaboration with an existing technical team or external developers.
What do you need from us before starting?
Useful starting material can include product requirements, existing interfaces, user feedback, workflows, technical documentation, business rules, analytics, or access to the people who understand how the product is used.
Everything does not need to be fully defined before the project begins. Identifying missing information is part of the discovery process.
How long does a product design project take?
It depends heavily on the number of workflows, product maturity, research requirements, and how much functionality needs to be defined.
A focused feature or workflow may take a few weeks, while broader product work can continue across multiple design and development cycles.
Before starting, I define the stages, deliverables, and review points according to the scope.