Collaboration, Communication And Expectations

2,034 views
1,907 views

Published on

Ground Rules for building a successful outsourcing relationship

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,034
On SlideShare
0
From Embeds
0
Number of Embeds
19
Actions
Shares
0
Downloads
44
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Collaboration, Communication And Expectations

  1. 1. Outsourcing Project: Collaboration, Communication & Expectations Dennis Stevenson May 20, 2008
  2. 2. How will we get there?
  3. 3. Collaboration & Communication <ul><li>Over communicate because… </li></ul><ul><ul><li>You only get one chance to say it the first time </li></ul></ul><ul><ul><li>It is too easy to misunderstand each other </li></ul></ul><ul><li>Listen as hard as you talk because… </li></ul><ul><ul><li>Accents & Telephone make it hard to understand </li></ul></ul><ul><ul><li>We are dealing with complex topics </li></ul></ul><ul><li>Write it down because… </li></ul><ul><ul><li>Your memory and mine is fallible </li></ul></ul><ul><ul><li>Someone important inevitably missed the conversation </li></ul></ul>
  4. 4. Collaboration & Communication <ul><li>Be Gracious with each other because… </li></ul><ul><ul><li>Neither of you would be here if you didn’t deserve to be </li></ul></ul><ul><ul><li>Tomorrow we will start all over again </li></ul></ul><ul><li>Focus on Problems not Personalities because… </li></ul><ul><ul><li>We’re here to solve problems, not fix people </li></ul></ul><ul><ul><li>There will be plenty of problems… no time for personalities </li></ul></ul><ul><li>Keep it short and sweet because… </li></ul><ul><ul><li>Time is limited and speed is critical </li></ul></ul><ul><ul><li>We want to build and maintain momentum </li></ul></ul>
  5. 5. Expectations <ul><li>No Repeat Mistakes </li></ul><ul><ul><li>First time mistakes are about learning – that’s ok </li></ul></ul><ul><ul><li>I expect teams to communicate lessons learned </li></ul></ul><ul><li>No Shortcuts without permission </li></ul><ul><ul><li>We will deploy this code to customers who trust us </li></ul></ul><ul><ul><li>Code performance and behavior is EVERYTHING. </li></ul></ul><ul><li>Consistency, Consistency, Consistency </li></ul><ul><ul><li>Do it well and do it once – don’t reinvent the wheel </li></ul></ul><ul><ul><li>This isn’t the end of the changes </li></ul></ul>
  6. 6. Expectations <ul><li>Next Day Answers </li></ul><ul><ul><li>Make the time differential work for us, not against us </li></ul></ul><ul><ul><li>If you don’t have an answer, say so and give a date </li></ul></ul><ul><li>Know the Plan & Critical Dates </li></ul><ul><ul><li>Ignorance is not an excuse </li></ul></ul><ul><ul><li>Your performance either helps or hinders the plan </li></ul></ul><ul><li>Escalate Issues at the first possible moment </li></ul><ul><ul><li>I can’t fix what I don’t know is broken </li></ul></ul><ul><ul><li>If there is a problem, I expect time to react </li></ul></ul>

×