- Let the others impress you. The problem when we join a new team is that we are eager to "show our stuff" and earn the respect of our new peers and bosses. But they are eager to do the same with us. A new guy is a disruption of the status quo and so you must let the other members of the team re-establish their status with you. Relax, you got the job--the starting assumption for everybody else is that you are coming in smart and successful from your previous gig.
- Cater to the group's self-acknowledged areas of weakness. Try to assess how the team sees you as adding value. We have a tendency to want to recreate past successes, but first understand the new problems and how the team sees you as part of the solution. For example, if a team thinks they have lousy templates and that's what they want you to work on, but you think their standards and style guides suck, work on the templates! Don't try to force yourself as an answer to a problem they don't think they have.
- Build something. You need to learn a lot, and there is a tendency to read, read, read. That just leads to forget, forget, forget. Build something that forces you to engage with the content you are trying to learn and that will give you a residual artifact. For example, don't just browse the portal you will be redesigning, build a site map of it. Build a Wiki that captures links to the resources you are discovering, construct a user matrix. Whatever.
- Don't squander your ignorance. You are about to see a lot of things for the first time that you will never see for the first time ever again. Stay focused on what that experience is like for the user. (Keep you mouth shut, however, and pay attention to points 1-3.)
Monday, January 04, 2010
New Year (Job) Resolutions
I'm starting a new job on a new team today, so it's a good time to summarize for myself the advice I give to others when they start a new position.