Developping for the translation industry RSS 2.0

 Thursday, March 18, 2010
InnovationHere are some tips to spot people who are likely innovators.  In this way, you can identify them more quickly, and choose to hire them if you want to be more innovative, or you can ignore and avoid them if the status quo is more your thing.  Good luck with that strategy, by the way.

Identifying people who are innovators is actually relatively easy.  They are the ones who don't actually seem to belong the organization in the first place.

Innovators tend to:

  1. Reject the standard framing of a problem and restate the problem or opportunity.  Rather than work within the given constructs or framing, many innovators want to toss out the framing and start anew.  Just like Galileo, this may require working against an orthodoxy, yet nonetheless, it moves and so must we.  Those folks who are so problematic about wanting to change or expand the framing of a problem?  Probably good innovators.
  2. Be optimistic.  They are almost always the glass half full people.  Pessimistic people will focus far too much energy on the "problem" while innovators will acknowledge the problem and move on to find interesting solutions.  They believe the problems are merely temporary barriers to more interesting solutions.
  3. Look to the future for signals rather than to the past.  In most businesses, many people will ask "has this been done before" and "what can we learn from that success or failure.  Innovators want to know "can we be the first" and what signals in the market or environment give us indications that we'll be successful
  4. Care about solving unmet or poorly understood challenges.  Often innovators are going beyond the obvious, ordinary problems to uncover deeper unmet or poorly understood issues.  If your team is captivated by solving an obvious and incremental problem, they aren't innovators.
  5. Network with people different than they are.  Evidence suggests that the best innovators are people who read outside of their industry, interact with people from many different backgrounds and interests and seek to bring solutions from outside their industry to the table.  People who are very deep in one industry but ignore signals and solutions from other industries are usually not very innovative.
  6. Are proactive.  Innovators actively seek change while many executives are content to wait and react to what other firms do.
  7. Are dissatisfied with the status quo and willing to change it rather than simply accept the status quo and merely complain.
  8. Are very comfortable learning, trying and failing, and then trying again.  They aren't stymied by a single failure and are usually very determined to start again, reframe the problem and try a new tack or approach, learning from previous failures and incorporating that knowledge.
So, if you are in the market to hire someone and want to know if he or she is likely to be an innovator, look for these signs:

  • Ask them about an existing problem that you have.  See if they are perfectly willing to accept your framing, or if they request the opportunity to reframe or change the frame entirely.  If the latter, a likely innovator.
  • Ask them about existing societal problems or corporate problems or challenges.  Listen to how they approach the problem and their willingness to suggest changes or alternatives and the possibilities they suggest for change.
  • In the context of a problem, what information do they seek - external, future oriented or internal information about the past?
  • Can they name a big failure in their lives and demonstrate what they learned and how that failure helped them gain more insight into an eventual solution?
  • Can they name five people in relatively senior positions they interact with on a regular basis who are from different industries?  Can they demonstrate an active network outside of their "home" industry?

The kinds of answers you get with these questions will tell you how strong the "innovation" force is within the candidate, and whether you should hire that person or turn the Force against them.

Photo source: vermininc


Other posts:

Once in a while, stop and pay attention...


What Are Customers Saying About You Online?

Hiring and managing geeks

Thursday, March 18, 2010 10:48:53 AM (Eastern Standard Time, UTC-05:00)  #    Comments [0] -
Hiring | Management
 Thursday, January 15, 2009

I’m back from my little vacation and I just found a great post on managing teams of developers, programmers and others geek-type employees.  I think the author is right on point and I agree with him on everything.

Here are my favourites from his post:

Try to measure productivity in output, not in hours.

Geeks automate. Geeks script. Geeks compile. They summon computing power to get things done quickly on their behalf. If your geek seemingly spends all day on Twitter and Fark but somehow manages to still complete tasks ahead of schedule, your geek is multi-tasking. This is normal.

Assign tasks to the geeks who are most interested in them, not the ones with the most experience.

When geeks are interested, they are passionate. When they're passionate, they learn fast. You'll get more productivity out of an interested geek with no prior experience than you will with a bored drone who's been doing the same thing for the past five years. Sometimes, the one with the most experience is the one that's most interested. In those cases, you are a lucky manager!

Segregate the corporate, compensatory hierarchy from the leadership hierarchy.
With a team of geeks under you, one or more will eventually become to go-to guy (or girl) for certain things. You don't usually need to assign a "team lead" - Through meritocracy, the Alpha Geek will emerge. That Alpha Geek may lack seniority, but will have the most influence. It's best to let this occur naturally. It's awkward when the one who best fits the role has to answer to someone else just because they've been around longer. Furthermore, the members of your team will still go to the Alpha Geek because the wrong person has the "Team Lead" label. As Paul Glen puts it: Geeks don't hate hierarchy. They hate your hierarchy.

You'll know you've found the Alpha Geek when you see people from your team (and likely other teams) at said geek's desk getting advice or validation on a frequent basis.
Don't grill us on our resume and work history.
You don't hire a geek for what he or she did two years ago. You hire them for what they will be able to do for you now and in the future. Ask your geek to describe scenarios where problems arose that required them to pick up a new skill set to solve. All geeks worth their salt have stories like that and love telling them.

Instead of asking about skills that qualify them for the position, ask about their interest in the kind of work they think they'll be doing.
Remember: Interested geeks work harder. The above requirement will still let you H.R. types ask that oh-so-predictable question: "What is it that you think this company does?" while offering your candidate a chance to really show he or she will be a good match.
Thursday, January 15, 2009 3:43:59 PM (Eastern Standard Time, UTC-05:00)  #    Comments [0] -
Hiring | Management

About the author/Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

© Copyright 2019
Stanislas Biron
Sign In
Total Posts: 135
This Year: 0
This Month: 0
This Week: 0
Comments: 1
All Content © 2019, Stanislas Biron