Tudor Whiteley Product Design Leader Senior UX and Product Designer

Design leadership for trust-critical products

Product design for trust-critical products

I design for products where trust is the product, and I build the teams that keep it that way.

I turn what users actually do, not just what they say, into product decisions across government, healthcare, education, fintech, and consumer mobile.

I work from discovery through production: talking to customers, framing the problem, prototyping, and staying with engineering until the work ships. Hands-on by default.

Start with the work How I lead
Millions of Ontarians served by platforms where I have led UX design
6 vendor teams aligned under one design governance practice
1,000+ residents in co-design sessions I led
15% support call reduction traced to a single fix
15% support call reduction traced to a single fix
3 applicant products on one design system I built
1,000+ residents in co-design sessions I led
Millions of Ontarians served by platforms where I have led UX design

Featured work

Selected engagements

  1. Designing the conditions for trust in AI supported health navigation

    A province-wide public health service was about to bolt AI symptom assessment onto a service listing.

    The AI Governance Table adopted my trust framing as its evaluation criteria, and the repositioning of Health811 toward a health concern problem solver is adopted and in build.

    I reframed the evaluation around trust conditions, not model performance.

    Read the case study

  2. Research at provincial scale: 1,000 Ontarians and the vendors in between

    A structured research plan failed because the method did not fit the residents it was meant to serve, while partner sessions were structured in ways that encouraged agreement instead of producing reliable evidence.

    Findings from more than 1,000 Ontarians informed shipped features, shared design standards, and the Health811 repositioning. Vendor testing was rebuilt to remove facilitation bias.

    The method bent to the people, not the reverse.

    Read the case study

  3. An AI that refuses to guess

    A system built for an audited domain, where a confident wrong answer costs more than no answer at all.

    A functioning prototype that abstained rather than guessed under audit conditions, pitched to funders in the US and Singapore and backed by early funding.

    I designed what happens when the machine declines.

    Read the case study

  1. An AI that refuses to guess

    A system built for an audited domain, where a confident wrong answer costs more than no answer at all.

    A functioning prototype that abstained rather than guessed under audit conditions, pitched to funders in the US and Singapore and backed by early funding.

    I designed what happens when the machine declines.

    Read the case study

  2. Zero to one for applicants the system could not see

    International applicants were routed through a domestic flow that structurally could not serve them.

    International applicants got a flow built for them. Completion rates rose significantly after launch, and one password fix cut total inbound support calls 15%.

    I do not wait for research budgets. I find the closest source of user pain and systematize it.

    Read the case study

  3. One system, three applications

    Three applicant-facing products had to look and behave as one system, and developers needed something concrete to build from.

    One system across the domestic, international, and college-branded applications kept design and code consistent, cut review and rework cycles, and sped up design and build.

    A design system is only as good as the decisions written into it.

    Read the case study

How I lead

I run design teams on one model: small groups explore, one owner executes, peers review. People develop faster when their roles build on their strengths. Decisions get made on evidence.

Read how I lead