yeah, gotta agree. without the methodology, no one will use it. plus, if the users don't even have admin on their machine, good luck installing stuff and keeping it installed when the real IT department finds out.
go for the offline solution like a whiteboard. put it in a location where everyone has to pass at least once a day, or in a meeting room where everyone goes to update it together on a regular basis.
either way, make a point to use it and stick with it, but be flexible enough to make changes to the methodology if it isn't working.
Can i get a hard hat for the office?
several lies here.
1) you have a wife. c'mon, this is slashdot.
2) you have a girlfriend. see above.
3) you bought porn. really?
uh. that's not a car analogy. where's my freakin' car analogy?!
I think that's only because his species are color blind.
to start something you're not sure you can finish. i wrote a framework in perl to generate some pdf reports, complete with graphs and automated text. took me quite a while, and a lot of "i'll come back to this part later". i went from the script being used to piece together bash/shell commands, to it doing everything.
but the point is, i kept at it. taking a little part at a time and futzing around with it till it worked a little better.
yeah, but whose head? if anyone, it'll be the guy who let him pass. the one earning $10 an hour. big deal. his supervisor (earning $12/hr), maybe gets written up. their manager? a stern talking to. that's it.