Traktor is a professional 4 deck software application for DJs. It has a fully customizable interface, supports effects, powerfull cueing and looping and works with all hardware controllers.
I was part of a few different teams that evolved together with company’s need to grow and reorganize the internal structure.
I first joined the company as a member of the Traktor design team formed by 2 product designers (incl. myself) and 1 team lead. In this team my duty was to prioritize features based on user feedback, conduct internal stakeholder feedback sessions, sketch and prototype new solutions, support the creation of user surveys, sync and coordinate with other internal departments like Customer Support or Industrial Design.
- identified and prioritized problematic areas of the existing product
- co-created personas for our product for better aligning the development teams and various departments
- created the initial development plan for implementing new features using the “User Story Mapping” technique, promoted by Jeff Patton, and thus making the development timeline more visible
- started prototyping in QT-QML using the actual product and therefore reducing the development time
For the second position I joined a exploration team for a pilot in-house incubator project using Design Thinking framework. I was part of a team formed by 1 product owner, 1 developer, 1 UX designer (myself) and 1 r&d team member. Our mission was to discover new market opportunities around our core business, music software and hardware. My duties were to conduct user research (in Germany and the US), structure and synthesize the gathered user data, prototype and rapidly iterate based on user feedback, conduct co-creation sessions, prepare the findings to be presented to the CxO level.
- conducted more than 48 user sessions gathering essential data many times directly inside the user’s own environment
- recruited candidates for the one on one user sessions
- synthesized the data discovering new opportunities of growth for our business in new areas
- validated the product strategy thought the use of various prototypes in our user sessions
- created wireframes, user journeys and storyboards to help the team n getting a better understanding of our user
- designed user experiments like card sorting or a-b testing
The third position I was assigned was a natural continuation of the previous one. I joined the development team tasked to bring to reality the newly discovered ideas in the new agile company structure. The team was formed of 3 developers, 1 tester, 1 UX/UI designer (myself) and 1 product owner. My duties were to conduct user research, gather qualitative and quantitative user data, communicate findings to the internal stakeholders, prototype new ideas and test them with the users, synchronize with other internal departments like Market Research or Customer Support, mentor other UX designers in the department.
- validated product vision and product strategy using UX methods
- validating our many new ideas by conducted hundreds of hours of user interviews
- developed product workflows and validated them with developers and users
- supported other teams in their user testing activities
- generated supporting concept documentation for development teams
- created and validated personas that served synchronizing the teams
- delivered concept and research findings presentations to internal project and management teams
- created prototypes rapidly using Framer and sometimes QT-Quick
- learned git and QT-Quick programming and started participating to the development process to speed it up
- helped synchronizing UX efforts across the department’s multiple teams (our department had 3 UX designers and 1 UI designer)
- mentored and supported the adoption of tools like Framer or Sketch by the other UX designers within the department
- led a cross department workgroup dedicated to unifying documentation across the company (team was formed by 4 UX designer incl. myself)
- contributed to the hiring and on-boarding of new colleagues