01
Learn the domain
Understand ISO-management work, the people responsible for it, and how one decision creates consequences elsewhere in the system.
AmpliFlow — Owning product design for complex B2B SaaS.
AmpliFlow helps organizations build and run the management systems behind ISO certification. I turn that dense operational domain into clear web-product decisions—from research and information architecture to a 900+ component design system and what ships.
- Role
- Lead UI/UX Designer
- Product
- Complex web SaaS
- System
- 900+ components
- Method
- Atomic Design
The product
The interface sits on top of an operating system for the business.
AmpliFlow is not a simple dashboard. It connects the work organizations use to become and remain ISO-certified: policies, goals, audits, requirements, risks, deviations, processes, documents, competencies, ownership, and follow-up.
A change in one area can create work in another. Roles and permissions shape what people can see and do. Records need traceability. The design challenge is to preserve that operational rigor without forcing users to think like the database underneath it.
- 01 Management systems
- 02 Goals & policies
- 03 Audits
- 04 Risks & deviations
- 05 Processes & documents
- 06 Resources & competencies
What ownership looks like
I own the reasoning between “we need this” and “this works in production.”
My job is not to decorate a product requirement. I clarify the problem, challenge weak assumptions, understand the system around it, make the interaction model explicit, and stay involved until the solution works as intended.
02
Frame the product problem
Turn ambiguous requests into flows, information models, states, edge cases, and a clear reason for what should be built.
03
Design the system
Solve the immediate workflow while strengthening reusable patterns, components, and conventions across the web product.
04
Own the path to production
Work closely with product and engineering through implementation, review, and iteration instead of stopping at handoff.
Product decisions
Make a large, configurable system easier to enter and navigate.
01 · Information architecture
Navigation had to explain the product—not just link to pages.
In a modular QMS, navigation communicates the product model. I reviewed the end-to-end structure, grouped related work, and redesigned entry points so users could understand where they were, what belonged together, and where to go next.
02 · Onboarding
Setup had to teach the system while helping users make progress.
Different organizations arrive with different standards, structures, and levels of maturity. I redesigned onboarding as the beginning of the product experience: a guided route into a configurable system, with clearer next actions after setup.
Design system at product scale
900+ components organized with Atomic Design.
AmpliFlow is web only. I built its large design system to give a growing SaaS product a shared language—from foundations and small controls to composed patterns and complete product experiences.
Atoms
Foundations and controls
Molecules
Reusable UI combinations
Organisms & templates
Workflow-level product patterns
Consistency
Shared states, behavior, hierarchy, and language across dense product areas.
Decision speed
New work starts from proven patterns instead of reopening settled questions.
Engineering alignment
Components give design and engineering a more precise shared language.
AI-assisted product design
AI increases the number of ideas I can test—not the amount of judgment I outsource.
I use AI throughout the design process to explore alternatives, interrogate assumptions, iterate on flows and prototypes, and validate ideas faster. It helps me widen the option space before narrowing it with product context, user needs, system constraints, and design craft.
Explore faster
Generate and compare more credible directions before investing in high-fidelity execution.
Pressure-test decisions
Surface missing states, edge cases, weak assumptions, and alternative ways a flow could work.
Validate sooner
Create testable artifacts earlier so feedback changes the idea before implementation becomes expensive.
From system to shipped product
Craft matters because complex work still has to feel clear.
The interface is the visible result of decisions about hierarchy, workflow, permissions, states, and reusable behavior. These screens are not the case study by themselves; they are evidence of the system working.
Impact
A clearer product and a stronger way to build it.
Delivery
Shorter path to production
Reusable patterns and close engineering collaboration reduced the distance from idea to shipped work.
Scale
Less repeated design work
The design system gave recurring decisions a durable home and new features a stronger starting point.
Business
Supported product growth
Better onboarding and product clarity contributed alongside product, marketing, sales, and engineering to increased acquisition.
Need someone who can own the hard parts?
I work with teams building complex SaaS and high-stakes products—where understanding the system, making sound decisions, and shipping well all matter.