Tuesday, February 8, 2011

Right Way, and Wrong Way

You are about to embark upon a major project to tie information together across your enterprise. It will produce new capabilities, cost savings, and potential revenue streams. Multiple departments/divisions are going to be involved. You are the architect. You have been knighted. Go forth and conquer thee...

Initial Meeting with Each Department/Division Head:

Right way: "Hello! I'm glad you could take some time out of your busy day to meet me. I'd like to see how we can work together to link our systems more efficiently."

Wrong way: "Hi. I need access to your data."

Asking for access to department/division resources (databases, etc):

Right way: "We are hoping to get a link from __ to query first and last name, title, office, dept, manager, and hire date from you system. We really don't want to reinvent the wheel since you already have working very well."

Wrong way: "I need to get access to ___ so I can get employee data. We are going to manage it over in our new system."

On explaining the rationale and scope:

Right way: "This effort will begin as a cost and transition into a revenue source that will more than pay for itself. The investment of $X will return $Y in Z months."

Wrong way: "I haven't done the numbers, but this will save us a ton of money. It will be cool!"

On meeting with each department tech staff:

Right way: "we really appreciate your help on this. We can't do it without the help of everyone involved."

Wrong way: "We know the answers. We know what we're doing. Just give us access to your stuff."

I've seen it done the wrong way more often than the right way (by a factor of 10 to 1)
Post a Comment