Thread regarding Open Text Corp. layoffs

Opentext needs to stop with the regulated environments

OpenText has spent almost 10 years building and running our FedRAMP environment. In my estimation, we must have spent at least $30–45 million on this entire exercise. And how much revenue have we generated? I will be very surprised if it is even $2 million in total. That also with our usual margins of around 30–32%.

Now you tell me, in which universe does this make any business sense?

But apparently, our great leadership looked at this fantastic financial performance and decided, why stop here? Let us take this same wonderful business model and expand it further! So we went ahead with IRAP in Australia and Protected B in Canada.

What a brilliant idea, no? If one environment is losing money, let us build two more. Surely three loss-making initiatives will somehow become profitable. Excellent strategy, sir. Absolutely outstanding.

And just when you think, okay, surely by now we must have learnt something, along comes Steven L and convinces our executive leadership that sovereign compute is the next big thing.

So once again, we are spending huge amounts of money, adding infrastructure, complexity, operational overhead and ongoing costs. Revenue? Profitability? Return on investment? Arre, why worry about such small things when we can put together a beautiful PowerPoint presentation about our strategic vision?

Now some of you may be thinking, why should I care? This is management's problem, no?

Unfortunately, no. It is very much our problem.

Because when these wonderful strategic decisions fail to deliver, who suffers? Certainly not the people who approved them.

Management has only one solution left. Cut people. Cut budgets. Stop hiring. And then tell the remaining employees that they must somehow manage everything.

Earlier, the magic word was efficiency. We were told to do more with less. Now the magic word is AI. Suddenly, AI is supposed to solve every problem, eliminate every inefficiency and allow five people to do the work of twenty.

Boss, please. At least give us some credit. We are not fools.

Call it efficiency, transformation, optimisation, AI or whatever fancy terminology is fashionable this quarter. The reality is the same. Management makes poor investment decisions, burns through millions, and then expects ordinary employees to compensate for those mistakes by working harder with fewer resources.

And the best part?

The same executives who approved these decisions continue collecting their big bonuses, stock awards and handsome compensation packages. Very nice.

Meanwhile, the rest of us are expected to be grateful for a 0–2% salary increase when the cost of living has gone up by around 30%.

Wah. What a fantastic arrangement.

The people making the mistakes collect the rewards. The people who had nothing to do with those decisions are made to pay the price.

And if you complain? You are not being positive. You are not demonstrating the right mindset. You are not embracing transformation.

Arre bhai, what transformation? We are simply rearranging the furniture while the entire building is on fire.

Management, seriously, wake the fu-k up.

First, please look at these regulated environments properly. FedRAMP, IRAP, Protected B, sovereign compute. Show us the actual numbers. How much have we invested? What is the revenue? What is the operating cost? What is the realistic path to profitability?

If the business case is not there, then why are we continuing? Just because somebody made a commitment in a boardroom does not mean the rest of the company should keep paying for it indefinitely.

Second, look at our product portfolio. We have so many products, platforms, technologies and overlapping capabilities that even internally it is becoming difficult to understand what we are supposed to prioritise.

Reduce the portfolio by 50–75% if necessary. Focus on what customers are actually buying, what generates sustainable revenue and what we can realistically support.

Instead, we keep adding more products, more requirements, more complexity and more commitments while simultaneously reducing the number of people expected to deliver everything.

How exactly is this supposed to work?

You cannot keep removing people from engineering and then act surprised when delivery slows down, technical debt increases, incidents happen and customers become unhappy.

And please, do not tell us again that AI will magically fix everything. AI is a tool, not some divine intervention that will compensate for ten years of questionable management decisions.

Those of us in engineering are already stretched. People are working ridiculous hours, covering multiple responsibilities and constantly trying to keep things running. And somehow, every quarter, we are expected to deliver even more.

Boss, there is a limit to everything.

We are engineers, not magicians.

And one more thing, which management really needs to understand.

Engineering is not your enemy. Engineering is probably one of the most valuable assets you have. But you need to know how to use us.

If you take a hammer and try to start a fire, or take a sc--wdriver and try to drive a nail, obviously it will not work. But then you cannot turn around and blame the hammer or sc--wdriver for being useless.

The problem is not the tool. The problem is the person who does not understand how to use it.

Give engineering a sensible strategy. Give us clear priorities. Give us realistic resources. Remove unnecessary complexity. Stop funding initiatives simply because somebody senior thinks they sound impressive.

And most importantly, listen to the people who actually understand what it takes to build, operate and support these systems.

We want the company to succeed. We want to deliver value. We want our customers to be successful. We are not sitting here looking for excuses.

But you cannot keep making bad decisions at the top, passing the consequences down to employees and then giving everyone lectures about accountability, efficiency and ownership.

Accountability should start with the people making the decisions, not only with the people doing the work.

Help us help you, yaar.

Because right now, management is behaving as if engineering is the problem, when in reality engineering is the only reason many of these questionable decisions have not already become complete disasters.

And please, for once, instead of asking us to do more with less, how about giving us less nonsense to deal with so we can actually do something meaningful?

That itself would be a very good start.


by
| 161 views | | 8 replies (last 27 days ago) | Reply
Post ID: @OP+1m50g5b80

8 replies (most recent on top)

@ab, the EU and the Canadian Confederacy were playing this game long before Trump came to office.

"Trump's protectionist policies have accelerated the global push toward digital sovereignty. Governments are increasingly willing to invest heavily in domestic infrastructure, data residency and sovereign cloud capabilities."

by
| | Reply
Post ID: @eh+1m50g5b80

@ac
100% agree. Their management of Active Directory and OKTA is an absolute jok3. The access control is suffocatingly restrictive and completely rigid, but what’s worse is how incredibly old-school and disorganized their approach is. I’ve been in the industry for 20 years across 6 different companies, and I have never seen infrastructure managed this poorly. To make it worse, their ticketing system is completely fragmented, and they demand pointless tickets for every little thing. Anytime you offer a constructive suggestion, it gets instantly shot down.

That Director of cloud service —is unbelievably arrogant. He sits on the highest system privileges in the company acting like he’s completely untouchable. Being arrogant is one thing, but his technical skills are non-existent. If he were actually that brilliant, he’d be working at Gooxxx or Netxxx. But he can't get in there. He’s just occupying a seat with zero technical substance to back it up."

by
| | Reply
Post ID: @dp+1m50g5b80

@b6 agreed and confirmed 100%. The company is expanding and getting much bigger

We need all our people and more for all our business units and future growth

by
| | Reply
Post ID: @c0+1m50g5b80

Wake up call. Open text simply doesn't own the field that they're playing on. Sovereign cloud is an infrastructure game and Open text is a software company. I know they like to pretend otherwise, but the reality is the only thing in play here for OT is to layer on to someone else's cloud or through partners, and going the partner route is very, very political and slow. OT is in emergency zone right now. No matter how they try to spin the numbers, there is zero growth our customers are fleeing for a million reasons. Even big players like orange + Capgemini are 5 years into building a sovereign cloud and they haven't even come close to secnumcloud certification. It's an expensive, super-smart game and OT can't compete. There's a ton still going on in sovereign cloud including the French way which may end up imploding the rules as OT knows them today. Ayman know the CO is trading water and that's all he is hoping on for the short term because there are big changes coming.

My guess is we're going to see some big announcements in February when Ayman releases info on the new path for open text that he promised in his recent leadership announcement.

A lot is for sale, there are a lot of products and business units on the auction block or being prepared for the auction block. My guess is a year from now very few of leadership of today will be around and OT will be slim and ready to be sold what's left of it.

by
| | Reply
Post ID: @b6+1m50g5b80

@ac Yeah. Had one of em ask me "What is autoscaling?" Not a good sign.

by
| | Reply
Post ID: @aq+1m50g5b80

The "Cloud Service Team" is easily the worst unit in the company. They couple a toxic, arrogant attitude with a complete lack of understanding of GCP, AWS, or Azure. The infrastructure they’ve built is an absolute, unoptimized disaster and practically unusable. Because they don't actually know how to build or manage modern cloud environments, their only response to any technical request is to instantly reject it. They operate like a brick wall simply to hide their own incompetence. Management seriously needs to clean house and replace this entire team.

by
| | Reply
Post ID: @ac+1m50g5b80

@OP
However, the geopolitical landscape has fundamentally changed. Trump's protectionist policies have accelerated the global push toward digital sovereignty. Governments are increasingly willing to invest heavily in domestic infrastructure, data residency and sovereign cloud capabilities.

So the real question isn't whether sovereign computing is a bad investment, but whether OpenText has the strategy, customers, technical expertise and operational capacity to capitalize on this growing opportunity. Cutting the very people who understand these complex environments while investing in more infrastructure seems contradictory. The opportunity may be substantial, but without the right execution, even a promising market can become another expensive mistake.

There is another side to this story. Last year, OpenText eliminated key architects and support teams responsible for these regulated environments, weakening the very expertise needed to sustain them. FedRAMP itself isn't one unified environment; it spans multiple platforms, some inherited from Micro Focus and others built by OpenText. Canada's Protected B moved to TELUS, while the IRAP initiative reportedly lost cu-------, and sovereign is for AI.

by
| | Reply
Post ID: @ab+1m50g5b80

I’m not reading all of this. High level, I can understand your thought process but completely disagree. This is a mandatory requirement and entry ticket to doing business with gov and gov adjacent customers. We would not be taken seriously at all without these levels of security. I also disagree with your assessment on the scale of business, considering what I’ve individually delivered..

by
| | Reply
Post ID: @a1+1m50g5b80

Post a reply

: