Hertz paid Accenture $32M for a website that never went live (2019)
henricodolfing.com
henricodolfing.com
The IT consulting firm will tell you they have experience with literally everything. They’ll dig up a case study from one of their 400 offices somewhere, claiming to be experts on whatever the topic is. Meanwhile, in actuality, your project will be staffed with a team of 24 year old kids where this is their first assignment. And it doesn’t matter anyways, because the people who worked on the original case study are long gone and would never communicate with other offices even if still around.
Meanwhile at the big company, you’ll have the opposite problem. A team of people with decades of experience, but who don’t really know anything about anything other than how to make their corporate machine not fire them. They’ll think they know what they want, and will confidently tell you…but in actuality, these people have zero understanding of technology or even how their business runs. And who can blame them, they’ve spent a 30 year career not doing or risking anything specifically, so its hard to learn how anything works with no feedback loop.
It then becomes a delicate dance, can the consulting team learn how to do the thing they sold the client fast enough, before the client does their best to try to ruin the project out of sheer hubris and incompetence.
This case is famous for being one where the dance went so bad it became a meme.
I lasted not even 6 months working in professional services, really woke me up to what "prestigious careers" really are.
When I was at a consulting firm in London that I wont name, I was charging them 700GBP a day, and they were charging the end client 1500GBP a day (I saw this on an internal presentation slide I was not supposed to see)
If you go as a independent contractor, you can bill close to that rate yourself, but may find that you can't bill quite that rate as the mandatory middle vendors will take their obligatory cut, you need health insurance and your own expenses and any moment you're not working whether between contracts or vacation is lost money. Still makes sense for some people, less for others. Depends on your expertise, preferences, sales and networking skills, and how good is your accountant. Always better to build reputation and then become small consulting company yourself, billing billable rates and paying salary rates to others.
(This is in the world of consulting. Math may be different in world of independent freelance technical developers)
Client hires company A, who bill 2.5kGBP.
Company A outsources to Company B at ~1.5kGBP.
Company B outsources to Company C for 700GBP.
Consultant at Company C makes buggery fuck all, and has to unravel the mess of Chinese whispers/obfuscation to work out what the job actually is and who they are meant to be pretending to be that day, whose report template was being used, etc.
I was there for 5 years, and with the exception of one single project that lasted 1.5 months, all of my teams would leave the office no later than 6pm, and not once did I or anyone I ever worked with ever go back to the office later in the night. Once we gathered at the hotel bar after dinner with our laptops to practice a presentation we were giving the next day, but that's it.
It also wasn't difficult at all to develop a life outside of the company, even with the weekly travel. I spent a lot of time with coworkers, yes, but on most of my teams I genuinely enjoyed that time (and even long after leaving I am still close friends with many of them). We had hobbies together (would go to the gym together sometimes, explored different neighborhoods in town, played video games together, watched sports together, etc). If you're the type of person that thinks "work is only for work and therefor I can never be 'friends' with a coworker", then consulting isn't for you, but not everyone is like that.
The work-life balance and the general fun that I had were my favorite parts of consulting. I left because I found that every project I was on was inherently a "this company is full of incompetent morons and so they're hiring a bunch of mediocre consultants to come in and hold everyone's hand", and after several years it just got exhausting to always be the adult in the room.
It's just about what kind of clients you want to work with. If you pick any client that comes to your door and never say no then you'll end up in the race to the bottom with these large outsourcing corps.
Oh, and also, if you suck as a client, they're going to drop you and never answer your calls again.
The business never learn and if it wasn't for experienced DevOps managers intervening they'd still use sweatshop devs that barely speak English on their first gig.
https://mattstoller.substack.com/p/why-taxpayers-pay-mckinse...
And not for a cheap fee either!
http://www.newyorker.com/magazine/2002/07/22/the-talent-myth
A very wise investment (basically the Accenture partners needed to pay off the rest of the AA partnership to leave) in retrospect.
AA based on my impressions was the top of the big 6 accounting firms in size and reputation. Wow did they bite it hard in Enron. They probably all fled like rats to the rest of the former big 6, but all that hard earned reputation....
https://mattstoller.substack.com/p/why-taxpayers-pay-mckinse...
At this point in his career, 3 years after his PhD, he was unable to do anything except put on cufflinks and produce 120-slide Powerpoint presentations that went 30min overtime like he was working for the DoD.
It was an incredibly saddening sight. I talked to him about this and he was 100% convinced that he was doing his absolute top work by having pointless meeting after pointless meeting talking about nothing at all at great length.
The mindset of charging the maximum number of hours for minimal output is really hard to break out of. You can take the man out of McKinsey, but you can't take McKinsey out of the man.
It. Was. Insane.
"Let's sync this week for the pre-sprint Jira climbing"
(Hey, what are the worst bits of waterfall and agile? Let's combine them into our methodology!)
Now I know someone that do that for the software for subparts of nuclear reactors and it’s exactly all the same. The specs, the time to review, the politics of hierarchy, the time to fix a simple bug (can take 2 weeks for a simple if)… But at least the specs are in a software.
Now 2 weeks for a simple change in a if. Some changes can take months and the software is not just a few line of code so if you do the math you may start to have rust on your hardware even before the v1.0 is out. Also nobody is going to read this type of “doc” but another schema spec coder if that’s the name.
Plus, I could have used the compile, test, debug cycle to verify that what I was writing actually worked.
My specs were the same complexity as the code: Let's pretend, for example, there were no "sort" statement in the computer language. My spec couldn't just say, "sort the names in alphabetical order". My spec had to have the exact logic of a sort algorithm, but drawn as a flowchart (actually, not a flowchart but an AA proprietary format)
I didn't have to do "sort", but I did have to code algorithms that were more complex than that.
BTW, to make it more fun, there were rules about who was allowed to talk to whom. I was not allowed to talk to the programmer who had to retype my spec into actual code. I didn't even know who he/she was. And the programmer wasn't allowed to talk to me directly, but had to go up a chain.
And I don't think there was much that we as UAL employees could do. The fact that upper UAL management brought in AA to lead the project, to me, that means they were already dismissive of their in-house people and seduced by the outside people. Later in my career I experienced both sides of this a few times.
I only worked on the project 14 months. During that time the top AA partner in charge quit AA. Then the replacement quit AA, and maybe another. Maybe even they knew. I think a lot of people knew it was insane, but not able to change things as individuals.
https://dilbert.com/strip/2000-01-01?utm_source=dilbert.com/...
I don't think we have such a strong tech scene here or that many household names, to work in SaaS companies, though I've also just seen that quite a few EU job vacancies are for companies for whom software development is a supporting activity (sometimes very important, other times less so) as opposed to their main and only way of earning money.
Maybe I've just been looking in the wrong places, but I don't think almost any of my direct acquaintances work for SaaS/IaaS/PaaS vendors either.
I had never touched Java before, we did C at college, and became a Java developer after 3 days holed up with 10 other people doing coding challenges on a laptop.
I didn't get to go to any of the training centers until I'd been there for a year.
Eventually they did switch to C. I wonder what the curriculum is today.
I don't know why anyone would hire these consulting firms other than plausible deniability of blame.
I would imagine that most large corporations and government code is still Java, only specialist systems are still COBOL.
I'm floored that you mentioned this. One memory I often cite of my early days there was walking past a colleague's desk and seeing a diagonal line of text from the upper-left corner of her monitor to the lower-right. Closer inspection revealed that she was processing a 30-character part number with as many nested IF statements, instead of iterating through it.
Even as a 21-year-old I was appalled that this was being delivered to clients.
I still have to use Java from time to time, and I dislike the amount of "Spring magic" that colleagues try to use with it. No wonder the kids end up writing junk, they are used to never understanding what's going on anyway.
1998 - walking around you saw dozens of copies of "ASP for Dummies" on various desks.
I started at $21/hr, then found out later some other folks hired after me came in even a bit less ($19?! - but hey, you get 'benefits' too!). They'd hired a 'real' HR person right after hiring me, and they clamped down a bit more. My interview was one of the last ones where there was no HR screening, and I was just talking to the top dev/eng folks directly.
1) EXCESSIVE Timekeeping (I had to log every hour basically I was at work, felt like an inmate). Sure that is there business I get it. But it's not for me.
2) Many projects(Same-Same): I also learn that for my personality (and sanity) i work better if I can focus on one or two long term projects. Doing 5 little projects different days of the week, was horrible. To rephrase, dealing with 5 different clients a week was horrible, 7/10 times you basically just undid half the work you did previous week. Since you know, "requirements change" or it took them two weeks to let me know "oh it has to work like this not that, I thought you will know this" type convos.
Anywhoo programming can be wonderful or it can be awful !
I tried another agency job 2 years later and it was exactly the same. Changed again a year later, and the same story. Had enough experience to quit and go freelance at that point.
Never again.
Come over, we have Thinkpads, whiteboards and friday beer.
Because "delivering a usable product" wasn't incentivized (specifically the 'usable' part, or what usability even meant), it was simply a race to generate specs, report on them with glowing optimism, and then stick as close to the letter of the specs as possible.
At least, that's the theory of why the insurance marketplace failed so spectacularly.
Once you get to an organization of a certain size- private or public- the people with purchasing power are never the ones who need to use the service. As such, purchases are never made with the end users in mind. Instead, there'll be a list of checkboxes of things that sound nice, and if you're lucky, that list wasn't specially crafted to exclude everyone other than some Manager's buddy's business.
That sounds like a certain "mega moon rocket" that's been under construction for some time.
The consultant way.
Just had a consultant who literally got me to womp up a summary of everything going on (which was pre-existing analysis). They then added it to a PDF with some titles and a bit of fancy colour-shading, and BANG. £Xbillable hours and some expenses to boot. Honestly, the only "added value" they brought was to add on a cumulative growth percentage they obviously pulled out of their ...
Joke.
But I place the blame with the CEO, not the consultant. Consultants gonna "consult".
I've spent my career at startups and growth companies building and scaling engineering orgs. So I take it as a given that I could get a highly capable team but wonder how much it would matter. Would we still be weighed down by internal bureaucracy to the point of failure?
I suspect that might be the case.
If so it's hard to fault a CTO for outsourcing. If your company isn't built to support having a tech org then you might see these kinds of failures no matter what you do.
It's possible. But it's really hard work, very politically expensive, and extremely high risk. So, yeah, not surprising.
> Branded as a success
I fear you aren't cyncical enough.
Was it a filure? Did the company's balance sheet improve? Did the company's stock price increase? Did the spinout attract a load of investment for its (pre-destined) success and turn that into a rich revenue stream?
Markets -- for both debt and equity -- are mostly idiotic machines on short timeframes. Your ability to generate free cash flow puts a floor on your price. Others' imagination and available liquidity are the only ceilings.
Additionally, these types of spin outs can behave like generational wealth. They may be incompetent idiots, but who cares? Daddy's money is more than you can raise and mommy's rolodex is richer than you could possibly imagine.
You have dozens of people with competing interests some of who are actively working against you and the C suite doesn't know what is really going on our what to do because all the information they are receiving is intentionally being distorted by people trying to spin it so they can keep creeping up the ladder.
The biggest enemy of a large organization is almost always itself.
Software development requires placing millions of bytes exactly at right places to make billions of transitors sing and dance in precise sequence about billion times a second, every second. This is of complexity unlike anything humanity has ever encountered before.
I just want to point out that this isn't just legacy corps - I previously worked for a manager who went straight from a theory heavy CS degree to a theory heavy PhD to consultancy to management.
You still get companies like this where some middle manager with 0 years of SWE experience has to hire Software Engineers with 5+.
1) decision makers take on less career risk (we hired Accenture and they defrauded us is probably better than we tried to do it ourself and we screwed it up)
2) Larger organizations can’t staff up and build a capability quickly and efficiently in non-core competencies.
When I read "Agile Model" I could already see it, Accenture signing a Time & Materials contract, giving no shit about the badly detailed scope on the clients side (after all this means more hours), and some bad PMing on both sides. I bet the responsive detail was not clearly stated on the scope, Accenture noticed it but let it pass since it is T&M...
I'm an ex-Accenture (and also ex-IBM iX, that fixed Hertz site in the end) and to be fair this is not a widespread behavior on those companies, it really depends on who is the Senior leadership for those clients and areas are. I've seen some good and caring ones on both companies but I've also seem some terrible used car salesmen whose dominance in the higher executive levels (since they bring money) made me decide to switch from both.
Can they find a loophole in a document somewhere or a mistake in some email that they can use to claim what they sold the client is out of scope, you mean.
I'm not trying to claim moral superiority here or anything. Figuring out tricky ways to get the clueless rich to enthusiastically give up their money can probably be argued to be a moral good, provided the money isn't just going to some other even richer people. I'm just intellectually and emotionally unsuited to it.
Maybe I am just optimizing my employment the only way I know how, because I'm not suited to the more powerful ways.
Nothing against them as we all started somewhere. I respect the ambition but part of me feels a newly grad that has recently done a CKA, Az-400, Az-104 just isn't going to know the real world or compete with someone who has been around pre-cloud and witnessed the transition, or have enough hands on when things break very badly. They sure do know how to talk the talk however and make big company sound win some £££ contracts.
New devs/ops will never be able to appreciate pre cloud and how things are now, why they exist and what problems cloud has solved.
I guess when things get real messy they'll put one or two experienced staff onto the project still netting massive returns by billing by the hour in three figures.
On top of it they still want the software but they are not ready to pay the price for the software so they go for these con artist companies and in the end they have been milked 32M for a website that doesn't work.
#TRUESTORY
The amount of bureaucratic inefficiency in large businesses made me want to tear my hair out. Half the people I worked with knew absolutely nothing except how to protect their own jobs.
> Hertz claims that they were far from experts in these technologies and that Accenture was deceptive in their marketing claims.
Colour me surprised.
> Accenture also failed to test the software, Hertz claims, and when it did do tests "they were seriously inadequate, to the point of being misleading." It didn't do real-world testing, we're told, and it didn’t do error handling.
> Accenture’s developers also misrepresented the extent of their testing of the code by commenting out portions of the code, so the code appeared to be working.
> Despite having specifically requested that the consultants provide a style guide in an interactive and updateable format — rather than a PDF — Accenture kept providing the guide in PDF format only
So, like always, they sold a fantasy to a bunch of executives asleep at the wheel who lacked even the most basic technical skills needed to see that it was a fantasy, then farmed the work out to the cheapst developers possible and pocketed the difference.
At some point, someone with technical acumen took stock of the situation and said "this is garbage". Why does this step always come last?
WTF. "They said they were the best, but they lied!" I bet you as Hertz had some competent technical folks who could have vetted them. You either have them inhouse (but you've overlooked them for years) or you engage an inspector/reviewer to vet the claims or review previous work. I buy a car, I can get a private inspection done. I buy a house, I get a house inspector to verify the claims.
They very likely did (and negatively), but no excecutive ever wants to hear that, so they just barrel ahead anyway. Because what do those lowly peons know, right?
Then there’s always the risk that the internal Hertz guys are just terrible and just trying to keep the contractors out to make sure they aren’t exposed.
From the executive side it’s hard too.
I was fired from a project because I told an executive the wrong thing about how shitty a product was that I was trying to save after a contractor fucked it up, thus revealing the ruse of my boss.
> Then there’s always the risk that the internal Hertz guys are just terrible and just trying to keep the contractors out to make sure they aren’t exposed.
This was why I was hired there in the first place, so basically I was hired as the fall guy and then my boss executed on that plan.
> From the executive side it’s hard too.
I'm sure it was stressful, lucky for my boss he was able to successfully pass the buck and still works there to this day. I've also heard from customers of my current company that the company that "recylced" me is not doing well in my former bosses department, so perhaps he will not survive forever?
Either way: fuck useless execs.
Sometimes comes first but the outcome is the same regardless.
I was once brought in to sit on early discussions with a consulting group. I pointed out very real problems with their ideas about how to solve our problem. That was on the morning of day 1. I was explicitly uninvited before day 2 for "not being a team player."
3 years later we were in court suing this consulting group for millions.
Not true! They get multi-million dollar golden parachutes when they decide they're tired of playing business and would rather play golf.
I'll take an uncertain payoff as an entrepreneur or job as a developer over that - thanks for reminding me.
I ended up taking a tech job anyway but once I retire from this, I'll probably apply to an executive-asleep-at-the-wheel job.
If you want to blow a massive development budget AEM is a great choice; otherwise I'd advise you to pick a different content system.
This decision alone probably sunk multiple millions of dollars.
The platform license alone for their operating scale was probably a half million or a million. What you get with that license is... the world's most complex and difficult content management system, that you now have to develop your whole platform around. Since it's so difficult to learn and work with you basically need a full time AEM specialist team, which again blows your budget up potentially in the range of millions of dollars, and then continues to burn strong every time you need any kind of update.
My agency had a contract to make a site for an Amazon event. They specified that we had to use AEM, probably because Amazon uses AEM on some of their other properties, but it was not a good fit for quickly standing up a limited scope event site.
I work with Drupal and WordPress, but would not recommend them for user data or transactional data (although in my case, we bridge Drupal/WordPress with CiviCRM, and that works relatively well).
Also, I can't prove this, but I am highly suspicious that Adobe and their integrators cook up a lot of these deals and get service firms like Accenture to recommend their products for a kickback. I've been stared at by their sales team asking me to help sell their products and refused. Not ever offered anything under the table but I felt like I was getting winked at.
Just wait until your BigCo is buying stuff from the consultants/SIs and Adobe/SFDC/IBM/etc and they are all YOUR CLIENTS as well buying tons of services from your company in a totally different market.
"Balance of trade" is the term you'll soon learn about in deal negotiations :)
Instead of these heavy systems, my favorite has been https://www.sanity.io/ . Headless is the way to go, when your anyways building a custom frontend.
And closing that deal and having their reports implement the roll-out was milked for an entire quarters worth of performance metrics for that manager's brag-sheet.
It’s tailor made for this. Management will always sign off because they’ve heard of Adobe.
The boss doesn't know what content management even is, but they have heard of Photoshop and Acrobat so AEM must be good.
At least it's tolerable at all compared to the shitshow that is AEM.
just an example of the kind of companies that use it. apple, intel,etc .e.g https://jobs.apple.com/en-in/details/200207733/aem-engineer
I advised him to do AEM certifications. He did and then contract recruiters has started to flood him. He collects tons of cash as independent AEM consultant now. And with Java, he does "fulfilling" Java stuff on the side.
I was hired as a developer to work on the front-end of a very ambitious app for one of the biggest oil companies in the world. One year later we delivered a crappy single page app, a relational database and some data pipelines, and in exchange we billed them no less than 20 million.
I think I mentally checked out at 6 months in when I realized I couldn't fight against the current. Management was incompetent, half of my team mates had no experience or ability to work as software developers, and all the individual contributors were the ones with the pressure to deliver and work on weekends. Yeah, I'm not going to work extra hours because you don't know how to say no when the client tells you they want this extra feature and they also want to cut down the timeline.
The only reason these companies are successful is that the top execs are friends with the other execs at fortune 500 companies so they mostly figure out a way to spin it as a success so everyone gets their bonuses even if no value was created.
It's also usually that the big companies are so incompetent that paying 20 million dollars for nothing is still cheaper than hiring their own people to do it in house and ending up paying 40 million dollar for a team that will actually break stuff down and make everything worse.
It is so bizarre that blowing $20M on a large, complex project that obviously fails can be rebranded as success. Its harder to pull that off with smaller projects and less stakeholders, but if a project is big enough, you can obfuscate the details and make it look like a win.
An oil major probably makes $20MM in profit every few minutes or at most in an hour. (Apple makes ~1700.00 per second ..)
Another perspective on the 20M is the salaries and total running cost of an office of 1500 in Southeast Asia for ayear (or potentially Latin America, or Africa, but I'm less familiar with pricing there than in EA/SEA).
ExxonMobil made $23 billion in profit in 2021; that works out to just over three days and three hours to get to $20 million.
Shell made $20.6 billion in profit in 2021; it would take them even longer.
The other majors made even less.
A project which wastes over three days of profits is hugely expensive.
Their big name experts come in, tell you how you're doing it all wrong and they have the best solution around for only $X million and they can deliver in 12 months. Management nods, gives the greenlight, tells you to cooperate fully with them.
Their layers of consultants then tie up a ton of your time/resources over the next 12 months figuring out what they actually should be doing, and why what the Expert said only has a passing resemblence to what's actually needed. So there's then rounds of discussion on how this and that change will be a variance, all billable extras.
After the 12 months is up, nothing is delivered in a workable state, it gets rejected, sent back for changes. This is all more billable variances, because of course it was delivered to the approved spec, and if you squint, and really push the definitions of words then it might vaguely resemble what it is that the spec said.
I've seen this play out multiple times.
The only surprising thing here (to me) is that Hertz pulled the plug while their spend was only $32M. Well done Hertz.
I can only hope that someone learned their lesson to stop using consulting groups for this kind of thing. I won't be holding my breath on that one, though.
Regardless of what your project is.
Now whether they will or want to (the executives anyway) is a different question.
It’s much easier to tell your boss that the project failed despite the hundreds of developers working on it. Clearly nobody would have been able to do a good job of it.
The company would, but the relevant executive would be worse off. A $xx million consulting engagement failing is the consulting firm’s fault (politically speaking). Hiring and directing a $y million team that fails is the fault of the exec in charge.
Executives in large companies are frequently not the bumbling idiots they’re portrayed as - their decisions make perfect sense in terms of protecting and advancing influence within the company, which wins out over good execution in driving decisions.
hy is it so hard to consistently find qualified individuals? Do most other industries experience this same problem at the same scale?
Ideally it’s not Accenture’s battalions of scrubs, but it’s not like the problem is just gone.
If things go wrong, you get to blame the outside company for screwing it up.
Setup a team internally and your neck is on the line if they fail to deliver.
Then, you need people to manage the computers — but now you need twice the number of people to do that than you think you would.
You need to ship computers, recycle computers, ...
The economy isn't zero-sum: I think the nonpeople economy is only limited by our ability to run companies, and there's no limit ti the wealth of a company? Maybe? I dunno...
[]https://en.wikipedia.org/wiki/List_of_countries_by_governmen...
edit: how many discontinued google products are there? They're got to be worth tens of billions in developer costs and perhaps more in opportunity costs.
It's about comparing global economies in terms of actual, physical production output instead of GDP numbers that include nonsense like the big "service" companies. Results are unsurprising.
I am an Indian (though I only worked for a year in IT before leaving for actual work), and let me tell you, we Indian IT developers are a complex bunch.
3 out of 100 know the actual work, actual technology, impact of choices, etc. 80 out of 100 just get by, as in, do the bare minimum required to get by the day and the task assigned to them. The remaining are bootlickers who get promoted to management.
And there are no qualms about ethics. Want to pass a test by commenting some code? "we will do it once to check first, then we will repeat it without commenting" (and the latter will never happen). I would not be surprised if they have a "test" set of code, solely to pass the specs and an internal "actual" code that will be delivered to the customer.
Also, after 20 years or so of outsourcing, I am sure most of my fellows in MNC IT companies have set up practices and navigation rules to deftly distribute the blame such that even senior management is clueless about whom to punish in case of a failure like this.
Any proof of that statement? Or are you one of those people who believes in the invisible hand of providence the way religious people believe in God?
Hey, remember back in the good old days of cotton plantations, when the African slaves were well compensated for their extreme talent in picking cotton under inhuman conditions? They were obviously receiving higher compensation than whites, who would have died under the same conditions.
Man, that good ol' magic of the market huh? Never fails.
I mean, if you pay 32million for a website, it's obviously going to be good, right? Or at least, it'll go live, right?
sorry if that was a bit mean, but honestly you seem to be naively believing in something that does not actually exist, and then assuming people who are unlucky are in fact untalented <3
Except that there are concrete proofs of God.
It’s inherent fact of the reality we live in. People like money and higher compensation.
”Hey, remember back in the good old days of cotton plantations, when the African sl…”
Slavery is opposite of free market. I don’t know why you bring up such an bad example.
I figure most of these big companies (including the one I worked at) burn millions each year or efforts that never get shipped. I would say that a lot of times the projects weren’t necessarily intended to make a dent in anything, but just to keep teams busy and justify headcount.
Then I changed to consulting (midsize company, 75-300 people) and it was a breath of fresh air when there actually was a paying customer that wants a working product and will publish it. I really think we did honest, good quality work.
Hertz is even suing Accenture to recoup the development cost, but it seems they are missing the bigger problem, which is that their aging digital presence has probably harmed their ability to acquire or retain customers to a bigger extent than the lost cost of development...
Never had any problem renting cars online from hertz, unsure what the problem is.
Since renting apparently works fine, the backend APIs seems to be working.
A page redesign? I can not care less what the page looked like as long as I can find the rent botton.
Just a few weeks ago, I showed up at a Hertz location to pick up a car rental I had already paid for. They refused to give me the car saying that they didn't have some kind of required booking number in their system and that I would have to pay a second time to get the car. I showed them the withdrawal from my bank account, and the email receipt that Hertz had sent me saying that I had paid. They had all of my information in their system and the car was ready to go, they just insisted that I needed to pay again because their system did not have some number that they required. I spent 3 hour on hold with their customer support phone number, and they were unable to help. I eventually told them to go f themselves, disputed the charge on my credit card, and rented a car from the booth next to them at the airport. Hertz is a completely incompetent company, and that's before getting into the horror stories of returned rentals that they've reported as stolen, landing people in jail for the crime of renting a car from Hertz and returning it on time. I will never do business with Hertz (or Thrifty, which is also Hertz) again.
They can do good work for some things, like regulation, audit, tax, etc -- there's a decent chance that whoever wrote the regulation you have to comply with works for one of the big4, which is quite advantageous.
However, for a technical project, complete boondoggle.
There's also the "Big 3" or "MBB" which refers to the big 3 prestigious strategy consulting firms, Mckinsey, Bain, and BCG.
And then on the other end of the spectrum there's "WITCH" which is the consulting firms generally known as "body shops" that hire for quantity over quality. That's companies like Wipro, Infosys, TCS, Cognizant.
Accenture usually isn't included in any of the acronyms, it's just kinda an outlier despite how big it is. It's very much the same as how technically Microsoft isn't part of "FAANG", but whenever someone does say "FAANG" they typically just mean "the big tech companies" and you subconsciously think of MS as included in that.
> FAANG
I always hated that acronym, mainly because it classifies Netflix under the same umbrella as Microsoft (while I'll acknowledge that they're tech-savvy, Netflix has been (and still is) mainly a media company).
The story described in this article just sounds so classic. I'm consistently surprised that more consultants don't get sued.
Mind you, this was over ten years ago.
Maybe TCS outbid them on the low end and they're pivoting back to inshore
Those companies who thought IT was an annoying cost with nerdy ugly employees rather than the core efficiency driver of their business then became utterly dependent on Accenture and at best could swap them for either equivalent junk from IBM or Deloitte or went further down the toilet with TCS.
What's notable is the lawsuit, Accenture will usually eat money for a failed project in hopes of keeping Future project jectd and general reputation.
Hertz must be terminating the overall relationship.
https://www.statesmanjournal.com/story/news/politics/2016/09...
The manager I worked under was absolutely complicit in this process of ripping off the customer. And while he was one of the worst managers I’ve ever worked with, he was very good at his main job, which - as I came to understand - was to get a job at Accenture.
Are you sure? It's not a name that inspires confidence.
> I was hired by Hertz to integrate and optimize technology infrastructure following the acquisition of Dollar/Thrifty car brands into Hertz Global Holdings. Reported to the CEO and led a team of 1,200 professionals in eCommerce delivery, customer digital experience, digital business processes and communications, information security, IT operations and delivery, and new digital ventures. Consolidated car rental systems, transitioning from legacy mainframe to the Cloud and rebuilding the fleet reservation and accounting system to streamline all aspects of the customer lifecycle. Aligned digital initiatives (IoT, AI, CRM, Big Data, Mobile) into the strategic business planning process.
> My Achievements Include:
> § Drove technology integration of the multi-billion dollar acquisition of Dollar/Thrifty car brands. Transitioned Mainframe/Cobol to Cloud/Microservices to support the new technology infrastructure utilizing an agile development cycle.
> § Reduced technology spend by 20% and enhanced customer service and product offerings through a complete system project redesign (CRM, Fleet, Rental, Reservation, Data Warehouse).
> § Improved marketing and revenue segmentation by optimizing technology to more effectively align brand/service offerings to Corporate vs. Leisure consumers.
> § Realized a 35% increase in website visits and 12% growth in conversion rates by spearheading redesign and modernization of the e-commerce platform utilizing microservices technology and AWS Cloud environment.
Veteran CIO provides his team with accountability, board exposure, and continual feedback to turn them into tomorrow’s IT leaders.
These all look like your typical resume inflating BS.
Reminds me of the Silicon Valley series satire from Mike Judge.
He hasn't heard about gradient descent, not by name, not by maths. He was quite impressed when I described it to him, in fact.
If it didn't happen to me, and i still have written records, i wouldn't believe it today.
Like, I could write these exact same things, and they’d be true, except I’d have to scale the number of employees down to 15… and change a few instances of car.
The cheapest people possible.
Then again, Accenture shows they can be a nightmare too.
Imagine the position of the CTO if the project went to a smaller sized, not so well known, consulting firm, and it failed. The CTO would be responsible for the failure.
But with firms like Accenture, it would be the firms fault as they "are the experts".
Sadly, IT knowledge is low enough in the general population that this shifting of blame will be the norm for the foreseeable future.
If you're Hertz, your website is central to what you do, it's how most people will rent a car. It's something you should do in-house.
I used to read https://thedailywtf.com/ and it was full of stories of consultancy project that failed in the most horrible and insane ways.
So, she asked me if I could spare a few hours to sit with her and get her up to speed on electricity regulation and policy so that she would "know all about it" for the kickoff meeting in two days time...
'30 rental processing systems' interesting opportunity. the airbnb / squarespace rental ecosystem has a bunch of standards for syncing bookings, but I think they mostly amount to exchanging ical files. would be neat to develop a modern open protocol for inventory + then develop a hosting business around it -- applications in cars, retail (like that 'pointy' company google bought), sharing economy
like IBM is doing this now, zero chance their system is usable https://www.ibm.com/docs/en/inventory-visibility?topic=data-...
or this mckinsey whitepaper that's clearly not a thing you can use without a bespoke contract https://www.mckinsey.com/~/media/McKinsey/Industries/Retail/...
We were supposed to get all this with the promise of SOA, SOAP, data routers etc, but that never really happened outside of the enterprise.
Funny enough, when Hertz brought DTAG (Dollar / Thrifty) they might have purchased part ownership of a software Company called BlueBird Systems which developed a modern front end system built on Progress, which was light years ahead of Hertz internal nonsense at the time according to people I spoke with.
The car rental software world was a weird and wonderful place. They even had their own operating systems called SuperDos once upon a time specifically built to run dumb terminals throught multi-mux's over phone lines. When Enterprise innovated and used satellites to connect their locations together, the industry thought they were mad. Turns out their ability to do real time yeild management of their fleets was a game changer and enabled them to grow at an astounding pace and unseated Hertz very quickly.
The entire industry is filled with crazy consolidation, public / private takeovers and companies thinking their way is the better way to do it. Astounding levels of tech debt, hubris, money and larger than life personalities. A near perfect ecosystem for consultant grift.
Why, oh why, doesn't high-end project management training include case studies of mission-critical systems in large long-lived organizations? Large === hundreds of thousands of people affected. Long-lived === centuries. I'm thinking of, for example, the signaling systems in the New York City subways. You get the idea.
You can't just delete and replace a big system like that like you can a malfunctioning virtual machine at a cloud provider. You have to work with what you have. And, a decade out, you'll still have to work with what you had back then, just less of it.
Any gang of $200/hr fresh-out-of-school devs can do a greenfield system. But maintenance is hard. Upgrading existing business processes without disrupting the business is hard.
In health care, EPIC seems be able (mostly) to do that. Peoplesoft. We don't hear from the govt much, but Social Security seems to be doing it.
What track record of successful business process upgrades do the big-four contractors have? That would be the question to ask.
Even the so called success stories seem ... mediocre at best.
Has anyone been part of such a project at a firm like that?
It's been developed for almost 10 years now, by a relatively large consulting firm.
But I believe a large part of the success comes down to the following:
- The core dev. team is still mostly the same. When you think about it, 8-10 years is pretty much an eternity in the world of software development, so it's pretty incredible that they've managed to retain so many members.
- Development cycles are very fast, and communication between end-user (us) and the product manager is very good. There's very little red-tape or committees between us.
With that said - even though the product is quite extensive, the number of users is quite small, only around 500 active. And they are all gov. workers, though in different departments.
On the other hand, I've also seen some dogshit products in the wild. Usually in the scale has been much, much larger - and the budgets, too.
Observations from those have been pretty much the inverse of the one I mentioned above. Huge, huge teams - always new people. Insane turnover. Getting new features takes years, and everything goes through multiple levels of bureaucracy. By the time something has been implemented, interest has changed.
I've been part of a handful of these projects. You have to understand that these types of projects are, from the start, never intended to be smashing successes. Nobody says "everything is going great and we have a ton of smart, capable people working here, we should also hire some consultants". No, once your company or project is at the phase where you're hiring consultants, 9 times out of 10 its because shit has hit the fan and you need someone to pull you out of the mud, and quick. Consulting engagements are almost always band-aid fixes just trying to achieve a level of mediocrity.
And as much as people shit on the "24 year olds who don't know anything", the sad truth is that 24 year olds (aka people with 2-3 years experience in consulting that are now on their 8th project doing this exact same type of implementation) may not have much experience, but they still are probably more productive than the vast majority of knuckle dragging drones that work in corporate america. When I was one of those 24 year old consultants, most of my projects were roles where I was supporting "IT admins" who literally had trouble remembering how to open Excel. The people that these consultants are meant to supplement aren't your "average HN commenter", they're not even "average redditor". They're "average facebook poster".
I talked once with an airline who had outsourced their entire dev and dev management to some foreign companies; they wanted to hire a mobile dev to go to where the team was and try to figure out why nothing was getting done, as they had no in house knowledge about mobile at all. I said hell no. Nothing ever shipped that I saw and I think they gave up and went back to in house again eventually. Just because you are a big company doesn't mean you have a clue.
We lost the sale because we told TELCO honestly that we could deliver what they wanted in the budget they had set. So TELCO went with the consulting company.
18 months later the consulting company came to us and offered to give us a subcontract to complete the project, within the scope we had originally offered to TELCO, for the same amount we had offered TELCO! We were stunned and could not understand how this could possibly make any sense economically. We had a meeting with the consulting company and took a look at the project status. It was a colossal pile of shit. Nevertheless, the consulting company promised that we would only be responsible for the scope they had laid out, which we were very comfortable delivering.
We were about to sign a contract to do so, and one of our advisors said we should flip the desks, run out of the negotiation, under no circumstances sign the contract, and for good measure close the offices for a month and not answer any phone calls or emails from the consulting company.
According to him getting involved in that project was in the very best case scenario going to destroy our morale and therefore destroy our team. And in the worst case would enmesh us in litigation and ruin all of our careers.
We thought hard about it, because we needed the money, but ultimately we didn't sign the contract.
Years later I met someone who worked for the consulting company and they told me that the project was an internal meme for a colossal disaster and shitshow. Apparently several consultants had nervous breakdowns over it. And one partner left the company. Meanwhile the project never saw light at TELCO.
My general impression was that my role was actually "budget filler".
Saved up for a laptop and a driving course, so can't complain.
Once there was an enormous tanker truck fire under an overpass in the Bay Area on a major freeway. A section of the overpass collapsed.
The state asked for bids, but the contract had an interesting feature: substantial sums would be paid for each calendar day the work was completed ahead of schedule.
One contractor underbid everyone by a substantial margin, and got to work 24-7.
Wikipedia:
A contractor with a proven track record of rebuilding damaged freeways (most notably the Santa Monica Freeway after the 1994 Northridge earthquake) well ahead of schedule, C. C. Myers, Inc., submitted a winning bid of $876,075 to repair the damage to the I-580 connector. The bid was estimated to cover only one-third of the cost of the work, but the firm counted on making up the shortfall with an incentive of $200,000 per day if the work was completed before June 27, 2007.
On the evening of Thursday, May 24, the I-580 connector re-opened, just before the busy Memorial Day weekend. The deadline to finish the project was beaten by over a month, with the contractor earning the $5 million bonus for early completion. The entire reconstruction project was completed only 26 days after the original accident.
This is a case where this was "gamed" by Accenture and Hertz was just clueless, but it can happen the other way around. (Unreasonable) outcome based, and the contracting firm gets stuck with an impossible, money-losing project. Or some unexpected thing happens and same result.
There's a reason why billable hours is a thing.
It doesn't matter if their private, local, state, or federal government, charity, or whatever - the larger the organisation, the less efficient, and more failed projects there will be.
My personal opinion is that this is caused by a combination of communication overhead, politics, and larger organisations giving more places for useless / lazy people to hide.
Here's what I'd choose as someone who hasn't done something like this in his 25 year career: Some front-end framework (is React still relevant?), Java/SpringBoot, Kubernetes/KNative, some mesh, some back-end mainframe integration with their legacy systems...
Mulesoft, personally hate it - but it's definitely an option if you're trying to abstract out a whole bunch of legacy systems into clean APIs. Personally, I'd probably create some lightweight integration components in custom code (whatever language you like) deployed in containers on some scalable cloud platform over buying a chunk of enterprise middleware and trying to find the skilled resource to configure it. But, I don't think Mulesoft was a death knell here - merely a bit of a money pit. Same thing for AEM.
Overall, it doesn't look like they were choosing unreasonable tools to do the various things they wanted. e.g. they weren't trying to use Salesforce as a transactional database platform.
You could definitely pick a better stack, largely from open source, and deploy to the hyper-scale cloud provider of your choice - but I don't think the tech stack that's what screwed this project up overall.
- Monolithic Haskell web application.
- Very little JavaScript.
- Small team of people who know what they're doing.
- A couple of servers.
- Postgres and Redis.
With the remaining $31,500,000, I would buy weapons for Ukraine.
I've literally witnessed teams where a single contractor out-performed a team of twenty people by a factor of 10 because they were reasonably competent. I guess this is where the myth of the 10x programmer comes from!
The very unfortunate thing is most of my ex-colleagues have climbed the ladder to a point with no perceived way down or up. They think they are “managers” and believe they are equivalent to one in tech, but no tech company wants some 7+ year tenure Accenture “manager” managing their engineering teams when all they’ve done is sent out product specs to an offshore team. Even if that offshore team is awful, they’re still doing the hard work of architecting and creating the code. The onshore “manager” is just a face for the team.
Some are genuinely good at their job, but they’ll need to transition to non-tech F500 companies to do anything with a similar prestige to what they’re doing now.
I mean, if you don't get fired, make a nice salary, and you don't care about actually doing interesting work with technology, then I suppose it's not that bad.
If you try to change jobs, especially if you decide you wanted to actually learn real tech, it's a real burden.
I remember while the proposal evaluation process was happening, Accenture sent their proposed PM to the town where the agency was based and he literally bought a house there to show Accenture's commitment to the agency. Of course he sold it after the project was awarded.
Accenture was awarded the contract, who then came to us and hired our company as a subcontractor to actually do most of the development work with the exception of the project management and two other devs. So the agency paid millions of dollars to get Accenture but in the end still got us essentially. Nice use of taxpayer dollars there.
On the plus side, since Accenture was so tight with Microsoft at the time, Microsoft got Accenture to agree to use .NET for that project which wasn't even publicly available yet..let alone complete. It would look good for Microsoft to show that a state agency had adopted .NET and they had planned to do a case study on the project. So we got to use .NET before many other developers. There was 0 documentation, so that was fun, but we got access to the actual MS devs working on the nuts and bolts of .NET. Fun times.
Accenture sucks.
Full Time Employee is a funny institution in many countries. Leave a comment below if you had ever (or regularly) been asked to report 8 hours a day on a time sheet even if you actually worked 4.
You have to find different project codes to make it “look right”. If you feel bad and bring up to your manager that you have some downtime, it becomes their problem and they have to find you more work but then you might be overloaded other times. So most people don’t rock the boat, why bother?
So around the country, most FTE jobs in large corporations are like this. People sitting around the watercooler or in meetings, getting lunch and doing one or two things per day. Government employees, too.
With the rise of automation, we’ll have even more productivity. Hopefully with UBI people can start being more honest and work 20 hour workweeks, and spend the rest of the time with their family or pursuing hobbies.
7 million dollars for requirements gathering?
Hertz should have known better. I'd pay just to see these contracts for entertainment value.
Trying to coordinate between 10+ managers of varying seniority (in a legacy company who's struggling with tech) and prevent scope creep at the same time is an absolute nightmare scenario.
I'd hate to be the Business Analyst in charge of that.
That's a whole team of business analysts to create so many spreadsheets.
if your billion dollar business relies on the web site working well, you wouldn't think of trusting it to a small freelancer that quotes you 50k or whatever, it's almost like they start with a budget in mind (7 digits ought to do it) and then find someone who will take that much money
disclaimer: I have no experience here but I think this lecture on pricing design touches on it, that big corps aren't going to touch you if you're not charging them outrageous fees
This level of spending and failure reeks of severe levels of incompetence, negligence, and stupidity. They probably have layers of management covering each other's asses. And now they are forking cash over to lawyers as well. Maybe the lawyers do better than the consultant, but either way, they'll get payed a lot. They'll squeeze them hard probably. Easier to point fingers at Accenture than to admit management and leadership was asleep at the wheel for years.
Of course, Accenture probably dropped the ball here as well. But what are they going to do when faced with a customer this dumb asking for all sorts of things and probably constantly moving the goal posts? Say no? Of course not.
So, they did the obvious thing: pick expensive enterprise solutions and dangle nice sounding buzzwords in front of the customer. Tell them what they want to hear basically. And then pick some boring/conservative technologies and go to work. Angular was still reasonably fashionable around the time and 25 year old "senior" Javascript "specialists" are a dime a dozen. So it's not surprising that that became a thing. And we're all so agile these days that you wouldn't believe it. Standard sales pitch and practice for the last 2 decades.
The reality is of course that Hertz signed up for classic waterfall complete with blueprints and everything and Accenture was smart enough to not go fixed rate here. Better still, Accenture was smart enough to realize that IBM, Oracle, and others also were in on the action so they did not take responsibility for any of that; only for their part. Classic recipe for lots of scope creep and budget overruns. Which of course happened and was probably encouraged to happen.
That CIO looks like he knew what he was doing. Big spending, fat pay check, and be gone and take the package when the shit hits the fan.
With a small budget you are forced to find or assemble a small skilled team. With a big budget you end up funding a bureaucracy of middle managers and a big unskilled team.
https://www.google.com/search?client=firefox-b-d&q=canada+go...
Made my media buying strategy that much more difficult. To question the scheme was verboten, view=intent was sacrosanct.
In the early to mid-00s, a popular scripting language called ActionScript (sister of ECMAScript) powers Flash. A large Outsourcing company contacted me to ramp up a development team for a high triple-digit thousand dollars project. They had bought/inherited a code library, one of the most beautifully written codebases -- Object Oriented Java-Styled code with well-documented comments. I emailed the original programmer (part of the same forum group, I think), and he replied that if I need help, he is there.
The company was trying to set up a team to start with the code and build an entire application. When asked, why not just talk to the original author of the code, and he will do it easily instead of struggling for many months. It will take ages for the team to understand how things are written and why.
Well, the idea is all about cost and margins. They seriously don't care how good or even if the project completes. Their only motive was the number of hours and code volume (number of lines). They even factored in attrition from the team and the replacement cost in money and time.
So, the original programmer cost them $100 /hr (a good amount during that time), so the company spent a set budget to get just the needed framework. Then, they got a trainer (me) at about $20 /hr, which was costly (but had to) at that time (and geographic location). Finally, they cut and save by training those "engineers" who thought they could write ActionScript by clicking on the timeline on Flash.
There are excellent Services/Consulting companies and even brilliant teams inside these big companies. However, most people are just optimizing on volume and billable hours and have no care in the world about pride, dignity, or what the final product will be.
Individual consultants can be okay. Consulting firms tend to be complete trash and make a living off the technically ignorant. Seems to be worse in web than other areas.
It's the old "nobody ever get fired for buying IBM". It is easy to justify this kind of outsourcing decision, these are multi-billion dollar companies and they must be that successful for a reason. Right? Whereas if you do something in house and it goes titsup, then the first question will be "why didn't you get an experienced consultancy to do it?"
So my question is how do we influence senior management away from the mentality of employing consultants as they default decision and instead look at all the options fairly.
90% of the functionality they claimed to support did not work. It was way way harder to use than anything else I've seen.
--
Going into consulting: I will never go back. The problem is that all of the good devs leave once they realize the clients are assholes and are in complete control. Then you are left with people who are ambivalent to what they are making, or too bad at their job to make it anywhere else.
I've never experienced such micromanagement, rudeness, sabotage, and meanness in my entire life. And it doesn't even pay that well!
The only thing I'm wondering is how companies can be so naive thinking they get experts with multiple YoE from Accenture.
That right there is a warning sign. It may make sense to outsource legacy systems after their replacement is ready; it makes no sense to outsource them before it has even been started.
I just don’t understand it. Im not trying to be sarcastic. I’ve been scratching my head trying to understand this since I created my own consulting firm years ago.
Please, sincerely, explain it to me.
As mainframes moved from the white glove ivory tower to more access for programmers, then to minicomputers, then especially in the microcomputer revolution of the 1990s, Arthur Andersen was well connected to sell IT and development services to a very very large range of clients. This wing was "Andersen Consulting".
Andersen Consulting's partners got tired of taking all these sweet revenues and shoveling them to the tax partners of Arthur Andersen, so they split off in 1998 or 1997 or so, and became Accenture.
Also around this time, Accenture signed many deals to outsource entire IT departments to them. Stupid companies not seeing IT as one of the primary efficiency and market advantages (see:Amazon) but instead as an annoying cost center jumped at the chance. This made them beholden to Accenture.
Anyway, Accenture had the salespeople and contacts, the size, and the reputation of being able to deliver large projects, or they'd stick them out. Would they be great? No. But they'd stick it out.
All the big 6: CoopersLybrand, Ernst and Young, Deloitte, Price Waterhouse, KPMG, were all in on it at this point. But Accenture had the largest partner-to-workerbee ratio, so they raked in the cash. Accenture had the ability to hire armies of workers, rarely from computer science backgrounds, crash course them in programming over 6 weeks, and then shuttle them off to be vastly overpriced consultants. They even had their own private college for this (St. Charles).
Basically, they had contacts and a good enough pipeline to create worker bee programmers for large projects.
The partners generally came up the ranks so they could speak the IT lingo, and they were promoted/selected based on ability to produce revenue and sales. With the huge size and contacts and labor pool, plus happily jumping into any and all software implementation.
Accenture and their ilk were also key for supplying huge numbers of people for SAP and other package implementations. Basically, these software companies couldn't muster the armies of implementers necessary to install and customize their software. Accenture and their ilk could. These ERP packages likely helped fuel the productivity boom (all of it went to the rich) of the Clinton era as computers went from 10s of MHz to gigahertz processers as well as memory and storage increases and the internet boomed.
You probably can't imagine an executive management team that is ignorant of IT and IT practices, and of course the old enterprises have plenty of these. These execs just wanted to hand off these annoying things to someone, and Accenture was there for them.
Modern executives need to be IT-aware. I'd say this is only very very very recent, with the rise of Amazon. Before then you'd have the CEO that proudly annouced they don't even know how to use Email.
Those CEOs are a dying breed. Your orgs will live and die by navigating the IT landscape. Amazon sucks for many reasons, but they do a lot right, and one of those things is "don't use consultants, build it in-house".
As someone who focuses on being effective and efficient, this hurts my soul.
I guess I have to admit they provide some value, but capture 99% for themselves?
Makes me wonder if they’re actually destroying value overall?
Outsourcing? Did it provide value? Maybe immediately on the books, enough to cook to hit the stock options and cash out.
Could companies have built internally? In an ideal world that's definitely a yes. Amazon sucks in so many ways, but one thing they don't is the fundamental value they place on their IT systems and workers.
Old school companies could not handle that culturally. Ugly nerds? Paid more than managers would be several levels up? Treat them respect? Structure the business around them? They couldn't handle it.
Accenture had the organizational gravitas with the execs. Through that came the temporary infusion of valued IT change. Were they vastly overpaying? Yeah. But that price tag meant they needed to take the implemented system seriously.
Ultimately Accenture kept showing up and selling services somehow, despite many many many other options. Should there be a kick-ass IT consultancy that competes with them and embarrasses them? Probably, but ... where are they? If Accenture was charging 250/hr for 50/hr talent, why didn't some leaner org at 150/hr with 100/hr talent (a fundamentally different tier of worker) vastly outperform them?
Well, the world is run by the rich, and they only respect the rich. It might be as cynical as they respect how Accenture rips off its workers and still delivers acceptable product, exactly like the execs in the companies like their companies to be run: extracting maximum value from the plebe workers.
Marketing and connections are so so powerful. As stated elsewhere, Accenture is generally a "safe" choice for an "important" project. And don't forget those "approved vendors" rigamarole that companies have. Because Accenture and their ilk extract so much excess from clients and labor, they can buffer the failure scenarios and throw more labor at the problem.
In large companies where budgets are abstract in relation to value, more that budgets align with how much power and influence a subsection of the org has, cost can become secondary.
And sweet jesus would I like to know how much kickbacks and the like exist in IT procurement. It must be extensive, based on the mystifying decisions I've seen in my career.
Reading the linked article all I could think was: Hertz doesn’t deserve to exist. It just seems like they’re a Frankenstein of 30 years of mediocre to poor decisions.
Ultimately I think a lot of companies that use Accenture don’t deserve to exist, and ultimately will be outcompeted.
In the US, most "markets" are largely dominated by monopoly, duopoly, or cartel conditions, and thus rent extraction. Combined with the efficacy and returns of lobbying congress for market barriers and subsidies, most companies are entrenched.
There are so many reforms needed in the US, but breaking up monopolies, or just stopping mergers, would be task #1. Price, creativity, options, innovation, worker empowerment, amount of employment, wages, all improve with more companies, more options, and more competition.
2) airport counter real estate or the real estate at the "car rental satellite facility" is probably hard to get
3) fleet sale discounting with the car companies
But #1 is probably the main one.
Car rentals are actually decent in competition, although there may have been a merger flurry at some point.
Yup, Enterprise, Avis, and Hertz own them all.
It would probably take self-driving so an off-airport lot could dispatch self-driving cars to someone.
Customer service at car rentals is awful, it always seems to take an hour to get a dumb piece of paper and someone that says "go to this spot"
Disclaimer: not an industry expert, but all I see is three companies with the market share and no one new in probably 40 years, awful IT and customer service, and companies mistakenly calling the cops on their own customers for not-stolen cars.
Extremely poor customer experience across the board sounds ripe for disruption. Companies just don’t understand how vulnerable this makes them. There’s absolutely no loyalty or connection built with a bad customer experience.
A few years from now there will be a startup that shows us a better way and we’ll have a hard time understanding why we put up with crappy customer experience and mediocrity for so long.
Once a company reaches a sufficient size, they need someone like Accenture, its really as simple as that. Every FAANG or F500, really none of them do it themselves. Why would they do use any of their own expensive engineers on their back-end systems. The value is in outsourcing to someone with economies of scale for several months instead of hiring FTEs or reallocating existing staff for an x month project every 5 years.
> A spokesperson for Accenture tells The Register...
I sat near the consultants, and they would just spend all day working on projects for other clients.
if there's a lesson, i'm pretty sure it's "if you choose to outsource something because it's sufficiently special that you don't feel comfortable doing it, make sure you outsource it to someone who specializes in what you need done."
Could not find what's the latest status of this case. Anyone?
The main stakeholder was always busy and in meetings, so I would mostly clock-in and clock-out after having waited outside the meeting room for hours while coding on what we had agreed upon on a very hurried 15 minute meeting months ago.
After 6 months of not having meetings, and having no access to any data, specifications, or feedback, the end result was a glorified Lorem Ipsum placeholder of a forum with a chat applet on the sidebar that I'm relieved didn't ever go live.
Apparently my experience at the State of Colorado and Accenture wasn't an anomaly.
I worked for Andersen, Price Waterhouse, and a couple smaller firms after that. The stuff I saw induced anxiety in me on behalf of the client. If you actually showed initiative and did your job too thoroughly, they had no idea what to do with your work product.