75 replies
She's making decisions which is definite plus point in my experience.
Do what she says you'll either be diagnosed with paranoia , or another decision will be made.
Against all my advice I was told to join up two networks. A week later the other network was using HP's find all our printers on the network gizmo and dropped an entire manufacturing plant. I didn't know that particular problem would occur, I just knew there could be problems and that they were potentially expensive. That one certainly was.
People mainly learn from their own screw-ups.
by chrispy1
OK, well any screw ups in my department won't cause a huge kerfuffle like yours, just put about 60 people off-line for a couple of hours...
Thanks for your advice. Being the only ISIT guy in a group of 45 people, I get lonely for fellow Geeks every once in a while, and find solace in TR's community...
Chris
by mart1n
by dmambo
by jck
But, get it in writing. Get an email from her, hard print that sucker, and reply to her with your concerns and CC yourself and print. If she still tells you to do it, then print that email and do it.
When/If it crashes, then you have your arse covered when the hammer comes down from the upper management, and you can show that you objected to it but were ordered to do what you said would cause issues.
by chrispy1
You've put my mind at ease. I think I was a little um, perturbed/stressed as I saw the consequences of this decision (me having more work) and knew that the solution was relatively easy. Have a coffee on me!
Chris
by amcol
Documentation works both ways. Definitely get any orders you disagree with in writing from your boss (and be careful how you go about that, you run huge political risks depending on how you ask), but also document in return all the reasons (professionally stated, and in terms of demonstrable facts only) why you believe the mandated course of action is not in the best interests of the organization.
When the proverbial hits the fan you can't simply whip out a written manifesto from your boss and say "I was just following orders". You have to be able to document that you expressed your reservations and were overruled.
Good luck, you're going to need it. This is a bad situation with no obvious resolution. My advice is to consider moving on.
by chrispy1
I needed to reindex the database this a.m., and guess who was in it? The woman to whom I provided full admin rights - durn it. The documentation and emails are politically, um - delicate, allowing for my complete reservation yet at the same time saying "I understand why, but think that a b and/or c would be better options"...
Thanks for the luck, you're right - I am going to need it. (Oh, and here's another one for you - her suggestion for me to deal with a couple of issues, instead of having a team meeting? PUT POSTIT NOTES ON EVERYBODY'S MONITORS TONIGHT AFTER THEY LEAVE. I'm still laughing/shocked/astounded that this is my manager's way to deal with some really tough issues - she wants me to spend 20 minutes writing out 45 postit notes, and then sneak around and put them on people's computers? ROTFLMAO...)...
by jck
When I said:
"Get an email from her, hard print that sucker, and reply to her with your concerns and CC yourself and print. If she still tells you to do it, then print that email and do it."
The "concerns" I mentioned are demonstrating what is wrong with the work she has proposed.
I just didn't get as verbose as you about what to do. I didn't figured I needed to be.
Covering your arse is covering your arse.
... and one of them had a Sr. Manager who called "I was just following orders" the Nuremburg Defense, as in "Why is XYZ all up and doen't give me the Nuremburg Defense."
My contract ended shortly after a company-wide newsletter (on real paper) that stated that the CEO knew about all the problems but "our manager trainees are here to learn from their mistakes".
by chrispy1
Well, I was right. I've now got a database with three seriously corrupted tables, blank UIDs, and a whole slew of other problems. All because when the person who my boss insisted I give full admin rights to ran her report, she didn't read the fields carefully (although how can you miss size 11 red bold font, I will never know), and has pooched my system.
Oh well, I didn't want to see my wife tonight anyways. (that was sarcasm, in case it wasn't clear) 8-)
by wayne m.
I have two comments, but not a lot of pity.
One, you provided the minimal support requested. I see nothing in the above that requires you to stay late. Why not address the problem tomorrow?
Two, you provided the minimal support requested. It would have been more beneficial to actually help the new user do her job, rather than sit around afterwards and search for her mistakes. If the system is really that complex, given your concerns, why didn't you create a backup before the user ran her report?
There are more productive ways to get things done than starting turf wars over who "owns" the system. No one did anything to "your" system; you allowed a company system to become corrupted through intentional inaction.
by sql_joe
If you are an administrator and are ordered/instructed by management to give out an administrator password, then this must be documented for your own protection.
If your company is publicly traded, then you must consider that by giving out admin passwords you may be in violation of Sarbanes-Oxley, therefore you must be doubly sure that all of this is in writing.
If you have a normal user access request process, require that the new access request go through that before you will grant it - this will ensure that the access was documented, and will point to who authorized it as well.
Sometimes, while you may not agree, you have to remember that it is the businesses database, and once you've appraised them of the risks, it is the businesses risk to take, because it is, after all, their money to lose. It is your reponsability to notify them of the implications, but ultimatly, the decision belongs to the ones writing the checks.
George
by cburgess
The first thing to consider, as others have already pointed out, is your company subject to growing regulations requiring various levels of due diligence in information security practices?
The next question is does your company have a formal Security Policy? If yes...then inform your boss, via email, if her requests would result in a violation of security policy. If she insists then report her to the big boss. People who do not take security policies seriously are a liability.
Her requests concerning providing admin permissions to people who shouldn't have them is an indication that permission levels need to be reworked...there should be a graduated series of levels with increasing rights.
I would consider finding a job somewhere else. That is why I own my own firm.
Regards,
Charles
http://ipaladin3.com/
by thefred
by amcol
by jck
don't feel alone...I couldn't even read straight a while back.
Of course, that's what I get for only being about to sleep 2-5 hours a night and having 3-6 ongoing software projects at work at once, and having 2 elderly parents I have to make 5-6 hour roundtrips to help out.
One of these days, I'll get married...and life will actually get easier! :D
Ain't no biggie...we're all human.
well...except me...I'm swill :) (King Swill!! ]:) )
by realme
.
...the true dynamics of a relationship, business, personal or otherwise, and to get an accurate overall assessment of a situation like you described in the course of reading a few messages. There are usually three sides to every story; and in this case, I would call them your side, which we've heard, your boss's side, which we have not heard, and the true story, which usually might fall somewhere in-between.
I'm certainly not suggesting that you're the problem, or that you're blowing smoke, or anything like that. But I would be interested to hear how your boss might describe the same situation. Would you care to give it a try? If you were to remove yourself from being personally involved, how would your boss describe the very circumstances, problems, and situations that you did?
This can really be an interesting and useful exercise when working through such a problem. Write down the issues and the problems, just like you did, but do it from the other person's perspective. Try not to interject your personal observations or opinions, such as, "...since I'm a suck-up, I have to blah blah blah...", but really try to assume the personality and possible motivations of this other person, try to see yourself as this other person might see you, and let 'er rip.
A couple of my favorite maxims might apply in a case like this.
Seek first to understand, then to be understood. (Thank you Stephen Covey)
and
You can get what you want if you help enough other people get what they want (Thank you Earl Nightingale.)
Put yourself in her shoes, try to understand her, try to help her get what she wants -- and this means what she might really want, not the little insignificant things that people usually get bogged down with -- and most likely, the answer will become as clear as day, and everything will fall right into place.
... it would appear that the manager just really isn't technically grounded, and covers for same by giving orders. Being the "I" in team, as it were. (I've met a few like that along the way.)
Probably just out of someone in HR's favorite college, the bosses daughter or some such.
Not to worry, if a few years she may actually learn how to manage.
.
.....there's always at least two sides to the same story. And I'm always amazed at not only how opinionated people are, but how certain they are of themselves when only hearing one of them.
by mot_esach
I think this is the best advice in all the threads I read about your problem. As a former manager I have dealt with both ends of your issue.
First and foremost, you have to remember she is the supervisor. She, by holding that position, has certain rights and you have obligations to those rights. At the same time, she has obligations to you as her employee, namely to protect you from reprisal due to directed error.
New supervisors don't generaly comprehend this concept, they learn it over time (and through errors) if they are truly successful managers.
Secondly, you were hired to do a particular job. So do it, and do it well (which I think you probably are doing or you wouldn't be so concerened). Remember though that often you do not get to see the big picture so decisions are made and we all have to live with them. They are not necessarily good decisions, but we are going to live with them.
Most importantly, backup your paper trail. Whatever happens, at some point, someone will be having a discussion with you as to the why and where of it all. Make sure you can explain how the decision process occured over your obvious objection(s) but be fair in that analysis. Make sure the supervisor understands the reasoning (not technical) of your position, then let the chips go with their decision. By doing this trust is developed. With trust comes acceptance and soon you find that you might even become friends. Unless there is an action that requires some moral/ethical decision on your part then the boss is going to be responsible for the decision, that is why they were hired.
I found, over time, that I could trust my employees and our production level increased. New ideas and concepts were born from the people who also began working together as a team. My supervisor noted this and didn't interfere with my Unit. One day I found I had a new supervisor who did not wish to listen and didn't like how I did things. I followed his direction regadless of my own opinions because he was the boss. While I was frustrated temporarily, in the end I found he was taking the company in a new direction but simply didn't want to lay all the cards out until he was sure it would be a success.
So I agree with Maxwell, wear the shoes of the other side and see if you can picture it from their chair. Their world and vision is often different forom your own.
At the same time, make sure to CYA.
by jonw1701
by blieffring9
Summary: Database admin is being told by a new manager to give all permissions to a programmer not normally assigned to that function. Programmer runs code and corrupt keys appear in database. He fixed database.
Database is accounts payable. Invalid keys mean unlinked new entries, or deleted entries. Only accounting should make new entries, and accounting entries should never be deleted, only commented out with a negating ammount. Only Accounting and the database admin group need reprogram access. He is the local keeper of the keys and any changes should be run and verified by him and accounting.
There is a probibility that close insiders have entered falsifed accounts and entries and then deleted them. There needs to be an accounts
payable audit and security reestablished for accounting precedures.
Think about your advice and pretend you are CIO in front of auditors and Investigators.
by firstpeter
Perhaps I'm just lucky, but I've never had a manager claim ignorance and point blame back on me when things go wrong. The manager has ultimate responsibility for what happens, plain and simple. Or should, anyway. If the fingers are being pointed at others then you've got a dysfunctional system you have to deal with.
My advice would be to make sure you've documented (e-mail is good) your concerns and then proceed. Really the situation isn't for this particular instance (it's not a "CYA" thing), but more for future reference. If something does go wrong then the next time you offer your two cents you have something solid to back it up on. Not to rub in your manager's face but simply to say, ultimately, "you can trust me - I know this database/network/system/etc."
The bottom line is that your boss told you to do something. Right, wrong, or otherwise your boss is the one who is on the line. You've explained why you don't believe it's the best move, but your manager (should, anyway) has a higher-level picture and has ultimate responsibility for that decision.
Good luck!
by sfc byte
Where I work if you don't CYA you will be eaten alive. Keep emails, memos for record, notes on a cocktail napkin, whatever it takes.
Time and time again our managers will try to blame the technician for something that is really a fault in the process..i.e. management procedures.
Quick case in point. I arrived at a company that had no images for anything. Over 500 users! So I created multiple images and then requested that our Computer Continuity Board (all managers, one tech) thoroughly evalute these images prior to deployment. They had one meeting and spent 2 hours arguing about wether the default games should be removed or left. That was it. I have since grudgingly been directed to deploy the images. Guess what? There are some problems with the image. Who were the managers trying to blame? Me. My defense was a massive, time consuming, pain in the butt paper trail that pointed right back to the CCB. Silence filled the room...tears filled my eyes because it is all so sad and unnnecessary.
BLUF: The world is not filled with teamwork orientated management. A lot of them will do anything to keep their jobs including make you lose yours through their incompetence and irresponsibility. Analyze the group dynamic and make decisions based on that.
... to have chrisbat's manager come on this thread and give her side of the database access / pooching story.
*throwing down the gauntlet to chrisbat's manager, and waiting*
by chrispy1
...but in light of some decisions made today by my fearless leader, I'm rapidly losing any sort of faith/confidence/trust in her. The good thing for me is that she's been caught in a wicked-ass lie (ie. the VP of Finance for my organizational group that our budget was OK, when in fact we're screwed)...So, as my dear mother said, a person that screws you will eventually, inevitably screw the wrong person - and I think it happened today. Not that I wish ill on my manager, by any means, but there is some sense of sanity for me in that she's not just "after" me.... :-)
One more coffee, a little more code, and then it's bed time...
.
I'll come right out and say it. I think YOU'RE the problem.
I'm amazed at these B.S. discussions, griping about "management", but they NEVER seem to even want to consider the manager's perspective. And that says a lot. Weather it's a manager trying to articulate the subordinate's perspective, or the subordinate articulating the manager's, if a person is willing to do that, it shows that he/she is willing to see the whole picture, the true picture, and in a manner that's consistent with the best interest of the company. You didn't do that. You apparently aren't willing to do that. Therefore, the real light of the source of difficulty is shinning very brightly on you.
Instead of accepting my suggestion, or even considering it, or even commenting on it, you only continued your tirade against the "incompetent" manager. If you worked for me, well, you wouldn't work for me.
I wish you the best of luck in what's bound to be, at best, a mediocre career.
by chrispy1
No tirades, just frustration. I've only given about 25% of what's going on - I was looking to my peers in the industry for some advice as to how to deal with a situation. I have been through a lot of shite in this position, and before all of this stuff happened, I was constantly bending over backwards for my boss. As certain things have occurred, I have had to watch my back more and more, and at the same time trying to get some insanely large projects completed in very short time periods. So do i read all the comments posted? Of course - I respect and appreciate everyone's opinion, and am interested in the comments and discussion. Do I feel the need to reply? Nope, I'm too busy. I reply to those whom I feel require a response, either because they're asking a question, making a good suggestion, or being really really silly in their post. Finally, I realise I could be part of the problem - I'm self-taught, this is the first position I've had with the responsibilites that I'm doing, and frankly am a little overwhelmed. So I could be contributing, yes, but I do also try and see where my boss is coming from - she's a person and deserves that respect.
Chris
.
You said, "You're self-taught, this is the first position you've had with the responsibilities that you're doing, and frankly are a little overwhelmed. So you could be contributing (to the problem), yes, but you do also try and see where your boss is coming from - she's a person and deserves that respect."
Okay, now we might be getting somewhere. But first, a little about me. I've been in this industry a long time. I've been (and am) both a manager and a subordinate. I hire people, I train people, and I actually help people advance in the company so that they move on and move up and out of my department. I do some things right, and I do some things wrong. But I always try to understand what my employees want and need; I always try and understand what my bosses want and need; I always try and understand what my peers want and need; and I try to always understand what the company needs are, which are always related to what our clients' needs are. I try to avoid "griping" and people who "gripe", instead prefering to focus on solutions. I avoid people with negative outlooks, and never reinforce them.
One thing I've learned is this. If you look at a situation -- any situation -- through the prism of only your own wants, needs, and desires, then you're setting yourself (and others) up for failure or frustration, or both. But if you can learn to look at a situation -- any situation -- outside of yourself, and through the eyes of others, then you're setting yourself (and others) up for success -- and define success however you'd like. One of the most impressive things you could possibly do is approach a project, a problem, or a challenge, and explain how to achieve the desired ends through the perspective of that other person, and then be able to do it. Help them get what THEY want, and then you can better get what YOU want. (And sometimes what "they really want" is something beyond the obvious, or something bigger than just an immediate request.)
For example, if you're in a job interview, and you can actually tell the interviewer things about the company, the company's product, and so on, and how you can actually apply your skills specifically towards their product, you'll impress them more than almost anyone else they might interview. And after you get the job (and you will get the job if you do those things), if you understand your bosses needs, and you can actually explain a situation through her eyes, she'll be all ears. You may not agree with it, but if you can explain it and understand it, then she might be more open to listening to your take on it. But approaching it from a "you versus her" position is almost always doomed to fail, and that's how you've been coming across in your messages.
You're right when you think that you have tapped into some great resources by asking your peers at TechRepublic to help. These folks can be a great resource. There are some real smart cookies around here. But there are also people who only want to join you in whatever cry-in-your-beer session or complaint session you might call to order. You won't get any sympathy from me if all you want to do is gripe about "a bad manager". And you won't get a lot of sympathy from the others that I might consider those "smart cookies". But you'll sure get some reinforcement from those who are also pigeon-holed into seeing things from only their self-serving glasses. Avoid those people like the plague, because you'll get nothing from them except reinforcement of your own negative outlook.
So if you want help from people who can really help you, perhaps you should consider broadening your perspective a little bit. After all, if you want help "dealing with managers", which advice might carry more weight? Advice from people who always have problems dealing with managers, those who can "relate" to your problem? Or advice from people who know how to deal with managers, perhaps even managers themselves, and ones who can help you overcome? If you choose the former, you're destined to keep getting the same results you've been getting. If you choose the latter, perhaps you can find that elusive win-win scenario that will help both you and your boss. And unless you're willing to pursue a win-win scenario, someone's going to lose -- and most likely, it'll be you.
So I'll ask again. Can you articulate and write down the situation from the perspective of your boss? Explain the issues as she sees them, and describe the intended outcome how she might want it to be? Describe the whats and the whys just as she would. If you don't do it here in this open forum, that's fine, you don't have to. But if you just do it, you'll undoubtedly see some answers that have been, up to now, very elusive. But simply griping about it will get you absolutely nowhere.
And here's my take on some comments that I've seen:
Advice from others - cover your ass.
Advice from me - cover HER ass.
And I'm absolutely amazed at the "definite" advice people give you based on only a few sentences you've shared. They must assume that their office politics applies to your office politics. They must assume that their company dynamics applies to your company dynamics. If anyone gives you specific advice based on only a few sentences exchanged, you might as well go to the local palm-reader, since there's really no difference.
by chrispy1
...I saw your response, but am absolutely baked. Thank you for a response - I will read it in the morning. I have just finished building some of the most complicated, complex database queries that I have built in a very long time. That, and I'm crashing from too much coffee today. Hate that.
I will reply in the a.m. Have a good one.
Chris
and trying to follow the Mark Twain maxim.
Maybe by the end of the weekend?
by hi_herman
Sounds like a difficult situation.
Working for a woman and a young one too..
(no offence meant ladies)
But I would certainly follow up on Maxwell's advice.
Been working with a female manager myself and had loads of crisises ( I am really stubbern and grumpy at times... :) )
But we seem to understand each other better everyday.
It just takes time to get two know each other. She has to learn she can trust what you say and you have to give her the time and space to learn it.
She might actually have some good ideas.
So dont do the dead weight thing and try to make something out of it!
Remember you'll be working for a big part of your live.
Better make some fun while your at it.
Have lunch or a chat over coffee and get to know each other..
Good luck!
by bbcoachr
by scotty059
Did you go to the lady that requested the permissions?, she may really need them, don't assume, it will bite you in the but, guaranteed. I also find this is a big problem with network admins and some techies, don't want to do things like setting up permissions or adding one or two for someone who needs them, that is your job and and you shouldn't be whining because of it. The company puts a lot more $10 per hour in your paycheck.
Your boss is above you, don't forget that, but she must also be informed of the consequenses of the actions she requested from you, which you did, make sure you document them, CYA.
As for the post it notes, very, very, scary, she actually has time to write out 45 post it notes and go to each computer station. AAAAAAAHHHHHHHHH!!!!!!!!!!!!
Good Luck
by scotty059
by robroynj
If so, you have a responsibility to protect the company and your senior officers. SOX has made so many situations very easy to handle. Anyone with any kind of rights must be documented and often auditors will question the decision to give rights to individuals. In either case, your documenting what you've done, why you did it, your objections, etc. will not only save your job but create the paper trail your company needs. Auditors will find it and likely question it closely if there are issues.
If you aren't public, do you think your company may go public? Do you have significant investors that require full audits? I'm less clear on private institutions but your boss' move clearly has implications beyond your own workload.
Having said all that, I must agree with many here that in the end you document the happenings and your objections and then do what your boss says. Sometimes, a formal e-mail registering your objections will cause someone to reconsider as they now realize that they cannot put the blame on you if things go badly.
by ayuknotna
Hi,
Been in your situation before, I know how it feels like. However, I believe you know that you?re not gonna win this situation unless someone higher than your boss back you up.
So, I suggest you make your boss put everything she wants in writing ?compile everything. Make a scenario out of those writings?the risk if you implement those changes (this might be your big gun later on). Present it to your boss?s boss.
Create backup every time you make changes?I know this means more work for you but this is the only way you can protect your job and your work.
If you ever talk to your boss?s boss, make sure you sound like your asking for his/her advice not demanding or some sort.
Goodluck.
by mlayton
And I'm not saying that for a CYA reason, but more because in a year, someone is going to wonder why you did that. It could be you, it could be someone who replaces you, probably because you'll be fed up and move on. The IT world is smaller than you can imagine, and in 10 years when you run into someone who had to take over for you somewhere, you don't want them thinking bad things about you.
But also, if anyone ever questions why - for whatever legal reasons, you'll want that too.
by jdgretz
OK, you've read all responses to date and what do you have? A database you had to clean up because of a bad decision or two made by your boss. Well, she is your boss and entitled to make those decisions. If you documented your position well, and presented good business reasons for your position, then you have done the best you could. Not fun rebuilding a database (I loved Clipper - was also on the dBase IV beta team), but hey, that which doesn't kill me makes me stronger (yeah, remember that at 0300 when the Twinkies, Jolt Cola and Cheetos have all run out).
Perhaps she will take a different view the next time you present her with sound reasons why her chosen course of action may not be the best.
I always try to error on the side of conservatism when it comes to access (least privilege in security terms) to data/programs/etc. This includes myself. At one company where I was brought in as a contractor to be the Director of Operations and Technology one of the first things I told the Unix Admins was - do not give me root access. I don't need it and I don't know this system well enough yet to be safe with it. When the time comes, we'll both know. Worked out just fine. I had the privileges to do my job and if I needed something more, I either got sudo or had one of the Admins find it. It also made it easier to impose those same restrictions on other departments.
Then again, I listened to my folks and seldom overrulled them unless there was a compelling business reason to do so, and then the issue was discussed in our weekly meetings or if necessary in a special meeting so that all knew why the change/exception was being made and how we should/could protect the system.
Good luck,
jdg
Especially so since "minimum level of access necessary" to any given database has been a mantra for as long as I can remember (only 18 years or so for me).
Much as there are many good managers like Maxwell out there, unfortunately there are many more who are just holding the title and careening from bad decision to bad decision until they relize they don't know everything. Which I guess is where they start to be a good manager?
by blieffring9
by tniast
Bottom line if you have to survive, do what your boss says. Like someone said, save emails, print em off and do with full intent irresepective of success or failure.
You will know when you are the Boss!
.
In addition to the messages I've already left, I might ask you one question (and then I'll answer it myself).
What exactly is your job?
You might say that your job is to administer a database. And this might further "imply" that you see yourself as the Grand Pubah of "your" database.
To that I would say, no, that's not your job.
Without people who use that database to advance their real business, and/or to sell their real product, you have no job. You are only one spoke in a wheel that's spinning in order to sell a specific product and/or service, i.e. the preverbal widget, for example. Your job is to do your part to make that happen more productively and/or more profitably.
There are 45 people who are presumably "on staff" to sell that product and/or service, or to support the sale of that product and/or service. You are the lone IT guy to help them do just that. So your job is to make the process better and/or easier for those other 45 people. You work for them, in a manner of speaking, not the other way around. You exist to manipulate the database to suit them and their needs, not the other way around where those 45 people might have to limit themselves to suit you or your preferences. Without their need to access that database, and to use the database, your position is rather meaningless.
Are you privy to the sales and marketing meetings? Do you sit-in on such meetings when the sales staff and sales managers (or whatever you might call them) discuss how they can sell their product better and more economically? Are you privy to how they plan to grow their business and/or expand their product line? Are you privy to these top-level decisions? I'll presume that the answer to all these questions is no, you don't know. Therefore, you may not be aware of some bigger picture, or if you are aware, you may not be considering it. But your job isn't to administer a database. Your job is to help them sell more of their widgets and with a better bottom-line result for the company.
If you really want to put a feather in your cap, make sure you fully understand your company's product and their target customer. And then come up with a plan for the company database, either how it's written or used, that will show upper management specifically how you can improve their product and/or service, sell more of it, produce it more efficiently, help the sales staff sell more of it or more efficiently, deliver the product to the customer faster, or whatever, and then you'll certainly get some attention. And if you have to go through your boss, and possibly even make her look good in the process, all the better. You'll look good; she'll look good; and the company will benefit. And believe me, if this sort of thing happens, your efforts will not go unnoticed.
But my real point is this. If you look at your job and your company in any way other than some version of what I've described, then you're missing a big part of the whole picture. And if you can't see the whole picture, then how can you possibly suggest that you know better than those who do?
by chrispy1
(Been sick - nasty throat/flu thing going around - hence the delay in me getting back to people)...Thank you for all the responses. Maxwell, you're the one who, to paraphrase your posts, has kicked me in the ass the best. To answer a couple of questions that have arisen - I am the DBA for a Vendor Management Group in a large, publically held Utility Company; as such, we have huge, multi-million dollar contracts with various contractors, and therefore the information that I am responsible for maintaining is not only critical to my company, but to those companies who work for us (they do like getting their paycheques! :-)...). As the DBA, I am responsible for maintaining 12 different DOS-based databases, a pile of Access databases, and to do analysis on everything from productivity to contractor billing to trend analysis and forecasting. I know a lot of people reading this would agree with me - if you presented the job description of what I'm doing right now, I would apply in an instant (isn't that how we all got these jobs in the first place?) I do love my job - I don't love the stress and frustration that comes with being the only Computer/ISIT/DBA guy for over 45 people. I guess my problem (please wait, epiphany coming here people) is that I have trouble saying No. Someone needs help with Excel, they call me. Someone's computer has just crashed, they call me. I guess I've gotten so used to being *the* IT guy, that when it comes down to me having to say No (as in the case of giving someone admin rights), people are not only surprised, but shocked as well. Yes, it's an ego-booster, I admit. But it's getting to the point now where I'm going crazy, spending my days running around and my nights actually doing my work. Not cool. So yes, I am definitely part of the problem. I am finding more and more the ways that my manager and I do not work well together, and am doing everything I can to alleviate them (my personal favourite strategy right now is Reflective Listening...). I am now using a "Report Request Form", which is fairly detailed for the types requests that I'm getting, and the person is asked to put their Employee Number, Contact Number, etc. (I got it off a friend in the company that downloaded it from a Project Management site and modified it for his purposes). I take hard copies, and when I have compelted the report, I send the original request plus the report back to the person (if it's hard copy, I print and staple it). I've actually been complimented on this style by my boss's boss, which is always a good thing.
OK, I'm exhausted. Been working on a financial forecast for almost 10 hours straight, still not feeling well - I'm going to bed.
G'night all...and thank you for your support.
by absolutely
.
I'm all in favor of saving emails when they might be necessary to recreate some set of circumstances or chain of events, but it's in the "why" that I've read around here that doesn't sit too well with me. If it's done for the purpose of advancing or protecting the best interest of the company, then I'm all for it. In my particular business, for example, we've had to rely on old emails, both to and from clients and contractors, to actually show what was really said, what was agreed upon, when something was said, and so on, all in the course of discussing some problems with a project, and possibly even avoiding a law suit being filed against the company, and so on.
But when people start saving emails to cover their own back-side from internal strife, then they've either lost focus on what they're really being paid to do, or they're simply in the wrong place. For every minute you spend documenting some pissing-match between a couple of people, it's a minute not spent doing your real job. And if you find yourself in such a position that you feel compelled to do just that, then your very position is obviously in such a direct conflict with your own value-system, that you're actually doing yourself a disservice by staying there.
Documenting some pissing-match between a couple of people creates the ultimate lose-lose-lose scenario; and it does nothing but directly interfere with the quest for finding the more preferred win-win-win scenario. (Lose-lose-lose and win-win-win being applied to employee-employee-company.)
Think win-win-win, people, and always act accordingly. Anything less will always result in less than the best.
by jck
Maxwell said this:
"But when people start saving emails to cover their own back-side from internal strife, then they've either lost focus on what they're really being paid to do, or they're simply in the wrong place. For every minute you spend documenting some pissing-match between a couple of people, it's a minute not spent doing your real job. And if you find yourself in such a position that you feel compelled to do just that, then your very position is obviously in such a direct conflict with your own value-system, that you're actually doing yourself a disservice by staying there. "
I won't even go into your wasted minutes comments...everyone wastes minutes in a day. Even you, Max. We're all human.
I thought chrisbat's problem was a naive boss requesting he do operationally stupid things?
Sure if it's just a pissing match, then it's ludicrous. However as I understood it, this "naive" boss was asking him to do things that could be detrimental to the operational integrity for which he is responsible.
In this case, CYA is not part of a pissing contest. It is being used by him as a part of documenting direct orders from his chain-of-command superior which are not in the best interest of the company.
So the question to Maxwell: Is part of his job, as essentially the DBA, not only to keep things running, but also ensuring the integrity of technology for which he is responsible from uninformed or negligent decisions from anyone...management or otherwise?
And my question to chrisbat: If you don't trust the "naive boss" with technology decisions, then would you trust this person to actually come into a meeting and admit that they'd told you to do something wrong that you'd claimed you warned them would be bad to do?
Cover your arse, chrisbat. If you don't, all your boss would have to do is say "I never told him to do that." and you'd be in jeopardy simply because you're not higher in the company "food chain".
.
You said that you, "thought chrisbat's problem was a naive boss requesting he do operationally stupid things?"
You can think whatever you'd like. But I think it may be a problem as to WHY chrisbat sees his boss as naive, and WHY he might think her requests are stupid. So far, all we have is chrisbat claiming his boss is naive. Maybe she is and maybe she isn't. And maybe her changes have merit and reason, but chrisbat just can't see it, and maybe they don't.
Whether or not his boss is naive isn't the issue. It's chrisbat perception of his boss and what she is doing that's presenting the problem. And I can try to help chrisbat as much as he'll let me. I can't do a thing for his boss, however.
.
.....that "managers" don't understand technology, or some version of that sentiment. I'm amazed, however, at how ignorance always seems to be a one-way street for only the "managers", and at how all these technology employees presumably understand management just fine.
by rm3mpc
1. Get your resume up to date and into circulation.
2. Document every request you consider unreasonable, along
with your response. E-mail a copy to your manager. File a hard
copy in your desk. Take a hard copy home with you.
3. Do what you're told.
by firstpeter
Stupid reality.
:(
That's a good point - there's a lot of CMyA going on at the management level. My point was more that management higher up the food chain should realize that the manager has responsibility for the team's actions. Period. If they don't, are you sure that your career lies with that company?
I think of it this way. If my boss won't take responsibility for what his team does and his boss is okay with that...what happens if I move into the manager's role? My boss is going to support my finger-pointing because he's finger-pointing at me, as well. Bad culture. Bad mojo.
... you seem to feel that the tech employees don't give a damn about profit be it gross, net, or IBITDA (or "Income Before I Trick Dumb Auditors" as CNBC used to say).
Truth is, most tech people understand that the company has to make money in order for them to keep their job. They also understand what it takes to keep the systems running so that the business side can have the availability necessary to make money.
Most companies understand that you just don't let everyone have access to everything, either from a security, SARBOX, HIPAA or "we don't wanna pay overtime to rebuild the database" standpoint. Even on the systems I've set up and strive to maintain I use my "Joe User" account unless I really have to do admin tasks. It is just plain old common sense.
But since you have the executive view, enlighten us techs: What business case will make the company more profitable by giving unlimited known flakey database access to a user whose first act is to blow up the database?
.
When you approach such a situation with a "them versus us" (or him versus me) mentality, breakdowns are bound to happen, and a full understanding of the whole picture will be fuzzy at best. I'll choose not to do that, regardless of whether I'm an "us" or a "them".
As far as your question, "What business case will make the company more profitable by giving unlimited known flakey database access to a user whose first act is to blow up the database?"
I'll not even comment on such nonsense.
by cactus pete
by jck
by jck
You're right: chrisbat *could be* misperceiving the situation.
However: It *is* chrisbat's *professional responsibility* to ensure data security and integrity as the person who is in charge or maintaining and administrating his databases.
You said:
"So far, all we have is chrisbat claiming his boss is naive."
Chrisbat wasn't that vague, and did state:
"I've tried breaking down every issue with the pros/cons of each situation, I've tried explaining to her about the integrity of the database being compromised, etc. etc. etc. - all to no avail - she still wants me to, in the latest instance, provide one particular member of our group with full permissions to one of my databases."
So, you were not accurate in that assessment.
Any manager who would request that a member of staff, who is not administrative over that database, be given full rights to a database is *technically naive*. The administrator is the only person who should run over a database in "God mode".
When you say:
"Whether or not his boss is naive isn't the issue. "
For chrisbat, it *is* an issue if his boss is *technically* naive and it *is* his responsibility to inform his boss of any problems that her policies and decisions can make in the future regarding the technical operation of his company in regards to the facilities for which he is responsible.
I still say the boss should be told in emails (or at least in a meeting in the presence of others within the group or department) of any problems that decisions she makes can cause. That way, she is held responsible if her orders cause detrimental events to occur and he's not held responsible for the technical ineptitude of a member of management because he didn't voice his concerns.
To encourage him not to do is to tell him not to perform his job function and possibly jeopardize him professionally.
And as for wasting time in emails, it would take a lot more time to recover database information from a backup than it would to write a 2 minute email and possibly prevent such a mishap.
.
You see a stated problem and approach it one way, while I see the same stated problem and approach in an entirely different way. We have a totally different take on it, a different perspective, a different outlook, etc. (Which, by the way, doesn't surprise me in the least.)
.
Dissect the question to consider the premise (premises), and you, too, will conclude that it's a nonsensical question to which a reasonable reply is impossible.
"What business case will make the company more profitable by giving unlimited known flakey database access to a user whose first act is to blow up the database?"
"What business case will make the company....."
I don't presume to know the "business case" of each and every company.
".....will make the company more profitable....."
I don't presume to understand the profit (or lack thereof) motivations of each and every company.
".....by giving unlimited known flakey database access....."
Where do I start, "unlimited", "known", "flakey"? All of these are editorial comments, none are a statement of fact.
".....to a user whose first act is to blow up the database."
OH MY! Call the Department of Homeland Security.
Sorry, I'll pass on posting an answer to such a stupid question.
Besides, you've missed my entire point. It's not about breaking down each and every he-said, she-said. It's all about outlook.
Outlook - no more, no less.
by jck
you should have left it at that.
Your dissection was irrational and twists words to meanings they obviously weren't meant to express. Your dissection reminded me of tabloid quotes.
The fact of a business case though is a theoretical business model with a particular theoretical situation. So, he didn't ask you to apply it to *all* businesses, but to theorize *a* case where it applies to chrisbat's situation to back your argument.
I'm agreeing with TooOld and others. Your views are twisted because of your position in the IT industry. You are, in essence, defending the managerial role because you need to validate your own decisions that are of a similar nature.
There is no business case or technical excuse to allow a non-administrative user full rights to a database he or she does not administrate.
QED
As for causing conflict/strife/etc within a company from the employee end, management should step up to the plate and clean up their act in regards to causing "us vs them" dilemmas before they worry about what employees do in that regard.
Management tends to fall back on the "policy requires us to do it this way" when they need validation for doing something to employees, rather than just telling employees "you were the easiest people to take from".
Maybe I should get into management. I know enough about forecasting and budgeting and "overhead" and "capital expenditures" and have a large enough vocabulary, mixed with my experience in various technical roles, to move up the ladder.
About all I'll have to do to make it there is drink enough to lose my conscience.
Here I come, Will Riker...take the captain's chair or get out of my way. hehehe (hope you have watched a lot of Star Trek TNG or that will go right over your head too.) :D
.
You're acting as though it was YOUR message and YOUR question that I didn't deem worthy enough to answer. Let the author of the question speak for himself, for Pete's sake! Talk about the epitome of presumptuousness; you seem to have cornered the market!
As far as your other comment to me, that I'm "defending the managerial role because I need to validate my own decisions that are of a similar nature." Up yours, dude. You have no idea what you're talking about. Go have another drink.
And besides, here you are questioning what other people think about my messages, and the very guy who started the thread has said that I'm the only one who seems to have connected to the real problem, or in his own words, "Maxwell, you're the one who, to paraphrase your posts, has kicked me in the ass the best".
Man, oh man, jck, you speak for other people like you're a friggin' mind-reader. Get over yourself, already.
.
I've offered more "technical help" around here than almost anybody else on the entire site. You, on the other hand, have offered virtually nothing.
And another difference between you and me is that your vision is limited. I can see the difference between a "technical problem" and one that might fall into the inter-personal relation (or just personal) realm. Sure, in your eyes, the manager's the idiot, all managers must be idiots, all managers are technically illiterate, and so on. The truth, however, is that you're an idiot, jck, pure and simple. (Now is when you cry foul about "name-calling".)
I'm a great manager. And I don't need anyone to tell me in order for me to realize that. All I have to see is the scores of people I've hired, I've trained, I've helped reach their potential, and I've helped get promoted and onto a better career. Out of almost all of the people I hire and initially train and manage (and it's been in the many dozens), very few quit, I've fired practically nobody, but almost no one remains in my department; and it's because I get almost all of them moving up in the careers. I know what it takes, and I know how to do it.
But no, in your estimation, I seek some sort of validation from this silly message board. My validation comes from those people who look back at me as their first boss who gave them their start. And I actually do look for rookies, fresh out of school, without the bad-habits or bad-outlooks that comes from working with people like you.
Yep, you're definitely an idiot.
Max, I can appreciate how you wouldn?t like how my question was posed. I can also appreciate that I don?t have the first clue what it is like to have an executive position in IT, and have a viewpoint from same. (I'd be more than happy to try it some day, however.) However, your dissection infers that I don?t have the rhetorical ability of a flea, and there I think you are wrong.
"What business case will make the company more profitable by giving unlimited known flakey database access to a user whose first act is to blow up the database?"
"What business case will make the company....."
> I don't presume to know the "business case" of each and every company.
I wasn?t asking for the business case of chrisbat?s company; just generally any company. All of them have use a business case for decisions, or should.
".....will make the company more profitable....."
> I don't presume to understand the profit (or lack thereof) motivations of each and every company.
But we can presume they want to profit, or make decision to make a profit, rather than a loss, or just to be neutral.
".....by giving unlimited known flakey database access....."
> Where do I start, "unlimited", "known", "flakey"? All of these are editorial comments, none are a statement of fact.
Administrator (or God Mode) access then. And we can say known, or at least within the confines of the example at hand, known in advance to the entire IT department than the extant old Clipper database was flakey. Maybe not to management, but to the people (IT) who should have known.
".....to a user whose first act is to blow up the database."
> OH MY! Call the Department of Homeland Security.
> Maybe ?blow up ? was too colloquial. How about ? ... to a user who neither required, not had the necessary skills, to operate the database in Administrative mode??
> Sorry, I'll pass on posting an answer to such a stupid question.
I so love it when my betters try to intimidate my by calling me stupid just because I didn?t hit every career fork in the road dead on.
> Besides, you've missed my entire point. It's not about breaking down each and every he-said, she-said. It's all about outlook.
And your outlook is fairly clear: Management can do no wrong, and employees? sole job is to make management look good.
But that is not the job of employees. It is their job to make the company succeed, and management succeed, and if that means occasionally a record of potentially questionable decisions, so be it. It is just part of the job. At the company I?m contracted to presently, there are whole groups of people over in Project Management whose job it is (in part) to document the decisions, the planning that went in to them, and maintain the paper trail. It sound?s like chrisbat?s organization could use a little more project management, but that?s just a subjective opinion.
So, back to my revised question:
In theory, is there a business case than can be made for giving Administrative access to an employee who does not have the ability or the requirement to run a database in Administrative mode when that database is know to be easily corrupted? (Assume increased gross profit is the motivating factor. Assume also that your IT department is understaffed, and database professionals for you database are not easily obtained.)
Hey, anyone else who wants to take a swing at this one is welcome too!!
by wayne m.
I have to fully agree with maxwell edison's two posts above. CYA is never an effective solution and whether the boss is naive is not the question.
Obviously, the boss wants something. Complaining that the boss is naive does not make the need go away. The mark of an effective employee is the ability to understand the underlying need and present an acceptable approach to meeting that need.
I am not going to play amateur psychologist here, but I do note that the tone of the discussion does not appear to be "How can I help my boss get his job done?" but rather "How can I tell the boss how to do his job?"
by chrispy1
I came onto this site looking for advice, support, and encouragement. I came to my peers looking for direction to what has turned out to be a very sticky situation. I came to what I thought was going to be a mature group of professionals. Instead, I found that except for a very select few, IT Professionals seem to suffer from "Small Penis Syndrome" as much as every other industry - you're all out to shout louder, more often, and more adamantly that YOU'RE right, that you're opinion is the only one that matters. It's all bull s**t as far as I'm concerned. If everyone had said something along the lines of "Hey, you know what, I've found _____________" to be the best in this situation, it would've been a totally different story. Instead it's turned into a freakin' pissing contest. Holy crap, it's no wonder non-ISIT people see us as a bunch of condescending, arrogant snot-heads - because even in a group such as this, trying to help out one another, WE ARE. "I'm right!!" "No, I'm right!" it's amazing companies like Microsoft and Sun survive if all techies are as narrow-minded as many of the people on this post. OK, I'm probably going a wee bit over the top here, but I figure I'm just following suit with the rest of the crowd.
If you have nothing productive left to say, please don't post anything else. I've gotten all the suggestions and advice I need to carry on with what very likely may be my last ISIT job......
Thanks y'all for making this a very enlightening experience.
by sixwings
I also happen to serve an all-powerful but not-quite-all-knowing boss who has adopted a habit of imitating setups and policies from his CEO buddies, some of which are downright ugly.
When straight explanations fail to derail him from his path of potential destruction, I usually employ one of the tactics below depending on applicability. These tricks are not meant for the faint hearted, mind you, and I advise that you get your resume into circulation before attempting these for yourself.
---
1. The One Up
Tell him how infinitely intelligent he is for thinking up such a great plan/policy/solution on his own and that yes, you will go along with it as long as he agrees that you do one of the following:
a. formulate contigency plans in case of system failure
b. establish "a few minor restrictions"
c. prepare a stage-2 proposal which will use his brilliant idea as a springboard
What you wont tell him is that options A to C are all designed to improve, circumvent, reverse or totally negate his decree in one big lump or one nybble at a time.
---
2. The Straight Lie
Some configurations or setups can be altered with little to no impact on users but with significant benefits for the administrator. If the boss insists on a particular setup, just tell him you did it and go ahead and proceed with your plan anyway. This works if you've established a secure circle of trust with your staff/deptmates. But just in case he finds out just tell him how smooth your setup has been running for the past N Months.
---
3. The Witness
When my boss calls me in to discuss a change, I always bring a member of my staff with me, explaining that he (my staff) will be implementing the changes. This way, if my boss and I disagree on certain points I can defend my views in front of a third person. Apparently, this multiplies the burden of making a bad decision a thousandfold. Aside from being a slimy CYA move, it also offers the following benefits:
a. my staff learns from the exchange of views
b. I gain additional respect points from my staff
c. my staff could express his view on the matter
If the boss insists a bad decision, he will not be able to squirm his way out of any bad consequence.
**** Disclaimer ***
I may not be held responsible for any ugly scenarios you may encounter by following the above tips. Have fun! ;)
.
You come here for help, and people obviously give it to you. They don't have to, you know, but they do anyway out of the goodness of their heart, free of charge, and all for the want of nothing in return. Whether or not we will all agree in our assessment of your issue doesn't mater. In fact, it's probably good that we don't, as it gives you more to consider and to apply to your particular circumstance.
But for you to go-off on those who HAVE tried to help you is what's disappointing, not that a couple of them don't agree. Where in the hell do you get off by such behavior? I'm more convinced now than ever that you are indeed the cause of your own problems, and it's your boss who has a naive employee to deal with, not the other way around. Get off your friggin' high-horse, dude.
And just so you know, your discussion is nothing special. Besides, you don't know the history between these posters, jck and myself, for example. They ALL go off-topic, and often-times might have a thread that picks up where another may have left off. jck has always been an idiot, not just in your discussion. And he looks for things in my messages to criticize; that's his game. And you should know me by now, I call 'em like I see 'em.
So open your damn eyes; don't be so narrow-minded; don't be so naive; don't be so friggin self-centered; and go do what your boss tells you to do.
.
First of all, I don't usually dissect questions like that, but I only did it to illustrate how it simply could not be answered; and I did it only because another pain-in-the-ass third-party pressed the issue.
Your question was establishing a premise that was either untrue or unknown; it presented a problem that was also either untrue or unknown, and then it drew a conclusion that was stretched to the absurd. It was simply not a serious question. Why would I even try to answer it? And I called the question stupid, not you. But smart guys can ask stupid questions. (And that must be true because I've asked stupid questions myself.)
And something else you just said illustrates how I see such employee-manager divisions, and how I try to avoid falling into such traps. You fell into the "us against them mentality" AGAIN. I never said, and I never even implied, that managers can do no wrong, but you claimed that was my conclusion. Jesus friggin' Christ, get over it, already. No, not all managers are always right, BUT NEITHER ARE THEY ALWAYS WRONG!
I called this problem (with chrisbat) just like I saw it. And do you know what? It appears that I've seen it clearer and more accurately than anyone else. One thing you might heed is this. Just because Person-A tells a story about Person-B, it doesn't mean that Person-B will see it the same way; and it doesn't mean that Person-A is necessarily right. And if we, as recipients of that story, don't consider that we don't know what could be accurately called, the rest of the story, then we are doing everyone, including ourselves, a disservice by drawing any specific conclusion.
No, I'm not going to take chrisbat's word on it that his boss is naive .... or that his parents are naive ..... or that his co-worker is naive ..... or whatever. The way it all comes together is often-times more telling that the words themselves.
It was obvious to me that there was so much more to this story than chrisbat was sharing with us. And all I did was question the conclusion that people were drawing, and wondering HOW they could come to those conclusions, when they obviously weren't privy to the whole story.
But go ahead, knock yourself out. If you want to contend that chrisbat's boss is naive and that he is right based only on his word, perhaps that will give you the clue you've been seeking about that elusive fork in the road you mentioned.
And to answer your rephrased question. Yes, a business case could certainly be made for such a scenario; but without knowing ALL the factors involved in making such a case, it would be silly to try.
by jessie
by jck
It's obvious that you only take your own position and point-of-view seriously.
Chrisbat lined out what the manager had told him to do, and he outlined how he'd informed the manager of the downfalls of that decision in (which at least was very evident to me) giving a non-administrative user full rights to a database.
To me, any technical manager who would tell his DBA to give a user full rights to that database is technically inept. That puts corporate data, and the operations of that corporate, in unnecessary danger. The DBA should be the one person who has complete access to all functions upon the database.
Endangering that operation can cause unnecessary downtime and loss of productivity, which in turn effects other projects and can negatively impact revenue.
Hence it's not only technically inept, it is also an unsound business practice.
So, think what you will.
As for answering questions, I have offered input on technical issues here before. However, my scope of technical offering isn't limited to either the abstractness or cyberspace, or the singularity of TR.
So, don't be assumptive about my technical capabilities or contributions. Fact is, I do roam more than one technical site and offer up help in other places besides TR. Just because you can't see everything I do doesn't mean you know everything about what I do.
And just because you've been here 4 years and myself having only been a member 8 months doesn't make you any better. It just means you've had more free time to be in here answering questions.
Also, I don't think "all" or "every" manager is stupid. In fact, I commented previous to this in another discussion about my software systems manager when I worked at the government contractor being quite brilliant.
So, you're assumptive of my opinions as well. And, you're dead wrong about them.
So, go back to reading your emails and doing your Microsoft Project or something. I'm sure there's something in your office that needs to be done as well.
I'm going back to doing my programming and DBA work.
Max, I think you and I may have wandered into agreement on something: "Change the database to let person Y have administrative access." is not an end unto itself, but part of a larger whole.
Or a larger project.
(Opinion) Hence my thoughts that some project management may be in order, so that all aspects of the project may be vetted. Somewhere between creation of the project charter and lessons learned, this small request will attract some thorough review (or one could hope).
It is just possible that the request would still be given the green light, but likely only after backing up the database and storing the tapes off-site tasks were performed and signed off.
Probably why my PM buddies keep saying that smaller shops may need a professional project management team more so that larger shops.
Then there is SOX compliance, yet another 800-lb gorilla in the room these days.
... as it sounds as if some "corporate IT governance" is what is needed here, to keep requests for IT service within the process, rather than Project Management (the piece is part of a larger whole that needs to be vetted properly).
mea culpa to all, especailly Maxwell Edison
This discussion is closed to new replies.
Trending Community archive posts
Sort by Trending