Thursday, March 13, 2008

1.2 There is no "I" in "Meme": Language


The language we use, whether it beongs to our culture, subculture, technical tool or organization, affects our fundamental perceptions, choices, and behavior (and we rarely notice).

[T]he language a person speaks [affects] how that person both understands the world and behaves in it. [...] Different language patterns yield different patterns of thought. -- Sapir-Whorf Hypothesis, Wikipedia
The world, and the process of living, are inherently continuous and nameless. To communicate about them, we humans use our amazing minds to interpret them down into structures, finite bits with ends, beginnings and apparent affinities with other bits. We come up with those structures by drawing from our history, our cultural biases, our priorities, which themselves are created by language in an ongoing feedback loop. There is no "accurate" way of describing the world, and thus there is no objective way. There's just the way that you happen to be using.

A language is a very heavily biased cultural description of the parts of the world that it cares about, and its own priorities. For example:

In American culture (and some, but not all, other cultures), words about sex and sexual organs are used as the strongest forms of insults. It would be ridiculous for me to insult you by calling you a "stupid arm," but we find the word [cxxx] so offensive that I can't even directly reference it in this blog. This use of language reflects, and perpetuates, certain cultural assumptions about sex.

The languages of subcultures and organizations also codify, teach and perpetuate, unconscious cultural values and expectations.


A close friend of mine just became a cop. He is a deep and thoughtful person with a strong protective instinct. I was thus surprised, in recent conversations, to hear him talking about apprehending and charging people as "contacting" his "clients."
For me, "contacting a client" means calling someone who has voluntarily hired you and maybe leaving them, say, a voicemail, or perhaps a nice fruit basket. For his unit, "contacting" someone might mean chasing a guy four blocks, fighting him to the ground with the help of three other officers, finding a gun and a gram of coke on him, and taking him to jail where he will develop his first criminal record, permanently changing the course of his life.

Contrast this linguistic convention to some other options: instead of "Today I contacted four clients," make it "Today I handled, then made life-changing decisions towards, four human beings." Or, alternately: "Today, I wiped the floor with four more scumbags." The neutral language employed by my friend's unit serves two instructive purposes: it facilitates the emotional detachment that makes policework possible, and it restricts that detachment to the universe of professionalism and service.

So, yes: the linguistic structure you use effects how you think and act. But while changing a language is often a part of changing a social system's rules and behavior, it is rarely the direct route. If you had a goal, for example, to make all police highly sensitive to the human realities of the people they are arresting,* you might think it would be smart to change the institutional language from "contacting clients" to "Making Choices to affect Human Beings." But if your police still (for example) (1) have to fill an ambitious weekly quota of arrests to succeed at your unit, and (2) only see the perp at the time of the arrest (no exposure to context or after effects), your new language won't change their approach to the job. It will just irritate them as phony polish on top of the job's harsh reality.

I don't know about you, but I see surface-level language "fixes" in the industry all the time, and they drive me directly to drink.

To learn more about this fascinatng topic, you may want to read this highly-recommended book: Sorting Things Out: Classification and its Consequences.**

* And I hope you do not
** Lord knows I want to read it. It's on my short list.

Stay tuned for: 1.3 There is No "I" in "Meme": Culture

Tuesday, March 4, 2008

1.1 How to Build Horrible Social Systems by Accident: Incentives


In the last entry, I proposed that tools and organizations, often (make that usually-- actually make that almost always) unintentionally bake into their very structures a set of implicit instructions for their members / users about what behavior is appropriate, rewarded, or discouraged.

How, exactly, do they do that? Here are some of many possible answers.
Incentive Systems. Behaviors rewarded by your system or tool will grow in emphasis and frequency; behaviors that are punished will become less frequent. This statement may seem obvious; people are always trying to leverage positive or negative incentives to get one another to do things. Unfortunately, those conscious incentive programs are usually laid on top of preexisting incentive systems that are deeper, more subtle, more ubiquitous, and far less intentional. In other words, they are much more convincing to the people involved, and are impossible to casually override.

Example: You have a new software company, and you have to hire some people and then give them employee reviews of some kind. Like many orgs, you base your employee review system on whether or not an employee succeeds at his projects. If he succeeds at all of them, he gets a raise; if he fails at his projects, he gets a poor review and a lower bonus. If he gets three poor reviews in a row, he gets fired.
While this seems like a simple and obvious incentive system, you are literally incenting your average employee (let's call her Martha Generic) to succeed at her own projects… even if that messes up everyone else's. If she sacrifices her own project, one quarter, to enable four other projects to succeed, she will still be punished by your system.

Example, Cont'd: Five years down the line (after every manager in your company has worked your incentive system into dozens of mini-processes and deliverables), you discover your employees aren't collaborating. You say to yourself: "These poor geeks just don't know how to collaborate. I've got to get them thinking like a team…"

You start publishing some weekly articles on the importance of collaboration. You deliver a motivational speech to the whole company about how software development is really about putting "people first." You offer a trophy for the "most collaborative team member."

Will it work?

What would happen if you created an online community (let's say, a "resource group for workaholics") and let your members give each other public ratings (1-5 stars) on two things: "Humor" and "Best Vocabulary"? … What if it were an automated system that gave privileges based on "Most Links Contributed"?


Next up: 1.2 There is no I in Meme: Language and Messaging

1.1 How to Build Horrible Social Systems by Accident: Incentives


In the last entry, I proposed that tools and organizations, often (make that usually-- actually make that almost always) unintentionally bake into their very structures a set of implicit instructions for their members / users about what behavior is appropriate, rewarded, or discouraged.

How, exactly, do they do that? Here are some of many possible answers.
Incentive Systems. Behaviors rewarded by your system or tool will grow in emphasis and frequency; behaviors that are punished will become less frequent. This statement may seem obvious; people are always trying to leverage positive or negative incentives to get one another to do things. Unfortunately, those conscious incentive programs are usually laid on top of preexisting incentive systems that are deeper, more subtle, more ubiquitous, and far less intentional. In other words, they are much more convincing to the people involved, and are impossible to casually override.

Example: You have a new software company, and you have to hire some people and then give them employee reviews of some kind. Like many orgs, you base your employee review system on whether or not an employee succeeds at his projects. If he succeeds at all of them, he gets a raise; if he fails at his projects, he gets a poor review and a lower bonus. If he gets three poor reviews in a row, he gets fired.
While this seems like a simple and obvious incentive system, you are literally incenting your average employee (let's call her Martha Generic) to succeed at her own projects… even if that messes up everyone else's. If she sacrifices her own project, one quarter, to enable four other projects to succeed, she will still be punished by your system.

Example, Cont'd: Five years down the line (after every manager in your company has worked your incentive system into dozens of mini-processes and deliverables), you discover your employees aren't collaborating. You say to yourself: "These poor geeks just don't know how to collaborate. I've got to get them thinking like a team…"

You start publishing some weekly articles on the importance of collaboration. You deliver a motivational speech to the whole company about how software development is really about putting "people first." You offer a trophy for the "most collaborative team member."

Will it work?

What would happen if you created an online community (let's say, a "resource group for workaholics") and let your members give each other public ratings (1-5 stars) on two things: "Humor" and "Best Vocabulary"? … What if it were an automated system that gave privileges based on "Most Links Contributed"?


Next up: 1.2 There is no I in Meme: Language and Messaging

Monday, February 25, 2008

1 of 4: Structure Influences People

Premise #1.0: The structure of a tool influences the people who use it, and the structure of an organization influences the people who belong to it.

Premise #1.1: We don't act nearly as independently as we think we do. All day long, we are listening for cues about what behavior is appropriate in each context. We also broadcast cues as to what behavior is rewarded, acceptable, or inappropriate.

Example A: You're invited to an acquaintance's house; he's "having some cool people over." He has spiky hair and a nose ring. So, you grab your Immortal Technique CDs and take a cab out to his place, expecting to tie one on and get loose. You get there and discover that, (1) the table is set with a white tablecloth and matching silverware, and (2) there are wine glasses. You instantly realize this is a Grownup Party. Chagrined, you start greeting the other guests with conversation about work while privately lamenting your wasted $30 on cabfare.

Example B: Usually, the lady checker with the orange hair at the Red Apple asks "How are you?" in a monotone while she's typing your produce codes with one hand and checking her watch with the other. You respond: "Fine, thanks, and you?" But today, she notices you look kinda off. You come up to the counter, and she sets her pen down and places both hands on the counter. She looks into your eyes, and says: "How are you?" You say: "Pretty lousy. I'm just not sleeping well. I stress too much."


This is our symbolic, implicit, fantastically complex language of human aggregation: we tell each other what to do all day long without saying a word.

Organizations and tools bake these messages into formal structures that tell people what behavior is desirable and what is unacceptable. When we successfully and ritually use the tool or belong to the organization, we adopt those behaviors. Usually, we adopt them unknowingly; often, we do it involuntarily.
Premise #1.2: It's important to set up tools and systems to encourage the behaviors that you want, and discourage the behaviors that you don't.
The more unconscious those behavioral handshakes between us and our org/tool, the more likely they are to affect our perception of ourselves, and our ability to see a broad set of options and to make decisions.
Premise #1.3: If you have a system where a group of people are doing the same odious thing over and over again no matter how often you try to get them to stop, look at the rules of the system they belong to.
Next up: 1.5: How to Build Horrible Social Systems by Accident: Incentives. This is one of several entries fleshing out the theme of "Structure Influences People." It will be the first in, time willing, a short list of tools I learned about in academia that aim to analyze structure and its influences.

Sunday, February 3, 2008

Like a Pimp

So I'm walking near my house and ahead of me is this very animated Black guy, mid-50s, talking exuberantly alongside his long-suffering, fat, disenfranchised girlfriend.

"You know, you know!" He's saying. "Like a pimp." He's faking a big hitch in his step. "You know."

I am highly amused by this. He looks over at me, catches my eyes/smirk, and, thrilled, re-directs his story to me. "YOU know," he calls, with a huge grin, exaggerating the hitch in his step. "Like a, like a pimp!"

I nod at him in empathy, continuing on my way. He calls back to me: "They said-- They said I couldn't be a pimp." I laugh, and his excitement redoubles. His fat long-suffering girlfriend pretends not to notice.

"See, I can't be a pimp," he yells down the block at me. "Mm-mm, yep! See I filled out, I filled out the paperwork to be a pimp, but they said I couldn't be a pimp. They said I couldn't be a pimp because I fall in LOVE too easy!"

I am trying to control my amusement as I enter my building. "See," he shouts after me, just delighted with himself: "You can't be a pimp if you fall in love!"

Monday, June 18, 2007

Bullet Points are a Privilege, Not a Right

From a recruiter email that wound its way to my inbox:
Requirements:
  • Must have worked with "Infopath 2003" and a Project exp on Infopath 2007
  • or at least very good understanding of Infopath 2007
  • Infopath is the main Skill.
(Unless you are Louis Borges. If you are Louis Borges, lists, bulleted or otherwise, are in fact a right.)

Tuesday, February 6, 2007

Ways to Die in Your Home-- The Musical

Rules:
  • must be a song title (or band name, or album name); may include surrounding lyrics
  • must be a way to die -in your home- (So "in the jungle / the mighty jungle / the lion sleeps tonight" does't count)
  • must be a primary, not secondary, cause of death (so no "slipped while putting on Blue Suede Shoes"-- rule can be broken if justification is funny enough).
Ways to Die in Your Home, General
  1. Zombie
  2. (if diabetic) Pour some sugar on me
  3. Take my breath away
  4. Maneater
  5. (bitten by) Karma chameleon
  6. You dropped a bomb on me
  7. I'm too sexy (for my pulse)
  8. Be still my beating heart
  9. Winona's Big Brown Beaver
  10. She's a maniac!
  11. Smoke gets in your eyes
  12. Jump
  13. Love bites
  14. Tainted love ("if only there was a song called 'tainted meat'")
  15. Hunka hunka burnin' love
  16. Sabotage
  17. Barracuda
  18. Magic Man
  19. That old black magic
  20. Love will tear us apart (again)
  21. I've got my love to keep me warm (ineffective!)
  22. Worldwide suicide
  23. The macarena
  24. The... Larch
  25. Rock lobster
  26. The boxer (picture "Pulp Fiction")
  27. Peace train
  28. Lightning striking again
  29. Criminal (Fiona Apple)
  30. Killing me softly with his song
  31. Crash (Dave Matthews)
  32. Walking on broken glass
  33. Fast car
  34. That girl is poison
  35. Cats in the cradle (they kill babies)
  36. Everybody was Kung Fu fighting
  37. Pachebel's Canon
  38. Rock me (as in Biblical stoning; let he who has no sin cast the first power chord)
  39. Rock me, Amadeus
  40. Go, Go Godzilla
Natural Disaster / Plague
  1. Great Balls of Fire
  2. Millions of peaches
  3. Ice, Ice, baby.
  4. The tide is high
  5. Chariots of fire
  6. Heat Wave
  7. Rapture
Illnesses
  1. He gives me fever
  2. Cat scratch fever
  3. Saturday Nigh Fever
  4. Heart of glass
  5. Achey breaky heart
  6. Lump (think: oncology)
  7. Groove is in the heart (how tragic... they say it's hereditary)
AAAAIIIiiiieeeeeee
  1. Walking on sunshine
  2. Walking on a thin line
  3. Hangin' 'round
  4. He ain't heavy, he's my brother "Oh, wait-- he IS heavy!"(AAAAIIIiiiieeeeeee tumble tumble tumble CRUNCH)
"Clue" Version
  1. Sledgehammer
  2. Brass Monkey
  3. Monkey Wrench
  4. She bop
Death by Trogdor
  1. Burning down the house
  2. Beds are burning
  3. Disco inferno
  4. Burnin' for you
  5. She's on fire, my baby's on fire
  6. Doctor, Doctor, can't you see I'm burning, burning?
Darwin Awards
  1. Why don't we do it in the road
  2. All she wants to do is dance (and doesn't eat)
  3. One burbon, one scotch, one beer (repeat)
  4. Highway to Hell
  5. Highway to the Danger Zone
  6. Cocaine
  7. One toke over the line, sweet jesus
  8. (Died while) Fighting for my Right to Party
  9. Tripping on a hole in paper heart
  10. Learning to fly
  11. Dancing on the Ceiling
Not Politically Correct
  1. Baby hit me one more time
  2. Hit me with your best shot
  3. Little red corvette (picture baby + matchbox car)
Situations Which, if Not Carefully Monitored, May Cause You to Die in Your Home:
  1. Celebrate good times, come on
  2. Hurts so good
  3. She's so heavy
  4. Do that to me one more time
  5. Blister in the sun
  6. Everybody hurts
Things Which will Make You Wish You had Died in Your Home:
  1. Losing my religion
  2. Shiny happy people
Most Existential way to Die in Your Home:
  1. Time keeps on slippin', slippin', slippin' into the future



Band Names: Ways to Die in Your Home
  1. Fine Young Cannibals
  2. Sting (saved by: The Cure)
  3. The Beatles
  4. The Rolling Stones
  5. (comic book style) Wham!
  6. The Scorpions
  7. The Cranberries
  8. AC/DC
  9. Bjork



Album Titles: Ways to Die in Your Home
  1. Jagged little pill
  2. Automatic for the people