my goal has always been to facilitate proactive infrastructures with this appliction. in fact, de-facto testing suggests holistic mindshare will benefit from not only having buyin, but viral buyin as well. In other words, if anyone had problems with buyin(when did we start talking like 'knowledge workers' here btw?), i assume they would have mentioned something while testing it. or is that too simple?? :) .djc. Martin wrote: > Martin wrote on 28/8/01 5:32 pm > > >>rudy wrote on 28/8/01 5:20 pm >> >> >>>speaking unofficially, i'd say you should have the buyin you need to move >>>to production... >>> >>From thesite, sure. It'd be useful to get a formal admin signoff, tho' > >>I don't see a problem with getting it - just need to ask the question. >> > > Sorry for the misquote earlier (it looked like my 1st line was what > Rudy said). > > But this would be A Good Thing for 2 reasons: > 1) Admin is the policy body for day to day stuff, so it's rightly within > admin's remit to signoff on this. > 2) It's Admin who are going to be using it, so just having a check to say > "Yeah, we're happy with the way this works for us" is useful. > > Both reasons will prevent it coming back to haunt us if Admin turns > around in the future and starts complaining about new ways of working - > you can just point to the signoff and say "No chance - you explicitly > signed this off. If you want to change it back, you've got to start the > requirements process of 'why do we want this?' all over again" > > In other words, it'll be more fully entrenched.