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
"Jazz soloists draw from a lifetime of patterns, sometimes quoting TV theme songs like the Muppets or Sanford and Son."
Jim KalbachJazz Improvisation as a Model for Team Collaboration
November 6, 2017
"You want someone who writes with equal parts empathy and authority, not just pure authority."
Louis RosenfeldCoffee with Lou: Should You Write a (UX) Book?
March 7, 2024
"Levels can mean really different things at different companies, so ask a lot of questions about expectations for each level."
Catt Small Micah Bennett Brian Carr Jessica HarlleeWhat's Next for ICs: Exploring Staff and Principal Designer Roles
February 22, 2024
"Typically we get stuck answering the questions we know we can answer but lose the chance to see the big picture."
Marieke McCloskeyUser Science: Product Analytics & User Research
March 11, 2021
"Processing limits and licensing terms currently restrict how much video and audio these AI tools can handle."
Llewyn Paine[Demo] Deploying AI doppelgangers to de-identify user research recordings
June 5, 2024
"You don’t want to overdesign just to make something more data interpretable because that can lead you down a dark path."
Joshua NobleCasual Inference
October 6, 2023
"Stakeholders are users too; the product we’re sharing is the research and learnings for their decision-making."
Sara LogelYour Colleagues are Your Users Too
March 29, 2023
"There will be session notes and sketch notes so you don’t have to take notes yourself unless you want to."
Bria Alexander Louis RosenfeldWelcome
January 8, 2024
"Timely interactions that log users out without saving progress cause abandonment, especially for people with disabilities."
Sam ProulxOnline Shopping: Designing an Accessible Experience
June 7, 2023
