MĒLVIN JAYSON™Immigration services combine complex requirements and diverse needs.
All case studiesOriginal explanatory visualisation created for this portfolio. It illustrates design thinking, not a reproduction of a confidential client screen.
Public-service interactions often involve complex eligibility rules, documentation and unfamiliar terminology. People may be using these services at consequential moments in their lives.
The UX contribution centred on information architecture, service journeys and making complex processes easier to follow. This included thinking through user expectations, clarity of instructions and understandable progression.
A simplified conceptual model to explain the experience principles. It is not presented as a historical project deliverable.
The key design question was how to make an institutionally complex process feel navigable without oversimplifying its legal or operational requirements.
This public-safe overview omits internal government processes, screens and restricted project materials.
My public case studies focus on the problem, experience rationale and transferable lessons. Detailed discovery findings, artefacts and individual attribution will be added where evidence and permissions allow.
Explore more workImmigration processes can carry real consequences for the people navigating them. The brief was to explore a self-service experience where people could understand requirements, manage appointments and see what was happening with their application.
As part of an Accenture RFP response, I helped design the MyImmigration self-service portal concept, including appointment booking, application tracking and an AI-assisted help channel. The challenge was to make a complex service legible without oversimplifying it.
An explanatory reconstruction of the design process, not an original client artefact.
I took away a sharper appreciation for designing around uncertainty: when someone is waiting for an important decision, visibility and understandable language are not decorative features.
This was a design contribution to an RFP response; the source does not establish deployment.
How can complex public requirements be made understandable without losing accuracy?
Inclusive service design, plain language and information architecture. The interface should reflect how people interpret information, recognise risk and decide what to do next.
Stepwise journeys, contextual instructions and transparent progress. This is an interpretation of the design approach rather than a claim that every technique was used in a documented research session.
Reduced avoidable confusion in consequential interactions. The experience should help people understand the state of the system and retain meaningful control.
Portfolio-created framework illustrating the design rationale. Not an original or approved client deliverable.