Disclaimer:
Jenn Steele does work for Amazon.com, but absolutely nothing on this blog or its comments represents the views of Amazon or its other employees.
Nor is it about Amazon or its other employees.
This blog is not affiliated with Paul Glen's company, but he's a great resource, too.
Twitter Updates
- Replied to a colleague's "I'm congested" comment by saying, "Out, damn'd snot!" I'm still giggling 5 minutes later. 1 day ago
- Still drives me nuts. t.imehop.com/165vI4I 2 days ago
- Incredible glass. instagram.com/p/ZgSO0IG9uZ/ 4 days ago
- Omg. instagram.com/p/ZdnDCuG9k3/ 5 days ago
- "Such a happy drink. I was too slow to catch the sparkler tha…" via #Happier happier.com/moments/bbc6b9… 1 week ago
Connect with Jenn on LinkedIn
Excellent advice. Identifying wars and battles is a skill that should be taught (or at least acknowledged) in higher-education and training programs.As a geek, I find that the technical aspects of my responsibilities are often the easiest and have certain/predictable outcomes; defining problems, choosing battles, and convincing others are the more challenging aspects.
It it counter-intuitive as a geek, but sometimes the way to do what is right is to reinforce the status quo. As a Geek you are hoping the other participants will come to their senses and realize how bad the process or idea is. There are some people who will only change their mind when they reach a conclusion on their own.I've read that Benjamin Franklin did a lot of coaching by asking questions to lead people to the answer he wanted to arrive at this way. Certainly he was more patient than most people today.