Summary
We will see how we developed a design maturity model, adapting models from invision, McKinsey and papers measuring design impact from IBM to our particular context, in order to discover the main growth opportunities we had in our design practice and how we used outcomes/OKRs to define a detailed strategy for the designOps team.
Key Insights
-
•
Organizational restructures can leave design teams feeling lost and without clear guidance, similar to being physically disoriented.
-
•
Creating a design maturity model based on recognized industry reports helps provide a map and compass for teams to regain direction.
-
•
Individual one-on-one conversations are critical to gain team buy-in when introducing complex models or change initiatives.
-
•
Early versions of strategic tools may feel nebulous and need iterative refinement with team involvement to become useful.
-
•
Combining behavioral indicators from multiple sources (McKinsey, Ambition, IBM) strengthens the relevance and applicability of a maturity model.
-
•
A collaborative evaluation of team maturity encourages transparency about current state and highlights key areas for improvement.
-
•
Dividing priority areas into smaller groups and assigning objectives fosters ownership and focused action within large teams.
-
•
Using OKRs or other goal frameworks aligns design teams towards measurable progress within a broader organizational context.
-
•
Understaffing in design ops teams is common even in large organizations but can be overcome through clear strategy and collaboration.
-
•
A maturity model evolves from a theoretical framework to a practical GPS-like tool that guides ongoing team development and strategy.
Notable Quotes
"It was like giving a map that you could not read or even understand."
"We were lost in the forest and you come across this compass, maybe all time rusty, but still something a little bit useful."
"I was not able to come up for them to be involved so I had to learn how to structure it in a way that we could share how this was important for the team."
"After four years we were able to see in a concrete way what happened, the changes that we have been able to do for the organization."
"We finally instead of using the compass and the map we finally were able to build a GPS."
"It was like arriving to your home after a long day and just right to rest but at the same time you know you could not wait to continue working."
"Understaffing is consistent in design ops no matter where in the world you are."
"We chose to focus on research because we wanted to mirror, a bit more robust, the capability of the design teams to understand client needs."
"The model was the work of everybody, it was not just my job."
"I believe that maturity models could help define the strategy of the design team."
Dig deeper—ask the Rosenbot:
















More Videos

"The person sitting next to you probably solved that problem already—just talk to one another."
Etienne FangPower of Insights: Why sharing is better than silos with Uber’s Insights Platform
December 16, 2019

"Learning as you go is necessary; you won’t complete all your learning before completing a project."
Victor M. GonzalezPracticing Learners and Learning Practitioners
March 10, 2021

"Collaboration helps you look at problems from different angles, which makes your work more robust and nuanced."
Roberta Dombrowski Sam Duong WoloszynskiMaking Research a Team Sport
March 11, 2022

"If the phone dies, Bigfoot’s insulin pump continues working independently, but without new data input."
Daniel J. RosenbergDigital Medicine Design
September 26, 2019

"Establish a design system council where all stakeholders gather regularly to maintain and evolve the system."
Jaime CreixemsBest Practices when Creating and Maintaining a Design System
June 7, 2023

"Fear of AI comes from not trusting the inputs, the data powering these models."
Tricia WangFrom Users to Shapers of AI: The Future of Research
March 25, 2024

"We were a pawn. And a pawn can still win the game."
Shahrzad SamadzadehWhat Is My Value? Two Takes and Some Mistakes
January 8, 2024

"Design thinking has helped raise awareness but often lacks the depth of design practice which requires dedicated craft."
Jorge ArangoDesign as an Antidote to VUCA
May 9, 2019

"Peter van D**e really pushed us to think about the bot as part of a conversation, not just a query-response machine."
Louis RosenfeldThe Rosenbot and the Rosenverse: An AMA with Lou Rosenfeld
June 5, 2024