KPI Dashboard Tool
GKN desktop app
company
Abuscom x GKN Automotive/Aerospace
timeline
Sep - Oct 2018 (3 months part-time)
role
Sole designer working in close collaboration with developers at Abuscom.
tools
Photoshop, Invisionapp, Trello
Introduction
————————————————————————————————
My first UX design experience. I started the app design based on design guidelines in the form of a mobile app mockup, used by GKN for a different purpose. I had to adapt the colour palette and main elements to a desktop app used as a dashboard to insert and view key performance indicators.
Given my low level of experience and the PM’s understanding of my capabilities, I was given the freedom to choose the right tools for the process while accounting for my shortcomings. Large part of the decision-taking process was centered around verbal communication with the PM, so instead of focusing on visually documenting the process and tools used, I relied in large part on memory and rough sketches, thus brute-forcing my way to a passable result and only using tools when needed to gather actionable information, when I encountered roadblocks.
Process
————————————————————————————————
We used Trello to set up the design process, focusing on steps to help me learn the UX and UI basics. The first steps included learning the basics of Invisionapp, playing around with bootstrap themes to learn about the development process and creating a provisional quick mockup to learn how to adapt my Photoshop skills to UX and work with the Invisionapp plugin.
As soon as I had the basics down, I jumped into project specific tasks. I started by inquiring information about the current and future KPIIT users, analysing the KPI tool’s functionalities and learning conventional practices from existing KPI dashboards. Lacking knowledge of how to effectively represent quantitative and qualitative data, I soaked up as much as possible and tried to memorise it for the duration of the project. Primary research was mostly lacking throughout the process and behaviours and preferences of the target users were communicated to me via a 3rd person. No testing took place beside role-testing with the PM.
key learnings
————————————————————————————————
While efficient in the short-term, this largely mental-based process was prone to making me loose oversight and stress-inducing in the long run. It would also have been vastly inefficient if the UX team consisted of 2 or more designers as verbally communicating an entire design and thought process to more than 1 person would have been too time consuming.
Even though the end result was satisfactory, I learned that churning out fast architectural sketches and rudimentary wireframes would help immensely with reducing my mental load and with more efficiently communicating my choices with the product manager.
Other Pages
————————————————————————————————
KPI Dashboard Tool
GKN desktop app
company
Abuscom x GKN Automotive/Aerospace
timeline
Sep - Oct 2018 (3 months part-time)
role
Sole designer working in close collaboration with developers at Abuscom.
tools
Photoshop, Invisionapp, Trello
Introduction
————————————————————————————————
My first UX design experience. I started the app design based on design guidelines in the form of a mobile app mockup, used by GKN for a different purpose. I had to adapt the colour palette and main elements to a desktop app used as a dashboard to insert and view key performance indicators.
Given my low level of experience and the PM’s understanding of my capabilities, I was given the freedom to choose the right tools for the process while accounting for my shortcomings. Large part of the decision-taking process was centered around verbal communication with the PM, so instead of focusing on visually documenting the process and tools used, I relied in large part on memory and rough sketches, thus brute-forcing my way to a passable result and only using tools when needed to gather actionable information, when I encountered roadblocks.
Process
————————————————————————————————
We used Trello to set up the design process, focusing on steps to help me learn the UX and UI basics. The first steps included learning the basics of Invisionapp, playing around with bootstrap themes to learn about the development process and creating a provisional quick mockup to learn how to adapt my Photoshop skills to UX and work with the Invisionapp plugin.
As soon as I had the basics down, I jumped into project specific tasks. I started by inquiring information about the current and future KPIIT users, analysing the KPI tool’s functionalities and learning conventional practices from existing KPI dashboards. Lacking knowledge of how to effectively represent quantitative and qualitative data, I soaked up as much as possible and tried to memorise it for the duration of the project. Primary research was mostly lacking throughout the process and behaviours and preferences of the target users were communicated to me via a 3rd person. No testing took place beside role-testing with the PM.
key learnings
————————————————————————————————
While efficient in the short-term, this largely mental-based process was prone to making me loose oversight and stress-inducing in the long run. It would also have been vastly inefficient if the UX team consisted of 2 or more designers as verbally communicating an entire design and thought process to more than 1 person would have been too time consuming.
Even though the end result was satisfactory, I learned that churning out fast architectural sketches and rudimentary wireframes would help immensely with reducing my mental load and with more efficiently communicating my choices with the product manager.
Other Pages
————————————————————————————————
KPI Dashboard Tool
GKN desktop app
company
Abuscom x GKN Automotive/Aerospace
timeline
Sep - Oct 2018 (3 months part-time)
role
Sole designer working in close collaboration with developers at Abuscom.
tools
Photoshop, Invisionapp, Trello
Introduction
——————————————————————————————————
My first UX design experience. I started the app design based on design guidelines in the form of a mobile app mockup, used by GKN for a different purpose. I had to adapt the colour palette and main elements to a desktop app used as a dashboard to insert and view key performance indicators.
Given my low level of experience and the PM’s understanding of my capabilities, I was given the freedom to choose the right tools for the process while accounting for my shortcomings. Large part of the decision-taking process was centered around verbal communication with the PM, so instead of focusing on visually documenting the process and tools used, I relied in large part on memory and rough sketches, thus brute-forcing my way to a passable result and only using tools when needed to gather actionable information, when I encountered roadblocks.
Process
——————————————————————————————————
We used Trello to set up the design process, focusing on steps to help me learn the UX and UI basics. The first steps included learning the basics of Invisionapp, playing around with bootstrap themes to learn about the development process and creating a provisional quick mockup to learn how to adapt my Photoshop skills to UX and work with the Invisionapp plugin.
As soon as I had the basics down, I jumped into project specific tasks. I started by inquiring information about the current and future KPIIT users, analysing the KPI tool’s functionalities and learning conventional practices from existing KPI dashboards. Lacking knowledge of how to effectively represent quantitative and qualitative data, I soaked up as much as possible and tried to memorise it for the duration of the project. Primary research was mostly lacking throughout the process and behaviours and preferences of the target users were communicated to me via a 3rd person. No testing took place beside role-testing with the PM.
key learnings
——————————————————————————————————
While efficient in the short-term, this largely mental-based process was prone to making me loose oversight and stress-inducing in the long run. It would also have been vastly inefficient if the UX team consisted of 2 or more designers as verbally communicating an entire design and thought process to more than 1 person would have been too time consuming.
Even though the end result was satisfactory, I learned that churning out fast architectural sketches and rudimentary wireframes would help immensely with reducing my mental load and with more efficiently communicating my choices with the product manager.
Other Pages
——————————————————————————————————