TesterHQ - The Evil Tester Blog Aggregator

Jul 12, 2017 - 4 minute read - Instagram

Start With Why but Do Not Stop There - Instagram Post

Original Instagram Post

We are often told to “Start with Why?” and Simon Sinek’s book of the same name is worth reading.

When it comes to your work, and you decide to get your act together and Start With Why? Very often we go too high, too fast.

  • Why am I an activity X’r? e.g. Why am I a designer? Why am I a manager? Why am I a tester?
  • Why am I doing activity X? e.g. Why do we design? Why do we need managers? Why do we test?
  • Why is activity X important? e.g. Why is design important? Why is management important? Why is testing important?

I have no doubt that answer these questions will bring you important insight. But at this level you are targeting your own beliefs.

You can cycle around this high level Why? for quite some time and still come out with the answer “Because I want to!”

I’m assuming that you already think what you are doing is important. You may not be able to say Why? But I’m sure you already believe that.

What if you started with other people’s Why?

  • Why should person X care that I’m doing X?
  • Why should person Y support me in doing X?

At this point, you’re building a model of an other person and hopefully your Why? analysis will identify benefits for them.

Remember, that asking a chain of “Why?” questions creates a belief chain, so also sprinkle in questions like “How?”, “When?”, “Where?”, “Who?” and “What?” - these are more tangible and can identify concrete actions and benefits that Why might not bring out.

After performing this type of activity you can look at your model and start testing your model, i.e. by asking the person you have modeled “What if, you could get X?”

If you asked questions like “what?”, “How?”, “when?” and “Who?” then you can monitor:

  • did we get the results? (what?)
  • did the mechanism we identified work? (How?)
  • did we do it in the timescales we thought we would? Did we do it at the points in the process that we would? (When?)
  • did the people we thought would do it complete the task? do they have the skills? (Who?)
  • does our environment support the activity? (Where?)
  • etc.

You can explore and evolve to “Find Your Why?”. You can create actionable steps that lead to instant value on the way

We are often told to "Start with Why?" and Simon Sinek's book of the same name is worth reading.⠀ ⠀ When it comes to your work, and you decide to get your act together and Start With Why? Very often we go too high, too fast.⠀ ⠀ - Why am I an activity X'r? e.g. Why am I a designer? Why am I a manager? Why am I a tester?⠀ - Why am I doing activity X? e.g. Why do we design? Why do we need managers? Why do we test?⠀ - Why is activity X important? e.g. Why is design important? Why is management important? Why is testing important?⠀ ⠀ I have no doubt that answer these questions will bring you important insight. But at this level you are targeting your own beliefs.⠀ ⠀ You can cycle around this high level Why? for quite some time and still come out with the answer "Because I want to!"⠀ ⠀ I'm assuming that you already think what you are doing is important. You may not be able to say Why? But I'm sure you already believe that.⠀ ⠀ What if you started with other people's Why?⠀ ⠀ - Why should person X care that I'm doing X?⠀ - Why should person Y support me in doing X?⠀ ⠀ At this point, you're building a model of an other person and hopefully your Why? analysis will identify benefits for them.⠀ ⠀ Remember, that asking a chain of "Why?" questions creates a belief chain, so also sprinkle in questions like "How?", "When?", "Where?", "Who?" and "What?" - these are more tangible and can identify concrete actions and benefits that Why might not bring out.⠀ ⠀ After performing this type of activity you can look at your model and start testing your model, i.e. by asking the person you have modeled "What if, you could get X?"⠀ ⠀ If you asked questions like "what?", "How?", "when?" and "Who?" then you can monitor:⠀ ⠀ - did we get the results? (what?)⠀ - did the mechanism we identified work? (How?)⠀ - did we do it in the timescales we thought we would? Did we do it at the points in the process that we would? (When?)⠀ - did the people we thought would do it complete the task? do they have the skills? (Who?)⠀ - does our environment support the activity? (Where?)⠀ - etc.⠀ ⠀ You can explore and evolve to "Find Your Why?". You can create actionable steps that lead to instant value on the way

A post shared by Software Testing Tips & Videos (@eviltester) on