~/talk

Why modern cross-functional product teams create more friction than alignment

Talkat Agile on the Beach 2026 · 2026-07-02..07-03· [agile-and-product]
links:none on file
slides:none on file

Modern cross-functional teams break from invisibility, not incompetence: the research shows teams chase a 500-user mystery metric, spend two weeks reconstructing years of unwritten decisions, and burn £200k on a £200k telemetry mirage—all after hunting through Slack, Figma, dashboards and source code. The fix is concrete: create a shared system of record, draw what you’re building to surface mismatched models, and always define and assign metrics so numbers map to outcomes rather than prompts for frantic rework.

AI-written summary · about

  1. 0:00Introduction and context
  2. 1:28Cross-functional team friction examples
  3. 8:09Daily team communication struggles
  4. 14:56Engineering blind spots in product decisions
  5. 18:46Thesis on visibility and alignment
  6. 24:03Research methodology and findings
  7. 31:09Costs of lack of product visibility
  8. 33:15Drawing shared mental models
  9. 36:27Anchoring metrics to value
  10. 39:39Friction as a symptom of movement
  11. 41:25Call to action and resources
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.