Tag Archives: talk

Don’t tell me looks don’t matter

There’s a TEDx talk that says looks aren’t everything, and that we should believe Cameron Russell, the giver of the talk, because she’s a model.

Which is hilarious, because she starts off by saying image is powerful.

I mean, doesn’t the very fact that she is a model represent that looks do matter? The fact that there’s an entire industry that revolves around being pretty, an industry focused on tall, slender figures, and all the other physical qualities we’re biologically built to admire. Everything points to the fact that looks do matter.

The very fact that she’s the recipient of a legacy, someone who won a genetic lottery, something that she herself admits she’s been cashing out on, means that looks do matter.

I think she tries to make the point that as much as we admire the people in magazines, the glamourous people who always seem to look good, they’re all constructions. But again, isn’t the very fact that we have all these people working towards the ideal or notion of “pretty”, “hot”, or “sexy”, yet another nail in the coffin of “looks don’t matter”? Clearly, they do.

I like when she says there are people paying a cost for how they look, not who they are. Because, if nothing else, it serves to drive home my point that looks do matter, and thinking anything else is just burying your head in the sand.

Oh, she’s insecure because she has to think about what she looks like, every day? Hey — maybe looks do matter. She’s received all these benefits from a deck stacked in her favour (her words, not mine), and she’s telling me looks don’t matter?

Please. Don’t tell me looks don’t matter — tell me image is important, tell me it’s superficial, but don’t tell me looks don’t matter.

Continue Reading →

It’s Time To Talk Up!

Self-realisation:

Noun;
The fulfilment of one’s own potential.

Nope, that’s not the definition that I wanted!

How about: the act of becoming aware of one’s self.

I guess it’s my fault.

Lately I’ve noticed that I’ve been constantly talking down to people. Working in a retail environment with lots of jargon has contributed to this – usually, people don’t get what I’m talking about when I stick lots of jargon into the conversation, so as a result, I end up “dumbing things down” for them.

Now, that’s all well and good. It’s excellent that I can do that for people who maybe aren’t very familiar with computers, so they don’t understand what RAM does for them. In such cases, analogies are great. There’s this great one we use at work – it explains what the hardware of the computer (CPU, RAM, HDD, etc) does for the customer, while also comparing it to something that they already know (or can at least relate to). It’s not perfect, but it does a damn good job at explaining a complex situation to a customer.

Anyway… this constant dumbing down has seemed to affect how I talk to people who aren’t as technically savvy as I am. Instead of pointing out advanced features, I’m using the “shock and awe” technique more and more – using the simple things to make an impact. Of course, that doesn’t mean that I can’t point out those advanced features, I’m just not doing it as often as I should do.

It isn’t all bad, however. When I’m taking the training class (teaching others, not me), I merely glance over features that will confuse the hell out of people who are new to the operating system. Any mention of Spaces (virtual desktops), for example, usually elicits blank stares and entails me explaining Spaces – again, and again, and again. While keyboard shortcuts are mentioned, I usually leave it up to the user to see if they want to use them. I always give them the choice, though, as I think that keyboard shortcuts are an excellent productivity enhancer.

Now, dumbing things down for those that are technically-challenged is excellent, don’t get me wrong. It’s when I start to take the wrong attitude towards dumbing things down – being lazy and taking the easy way out.

There was one time where an upgrade path would have entailed a long and complicated discussion about RAM, CPU, Hard Drive, and all the rest of it. Now, I could clearly tell that this poor woman wasn’t up to the challenge (not knowing the details of her own computer gave it away) – and that’s exactly where I went wrong. Instead of having that long and complicated discussion, I decided to take the easy way out – and promptly recommended holding off on the upgrade until a new machine was necessary.

Of course, I later discovered her own computer was easily up to the task, and an OS upgrade was all that was necessary. I wasn’t very happy with my own performance on that occasion as you could imagine.

I’m just saying that in order for me to help you, you’ve got to help yourself. There are only so many details that we can elicit of out of you if you don’t know what kind of computer you have – sure, descriptions help, but CPU, RAM, HDD – all are basics that every computer user should know (or at least know how to find out). To this end, I’ve begun teaching the “About this Mac” menu in all my Intro to OSX classes – which will enable people to find out about their Mac should they need that kind of info.

At the end of the day, it was my stuff up. I should have asked the probing questions. I should have tried to get more details about her computer. Alas, I failed.

So gentlemen, it’s time to talk up. Don’t patronise people by assuming you know things that they don’t. Don’t talk down to them because you think you’re somehow better than them.

It’s time. Time to talk up.

Comments below.