Who does what by how much?
Summary
More than ever, we’re tasked with building ways for humans to interact more efficiently with one another, with services, with machines, and now with AI. As the toolset grows as quickly as the challenges we need to solve, how do we know we’re building the right things in the most valuable way? In this practical talk, Jeff will bring together the world of product and service design to focus on the humans in the mix and how to ensure that everything we create has a meaningful, positive impact on them.
Key Insights
-
•
The core value equation in designing services is who does what by how much, focusing on measurable changes in human behavior as outcomes.
-
•
Historically, learning loops to validate product value took 6-12 months, but modern digital services like Amazon enable deployment every second, allowing rapid feedback.
-
•
Managing towards output—the delivery of products or features—often undermines true customer value and slows organizational agility.
-
•
Effective OKRs focus on qualitative objectives describing the desired future customer state without prescribing solutions or features.
-
•
Key results must be outcome-based metrics measuring actual behavior change rather than output milestones.
-
•
All teams, including HR, finance, and legal, can and should use outcome-driven OKRs by focusing on how their outputs change human behavior.
-
•
Product discovery processes like design thinking and lean UX are essential for teams to identify the right solutions in an outcome-driven OKR framework.
-
•
AI-powered customer experiences introduce unpredictability in inputs and outputs, increasing the complexity of designing effective systems around human behavior.
-
•
Successful OKRs require both top-down strategic alignment and bottom-up team goal setting, with negotiation to ensure cohesion.
-
•
Changing incentive systems from rewarding output delivery to rewarding learning, evidence-based decision making, and customer centricity is crucial for OKR adoption.
Notable Quotes
"We can’t predict the future; all we can do is make the best guesses based on what we know right now."
"Amazon deploys new code into production into the hands of customers once every second."
"Managing towards outputs means someone has decided what the solution is going to be and told you to make that thing."
"Our goal ultimately is not to deploy a static solution but to make sure humans in the system achieve their goals successfully as often as possible."
"Objectives are qualitative, inspirational statements about the future we want to create for our customers without mentioning any solutions."
"Key results must be measures of human behavior and outcomes, not output metrics like 'launch this service'."
"Everyone has a customer — whether external users, third-party vendors, or internal colleagues; those humans consuming your product are your customers."
"If you don’t tell teams what to make, they need a product discovery process to decide what to build."
"Changing course based on evidence of actual human behavior is what agility really means."
"For OKRs to work, incentives have to focus on learning, customer centricity, and evidence-based decision making, not just delivery."
Or choose a question:
More Videos
"Stress makes us stupid because our creative thinking gets cloudy when under pressure."
Laura WeissTurn Down the Heat: 3 Ways to Handle Conflict in the Moment
November 20, 2024
"We have two competitors: Canine Corp and e-pets, but e-pets is over-diversified, even pet rocks."
Ted NewardTheme 4: Enterprise Organizational Journey
June 4, 2019
"Apple solved the problem of making touchscreens accessible by inventing VoiceOver and providing rich APIs for developers."
Sam ProulxTo Boldly Go: The New Frontiers of Accessibility
September 9, 2022
"Building a network early can create amazing opportunities further along the career path."
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
"Without a design ops function, teams make their own flavors that dilute brand and accessibility."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025
"More frequent change isn't always better; good communication and team pulse are key."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"We connect design decisions back to business performance and risk metrics to answer the concerns of our partners."
Frank DuranPartnership Playbook: Lessons Learned in Effective Partnership
January 8, 2024
"Flow is different for each person; you have to adjust your style based on who you work with."
Ruzanna RozmanGetting in Flow with Your Team
January 8, 2024
"There’s no one-size-fits-all approach; budgets and needs vary widely across researchers and organizations."
JP Allen Carrie Boyd Malcolm EvansNavigating the UX Tool Landscape
March 11, 2021
