Thinking article · Working process

How I Approach Complex Product Problems

Understand, Reframe, Make to learn, Carry through — my adaptation of the Double Diamond.

I move between the wider system and the specific interaction throughout a project. A prototype can expose a missing constraint; research can change the brief; implementation can send us back to the model.

My four working stages adapt the Design Council’s Double Diamond: Understand, Reframe, Make to learn, Carry through.

  1. 01 / Discover

    Understand

    User research, resonance research, and system mapping.

    AI-assisted desk research, source-checked
  2. 02 / Define

    Reframe

    Find the problem behind the ask. Agree on what matters.

    Evidence, priorities & shared direction
  3. 03 / Develop

    Make to learn

    Prototype. Run RITE usability tests. Review with engineering.

    AI-assisted prototyping & iteration
  4. 04 / Deliver

    Carry through

    Refine the details. Partner through implementation. Learn from use.

    Design judgment & delivery partnership
Across every phase: connect people, workflows, technology, and ownership.
↺ Evidence shapes the next iteration. Adapted from the Design Council’s Double Diamond.

01 · Understand the task and its dependencies

I examine the people, tools, data, permissions, and ownership around a task. In reporting, that meant following content from creation through discovery, use, delivery, and maintenance.

User research, resonance research, and system mapping help surface different questions. Our early resonance work used concepts to explore needs with customer-facing colleagues; end users evaluated workflows later through RITE testing. AI-assisted desk research supports preparation, with source checking.

The decision: which needs and dependencies deserve closer investigation?

02 · Reframe and choose where to intervene

I trace visible friction to the dependencies that might explain it, then agree on a useful scope with the team. Report Library expanded from search to confident reuse and management. Publishing required a distinction between deployment and audience access.

For Report Library, an MVP workshop after RITE testing connected capabilities to experience priorities. In Report Builder, adjacent requirements changed my initial model; my co-lead and I retained a shared foundation with domain differences.

The decision: what problem should we address, and what is outside this scope?

03 · Make to learn

I prototype connected tasks, including transitions and failure states. AI helps scaffold alternatives; I check that the behavior reflects the intended rules.

Report Library’s prototype supported RITE testing and smaller refinements. Publishing prototypes supported engineering workflow and feasibility reviews. Those methods answer different questions: feasibility review does not establish user understanding.

The decision: what does the evidence support keeping, changing, or investigating next?

04 · Carry the reasoning through

With engineering, I refine details and work through constraints while considering connected workflows. Report Builder’s direction survived a platform change because we adapted interactions while preserving their purpose.

Outcomes set the limits of what I can claim. Report Builder reached production. Report Library moved from testing and MVP prioritization into engineering and was being deployed for launch when I left. Publishing reached proposal and engineering review, with later adoption unknown.

The decision: what needs to adapt, and what still needs evaluation in use?

Systems thinking connects these stages: people, workflows, technology, and ownership stay in view as the design becomes more specific.

Read Designing the System, Not Just the Screen for the deeper examples, or AI in my practice for how I use AI within this process.