sign up log in
Want to go ad-free? Find out how, here.

As promised, the rightsizing IT thread

Technology / news
As promised, the rightsizing IT thread

"You don't need that" and variations thereof invariably echoes through the comments sections on just about any story covering new technology. 

Most of the time the dismissal of the new is just annoying, as information technology (IT) is innovation driven and changes rapidly. Hearing about what's coming up is useful when it comes to planning for the future. For example, would you stick to wiring your house with awkward to run copper networking which runs hot due to high power usage, has thick cables that are difficult to bend and route, or would you give fibre to the room a spin if you knew about the latter technology?

Rightsizing is however an important consideration, relevant to other areas other than IT as well, and "you don't need that" can be good advice. Thing is, you can make do with very little if you have to, or just stick to what you have because... well, it works, doesn't it? Like the San Francisco municipal transport agency, which recently became the poster child of "technical debt" as they still use 5 1/4-inch floppy discs (do look them up if you haven't heard of them, they're that old).

But, it's difficult stuff that requires a solid understanding of the needs of users as well as possible, and then dimensioning a solution accordingly. This is much easier said than done, and there are difficult to remove hindrances such as users having learnt workarounds to get their work done - Shadow IT - which might be insecure, hard, and unproductive in the long run; it works for them so if it ain't broke, why fix it?

If you have been involved in architecting IT solutions, this won't be news. It's why on the enterprise side of things management consultants ride in with best-practices developed through past experience (and mistakes), software tools, and educational programmes for staff. Plus a truck load of patience, particularly for organisations where IT isn't their core business. Even then digitisation projects can go wrong.

As a general rule, finding a state of "IT Nirvana" is where it's at. This is a mindful state when users, be they business ones or at home, can just get on with what they want to do and don't have to think about the underlying technology that supports it. Life's short, and you don't want it to be even more brutish with angry users complaining and bashing you for IT under delivery. 

Generally speaking, giving yourself a bit of margin here while not blowing the budget can make for a happy user experience.

But even budgeting isn't always straightforward, and the cheapest solution isn't necessarily the best, as one commenter on the MacBook Air M3 review story pointed out. Longevity, and reliability could lower the total cost of ownership significantly, despite a higher upfront expenditure.

While hardly anyone bar sysadmins under active budget pressure are able to notice when a solution is over-specced, people do spot the under-resourced ones quickly. That's when delays in getting work done occur, causing productivity to suffer, or seemingly tasks like video conferencing being nigh impossible because there's not enough bandwidth available, so there's stuttering imagery and poor audio quality so it's back to long email threads instead. See also: Shadow IT as per above.

All of the above is a moving target of course, as needs change with time along with new technology appearing. It's also a more complex dilemma to solve in 2024, as we now have the cloud to factor in. With the cloud, it's vital to accurately match your actual needs with what you rent from a cloud provider. Failure to do so, and monitoring cloud usage over time, could cost users dearly. 

Without further ado, let's have your war stories from the ongoing battle of getting IT right. Yes I intended that terribly lame pun and refuse to apologise for it.

We welcome your comments below. If you are not already registered, please register to comment.

Remember we welcome robust, respectful and insightful debate. We don't welcome abusive or defamatory comments and will de-register those repeatedly making such comments. Our current comment policy is here.

14 Comments

The old addage "No one ever got fired for buying IBM" still applies.

Senior execs are easily suckered into buying over spec'd (&priced) systems if the big (4) consulting firms recommend it as they have neither the time nor inclination to understand what they are buying.

Up
5

Sure but big companies offer 27001, SOC2, and normally a very high match of features just needing configuration.

IMHO going with a solution from a small company who has limited clients can be a fast way to fail.

 

The maintenance budgets of solutions with 100s of clients help as well....

 

 

Up
0

If you're suckered into spending money on big (4) consulting, then you're going to be suckered into anything and everything else.

Up
6

The general rule should be never buy anything that the big 4 are implementing. They are hopeless implementors, more focused on consulting rather than outcomes. The general rule of thumb should be to avoid the big four (or any consulting firm at all), and seek out a specialty implementor for the software package that you have chosen, or the software vendor themselves....and make sure you have done your due diligence (big company/small company doesn't matter if you choose the right one).

Up
6

"Senior execs are easily suckered into buying over spec'd (&priced) systems"

I wonder how the UK PO execs got suckered into Horizon.

"they have neither the time nor inclination to understand what they are buying." They definitely complied with this statement.

Not sure if there is another one but if not his must rank as the biggest disaster in UK IT.

Up
3

You should see how much partying the sales teams from 'enterprise grade software' companies do. Easy for a VP to spend someone else's money (the companies) and personally enjoy the annual or quarterly partying under the guise of a 'conference'

SKF

Up
2

Hey we can save some money.....

https://www.theguardian.com/technology/2012/jun/25/how-natwest-it-meltd…

The bank was quick to deny claims by the Unite union that the "offshoring" of IT jobs to locations in India had led to the the problems which appeared on Tuesday night and which paralysed its systems through to Friday, and which have not yet been fixed.

However a number of programmers and experts who have worked on or with NatWest systems told the Guardian that they could not imagine the problem happening in the period before the redundancies of experienced staff since 2010.

Hey sandeep , did you mean reset or restart queue

Up
3

Software is only as good as the users, and most users either don't have the capacity or capability to use software effectively.

Orgs need to put much more effort into upskilling all areas of IT.

Up
5

I think this is a perfect example of why the bigger your company headcount grows the more inefficient you become. The real solution here is to have a tech literate individual in charge of making the decision themselves and backed by the ownership. If you're public or have more than 1 layer of management that almost never works, you end up needing to build systems and processes to decide, and the second you do that is the second that you incentivise overmatch.

SKF

Up
7

Shadow IT in global cloud is real. Lots of stories of cost wildly out of control and it's impossible to understand the invoice. Perhaps this is on purpose.

Up
1

In the last three corporations I worked for, the major stand outs in a crowded field:

1) The untrammelled joy of replacing an in-house 10 yo server running 12 yo software that had been bodged everywhere to run an entire corporation's operation. I did not endear myself to the C-suite when I pointed out it needed to be replaced with an off-the-shelf cloud version (new MacOS vs 10yo server software no longer supported, RTFM for once) and was told "we can't afford it" despite them having approved $250k worth of Macs that wouldn't work with the old system. I was asked to phone Apple to see if they would write the code to support our system! That call was never made.

2) The org had some poor individual who accidentally shared a Sharepoint doc with everyone's salary on it, so easy to do, so much drama created.

3) Moving to Google's from MS, then back again.

Up
4

I was asked to phone Apple to see if they would write the code to support our system! That call was never made.

Wow. Some expectations there...

Up
1

Yep, more than one set of raised eyebrows around the table - I'm all for 'there are no stupid questions', but that one definitely qualified. 

Up
1

I think you should have made the call :)

Up
2