Definition — 3rd “D” for Leading Project Escalations

To know what must be done…   — Pericles on leadership

In my experience, the informal escalations just discussed (here) are the hardest; nothing’s tougher than confronting the boss with a bombshell:

  • Implementation issues may involve resources one’s boss has sourced for the project.
  • Functional gaps may have been created by one’s own poor scope management practices.

You want to give the boss the heads up — without getting your head handed to you.  Preparing for conversations like these, however, is not always a strong point for technology professionals. Technology professionals often get a (sometimes deserved) reputation for knee-jerk overreaction to any new plan of action.  Nothing is worse than explaining why you don’t think a project is viable and then discovering you are wrong, so:

  • Proceed in a deliberate and measured way to gather the full scoop
  • Have all your facts checked before explaining your position
Advertisements

One Response

  1. […] has to be taught in most cases and takes some time and experience to develop. (refer to discussion here at […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: