Discussion about this post

User's avatar
Drew Harry's avatar

This strongly resonates with me.

I'll offer an extension to this argument that I see with data staff. I have observed for some years that data teams exist in part so that leaders can avoid having to exert their own autonomy. Even at the C-level in an org, people seek the sweet release of being presented a table that makes a decision so blindingly obvious that there can be no ambiguity about what to do next.

Sometimes this turns into feedback we offer our teams. "I wish your reports had more of a 'so what' to them." To which I say, who is making the decision here? Why is it my job to tell you what to do? It's not my decision, it's yours.

So often I have seen leaders convert a complex strategic question into a data question. Like "if I saw [metric] above [value] I would think we should choose [strategy]." These are not totally arbitrary connections, but neither do I think it's actually prudent to link the decision to that narrow value. It alway seemed to me like a desire to distance oneself from stating clearly "I think we should do [strategy]" and assume accountability for the consequences. Because if you can link a decision into a piece of data, then accountability becomes diffuse. It's not that you made a choice that turned out poorly, it's that maybe you didn't ask the right data question, or there was a mistake in the analysis, or something you couldn't measure was actually determinative of the result in a way you didn't predict. All this complex messy stuff.

Leaders need to make decisions. Data is sometimes a useful input. But it is very rarely indicative of one "correct" decision. What else is the point of agency?

Expand full comment
DJ's avatar

One thing I’ve learned from doing startups is you need a very high tolerance for ambiguity.

Expand full comment
21 more comments...

No posts