Design Staffing for Impact
Summary
The IBM CIO portfolio is comprised of thousands of tools and services. Given the organization’s obsession with the IBMer experience and their desire to positively impact IBMer productivity, it is extremely important that they allocate their scarce Design & Research talent to the projects that have the greatest impact on IBMers' work experience. To this end, they have refined their staffing processes and developed a new metric, The Design Staffing Score, that allows them to measure the degree to which their staffing approach aligns with project priority. Patrick will describe their refined approach to staffing, how progress is measured, and the tangible benefits they’ve realized.
Key Insights
-
•
Demand for UX support at IBM's CIO org outpaced capacity, despite team growth.
-
•
Lack of documented prioritization criteria caused stakeholder confusion and dissatisfaction.
-
•
Using two objective variables—number of users and usage frequency—made prioritization more quantifiable and aligned with mission.
-
•
The team developed a design staffing score metric correlating staffing with project priority to measure alignment and success.
-
•
Visible, agreed-upon priorities enabled smooth reallocation of designers to higher impact projects.
-
•
Introducing a tiered support model improved communication and set stakeholder expectations for lower priority projects.
-
•
Leadership, especially CIO Fletcher Prev, strongly prioritizes employee (associate) experience, easing adoption of prioritization.
-
•
Automating staffing data and weekly score tracking made ongoing prioritization upkeep feasible and visible.
-
•
Cross-domain design advisors act as knowledge hubs and liaison points for staffing and portfolio understanding.
-
•
Continuous reassessment of project scope and staffing needs ensures resources adapt to changing priorities.
Notable Quotes
"If you’re like us, you’d love to have 100% of the UX talent every project needs, but your team isn’t large enough."
"We never documented our criteria, leaving stakeholders feeling our decisions were mysterious."
"The two variables that stood out were how many people the project impacts and how often they use it."
"Anything below zero on the design staffing score indicates we’re staffing lower priority projects over higher ones."
"We immediately transitioned designers embedded on lower priority projects to higher priority ones."
"We created a tiers of support model so even low priority projects get some level of guidance, even if just a 45-minute consultation."
"Our CIO, Fletcher Prev, has always made the employee experience his North Star."
"Before transitioning designers, we reviewed and agreed on a prioritized list with all executive leaders."
"We automated everything — now we click a button weekly to produce updated staffing and priority alignment scores."
"When project scope changes, designers or design advisors raise their hand to reassess and adjust staffing accordingly."
Or choose a question:
More Videos
"It is impossible to survive in this industry by pushing against the current all the time; you must put yourself in positions to leverage the current."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"If you’re generating buy-in, don’t forget what it will mean for your difficult stakeholders—they may have external pressures you don’t know about."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Our communications is all over the map — email, Slack, Hangouts, face-to-face, GitHub — it surfaced some gaps we didn’t fully appreciate before."
Dave GrayGroup Activity: Making Sense of DesignOps
November 7, 2017
"A story lets people assign the meaning that's powerful to them and then think about the decisions they need to make and align."
John CutlerThe Alignment Trap
November 29, 2023
"When was the last time that you felt stuck? The one where you feel a sense of being stuck trying to understand something."
Abby CovertStuck? Diagrams Help
October 27, 2022
"We started to build an API for how other teams could interact with us like a contract."
Mark InterranteCollaboration Flows in Product Development
June 9, 2017
"Obsession with gadgetry and cool tech ignores the fact that most critical future changes are mundane and essential, like clean water."
Devon PowersImagining Better Futures
March 9, 2022
"Unbiased qualitative research does not exist. The best we can do is acknowledge and minimize biases."
Prayag NarulaHow to Empower Your Designers to Do Good Research – And Why You Want To
June 10, 2022
"Your short term memory is the context window; too big, and the model has trouble accessing everything."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
