I'm working on some language for an IT agreement and want to see if any of my readers want to volunteer an example or two. I have language to triage problems but need to incorporate how conflicts and unresolved issues move up the chain of command toward resolution?
Your suggestions are appreciated!
Best to keep a log of issues and resolutions before they become problems -- you assign responsibility for getting an answer (perhaps with a signoff for approval of the response). Anything without an answer after X days (and with a priority of Y) automatically gets covered at the next stakholder meeting. The issues list is always the first agenda item so it's more like a housekeeping issue than a confrontation. A lot of times issues list are kept, but they are only escalated if someone sticks their neck out. Usually, this causes divisions in the team. Better to make it an admin function than a showdown. My 0.02 FWIW. - Marty
Posted by: Marty | July 27, 2006 at 10:35 AM