MĒLVIN JAYSON™My work usually starts with a conversation about what isn't working: a product that's become hard to use, a service that doesn't quite fit people's lives, or a team trying to work out where AI could genuinely help.
I bring research, experience strategy and technical understanding together to help find the right questions, make sense of the trade-offs and decide what to do next.
Choose a focused assessment, a collaborative workshop or support for a larger challenge. Each engagement starts with scoping rather than a one-size-fits-all package.
The most useful place to start when the problem still feels bigger than the brief.
We look at where your product or service is today, who it serves, what is known, and where the evidence is thin. This is about identifying the right problem before committing time and money to a solution.
What you'll take away: A structured needs assessment, opportunity and risk map, and a recommended next step.
Discovery call · 45–60 minutes
For teams with a product that works, but not as well as it should.
I review the experience through user needs, information architecture, accessibility, key journeys and business context. We separate usability friction from deeper product problems, then prioritise what deserves attention.
What you'll take away: An evidence-aware findings report, annotated journey review and practical priorities.
Scoping call · 30 minutes
For teams integrating AI into workflows without a clear picture of what people should still control.
We map the human decisions, machine capabilities, authority boundaries, failure states and ways people can verify or recover from a system's output. The aim is a useful workflow, not an AI feature bolted onto an existing screen.
What you'll take away: A proposed human–AI workflow map, risk questions and prototype opportunities.
Workshop planning call · 30 minutes
For a new idea, changing service or team stuck between several possible directions.
I help teams frame the decision, understand stakeholder and user perspectives, surface assumptions and translate the findings into a manageable product direction. The sprint format and research depth are scoped to the problem.
What you'll take away: A clear problem frame, decision criteria and an actionable design or research plan.
Scoping call · 30 minutes
When product complexity comes from teams, rules, workflows and technology pulling in different directions.
We work through the service landscape, capabilities, roles and dependencies. I bring a UX and systems-thinking lens to architecture conversations, so technical choices remain connected to real tasks and constraints.
What you'll take away: An experience architecture direction, workflow model and delivery considerations.
Advisory call · 30 minutes
For designers, emerging product leaders, communities and event organisers.
I support practical conversations about career development, portfolios, UX research, design leadership and working with emerging technology. For talks and workshops, the content is shaped around the audience and the questions that matter to them.
What you'll take away: A focused mentoring conversation or a scoped talk or workshop proposal.
Introductory conversation
I don't believe in prescribing a workshop or redesign before we've understood the problem. These early steps help us decide whether and how to work together.
Tell me what you're trying to change, who's affected and what you've already tried.
We discuss goals, constraints, existing evidence and what a useful outcome could look like.
If there's a fit, I'll propose a sensible scope, deliverables and next steps. No commitment is created by sending an enquiry.
Use the booking request to share your preferred date and time. I'll reply to confirm a mutually suitable slot. The form does not reserve live calendar availability.
Yes. The approach and scale depend on the problem. A founder may need help framing an initial proposition; an established team may need an independent UX assessment or a more complex service-design conversation.
Scopes differ in research depth, stakeholders, delivery time and the degree of technical investigation required. I’ll discuss a suitable engagement structure and fees after understanding what you need.
We can discuss confidentiality and appropriate handling before any sensitive client information is shared. Please avoid placing confidential records or credentials in the initial enquiry form.
You don't need a perfect brief. A description of the situation is enough to start.
Request a discovery conversation →