jordan_lee0 views
I keep reading that you should write the measurement plan first. In practice I mostly see tracking added when someone asks for a report. Do you actually write one? What does it look like, and how long is it?
Be kind and specific. Read the community guidelines.
Mine is one page. Business question at the top, then for each question the metric, the event that feeds it, where the event fires and who owns it. When I skip it, I regret it at the first report.
One page, yes. The most useful column is the one that says what decision the number will change. If the answer is "none", we do not track it.
That column is going into my template. It also ends a lot of requests for "just in case" events early.
There is a worked example in Write the measurement plan before you write the tracking code, with the one-page layout people describe here.