Infuse IT

Due to my non-disclosure agreement, I can only dive so far into the work
I produced while contracting with Infuse IT.

I led the UX for Infuse IT’s MVP for a test automation tool, an area they have been providing service in for over 20 years in different industries and sectors with organisations like Channel 4, Vodafone, King’s College London and more.

Testimonial

“Kai has the honour of being my last consultant hire in my career. I needed a UX Consultant to help my product team develop its thoughts and understand some more on how to create a great user experience and style the user interfaces consistently and coherently according to their variant needs. I got lucky. Kai gave a masterclass in bringing the team up to the plate, forming the correct Q&A sessions, identifying persona's, developing clickable prototypes, style guides, colour palettes and generally mentoring the team. Thoroughly professional and great fun to work with.”

Marcus Catt - CPO - Infuse IT

I worked with 2 main stakeholders, a development team in India and closely with the Chief Product Officer.

Whilst they were highly skilled and knowledgable in development and testing, they required a UX professional to lead and ensure their MVP was user centric, someone to evangelise the benefits of good UX.

I finished working on the MVP once I had provided the team with:

  • Business and user Goals
  • A competitor analysis document
  • A personas document to refer to when building the product
  • A sitemap, fully detailed wireframes, clickable interactive prototypes
  • Brand guidelines
  • Pattern libraries and finished designs of the MVP
  • Usability testing document for when the MVP is released

The challenge

There are many automated testing software products on the market, but after completing several days of competitor analysis it was clear there was a value gap in the test automation tools/platform market that Infuse could deliver into. Our personas defined the detail for this gap which we used to design the product.

The approach

My experience with testing software was extremely minimal, but this led to my advantage as I couldn’t bring any preconceived ideas or prejudices to the table.

Testing software can be incredibly complex and the more I learnt about it, the more complex and fragmented it seemed to become which influenced the direction that I went into.

Due to the nature of an MVP we didn’t have any real data to work from, so I conducted a series of discovery sessions with the two main stakeholders to ascertain the:

1. Business and User goals
2. The personas
3. And then their vision of the MVP, the values and how best to present them.

The discovery

Over the period of the first month, and many discovery sessions it was obvious we really needed to simplify the whole process in every facet of the MVP. I would discuss the project with the 2 stakeholders using my UX knowledge and experience to challenge the ideas they presented by always putting the ‘user’ in the forefront of every part of the journey.

What was obvious to the 2 stakeholders wasn’t obvious to me: from the terminology used, to the user flow and how all the different areas of the MVP related with one another and sat in the user journey to satisfy the user and business goals.

Our discoveries were constantly documented on Confluence building a wiki for the MVP that could be referred to when needed.

The vision

Our vision was to provide the potential users defined in our personas the ability to automate testing easily, ideally within minutes.

The framework

Into the second month I had pages of different user journeys for the 5 personas we had created. Designing all the different user flows highlighted the many different elements of the MVP and so we were able to define exactly what was needed and refine until we had the core set for the MVP. This led to clickable prototypes and then finally design.

The execution

Due to the non-disclosure agreement I am unable to provide any designs of the product. Once I had formulated the wireframes, I designed three key pages of the MVP and also a pattern library for the development team to follow in their execution of the MVP. The MVP is set to be finished early 2025, where the team will then use the usability testing document I provided to further refine the product to meet the users and business needs perfectly.

Next Case Study - Yumove

KAI MOTTA UX/UI SENIOR CONSULTANT