This link has been bookmarked by 74 people . It was first bookmarked on 19 Jul 2006, by thynnus.
-
23 Oct 10
-
Geeks are curious. Let them feed their desire to learn things
-
Geeks like to be self-sustaining. Let them figure things out on their own.
-
-
09 Feb 10
-
06 Jan 09
eighteyesThere’s many ways to complete a task in the technical arena, why cram your solution down their throats? Don’t hinder their creativity, just let them f
-
14 Apr 08
-
28 Feb 08
-
21 Jan 08
-
01 Dec 07
-
26 Nov 07
-
08 Oct 07
-
19 Sep 07
-
This point is based on the notion that if a geek feels his ability to gain knowledge is hindered he’ll try to find it somewhere else. Let them satisfy their curiosities with the task of picking up the latest technologies and applying them as they see fit. (Even if it’s just for a prototype.)
-
Don’t hinder their creativity, just let them figure it out. The exception to this is probably in design. You obviously have to define your interfaces between components and have your requirements for the implementation. Let the details get figured out by whoever’s doing the dirty work. You can optimize things later if they aren’t up to par.
-
-
21 Aug 07
-
25 Jul 07
Matt SaundersBeing a geek myself, I think this is a subject I think needs to penetrate all levels of management in every company that values their geeks. By no means is this a rant, but for the last 10 years I’ve seen what motivates us and what doesn’t. I’ve see
-
13 Jul 07
-
07 Feb 07
-
19 Jan 07
-
17 Dec 06
-
12 Dec 06
-
2. Geeks like to be self-sustaining. Let them figure things out on their own.
I haven’t met a true geek yet that wants you to hold their hand through every step of an implementation. In fact I’ve seen quite the opposite. They want to do things their way. If you suggest something, odds are the solution is wrong in their mind because it’s not what they would have come up with first. There’s many ways to complete a task in the technical arena, why cram your solution down their throats? Don’t hinder their creativity, just let them figure it out. The exception to this is probably in design. You obviously have to define your interfaces between components and have your requirements for the implementation. Let the details get figured out by whoever’s doing the dirty work. You can optimize things later if they aren’t up to par.
-
3. Geeks are creative even if they don’t know it. Give them a chance.
One thing I’ve seen is that most geeks don’t see themselves as very creative. Give them the task of creating a GUI tool of some sort and they’ll butcher it up and say “get someone with art talent on the job; I just know how to make it work”. Now this may be true as far as what’s appealing to the eye, but geeks have creativity inside them somewhere.
When you give them a requirement for a component that’s just out of reach with the normal cookie-cutter solutions, who’s jumping at the chance to dig on the web for solutions that could work? Who’s rattling off a dozen ideas for things to try that might work with the newfound constraints? That’s right, it’s management.
(Just kidding, though everyone has their moment…who knows? Some managers are geeks too.)Even if none of the solutions the geeks come up with will work, it’s a vast pool of creative ideas to feed from. Though they see themselves as equation-solvers with little creativity, I see it as opportunity. Let them apply their creativity. They love to be in the brainstorm process instead of pushed to the wayside as a later-used resource.
-
-
03 Dec 06
-
19 Nov 06
-
08 Nov 06
-
04 Nov 06
-
25 Oct 06
-
24 Oct 06
-
21 Sep 06
-
14 Sep 06
A nice list of the ten ways you can best satisfy geeks in your organization (The Retrospector, June 21 2006).
leadership work business productivity management geek motivation docbadwrench
-
06 Sep 06
-
21 Aug 06
-
04 Aug 06
-
25 Jul 06
-
21 Jul 06
-
20 Jul 06
-
19 Jul 06
-
18 Jul 06
-
17 Jul 06
-
10 Jul 06
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.