Field note · May 8, 2025
Reader question — What a data team is actually for
The job is not producing numbers. It is reducing the number of decisions that get made badly, and almost everything else follows from that.
Reader question on What a data team is actually for, and the answer belongs somewhere more findable than an email.
The job is not producing numbers. It is reducing the number of decisions that get made badly, and almost everything else follows from that.
The question was, roughly, "when does this stop applying?" — which is the right question and the one lessons routinely fail to answer. Every technique has a range of validity, and stating it is what separates a lesson from a recipe.
It sits in the Foundations module. The exercise is a thinking one rather than a query one — some of this material is about deciding what to compute, and that does not need a keyboard.
Ordering matters here more than in most courses. It opens the module and leads into Rows, grain, and the shape of a dataset, and reading it out of sequence mostly works but costs you the setup.
Free means free, and it also means we can rewrite it whenever it is wrong. No edition, no errata PDF, nothing to repurchase. The whole course is 36 lessons and the fixes land the day we find them.