How many clicks?

How many clicks does it take for your business teams to get to the data they need?

Last week I had to access a database inside a customer’s secure network.

I had to log in to a desktop virtualization platform (citrix), sign in to a VM, launch a database client, log in to the server, and then issue my one simple query.

It took about 5 minutes, three multi-factor authentication alerts on my phone, three times typing in a long password, and a few uncertain moments when I looked at the long list of obscure server names and tried to remember which one I was supposed to use.

I didn’t count clicks and keystrokes but it was a lot.

All to find one piece of data.

That’s probably a bit extreme, but not as rare as most think. It makes for a terrible data experience.

Your business team will quit before getting to the data they need to do their job.

Building better data experiences means listening and watching how many clicks, links, logins, filters, or tables a user have to navigate through in order to answer their question.

Remove the friction points so the data can serve the business.

Thanks for being here,

Sawyer

p.s. Want help identifying friction for your data experiences? Hit reply or schedule a call.