My Process

Product design is chaotic. A repeatable process is what makes it succeed — for a molded part, a clinician app, or the lifecycle a whole team ships through.

One six-phase spine for physical and digital products. Methods and deliverables diverge by track; the sequence does not.

  1. Define

    Solidify a design brief with key stakeholders so the project keeps its trajectory.

    Questions

    • What is the objective, and why should this product exist?
    • What are the business goals and opportunities?
    • Who is it for?
    • What are the preliminary requirements and known constraints?
    • When will it launch?
  2. Understand

    Research gives a foundation for informed design choices and exposes pitfalls early.

    Methods, chosen by circumstance

    • Research plan
    • Personas and mental models
    • Interviews, observation, surveys, and feedback review
    • Audits and formative usability testing
    • Competitive and IP analysis, done after early concepts so existing solutions don’t anchor the work
    • Analysis: success metrics, new risks, and whether the brief should change
  3. Conceptualize

    Brainstorming, mind mapping, and sketching feed prototypes. Validation runs inside this phase so effort isn’t spent at a dead end.

    Both tracks

    • Brainstorming, mind mapping, and sketching
    • Competitive and IP analysis after early concepts

    Physical products

    • Sketch models and 3-D prints
    • Proofs of concept
    • Renderings

    Digital products

    • Storyboards and user flows
    • Wireframes (validation round 1)
    • High-fidelity mockups (round 2)
    • High-fidelity prototypes (round 3)
  4. Validate

    Research data and testing models quantify whether the concept works and the project is on track.

    Both tracks

    • Test plan
    • Benchmark testing
    • Design review
    • Usability feedback review

    Physical products

    • Prototype tooling
    • Mechanical testing and high-speed video
    • Basic FEA

    Digital products

    • A/B tests
    • Accessibility evaluation
    • Usability testing at wireframe, mockup, and prototype fidelity
    • Usability bug review
  5. Implement

    Serve engineering’s needs while making sure the project goals survive the build.

    Physical products

    • Manufacturing plan and design transfer
    • Manufacturing 3-D models, drawings, and first-article samples
    • Launch assets: instruction illustrations, packaging, photography, renderings

    Digital products

    • Style guide and asset library
    • Interaction animations to guide engineering
    • Design handoff specifications and state diagrams
    • Components published into developer repositories
  6. Review

    A project review improves the next one by naming mistakes and reinforcing what worked.

    Questions

    • What did we learn?
    • What compromises were made, and why?
    • What should be different next time?
    • How was the project successful?

How the process scales

Hired as a designer; in practice I build the infrastructure that lets product, UX, engineering, and leadership run this process together.

  • Frame the system

    Map what the product has to survive before the first sketch: people using it, regulators, manufacturing, the engineering stack, and who maintains it next.

  • Prototype as authority

    A 3-D print, a part filmed failing on a high-speed camera, or a clickable flow settles arguments slides can’t. What the team can hold, click, or build against is the shared source of truth.

  • Engineer the handoff

    Production CAD a toolmaker can cut a mold from; manufacturing drawings and first-article samples; components and icons published into developer repositories. On both tracks, the handoff is something built, not a file exported.

  • Encode the process

    Product development process with a manufacturer’s ops leaders; org-wide lifecycle at a small product company; AI-assisted lifecycle for product, UX, engineering, QA, and leadership. Same intake, criteria, and review rules whether the next step belongs to a person or an agent.


Philosophy

A design isn't finished until it survives the mold, the clinic, and the codebase. I build the systems that get it there.

  • Build the process the team runs on, then hold the line on it.
  • Solve manufacturability while it's still a sketch.
  • Break it on purpose before a customer does.
  • Hand specialists something they can build from.
  • Prefer a written trade-off over an unspoken one.