Blog

What gender balance in development teams means for digital outcomes – and why it matters to our customers

Aila Kronqvist Enterprise Designer, Solita

Published 20 Mar 2026

Reading time 3 min

When gender bias in technology is discussed, it is often framed as a cultural or HR issue. But my doctoral research suggests something more structural: How technology is built and by whom affects its quality, resilience, and trustworthiness. For our customers, this isn’t theoretical. It is directly connected to digital outcomes.

We know the imbalance exists

At Solita, as in much of the technology industry, gender balance in technical roles isn’t yet where we would like it to be.

In some of our technical units, the proportion of women is lower than in Solita overall. In Finland more broadly, women represent roughly 30% of technical professionals, while Denmark recently reached close to 50% in certain technical areas. The direction is positive, but progress is gradual.

We recognise this imbalance. And we know it matters.

Why it matters for our customers

Software and AI systems reflect the conditions under which they are built. Before data is collected and models are trained, teams define:

  • What problems are worth solving
  • Whose needs are prioritised
  • What counts as “normal” behaviour
  • Which risks are considered relevant

When teams aren’t balanced, certain perspectives are statistically less likely to be present in those early conversations. This isn’t about intention. It is about representation.

In AI-enabled systems especially, early assumptions scale. A narrow experiential perspective can lead to:

  • Overlooked user groups
  • Untested edge cases
  • Blind spots in automation
  • Increased regulatory and reputational risk

Inclusive design is therefore not a moral add-on. It is a way to reduce blind spots and risks in complex systems.

What we are doing about it

We don’t pretend this is solved. It is not.

Balancing technical fields is a long-term structural challenge, and change does not happen overnight. But awareness must translate into action. At Solita, this means:

  • Actively working toward more balanced technical teams over time
  • Supporting recruitment and career development pathways that increase diversity in technical roles
  • Being conscious of team composition in customer engagements whenever possible
  • Encouraging structured reflection on design assumptions in our projects

In customer work, this translates into a practical goal:

Whenever possible, we aim to build balanced, multidisciplinary teams because diverse perspectives improve solution quality.

We cannot always guarantee perfect balance in every project. But we can ensure awareness, structured practices, and continuous improvement.

Cognitive sustainability and innovation

My research also highlights another important dimension: cognitive load. When professionals operate under unequal credibility expectations or structural imbalance, cognitive energy is diverted away from innovation and architectural thinking.

Sustainable performance requires sustainable conditions. For customers, this matters because cognitive bandwidth directly affects:

  • Innovation depth
  • Risk anticipation
  • Design robustness

High-performing digital teams aren’t only technically strong. They are cognitively sustainable.

Why this is a strategic issue

Digital systems increasingly shape access to services, financial decisions, healthcare pathways, and recruitment processes.

Trust is becoming a competitive differentiator.

If technology is built from a narrow experiential perspective, the result isn’t only inequality, but less resilient technology. Addressing imbalance is therefore not just about representation. It is about building stronger, more future-proof digital solutions.

Interested for more? Read my research or check out what Tivi wrote about it

  1. Business
  2. Culture