The situation
BMW TechWorks India was growing quickly. New product teams and applications were entering an organization that already had BMW UX standards, design-system guidance, and DesignOps services available globally.
The problem was that teams were not starting from the same place. Some had regular design support. Some had very little. Some already knew which standards and measurement services to use. Others needed help finding the right entry point.
That made general enablement too blunt. A workshop calendar could keep people busy, but it would not answer the more important question: which teams needed support first, and what kind of support would actually help them?
BMW Group DesignOps already maintained the UX maturity framework. My role was not to invent that framework. My role was to help make it usable in the India hub: bring leaders into the process, encourage teams to participate, connect applications to measurement services, and turn the findings into a practical enablement plan.
I used leadership sponsorship to make participation real
A maturity assessment only works if enough teams take part. If it stays as a DesignOps request, the teams most likely to respond are often the ones already interested in UX. That creates a biased picture: the organization sees the teams that are already engaged, while the teams that need more help stay harder to reach.
To avoid that, I took the plan to a forum of around 20 to 25 senior technical stakeholders. I asked for three things: visible sponsorship, an application inventory, and a nominated lead for each team.
That leadership layer mattered. It gave the program a clearer route into product teams, helped identify who should respond, and made the maturity work feel connected to portfolio planning rather than like an isolated survey exercise.
The index was annual, but the response had to be faster
The maturity index was produced annually, but an annual report alone would not have changed much. The useful work happened after the assessment: understanding the gaps, choosing the right support, and following up with teams during the year.
Alongside the maturity work, I onboarded teams to two BMW Group measurement services. UX Measurement used a SUS-based approach to help teams understand usability. In-App Feedback gave product users a way to leave ratings and written comments directly inside applications.
My work included registering projects, configuring and releasing surveys, reviewing dashboards, and discussing the results with product teams. The goal was to help teams move from “we collected feedback” to “we know what to do next.”
The quarterly enablement cycle then used those signals to shape support: workshops, training, Knowledge Cafes, hackathons, standards onboarding, and measurement follow-up. Instead of running the same sessions for everyone, we could point effort toward the teams and topics that needed it most.
The maturity index only mattered because it fed a shorter operating cycle: targeted enablement, measurement onboarding, and follow-up with product teams.
FIG. 1 — SANITIZED OPERATING MODEL
WHAT SHIPPED
- India adoption of a BMW Group UX maturity framework, built and maintained by global DesignOps colleagues
- Sponsorship, application inventory requests, and nominated team leads secured through a senior technical stakeholder forum
- An annual maturity index and report, supported by a quarterly enablement cycle
- Product teams onboarded to UX Measurement and In-App Feedback
- Surveys configured, released, reviewed, and interpreted with product teams
- Workshops, training, Knowledge Cafes, and hackathons shaped around assessed gaps
The output was not just a report; it was a repeatable way to decide where UX support should go next.
What it changed, and what still needed work
The program gave leadership and product teams a more concrete way to discuss UX support. Instead of treating enablement as a general calendar of activities, we could connect support to what teams were actually missing: standards awareness, measurement setup, feedback interpretation, or more hands-on guidance.
It also made the role of DesignOps clearer. DesignOps was not only publishing standards or running sessions. It was helping teams understand their current UX practice, connect to the right services, and decide what to improve next.
There were still important limits. The application inventory was not fully complete, which made the assessment harder to interpret. In a growing hub, this matters. If the list of applications and team owners is incomplete, response rates become harder to judge and the maturity index becomes less representative.
There was also a difference between adoption and impact. Onboarding a team to a measurement service is useful, but it does not automatically prove that the team changed the product. A stronger next version of the program would trace selected examples from feedback signal, to recommendation, to team decision, to product change, and then to follow-up measurement.
One scope note is important. UX Measurement and In-App Feedback were BMW Group services used across roughly 350 applications Group-wide in 2025. My role was leading India adoption within that broader service landscape, not owning the global service footprint.
What I learned
The biggest lesson was that maturity work needs an operating map before it needs a questionnaire.
In a growing hub, even basic questions take coordination: which applications are in scope, who owns each team, who can answer on behalf of the product, and who will help follow up after the results come in. If that map is unclear, the assessment can still produce a report, but the report becomes harder to trust and harder to act on.
If I were restarting the program, I would begin by tightening the application list and owner model first. Then I would design the assessment around the decisions it needed to support: where to send training, where to set up measurement, where leadership support was needed, and which teams needed direct UX guidance.
That shifted how I think about maturity. The score is not the point. The point is whether the organization can use the measurement to make better support decisions.