Slashdot Mirror


Ask Slashdot: Biggest IT Management Mistakes?

snydeq writes: Sure, nobody's perfect. But for those in charge of enterprise technology, the fallout from a strategic gaffe, bad hire, or weak spine can be disastrous, writes Dan Tynan, in an article on the biggest management mistakes in IT. "Some of the most common IT gaffes include becoming trapped in a relationship with a vendor you can't shake loose, hiring or promoting the wrong people, and hiding problems from top management until it's too late to recover." What are some other career- and company-destroyers you've witnessed in your years in IT?

26 of 341 comments (clear)

  1. frosty by Anonymous Coward · · Score: 5, Insightful

    Implementing SAP
    Outsourcing
    Outsourcing your SAP implementation

    1. Re:frosty by ShanghaiBill · · Score: 4, Informative

      Implementing SAP
      Outsourcing
      Outsourcing your SAP implementation

      Whenever I talk to someone from a company that uses SAP, I always ask if they are satisfied with SAP and would choose to use them again.

      So far, this many have said yes: 0.

      For comparison, this is the number that have said they are happy with Oracle's ERP: 0.

  2. Outsourcing by Anonymous Coward · · Score: 5, Insightful

    People in India can't possibly know your business, your other employees or your customers as well as qualified, competent, real live boots on the ground in the US of A.

  3. Outsourcing and offshoring... by Anonymous Coward · · Score: 5, Insightful

    The two biggest mistakes I see is that a dev team which is doing fine gets cut and the people outsourced or offshored. Sales and quality hit the shitter, but management doesn't care one whit about that, since to them, the only people that matter are the S&M guys (sales/marketing), so more gets offshored.

  4. Failing to manage customer expectations by El+Cubano · · Score: 5, Insightful

    Practically every mistake in IT is recoverable, except for failing to manage customer expectations.

    In particular the two ways in which I can specifically think of that lack of customer expectation management becomes a project killer are lack of solid requirements (e.g., constantly changing requirements), and mismatch between the developer's idea and customer's idea of what the deliverable should look like.

    I think that the requirements one is the worse of the two because it is so easy to have this conversation:

    cust: Can you just add in this one little change here?
    dev: Sure thing
    cust: While you're at it ....

    Code Complete covers this pretty well with the analogy of building a house. "Moving" a wall is really easy when the house is just a drawing on paper. It is considerably more difficult once the foundation is poured, the walls are up and the roof is on. People building houses know that asking to move a wall in the later stages means lots of money and time on the project. However, because software is an intangible and you can't see it taking shape in the same way as a house it is much more difficult (for someone who is not a software developer) to appreciate that things that seem simple might actually be major architectural tasks for the project.

  5. Sales Engineer by Major+Blud · · Score: 4, Insightful

    Always make sure your sales team includes a dedicated engineer. They will help keep them in line, and mitigate situations in which a customer was promised something like running Internet Explorer on AIX.

    --
    If you post as Anonymous Coward, don't expect a reply.
  6. Failing to expand with the business by rgmoore · · Score: 5, Interesting

    The big one I've seen with my current employer is that they've failed to expand their IT staff as the organization as a whole has expanded. The predictable result is that nothing but the most urgent requests gets handled promptly, and minor problems fester indefinitely.

    --

    There's no point in questioning authority if you aren't going to listen to the answers.

  7. Hiring brogrammers who push out real talent by Anonymous Coward · · Score: 5, Interesting

    I recently worked for a startup with a real big asshole brogrammer who never was in the office and always was misunderstanding what was going on. Eventually I caught on to these charades. He was also lying to investors about our startup actually containing AI when it couldn't have been farther from the truth. To cover my own ass I sent a text message to the CEO warning him that we were committing fraud. After that the mark was on my head. Our "brogrammer" calls me into a room and says that I'm toxic. I counter by asking him his working hours and if he understands what fraud is. Over the next few weeks regardless of what happened I was ripped into a room and told how toxic I was.

    Of course I was let go shortly after because the dumb CEO who always called me "his brother" was well aware of the sham and apparently didn't care. The crazy sociopath actually thought that I would still be friends with him after being fired. He also thinks it's some point I will come back to work for him, likely whenever that brogrammer finally leaves. I wonder if he knows that I'm planning on telling the FTC and his investors about this "AI" company. It's a bunch of regex matching natural language to appear as if you are speaking to a digital assistant. They're actually telling customers that this is a real AI system.

    I would call this a serious mistake because their entire future is essentially in my hands. Since this Psychopathic CEO thinks I'm his friend and going to keep the lid on this, he's just plodding along blowing his money on other endeavors. I'll just let him build a little bit more of a paper trail for me before I strike. That's what you get for listening to the brogrammer.

    1. Re:Hiring brogrammers who push out real talent by redmid17 · · Score: 4, Insightful

      Right now this post makes me think of Ned Stark and his paper shield, except that you don't really have a paper shield, merely a piece of paper with no writing on it.

      I hope to god you have some actual proof and can take it to the FTC. If you don't and you file a complaint, you might well be facing a lawsuit on any number of grounds. To be completely honest, I don't expect this to play out well for you

  8. Too many to list by Anonymous Coward · · Score: 4, Interesting

    I've seen them all, but "buying products or services from Oracle" ranks pretty high up. Or more generally, putting faith in a vendor because of a glossy ad in "CIO Magazine" or somebody in management getting kickbacks. Nontechnical managers are incapable of making these decisions, but want to feel like they're in control, so they try anyway.

  9. "No. 1: Vendor lock-in" like buying Microsoft? by greenwow · · Score: 5, Informative

    In about March, we started moving everything to Microsoft, and they audited us in August. About $250k worth of internal time later, they gave us the final bill. We didn't know, for example, you couldn't run Visual Studio Professional on Amazon on nondedicated hardware. Amazon charges $2.185 per hour for that which is $19,140.60 extra per year. We're paying $1,199 per year already for VS for every developer, so we assumed we'd be allowed to use it with no extra charges. We were wrong. I think the total bill after the audit was over $130k plus the extra almost $20k per year on Amazon. We don't even yet use Windows for production(customer facing stuff)!

  10. If I had to pick one by AlanObject · · Score: 5, Insightful

    Not implementing and operating a data backup system properly.

    I have been bit by this myself and I thought I was doing a good job at it. (I'm not an IT manager -- I'm a software engineer who often gets shoved the IT manager's job for one reason or another.)

    Almost every other failure can be mitigated but not this one.

  11. Re:News stories: Intel and Microsoft spyware. by Anonymous Coward · · Score: 5, Insightful

    Show me an OS that can replace W10 with everyday apps. There isn't anything out there that can handle Acrobat, MS office, Outlook, Exchange and other items, other than Windows. Oh, AD capability is a must out of the box.

    Don't tell me what to use. Tell me what you are trying to accomplish, and I will find a solution. That's my job as an engineer. Of course you can't run Exchange on Linux without virtualization. But if your goal is to get e-mail, calendaring, and contacts I can do that for you.

    Need Acrobat? Sorry. Try coming to me and saying "I need to read PDFs" or "I need to save this document as a PDF". Sure. I can solve those problems for you.

    "I want Office on Linux". No, you don't. You want some of the *features* Office provides...on Linux.

  12. Like this? by rickb928 · · Score: 4, Insightful

    Arriving at the new hospital data center (a room 500 ft from the old data center) before anyone else (including IBM), doors open, snowing a blizzard out at 25 degrees, calling the CIO and asking him if he'd been in the room lately.

    Nope.

    Asking him if he had the electrical contractor's number Call it. There is not s single power outlet visible. Not one.

    Yeah, they closed up the walls and painted, the electrical sub never got called.

    Extension cords. Frantic 220 installs. Mangled sheetrock. The AS/400 came up about 5:30pm. I was secretly pleased our NetWare cluster was in failover...

    We got done about 10:30pm on a Sunday night. No one every asked if this was an IT blunder or or a contractor blunder, but I never discussed it with the CIO , ever. He paid the overtime. My boss was litersally, genuinely speechless, a first for him. This was the same client who had a Token_Ring network that would beacon furiously on a regular basis. IBM took three months to say they couldn't do anything with the CAUs/LAMs, and they should come out and be replaced with switches. Took me asn entire afternoon to find the loose DB-9 interconnect on an 8230 chassis, the ones that were welded on back then. Bolted it in place, problem solved, we did put in the T-C switches during the move. I credit Laura Chappell, her presentation on Token networks at Networks Expo when she was with Novell, and Lanalyzer, for making me a lot of money. Thanks you, Laura!

    Now there was the client who, after much analysis, believed his app vendor and replaced our 16MB Token-Ring network with 100Base-T, since they were adamant that Ethernet would outperform Token. This required recabling, drops from the ceiling, because we had reused the existing Cat 3 PDS in floor trays, but that wouldn't do for 100Base-T. No, it made no difference. The vendor them blamed NetWare and AdvantageDB, and in came the NT 4 server. The IT supervisor was the owner's son, but that's not why I questioned his competence.

    I don't know how that came out because they wouldn't use us for that, we were a 'NetWare shop', despite my finishing my MCSE. Fine. I know the new guys presented migrating NetWare to NT at our Novell user group two months later. That's how it was back then. Feh.

    --
    deleting the extra space after periods so i can stay relevant, yeah.
    1. Re:Like this? by Richard_at_work · · Score: 4, Interesting

      A month or so after I was "promoted" from lowly developer to "Systems Infrastructure Manager" during a whole-scale move from an old green screen AIX based system to a brand new in house custom rewrite in modern tech, we had some of the new replacement hardware onsite and being built up (although the replacement applications werent ready to go, but thats not important to this story).

      One friday, the UPS support contractor came in to do his servicing of the UPS - that went well, he finished up and switched it back from "bypass" to "protected". That triggered a surge on the electrical supply to both server rooms, which took the AIX box off line. Due to the nature of the green screen application, there was no way for it to be high availability - the data couldnt be replicated in real time, it didnt even talk to anything other than its own binary database files...

      A few hours later, the corrupted AIX box was restored and ready to go - by this time, the company (a busy call centre) had been on manual processes for the entire afternoon. On the advice of the UPS contractor, who said the surge was probably the result of too much load on the UPS at the time, we decided to do a full shut down of the entire system, switch the UPS back over into "protected" and bring everything back up - so we waited until 6pm and did just that...

      At 6pm, I threw the switch - and promptly looked over my shoulder at the comms racks behind me in the server room. The comms racks were billowing smoke. The comms equipment was burning. Before I could react, I heard loads of loud pops and bangs - both inside the server room and outside it.

      Another surge. This one did real damage - a dozen network switches dead, over 40 PSUs in the servers dead, one server dead outright, and loads of call centre desktops went (loudly) pop.

      Panic time. UPS contractor called back in - they gave the UPS a clean bill of health and promptly left, disavowing any responsibility.

      The board of directors shat themselves - at that point we didnt know the ultimate damage count, but suffice to say the company was dead in the water to any observer.

      Cue a desperate night of testing servers, pulling dead PSUs and swapping redundant PSUs between servers so that each server had at least one good PSU. Comms equipment was harder to solve, having to get some expensive switches from our local shop to tide us over. Desktops were bought from the local consumer PC store to give us enough desktops to run the company.

      Ultimately, we were back up and running for 8am Saturday - it wasn't pretty, but it was up and running. 3 of us in the IT tech team worked through the night scraping the bare minimum together.

      My predecessors DR plan was fleshed out to the point of "we have a DR site" (a commercial site a town over that we had a contract to use - no equipment there, no plans for how to fail over to it etc etc).

      So, on to the management failure....

      It just so happens that one of my things "to do" on the following Monday was to submit my DR plan for the "new world infrastructure" to the board, who were having their quarterly board meeting the following week (10 days after the company almost died). It was a modest one, but required some equipment outlay to make any DR event as smooth as possible - kept the same contract with the off site unit etc etc.

      They turned it down, said it wasn't needed.

      I quit the following week.

  13. Know your limits by AHuxley · · Score: 4, Insightful

    Know what results are needed.
    Does a medical database have to track phone calls, public and private databases to ensure every person who had a test got their results?
    If a person had contact with a professional over a result? That person never got a result and never saw the professional after a test was done.
    That a person actually got their results and did not move to another part of the country?

    Bring in an expert who has worked with the exact problem around the world and who can make a database work in your country.
    Real skills and the local experts get network and database they want.
    Have political and gov move in and demand they be allowed to build the network with gov staff and other contractors who have no skills.
    Thats how big gov can fail.
    Take a project from the gov that has the skills and give to the politically connected private sector.
    The contractors have no skills.
    Thats how contractors can fail.

    Stop using people with no skills. Stop allowing people to work on complex projects who did not pass their exams and got given a decade of social advancement.
    IT can work if the right experts in the private sector, gov, mil or as contractors are found.
    Stop advancing very average people with no skills into the IT sector every generation.
    Find professionals that can understand complex problems.

    --
    Domestic spying is now "Benign Information Gathering"
  14. Sunk cost fallacy by DeplorableCodeMonkey · · Score: 5, Insightful

    Time and again, it's the sunk cost fallacy. A system that an organization might have spent a few million dollars to build is just not shaping up into anything they can use, but they keep at it rather than ditching it and seeing what they can do to change things.

    What ironic about this is that I think agile actually encourages the sunk cost fallacy because teams will go "oohhh we can 'pivot' a little each sprint." Uh, no. If it's deep-fried dog shit for an architecture, and design you're not going to "pivot" out of this. It gets even worse when you have a management culture that doesn't understand refactoring; most of the agile teams I've been on have had managers who flat out don't care about technical debt and think they can default on it which reinforces the problems with the sunk cost fallacy down the road.

  15. Cloud computing ... by CaptainDork · · Score: 4, Interesting

    ... it was actually just RDP to a remote server.

    At the first management/vendor meeting, I got to ask the first question: "How will response time compare to what we have now, with our servers in-house?"

    "Oh, it will be much faster!"

    It got worse from there.

    I asked the owner if he knew that light slowed down in a medium and he said he did.

    We already used RDP to the desktop and he KNEW about the latency.

    Management ignored the red flags I threw on the play and put everything on the cloud against my recommendation.

    We were a law firm and a time came when an elderly couple traveled from far away to sign some wills and the goddam cloud was down.

    The family law practitioner blew her fucking top and confronted me and told me to implement Plan B.

    I told her, "Ma'am, Plan B is Plan A."

    It cost a fortune, but they paid termination fees and put everything back the way I had it before they went nuts.

    --
    It little behooves the best of us to comment on the rest of us.
  16. Switching to Windows Server by aaarrrgggh · · Score: 4, Interesting

    We were on Linux for our file server for a decade and ended up needing to switch to Windows. We were tired of not having a good consultant and Windows consultants were easy to find.

    The mistake incidentally was not in switching to Windows per se; it can easily do the added tasks we need of it and Linux could not. The mistake was in thinking the issue was in finding good Linux consultants-- the issue was simply in finding good consultants period.

  17. Re:Don't be like Equifax by lucm · · Score: 4, Insightful

    Don't hire a music major to be your CSO.

    The best CIO I've met was a music major, he even played in a symphonic orchestra for a while. He got started in IT because he wanted to design his own DSP.

    Some people are a lot more than their diploma.

    --
    lucm, indeed.
  18. Re: Biggest mistake by Billly+Gates · · Score: 5, Insightful

    Executives with no IT experience running IT departments.

    NO. More likely the executive making promises to customers and PMs without checking with the IT department and then demanding a months worth of work be done in 72 hours to one week and fire them if they can't get it done etc.

    If you do get it done then it will continue. You are screwed either way

  19. Re:News stories: Intel and Microsoft spyware. by johannesg · · Score: 4, Insightful

    What you're asking is extremely unfair, especially from users who are not used to think like IT-lawyers. To them "Acrobat" is not just "reading PDFs", it is a whole set of capabilities including things you won't find in free alternatives (like encryption, form support, etc.). Asking users to articulate those needs individually, when they can summarize with the phrase "I need Acrobat", which they already know and of which they already know it supports their needs, is both unfair and unrealistic.

    And it's not just capabilities, it's also a general lack of hassle. I use OpenOffice a lot, but frequently it fucks up the layout of Word documents. As a user I neither want nor need that hassle.

    Look at it from a users' perspective: what they have now works. What you are selling is a journey into a world of pain, hassle, and "sorry we can't do that". Why would they want that? What tangible (i.e. not abstract) advantage do you offer to make all that worthwhile?

  20. Re:News stories: Intel and Microsoft spyware. by Darinbob · · Score: 4, Interesting

    And some of the things I hate most about Acrobats are these unnecessary additions to PDF files. It should be a read-only format, impossible to turn into a vector for malware. But no, Adobe screwed that pooch. I cannot open a PDF now, with Acrobat or Preview, without it thinking I have just modified the document and so it will ask me when I close it if I want to save my changes. I don't want encryption, if I wanted encryption I would encrypt the file. I hate vendors that send me "secure" documents and then require me to check in every 6 months to get new certificates so that I can continue to read it. I just want to read the document and I don't need the heavy weight Acrobat with it's strange UI doing this.

  21. Re:Pretty Much Universal. by Z00L00K · · Score: 4, Insightful

    As soon as you outsource you are in the hands of the company you outsourced to and that company don't understand your business model, only profit for themselves.

    Putting things in "the cloud" is probably the most dangerous thing you can do these days. It's like peeing in your pants, it feels warm for a little while.

    --
    If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
  22. Re:News stories: Intel and Microsoft spyware. by Bert64 · · Score: 4, Interesting

    There was a story a few years ago about how google banned the use of windows desktops on security grounds. If you needed a windows desktop as a specific requirement of your job (testing, dev etc) you had to be able to justify it.

    But it does make quite a statement, the more technically oriented a company is the less likely they are to be using windows.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  23. Re: Biggest mistake by apoc.famine · · Score: 4, Interesting

    A friend makes bank now after his CEO got pissed at sales and marketing doing this shit. His sole job is to go to sales meetings and keep sales honest. He knows the business well, and studies up on the customer to understand who they are and what they seem to need. Then he shoots down sales during the meeting when they start promising too much or trying to sell something that the customer doesn't really seem to want or need.

    The marketing folks hate him, but the CEO, developers, and the customers love him.

    --
    Velociraptor = Distiraptor / Timeraptor