Renaissance philosopher and writer Machiavelli once said, “I'm not interested in preserving the status quo; I want to overthrow it.” How can you follow this advice and avoid stagnation without sacrificing quality and security in the process? Learn the three key words needed to strike this delicate balance in this challenge for you to shift your paradigm and be a catalyst for change rather than an antagonist.

Where is your organization now? Where do you want it to be in five years? Do you intend to get it there by using the same methods that haven't worked? It has been said that the definition of insanity is doing the same thing over and over, but expecting different results. Is that how you want your leadership legacy to be remembered? Do you project an image of being part of the problem or part of the solution? Find out how to be a catalyst for change and NOT an antagonist. Discover three types of flexibility in leadership needed to make that happen.


Outline/Structure of the Talk

This is a challenge for Agile professionals who wish to be more "agile" (pun intended) and facilitate innovation. Rather than stand around and watch things happen, resisting change at every turn, these three steps will motivate participants to embrace change and make things happen as an innovator. Here are the three steps with supporting points (after approximately 5 minutes of introductory remarks):

I . Recognize (that change is ...) -- approximately 15 minutes

  1. Inevitable
  2. Inexorable
  3. Inspiring

II. Resolve (to balance these two qualities...) -- approximately 10 minutes

  1. Deference
  2. Determination

III. Respond (with three looks...) -- approximately 15 minutes

  1. Inward - Enabling
  2. Upward - Empowering
  3. Outward - Encouraging

Learning Outcome

The participant will...
* Effectively RECOGNIZE characteristics and effects of change
* RESOLVE to take ownership of change (using 3 types of flexibility)
* Demonstrate appropriate RESPONSES to embracing change and facilitating innovation

Target Audience

Professionals who wish to go beyond the status quo, break out of their status quo, and embrace change.

Prerequisites for Attendees


schedule Submitted 7 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Sai Krishna
    By Sai Krishna  ~  5 months ago
    reply Reply

    Hi Joe,

    Thanks for your proposal!
    Could you please update the Outline/Structure section of your proposal with a time-wise breakup of how you plan to use 45 mins for the topics you've highlighted?

    And, to help the program committee understand how is this topic related to Selenium conference?



    • Joe Perez
      By Joe Perez  ~  5 months ago
      reply Reply

      Thanks so much for taking the time to comment.  To answer your first question, I have updated the Outline/Structure section of my proposal with a "time-wise breakup"  so that you can see how I am allocating the 45 minutes for my topic. The additions are in bold italic font.  I attempted to make the form color the text red, but that change would not persist, so I will need to settle for bold italics only.

      Secondly, to help the committee understand how this topic is related to the Selenium conference:  With every new software package, or new update to an existing software package, or idea for a novel approach for an existing software package (doesn't matter if it's Selenium, an Apple OS, Microsoft Office, Photoshop, or anything else), there is a fear of leaving the status quo behind; a fear of not wanting to break out of one's comfort zone.  This requires a shift in one’s paradigm, but it is necessary to cultivate the right climate before that can happen. I intend to show the audience how to do this as Selenium users with my three-pronged approach (the three key words in the outline: Recognize, Resolve, and Respond).


      This presentation, as alluded to in the promotional text, is a challenge for Selenium developers to refuse to be satisfied with the status quo, and rather than resisting change, EMBRACE IT!  Welcome it!!  I will challenge these developers to realize that change is an OPPORTUNITY for IMPROVEMENT and NOT a THREAT to the ESTABLISHMENT.  Since Selenium is referred to as “the truly Agile automation testing tool,” what better way to demonstrate Agile principles than to expound upon the principles needed to ensure developers are willing to embrace change and explore the three types of flexibility in leadership needed to make this happen.


      So in summary, I will not only help the audience to meet the three objectives listed in “Learning Outcomes” section, but in doing so, they will be better equipped to facilitate innovation in their use and implementation of Selenium, AND (hopefully) to be willing to share these concepts with other Selenium developers.


      Here are a couple of links to excerpts of my having presented other versions of this topic in other settings:


      Hopefully, these videos will show you a little more of my style of speaking and what the attendees of the Selenium 2020 conference will look forward to experiencing should you accept my proposal.  Thank you so much for taking the time to read this explanation.  Please let me know if you need anything else.