Creating welcoming, high-quality products requires more than good intentions; it demands systemic organizational structures that actively minimize bias and foster genuine inclusion. In both marketing and software development, teams often operate within homogenous environments where unconscious bias goes unchecked. When software QA testing teams and user focus groups lack diverse lived experiences, critical blind spots remain hidden until a public misstep occurs.
The Cost of Homogeneous Review: Two Case Studies
Recent high-profile controversies illustrate what happens when cultural due diligence is omitted during development and review:
- The Voyager Ad Controversy: Aotearoa-based Internet provider Voyager Broadband released an AI-generated YouTube ad depicting two brown men making animalistic noises and violently attacking a white counterpart after a sports stream lagged. While intended as humor, community leaders pointed out that portraying Māori and Pasifika individuals as violent reinforces harmful historical stereotypes. Voyager pulled the ad, acknowledging they needed to evaluate their content through a new lens and strengthen approval processes for AI-generated media. It should never have gotten this far, how many levels of approval did this ad pass before going live.
- The Converse KKK Controversy: International brand Converse faced severe backlash over a campaign photo featuring K-pop artist Karina. The lighting on her white skirt formed a triangular shape resembling a Ku Klux Klan hood, while dangling black high-top sneakers evoked lynching imagery. Converse pulled the campaign, admitted they “got this wrong,” and promised to overhaul the critical lens applied during internal reviews.
Neither organization intended to produce offensive imagery. However, because internal review teams lacked sufficient perspective, nobody asked the critical questions necessary to catch these harmful associations before release.
Rewiring QA Testing and User Focus Groups
In software engineering, development and QA teams often consist of people with similar demographic backgrounds, technical comfort, and access levels. Consequently, teams tend to test only the “happy path”—an idealized user workflow that reflects their own experience.
To build products that work for everyone, inclusivity must be baked into QA testing and user focus groups from the start. Bringing together diverse testers—including people of color (such as Māori and Pasifika communities in Aotearoa), women, disabled individuals, and users across varied locations or access speeds—ensures software is evaluated across multiple real-world workflows.
When reviewing products, QA teams and focus groups should adopt core allyship questions rather than simply asking, “Does this work?”:
- “Is there anything here that could be interpreted differently than intended?”
- “What associations, cultural contexts, or messages might we be missing?”
- “Is there anything that could feel exclusionary or harmful to specific groups?”
Taking Systemic Action Without the “Minority Tax”
Practicing allyship means embedding these review mechanisms into team structures rather than relying on informal checks. However, organizations must also avoid imposing a “minority tax”—overburdening the few underrepresented employees within a firm by constantly asking them to audit for bias.
Instead, businesses should expand internal training in ally skills, build diverse QA pipelines, and leverage global crowd-testing networks to gather authentic feedback from varied demographics. Proactive, inclusive testing protects brand reputation, prevents public harm, and ensures that technology truly serves all users.
If you’re ready to take the next step
Check out our services here, and give us a call.