The Paradox of Being Proactive

Dwayne Harapnuik —  March 9, 2010 — 1 Comment

To get out of the reactionary rut we have to actually be proactive, but unfortunately, reactive busyness is rewarded. We need to stop reinforcing the incorrect reactive behaviors and start reinforcing the proactive activities that will enable an organization to really move forward.

In the Tech Republic white paper, Get out of the information technology reactionary rut, Robert Bogue points out the paradox of pro-action with the following example:

Team members who are nearly always proactive are seen as unnecessary overhead because they’re not solving the real problems of today. They are sometimes seen as idealists who never seem to be around when problems occur. Conversely someone who is always reacting and not pro actively planning is seen as someone who is working hard but not necessarily working smart. In other words their diligence is rewarded but the fact that it is necessary due to lack of planning is shunned.

To get out of this reactionary rut or trap we need to:

  • Actually be proactive.
  • Stop reinforcing reactive behavior and reinforce proactive activities.

These activities can include:

  • Cutting ourselves some slack – create opportunities to be proactive
  • Scheduling Time to be proactive – start early or get some help
  • Force High Return Activities – prioritizing or building a task list is a simple start.

The bottom line is that when we are proactive we are also in control.

Read the full article…

Dwayne Harapnuik

Posts Google+

Trackbacks and Pingbacks:

  1. Sense of Urgency: Create It Now or React to It Later | It's About Learning - March 23, 2015

    […] a sense of urgency is ours but we often first have to get out of the reactionary rut. In the post Paradox of being proactive I point to the unfortunate fact that the busyness that reactivity spawns is rewarded because it […]

Leave a Reply

Text formatting is available via select HTML. <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.