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
"One-pagers are a lightweight, skimmable way for anyone in the company to quickly understand what’s been learned from research."
Molly FargotsteinMultipurpose Communication & UX Research Marketing
September 12, 2019
"Agile was built for speed and recovery but often misses depth, purpose, and vision needed for design."
Dave MaloufClosing Keynote: Amplify. Not Optimize.
October 24, 2019
"You want to be very clear about what was generated by AI and what is your own stuff in your notes."
Jorge ArangoAI as Thought Partner: How to Use LLMs to Transform Your Notes (3rd of 3 seminars)
May 3, 2024
"The AI is looking through material and that material’s changing every day."
Daniel J. RosenbergDesigning with and for Artificial Intelligence
August 11, 2022
"Unique names for components like message bars are crucial, especially when multiple instances are shown at once."
Alexis LucioScaling Accessibility Through Design Systems
June 9, 2022
"The design project tracker used 1900 Excel functions mostly for capacity planning in quarterly design cycles."
Peter BoersmaHow to Define and Maintain a DesignOps Roadmap
October 3, 2023
"White space risk is about the surprises that happen between organizational boundaries and roles."
Ben Reason Aline Horta Majid Iqbal Fabiano LeoniMaking the system visible: The fastest path to better decisions
November 20, 2025
"We devote 30 to 50 percent of the project time just on evaluation with real users and experts to ensure quality and safety."
Peter Van Dijck Louis RosenfeldCoffee with Lou #4: Taking a Peek Under the Rosenbot's Hood
June 14, 2024
"We often adapt within imperfect systems rather than fight them outright, aiming for longer-term change."
Taylor KlassmanShaping the Next Era of UX Research: Collaborative Forum
March 11, 2025
