✳flâneur — a map of the web's best reading

Goals, Signals, and Metrics | The LinkedIn DPH Framework

linkedin.github.io · 1,247 words · saved by 1 readers

Basically, first you decide what the goals are that you want to achieve for your product or system. Then you decide on the signals you want to examine that tell you if you’re achieving your goal–essentially, these are what you would measure if you had perfect knowledge of everything. Then you choose metrics that give you some proxy or idea of that signal, since few signals can be measured perfectly. A goal should be framed as the thing that you want your team, product, or project to accomplish. It should not be framed as “I want to measure X.” Most of the trouble that teams have in defining metrics comes from defining unclear goals. Webster’s Third New International Dictionary defines a “goal” as: The end toward which effort or ambition is directed; a condition or state to be brought about through a course of action. This needs to be stated in a fashion specific enough that it could be measured. Not that you have to know in advance what all the metrics will be, but that conceptually, a

Goals, Signals, and Metrics | The LinkedIn DPH Framework The LinkedIn DPH Framework Goals, Signals, and Metrics There is a framework we use for picking metrics called “Goals-Signals-Metrics.” Basically, first you decide what the goals are that you want to achieve for your product or system. Then you decide on the signals you want to examine that tell you if you’re achieving your goal–essentially, these are what you would measure if you had perfect knowledge of everything. Then you choose metrics that give you some proxy or idea of that signal, since few signals can be measured perfectly. Goals

Explore this link on the map →

related reading