On tech savviness
A user's tech savviness has nothing to do with design choices. If a user struggles with basic Gmail functions, how does that affect your design choices? Will you make a simpler experience with less friction? Why…
A user's tech savviness has nothing to do with design choices. If a user struggles with basic Gmail functions, how does that affect your design choices? Will you make a simpler experience with less friction? Why wouldn't you make that simpler experience for the tech nerds too? Cost? Because smoother simpler experiences cost more?
The only use for tech literacy in a product design context is giving research material a few more empty calories. It's the ice cream of Research. Sometimes, you just need to fill some space on a Powerpoint slide. Here are some things I would actually consider before tech literacy:
-
💫 Star sign: I hear Aries don't like material design
-
🍦Favorite ice cream brand: If it's not Häagen-Dazs, they enjoy life anyways, so just give them anything
-
🍔 Favorite cheat meals: if they like pizzas, burgers, and chawarma, they like round things. If it's Pene and Doritos, they like pointy things. Adjust your border-radii accordingly
Only after I have exhausted these ludicrous considerations, will I consider someone's relationship with IT. Tech savviness affects priorities in training, onboarding, and marketing, but certainly not the product itself 😉