Tech Life People don’t believe what they have not seen

The Great (Incorrect) Disappointment

First day of the new gig. You walk in the building knowing practically no one. Everyone is pleasant and nice… almost too nice. Everyone (including you) is not quite themselves because everyone understands the power of the first impression. They’re watching every single move and attempting to interpret how these moves might be perceived. It’s exhausting and it doesn’t reflect the natural steady state of the team.

You listen. You talk to every single person who is willing and you slowly form the impression of the tangible and intangible aspects of this group of people. A picture slowly forms in your mind of how it fits together and, as an aside, it’s almost always wrong because your brain hates discord. As quickly as possible, your brain wants a framework that efficiently predicts what is going to happen next. Your initial framework is a calming hodgepodge of past experience combined with your three most recent epiphanies, and you call this weak sauce, “The way they work.”

Good news: this poor assessment goes both ways. It’s the beginning of The Great (Incorrect) Disappointment. You discover your model for them is incorrect. They discover that you are not who they expected. It’s the end of the new gig honeymoon and the fact the end has begun is progress, but it mostly feels like disappointment. You’re in an unfortunate hole. It’s buyer’s remorse. It’s understanding the world is never, ever that simple.

You sense their disappointment, so you listen harder. You push yourself to talk with a wider variety of unfamiliar humans, because you continue to erroneously believe that one of them could tell you that elusive one rule that would explain this particular clan’s culture in a immediately useful and revealing way. You read every decrepit wiki page. You attend every meeting. You’re attempting to rebuild yourself in a new culture and it’s exhausting because you took all of this for granted in your prior gig. You had built blazing fast intuition, but it took months… perhaps years.

You start climbing out of The Great (Incorrect) Disappointment with a small, unexpected win. No one expected you to fix that; no one knew it was that broken; and no one thought it was that important. When you fixed it, no one really noticed. When the consequences of the fix became obvious, they thought, “He can do that?”

Your fix is your first legitimate reputation defining moment, because while people were told who you were, they didn’t believe it because people don’t believe what they have not seen.

The Great (Incorrect) Disappointment vanishes slowly and quietly each of these small wins. The wins don’t feel substantive or impactful, but they continue to incrementally define who you are to the rest of the team. They start to build a realistic model of you in their minds. You’re not who they expected, it’s not what you expected, but after three months you start to think of this strange place as home.

Leave a Reply

Your email address will not be published. Required fields are marked *

3 Responses

  1. The Great (Incorrect) Disappointment linked to this.
  2. THANK YOU. After exiting a 4 month mistake I find myself at a new place, meeting new people and pretty much in this EXACT situation. This week I over-delivered on a pitch meeting deliverable and got some hardware up and running that the team had sitting in a cardboard box.

    It feels great to climb out from under my resume and my credits-list.

    I needed this.

  3. Mark Peleus 9 years ago

    Dear Rands/Michael,
    I understand your point of view. Having just gone to a new university after 2 years in the old one, the struggle is but so real. Your post is really inspirational for me to overcome this disappointment.
    Btw, I have a request. Can you make a blog post describing on how to be a software developer? I want to be a software engineer myself, and I think I speak for a lot of readers that we want to learn about your journey and how you succeed. It would be awesome if you can show us what books you read, what websites you learn from ( constantly improvement) and how to be a capable software developer. I’m a complete beginner, learning a different discipline from CS in college, but love it and want to study it on my own. But I think your recommendations should not just be for me, but for every reader out there that wants to follow your footsteps.
    Thank you.