The doctor returned from his lunch break, a carefully regimented respite to relax his brain by exploring the nuances of the campus with a sandwich and coffee, to find his microscope wasn’t working. The door was locked. Nothing seemed disturbed. He tried a few things before calling in for help. “IT, this is Sam.” “Hi Sam, Dr. Florigen. My microscope isn’t working.” “Can we run some tests over the phone or should I run over?”
“I.T., this is Sam.”
“Sam, Tia. Got a weird one, but first, how’s your baby? Healthy?”
“She’s stoked to be over at my parents this week, thanks-”
“Sure. Occasionally seeing this since yesterday. Rebooted. Sent you photo. Says battery life: 6800 hours.”
“Huh. Well, does it hold a charge?”
“Yes, going bad?”
“Probably… I’ll email you the battery model. Expense it, send me the weird one, and let me know if it persists.”
“Sure, appreciated. Bye!”
“Let’s make a list of everything that’s been happening. We’ll iron the issues out one-by-one.” “Let me just tell you the truth. This thing is a piece of…” That’s my cue that the issue is not technical. We aren’t troubleshooting a technical issue, per se, instead I’ve stepped into the role of therapist helping ease the technojunkie’s technological anxiety. Without getting into specifics, here are five strategies I’ve used to talk people off their cliffs.
In last week’s brainstorming update to “The Story,” I covered how main characters Trishna and John (left) would clash. Even the most connected people clash, after all, especially when both are fiercely independent. It’s about balance: if one is more comfortable jumping into the fray than thoroughly researching, let them perform their strengths to build a more cohesive team. Let’s see how they solve problems, and how teams solve problems, in this Applied Psychology crossover:
Spoiler Warning Scale: None! (just brainstorming)
WANNA READ MORE ANALOGIES FOR CONFLICT RESOLUTION? KEEP ON READING!