Sponsored Ads

Syndication

AddThis Social Bookmark Button

« Let's not bring IT into this | Main | What to say and when to say it »

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341ccbc153ef00e55061e27d8833

Listed below are links to weblogs that reference Learning from my children:

Comments

Jeff, great post! In the engineering world (at least in MY engineering world), this is a way of life. We start with project objectives, develop a schedule, proceed to design deliverables, build the project, then are (sometimes) scored on how well we met the deliverables and schedule. We know the rubric before we start.

The more I read on this, though, I wonder how the non-engineering world does it. Is it normal NOT to have deliverables defined for work? From my limited perspective, I can't see how you can operate any other way.

Hey Robert:

I'm from the IT world myself, but currently work in marketing. I agree with you that many items are "written down" as part of a project plan, like scope and timeframes. What I think is also true is that often times many goals and expectations are not communicated, or not communicated well, so that they are not understood as deliverables. How many times have you delivered a result only to be told that it was missing something you weren't sure was part of the original agreement?

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment