2016 Designer Logbook

Designer Logbook 2016

This is my 2016 designer logbook. Last year, I embarked on an exciting journey into the world of designing digital experiences within the financial sector. So far, it has been a thrilling adventure that opened up new career opportunities for me in the Fin-Tech industry.

The 2016 designer logbook is focused on the new gig I accepted this year. As soon as I joined Avaloq I noticed (to my big surprise) the amount (and the quality) of IT products and IT services that a bank has to provide to run its own business in such a competitive environment successfully.

During this first year, as UX Designer at Avaloq, I worked on designing:

  • E-Banking Apps, the ones we use, for instance, to send money and/or to pay our bills with our tablet and/or laptop
  • Web Apps focused on financial operations run by bank employees, the ones, for instance, these people use to adjust the mortgage rate
  • Web Apps designed for Asset Managers and other Fin-Tech PROs, the ones, for instance, that support these guys while they estimate and monitor an investment

Together with my managers and the other stakeholders, we agreed from the very outset on some UX KPIs:

  1. To collect and analyse UX-related good and worst practices observed in the current product design process (eg. qualitative tests with colleagues to evaluate the impact of a specific feature on other products)
  2. To evangelise the Human Centered Design (HCD) approach keeping in mind the business model of our company (eg explain during the sale speeches our design approach)
  3. To enhance the way we validate the customer issues/requests (e.g. define a metric to estimate the added value in delivering a custom feature)

My closest ally in the pursuit of such a goal was the Avaloq custom framework AFP-JS.

By tapping into the huge potential, in terms of visual communication, of the showcase build with the framework, I managed to:

  1. Enhance the communication level and the interaction patterns between the people involved in the product delivery
  2. Reduce the time spent to deliver the prototypes, as well as involve customers from the very first stages of the projects
  3. Enhance the quality of the internal documentation
  4. Reduce the effort in maintaining the documentation
  5. Enhance the UX/UI consistency across the family of products

These approaches enabled the team to focus on:

  1. Enhancing the communication between business people and developers
  2. Reducing the friction between the business requirements and the tech feasibility from the early stages of the projects
  3. Focusing first and foremost on user needs

I successfully enhanced this process, which is inherently sensitive and complex, in trying to:

  1. Simplify written and oral communication, thereby avoiding the jargon
  2. Communicate in an effective way, emphasising the added value of the design vis à vis the business goals
  3. Support the Minimum Valuable Approach (MVP), evaluating the benefits from the user’s POV
  4. Push the use of cooperative design tools, onboarding no-design people in all the design steps. I found out how important this point is to prove the added value of the Design Thinking
  5. Criticise the design deliverables according to a specific list of topics, trying to focus on the UX and not on the style

What are the most important lessons learnt during this first year as Fin-Tech UX Designer?

  • The most important one is the importance of building and maintaining a high level of trust between designers and no design people
  • For successful product delivery, it is key that non-designers perceive, understand and agree on the design thinking added value applied to our product design process
  • Finally, it is pivotal to share goals and strategies in terms of UI/UX from the very outset with all the stakeholders and shareholders of the projects

Image credits

Photo by San Kayzen on Unsplash

Leave a Reply

Your email address will not be published. Required fields are marked *