Native Instruments
Z2 MKII Performance Mixer
Predecessor to the world renowned budget mixer.
Company
Native Instruments
Role
HW + SW UX, Interface Design
The project aimed to create an updated iteration of the Native Instruments Z2 performance mixer, targeting both the scratch DJ and budget DJ markets. My role as the lead UX and interface designer was focused on modernising the hardware interface, aligning with new branding, and enhancing workflows based on user feedback.
Challenges
The primary challenges included modernising the mixer while respecting existing workflows and integrating new features to remain competitive. We aimed to develop a product that served both professional and amateur DJs effectively. Additionally, balancing the hardware design with cost constraints and ensuring robust usability in real-world DJ environments were significant challenges.
User Research and Insights
We began by conducting extensive user research, including both online and in-house interviews with existing Z2 users. The goal was to understand how users interacted with the original Z2 and identify potentially lacking features. This feedback was essential for prioritising new features and refining the hardware interface.
Design, Development and Testing
The design process was divided into three key stages: physical interface design, visual software representation on the device’s screen, and hardware integration. For the physical interface, we created various iterations and conducted user testing to ensure ergonomics, button accessibility, and durability. We built physical models to test usability and prevent issues like hand slips or accidental spillage.
Designing the software interface for the small screen involved determining the most critical information from the Traktor software. The aim was to minimise the need for users to refer to their computers and allow them to perform most tasks directly from the hardware. We compared our design with similar devices in the NI portfolio to maintain consistency and consulted users to confirm that their needs were met.
Hardware Integration
Collaboration with the engineering team, who were based abroad, was crucial for ensuring that the design was feasible and aligned with manufacturing capabilities. One of the intended features—integrating Traktor effects for standalone mode—proved technically unfeasible. After discussions with our manufacturing partners, we resolved this by incorporating more generic effects from their portfolio, ensuring the product remained functional and within budget constraints.
Digital Interaction
Designing the software interface for the small screen involved determining the most critical information from the Traktor software. The aim was to minimise the need for users to refer to their computers and allow them to perform most tasks directly from the hardware. We compared our design with similar devices in the NI portfolio to maintain consistency and consulted users to confirm that their needs were met.