Amplification (and Hiring Evaluation Criteria)

Most of my favorite blogs, especially recently, focus on business and leadership concepts rather than BIM. A recent post on Presentation Zen detailed some interesting thoughts from Pixar that resonated with me on a few different levels.

Our industry talks about collaboration quite a bit, but often when we dig in, we aren't truly collaborating. I haven't really thought of a great way to communicate that idea internally or externally, but when I read what Pixar had to say about it I knew that it was what I was looking for:
Cooperation is not the same thing as collaboration. Cooperation is just that thing "which allows you not to get in the other's way," says Nelson. Collaboration means amplification. ... I think of collaboration as being like 2+2=5 (or 137, etc.).
I also love how they talk about hiring criteria. Since we've been actively hiring for two VDC positions, we've gotten so many resumes from people who know Revit, and probably know it quite well, which is exciting. However, we aren't just looking at "depth" of knowledge in Revit because most of the work that a new hire will do is undefined, because we are constantly pushing the envelope. As it is put in the Presentation Zen post: do you hire someone for something that has never been done before? ... past success alone is not enough
Pixar looks for experience with "failure and recovery", along with an entire host of qualities. I like to think that we are doing similar things. It's about problem solving, working in a team, culture fit, negotiating and a sense of exploration.

I'd be interested in what other people look for when they hire, whether for a BIM-related position or something else.


Gabe said...

I recently experienced a similar scenario when trying to hire a modeler for Revit MEP, since in our area - there is no one teaching Revit MEP except for the 3-day AOTC. So, we tried to identify positive attitude, learning capability, and a willingness to progress. If they are able and willing to learn, they can be taught.

Drew Halphen, LEED AP said...

When we look for VDC Engineers we try and find someone who has a basic understanding in the required software (Navis / Revit) but also has the problem solving skills to mix software applications to develop unique solutions. So often with VDC the best answer lies within one of 5-6 different pieces of software and it is important for an applicant to know when to look outside their comfort zone for the ideal solution.