how to deal with other people's mistakes
- Thread starter myname
- Start date
franklin1777
Time marches on
Lock the error making users out of the system.
When they complain, tell them a recent upgrade has a security device which detects computer hackers by counting the number of mistakes.
Above a certain mistake threshold the database automatically locks them out for a day. When they ask for a reset take two hours or so, you can always explain that although you reset the system, it takes a couple of hours for the unlock to update through all the files /servers etc. (this is what IT always tell me anyway)
The system obviously locks them out because it thinks they are a computer trying random record writes on the database to carry out a denial of service attack. The threshold was set high enough that no human user would be stupid enough to make mistakes and trigger the lock out.
Lock the users out long enough every day for a month and they will soon stop making mistakes.
If a manager asks to get the code fixed, shrug your shoulders and say it will cost money.
When they complain, tell them a recent upgrade has a security device which detects computer hackers by counting the number of mistakes.
Above a certain mistake threshold the database automatically locks them out for a day. When they ask for a reset take two hours or so, you can always explain that although you reset the system, it takes a couple of hours for the unlock to update through all the files /servers etc. (this is what IT always tell me anyway)
The system obviously locks them out because it thinks they are a computer trying random record writes on the database to carry out a denial of service attack. The threshold was set high enough that no human user would be stupid enough to make mistakes and trigger the lock out.
Lock the users out long enough every day for a month and they will soon stop making mistakes.
If a manager asks to get the code fixed, shrug your shoulders and say it will cost money.
pembrokestephen
New Member
I'd go a step further than this.silver said:
Write up your training notes, and number them - so you've got Module 1, Module 2, etc.
As you deliver these modules (ie. work through them with each user then hand over printed copy to the user), get the user to sign off that they've had the training on a piece of paper. File that.
Then, next time managerbloke turns up and says that there's dupes on the database and you're not doing your job properly, you produce the signoff sheet and point out that you have trained this member of staff, and explained what they need to do, and that you do not know what else you can do to physically force them to use the system properly.
Along the way somewhere, you're going to have to talk to the manager about being given responsibility without any authority, and how it is impossible for you to do the task asked of you if no-one is going to back you up in enforcing compliant use of the application in the first place.
Kid_Eternity
Quis custodiet ipsos custodes?
myname said:
Oh god I feel your pain, have had to deal with managing the db while our IT manager is away, it has a been GREAT fun...I'd email the offenders directly about it politely asking if they wish further training or a refresher tutorial.
Zorra
Suburban lazarus
I *heart* Raiser's Edge, I used to manage the DB and a team of staff on it in the last NGO I worked for... 
The way I dealt with mistake-makers is to change all their permissions so ONLY a small number of people could add folk, and then it just gathered all the information into a report for me to check and upload. No-one else could upload the info. I also changed the permissions for people like the CEO who needed to look at the reports etc but was a bit sticky fingered when it came to wilfully messing around with information
We had a really clear framework for who was doing what etc and it worked... There was only one person who consistently messed up (despite hours and hours of extra, very tailored training, support etc etc) who was eventually taken off the database altogether because she generated significantly more work than she achieved
Is it normal for the finance person to manage the DB by the way? Everywhere I've worked, finance has an input and will double check (and you can buy a module on RE which will import information directly from SAGE) the DB responsibility is with the fundraising dept...
Any more specific stuff, bung me a PM
The way I dealt with mistake-makers is to change all their permissions so ONLY a small number of people could add folk, and then it just gathered all the information into a report for me to check and upload. No-one else could upload the info. I also changed the permissions for people like the CEO who needed to look at the reports etc but was a bit sticky fingered when it came to wilfully messing around with information
We had a really clear framework for who was doing what etc and it worked... There was only one person who consistently messed up (despite hours and hours of extra, very tailored training, support etc etc) who was eventually taken off the database altogether because she generated significantly more work than she achieved
Is it normal for the finance person to manage the DB by the way? Everywhere I've worked, finance has an input and will double check (and you can buy a module on RE which will import information directly from SAGE) the DB responsibility is with the fundraising dept...
Any more specific stuff, bung me a PM
winterinmoscow
Returning Poster
i feel your pain, myname, it sounds like you're stuck between a rock and a hard place. I don;'t have any suggestions but I do feel for you!
Zorra said:I *heart* Raiser's Edge, I used to manage the DB and a team of staff on it in the last NGO I worked for...
The way I dealt with mistake-makers is to change all their permissions so ONLY a small number of people could add folk, and then it just gathered all the information into a report for me to check and upload. No-one else could upload the info. I also changed the permissions for people like the CEO who needed to look at the reports etc but was a bit sticky fingered when it came to wilfully messing around with information
We had a really clear framework for who was doing what etc and it worked... There was only one person who consistently messed up (despite hours and hours of extra, very tailored training, support etc etc) who was eventually taken off the database altogether because she generated significantly more work than she achieved
Is it normal for the finance person to manage the DB by the way? Everywhere I've worked, finance has an input and will double check (and you can buy a module on RE which will import information directly from SAGE) the DB responsibility is with the fundraising dept...
Any more specific stuff, bung me a PM
we're a small charity, and the person in fundraising who used to manage the database said he couldn't manage it anymore, it was too much extra work and he needed to focus on raising money, so they just lumped it onto the end of my job, i'm only meant to spend 1 and half days a week on it!
btw, how do you change people's permissions? I know how to lock them out of certain modules, like query, batch etc, but i can't see any way of stopping them from being able to add new people? Am i missing something really obvious? edited to add, i've worked out how to do this now, thanks for saying it was possible!
Also what report were you running, I run the duplicate criteria report and then look at that, but it's not perfect, I can change what criteria it looks through to decide duplicates but I still end up having to go into some records and checking them manually. I'd really appreciate hearing what reports/queries you were running, if that doesn't take up too much of your time.
Thanks
Similar threads
