Tina Turner on Google Analytics

Earlier this month I submitted an idea for a piece to UXmas. They accepted it, and now I need to get a final version to them.

It’s going to be a short post on the value of design documentation, and I’m trying to decide if I should make it into a video or make illustrations for it … I know which wine I’m serving — I just haven't decided what kind of glass to serve it in.

The problem has been stewing in the back of my brain all week.

This morning, in the shower, I had Tina Turner stuck in my head:

🎵 What's documentation got to do, got to do with it

What's documentation but a second hand emotion

What's documentation got to do, got to do with it

Who needs Google Analytics when a Google Analytics configuration can be broken

OHHHHH … 🎵

I need to get the thing done before I lose my mind.

In the meantime, I thought I’d ask how you handle design documentation at your work.

When you develop new content — launching a newsletter series that’s meant to bring in donations, for example — does someone record it in some way? Do you mark the dates so you can later study which emails were most effective at bringing in donations?

When you revise content on your website does someone first make a record as to how the original content performed? Do you have some shared repository that shows how the first version of that page contributed, if at all, to a business goal? Do you revisit Google Analytics after the new version is published to see if the work you did had a positive influence on visitor behavior?

Hit reply and tell me how your company measures the impact of design changes.

Even if you’re not documenting design efforts, maybe someone else in your organization is. Or, if no one is doing this kind of recording, what prevents you from doing it? Is it something you’ve never considered before? Maybe you’re not sure it’s worth the trouble.

Let me know either way — I’d love to hear from you.

Thanks for reading,

Kyle

Kyle Bowen