Yes — Let's Aim for Exploratory, Adaptive Teams and Organizations!
summary
Teams often face an “exploration deficit” where product work keeps optimizing past successes until technical and knowledge debt create a crisis. Recommends reserving part of the backlog for hypothesis-driven research (e.g., start with 1–5–10% or shift 2 of 10 items = 20%), embed exploration into OKRs, and either make exploration a PO-led activity or create a separate exploratory team, plus concrete research methods, sprint cadence, and decision criteria for judging learning.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:29Cliffhanger state
- 5:01Optimization traps
- 8:30Endless optimization
- 11:02Exploration vs exploitation
- 13:27Exploratory teams
- 16:17Building new peaks
related talks
39mReawakening Agile with OKRs
09mBuilding High-Trust Teams to Supercharge Product Development
11mEngage teams to achieve high performance
47mReawakening Agile with OKRs
28mUser Stories and other agile failures
33mAligning Goals & Processes between Engineering & Product
46mReawakening Agile with OKRs
46mHow to make OKRs Lean again