Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The Evil Tester Show - Episode 005 - Rejection [Podcast]

DZone's Guide to

The Evil Tester Show - Episode 005 - Rejection [Podcast]

Everyone experiences rejection. Watch this podcast for some strategies for how to respond to it, especially in a software development setting.

· DevOps Zone ·
Free Resource

Planning to extract out a few microservices from your monolith? Read this free guide to learn the best practice before you get started.

The Evil Tester Show Episode 005 covers the topic of Rejection and strategies of how you can cope with it.

Why?

Everyone experiences rejection.

  • Your defect got closed and not fixed
  • You didn't get a pay rise
  • You didn't get accepted to talk at a conference
  • You didn't get the job

Rejection is a daily phenomenon.

And the more you put yourself out there, the more rejection you will face.

  • The more you post on your blog, or create videos, the more negative comments you will receive
  • The more types of videos you release, the more thumbs down you will receive
  • The more work you pitch for, the more you will not make the sale
  • The more interview you go for, the more you will be rejected for

The obvious conclusion then, to avoid rejection, is:

  • Do less
  • Create less
  • Stay in your box
  • Do not try and advance

The obvious conclusion then leads us to the wrong action.

So we do not try to avoid rejection.

We learn to handle rejection.

Lessons From Sales

A common (meaning I can't remember where I first read or heard this) phrase to describe selling is:
The right offer, to the right person, at the right time.
Even if you have the best product in the world, at the cheapest price it has ever been or will be, and you still won't sell it to someone who doesn't know anything about it or care about it.

The great thing about this phrase is that it has at least 3 index points.

  • Specific offer
  • Specific person
  • Specific time

Which means that although you might receive a rejection. It does not mean that you will receive a rejection from the same person, with the same offer, at a different time.

Perhaps if you had adjusted your offer: how you presented it, what features you talked about, what benefits you extolled; to that person at that time, you might have made the sale.

This phrase has a built-in defense against giving up. And indeed, if we look at successful salespeople, very often it is the most persistent sales person that wins the sale.

Stay Down

Have you seen the fight scene in Cool Hand Luke? It might not be the best example of handling rejection since there was no change in strategy adopted after each knockdown. But it is a reminder of persistence.

When you receive rejection, you have to decide if you are going to persist on your path or not, and that comes down to:

Do you believe in what you are trying to achieve?

If you do, then no matter what knock downs you experience, you can keep going.

It won't be the rejection that stops you. You will stop when you no longer believe in what you are trying to achieve.

More

The podcast and show notes cover this in more detail.

The podcast is available to download from podbean and all good podcast retailers (I write that, but I have no idea if it is true, I assume that because it is syndicated through iTunes that other sites pick up on it, but I haven't checked. It might only be available from podbean for all I know).

And it is available to watch on video.


Learn how to measure the impact of every feature release on performance and customer experience metrics.

Topics:
devops ,career ,podcast ,software development

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}