• This chapter shifts from models to people, which is honestly where a lot of data work either survives or dies.
  • The strongest idea here is the definition of a Data Head:
    • skeptical, but not cynical
    • technical enough to question things properly
    • willing to advocate for data when it helps
    • aware of domain context
    • able to communicate without acting like the smartest person in the room
    • and, importantly, starts by listening
  • That line is worth keeping:
    • “Becoming a Data Head starts with listening to the entire team.”
  • Because a lot of data problems are not actually “data” problems. They’re expectation problems, communication problems, ownership problems, incentive problems, or domain misunderstandings.
  • And I like the quote at the top too:
    • “People worry that computers will get too smart and take over the world, but the real problem is that they’re too stupid and they’ve already taken over the world.”
    • That’s funny, but it’s also very aligned with the whole book: systems are powerful, but they still need humans who understand context, assumptions, consequences, and people.
  • I’d summarize the chapter as:
    • Good data work requires understanding the humans around the model as much as understanding the model itself.