Live data from Hacker News

A billion reasons never to buy IBM services

foliovision.com

181–190 of 200 posts

Re: A billion reasons never to buy IBM services

#181
post #125

Earlier quoted context omitted.

Payroll projects are always disasters. Any vendor will do exactly what is asked, no matter what. IBM, Dell, Accenture, Deloitte, McKinsey, etc. There is no reason why a customer should allow a contractor like this to run roughshod over them -- thats incompetence and bad governance. I've run big projects with vendors like this. You write good RFPs and hold feet to the fire and they will deliver.

> You write good RFPs and hold feet to the fire and they will deliver. That's the key bit though. Its not easy to write good RFPs. Unless done to an excruciating level of precision (which they very seldom are), you leave wiggle room which the vendor will naturally take advantage of when things get tough.

That is the face of the problem.

In the construction business, there’s no need to state that nails get hammered or screws turned, unless there is a very specific application. But they tend to structure projects in a way where there is an incentive for success and punishment for failure. That's not to say that it's perfect, but there are far more $10M+ failed IT projects than failed construction projects.

If you work in this industry, you've seen your share of IT vendors delivering barely literate offshore workers through 2-5 layers of contracting pimps. That simply doesn't happen with pipefitters and others.

In IT, the tenure of the CIO other senior leadership is often is lower than the vendor and the project. The incentive for the CIO is to listen to because they may communicate what is happening better AND they may want a job with the vendor later. Without the threat of reprisal, many organizations will make poor decisions (both vendor and customer).

Re: A billion reasons never to buy IBM services

#182
post #60

Earlier quoted context omitted.

Because government contracts have to be transparent, the award process tends to be overly bureaucratic and algorithmic. There's no real mechanism with which the Canadian government could bar IBM from bidding, and they're obliged to take the best bid. Usually this is lowest cost per rated point, scored against a large matrix of must-haves and nice-to-haves that are assigned weights.

Sounds like the system is set up in such a way as to deliver a under-performing product. Especially if it optimizes for "lowest cost per rated point". Quality things require significant investment. No wonder IBM has to go get developers outside of the US/CA/AU if they were the lowest bid. Now it all fits together. Whenever i go to my states web services and they look odd. I now know why. That is changing though.

I used to work as an in house contractor for the US Government on a team with two other developers. Our federal managers were pushing to replace a highly customized HR system with a 3rd party product. It was going to cost millions of dollars and take over a year. Our job was to help with the transition even though we built and maintained the original system. However, our contractor manager pushed for us to upgrade the existing system in house by hiring two additional surge developers. We ended up finishing the entire project in six months well under budget and exactly to spec with great feedback from the users. Funny thing about it is the federal managers took credit for the project even though they initially wanted to use a 3rd party system. Such is politics.

Re: A billion reasons never to buy IBM services

#183
post #27

Well, this news that came out last year is somewhat relevant. MD Anderson Cancer Center's IBM Watson project failed, with $62 million paid to IBM and PwC for essentially no results. However, I don't blame IBM, I blame people who dove in without clearly thinking it through. https://www.healthnewsreview.org/2017/02/md-anderson-cancer-...

We have all seen a project go wonky with requirements. However, I haven't heard of a successful product that IBM built/managed in the last decade. On the other hand, talking with friends in the government and government contracting, they argue that IBM and the major contractors have perfected the art of exploiting government into maximizing billable hours at the expense of results. It's a bit like the metaphorical ma…

IBM is likely the single largest government contractor in North America. Most governments at every level have contracted IBM for something, at some point. You don't hear about the successes because that's not news. That's just a government and contractor functioning as they should. Only large, expensive failures make the news.

Re: A billion reasons never to buy IBM services

#184
post #90
post #76

Historically Slovakia gets lumped with Eastern Europe in popular perception - Slovakia is nothing like Romania, the Ukraine, Albania or even Poland in turning out petty criminals or promiscuous online fraudsters. Not to forget Western Europe, France has a far more unhealthy work culture and fraud at work and as a way of living is far more acceptable than in Slovakia. Germany and Austria tend to value probity far more…

Thanks for calling this out. I think we should do more of it on HN (and everywhere else). People should try harder to decouple their biases from facts especially in their public writing.

https://www.thelocal.fr/20180314/what-drives-you-mad-about-w...

The work culture in France has been understood for a long time. I don't understand how you think it's bias, when you clearly have never worked there.

Re: A billion reasons never to buy IBM services

#185
post #79

Earlier quoted context omitted.

Another problem with governments is that they're made up of dozens or hundreds of different organisations, and they all make these mistakes on their own. Even if one organisation gets it right, other parts of the government don't benefit from that expertise. I think governments should have a special organisation that just maintains the expertise for handling these sort of big projects all across the government.

You’d think so but then you just have one more organization that doesn’t share anything with anyone else.

That organisation would have as its only job to make sure all other government organisations get this right. It should be able to work when that's their only responsibility.

Re: A billion reasons never to buy IBM services

#186
post #145
post #125

Earlier quoted context omitted.

> You write good RFPs and hold feet to the fire and they will deliver. That's the key bit though. Its not easy to write good RFPs. Unless done to an excruciating level of precision (which they very seldom are), you leave wiggle room which the vendor will naturally take advantage of when things get tough.

Not to mention government procurement processes do everything in their power to make it difficult to write a good RFP and the major players are highly skilled at responding to RFPs for the purpose of winning the bid, not necessarily to deliver on the RFP's requirements.

I've worked in government and commercial sectors. Big procurement organizations are a pain in any situation. Government adds some wackiness because of transparency and personal liability that procurement officers are living with.

But end of the day, if the people writing technical requirements have the time and know WTF they are talking about, it works. If you hire to write an RFP that responds to and evaluates, how could the result not be a shitshow? (Btw, that happened in a Fortune 500 org!)

Re: A billion reasons never to buy IBM services

#187
post #36

There's a dimension left out here on the Phoenix disaster: It wasn't really IBM's fault at all. The Canadian public service is really complex. There are multiple unions with multiple overlapping collective bargaining agreements, where the public service is allocated to different classes. These classes are paid specific rates, with retroactive pay being common for changing classes. The majority of the problems with Ph…

the problems with part #2 have been pretty extensively discussed and detailed already: https://news.ycombinator.com/item?id=16494387 my earlier post: https://news.ycombinator.com/item?id=16495431 basically, it's a political game... the same jobs they "lost" in miramichi because of the firearms registry legal change, they tried to get back. Same pork barrel politics that congressmen in the US play with trying to bring…

I missed that article two weeks ago, thanks for linking the discussion.

Re: A billion reasons never to buy IBM services

#188
post #95

Earlier quoted context omitted.

If you don't have an organization that can break it down to a smaller projects then there is a question if doing it as one large project has a higher or lower chance of failure.

Shouldn't that depend upon complexity of change but who cares. CIO have a short tenure so collecting the bonuses and leaving before house of card collapses works. It's all about managing the personal bonus and career, who cares for the success 9f project?

It depends on complexity, but I think it's more of a situation akin to refactoring or rewriting a complex code base. A total rewrite is always an attractive thought, but a real focus on continuous refactoring in smaller portion at a time is often lower risk, lower cost, and faster in the end - and I suspect it's the same with large bureaucratic processes too. It's also a way to sharpen the skills of the organization in small steps with lower risks for failure (and improving future project steps...).

Re: A billion reasons never to buy IBM services

#189
post #145
post #125

Earlier quoted context omitted.

> You write good RFPs and hold feet to the fire and they will deliver. That's the key bit though. Its not easy to write good RFPs. Unless done to an excruciating level of precision (which they very seldom are), you leave wiggle room which the vendor will naturally take advantage of when things get tough.

Not to mention government procurement processes do everything in their power to make it difficult to write a good RFP and the major players are highly skilled at responding to RFPs for the purpose of winning the bid, not necessarily to deliver on the RFP's requirements.

I've seen multiple government projects where the RFP's were actually written by the company eventually winning the bid - what a surprise...
Post reply on HN