An application to facilitate the exchange of information on request (EOIR) that takes place when the tax authority of a requesting jurisdiction asks for particular information from the competent authority of a partner jurisdiction.

Once I had the background research I broke the scenario into a simple set of stages.

To better understand the complete landscape with regard to how we might design a digital experience for users we mapped the 'As Is' and the 'How Might We'. This involved me working with the UX researcher and the Product Owner to consider all possibilities.

Mapping the landscape helped us to understand not only how each piece of the application fits together, but also how each function would relate to all the other functions within the application structure. This allowed for setting out the objectives of each screen and the role the screen would play for the user. For me the process mapping and streamlining the work processes helps plan projects and allow the team to visually communicate the important details rather than writing extensive directions.

The next stage involved planning the project. Having established the functions that were key to the application module. We could create the requirements and define the desired outcomes.

User journeys, identifying personas, identifying the goals of the user, all here helped the team understand user behaviour and anticipate how users will interact with a new application. By understanding this we were opening up the opportunities to design a service that anticipates the users needs and provides them with an effective tool.

Once we had a project plan and had established what the key functions and important features were that we had to design, I worked in low-fidelity creating the main user flows and interactions.

I organised a workshop presentation of our proposed EOIR solution and stepped through the wireframes with clients. I had five clients agree to get involved in a Beta review. The reviews allowed us to iterate and refine the proposed flows before we pushed forward.

In creating the main screens in low fidelity I was able to create and propose the navigational components, input controls, the buttons, text fields, checkboxes, radio buttons, dropdown lists, and the modal windows.

It also allowed me to understand how users would interact with the proposed application. The context for them, the pain points that they have.

In this phase I concentrated on building screens and interactions, building components. The page structure, the master layout, components; controls, buttons, a complete design language.

The components I created using a combination of Sketch and Figma. Some custom elements I created in Illustrator.
‍

Based on the reviews and feedback from stakeholders, our own domain experts and users, the designs evolved into an application environment consistent with user expectation.

The developers were heavily involved at this stage as I built out the design system, in tandem we began to build out an Angular component library.

Given the extent of the application functionality before pushing to full production I created a prototype to engage clients and validate the user flows and proposed solution.
‍

User feedback gathered from the prototype.

The MVP version of the product was launched in June 2021. There are currently six tax authorities using the application with fifty four licences. We have continued to refine the product and develop additional features.

In July of 2022 I began work on a new refined design system to incorporate the module pithing the Regnology suite of regulatory products.
‍