Slashdot Mirror
IT Executives Believe Service Management Is Key To Digital Transformation (betanews.com)
Ian Barker, writing for BetaNews: A new survey reveals that a majority of IT executives believe investment in IT service management (ITSM) is important to gain the agility needed to compete in an era of global, cross-industry disruption and digital transformation. The study of more than 250 IT executives for enterprise management specialist BMC conducted with Forbes Insights reveals that 88 percent of respondents say ITSM is important to their digital transformation efforts. In addition 86 percent see ITSM as important to related initiatives around cloud computing, 83 percent to mobility and 83 percent to big data. Also 75 percent believe the time, money, and resources spent on ongoing maintenance and management is affecting the overall competitiveness of their organizations.
A new survey reveals that a majority of IT executives believe investment in IT service management (ITSM) is important to gain the agility needed to compete in an era of global, cross-industry disruption and digital transformation.
Translation please? I don't have my buzzword translation chart handy.
The only thing necessary for evil to triumph is for it to be pitted against a slightly greater evil
bingo
"we are all atheists about most of the gods that societies have ever believed in. Some of us just go one god further."
If you lean over, maybe some of us can leverage that synergy out of your ass, positioning you for a go-forward mission.
Don't disappoint your bird dog. Go to the range.
the services they supply to be critical and companies should invest more in them. In other news, water is wet.
I'm a consultant - I convert gibberish into cash-flow.
>> 83 percent ... and 83 percent ...Also 75 percent...
I'm guessing there were 12 "executives" surveyed, counting the marketing assistant twice and the guy who wrote the press release three times.
...BMC, a company who happens to make "service management" software does a survey with Forbes and Shazaam! the Majority of IT Executives, who probably never heard of this thing called ITSM, think it's important.
Just more bullshit in the river of bullshit from software companies seeking to be the new imperative of the decade.
When Fascism comes to America, it will call itself Anti-Fascism, and tell you to give up your guns.
The article states the survey was conducted for BMC, maker of massively bloated ITIL-happy IT service management tools of all stripes. Ever use Remedy to do service desk tickets or fill out the 2 hours of paperwork for the Change Management Board meeting? That's those guys.
If I had to boil it down to one point, I'd say the article says IT executives are looking at offshoring or outsourcing IT -- again, totally obvious given the audience. No MBA executive has ever seen a service they don't want to outsource. It results in big bonuses for them, a wasteland of fired employees and awful offshore-delivered IT service for those left behind, and copious lunches, rounds of golf and strip club visits paid for by the vendor.
The only nugget of useful info in this buzzword bingo card is the idea of multi-cloud. That's something I can definitely see becoming important because I'm in the middle of a cloud project now. Reining in the developers while letting them use Amazon, Microsoft or in house stuff is a huge challenge. No one is going to stop the IT execs from moving stuff back and forth between cloud providers, and having some way to do this in an orderly fashion will be important once the big cloud players gain a duopoly and raise their prices.
Did the article really use "agility" and ITSM in the same context? Hahahahaha.
I 3 "executives".
https://www.youtube.com/result...
Hello BetaNews and Forbes marketing staffers!
The reason that everyone here thinks that BetaNews and Forbes articles are written by and for tools, is nicely summarized here:
http://lurkertech.com/buzzword-bingo/
The key to agility would be less executives, IT or otherwise. Executives rarely ever produce anything and often act as an inhibitor to those who do. Also, renumeration tied to real performance. This would lead to more value for stock holders and hungrier executives. If an executive who claims to have to layoff a significant part of a company workforce to remain "competitive" while retaining giant salaries and getting huge bonuses because they met some goal setup by a friend on the board should be fired immediately and investigated for fraud.
I think what they're trying to say is that Digital Transformation will be the disruptive self-driving Uber of dashboards.
I think.
If we really wanted to get to the bottom of this, we should get IT executives together in a room and then shoot the room into space.
You are welcome on my lawn.
The title sounds like it came out of a buzzword generator.
Hey, Windows users, there is no such thing as "forward" slash, there is only slash and backslash.
IT PHBs love buzwords and are entirely missing the point...
Fully licensed blockchain psychiatrist
I've been building and using various "tracking" systems and applications for almost 3 decades to track people, projects, issues, equipment, etc.
They usually end up disappointing. If you put too few features in, people complain it doesn't do enough. If you put too many features in, then it's confusing and either requires systematic training or people avoid using it.
And anything that becomes popular enough to be used heavily becomes a political football such that high-ranking people want to muck with it to make themselves look better. It's hard to prevent such pressure from gumming things up.
If you want a successful one, then it at least needs enough meta-ability to be flexible: hierarchical when you need it to be or formatted hierarchically, yet apply some set theory when needed (such as potentially overlapping groups/categories), and neither trees nor sets alone will make everybody happy: it has to be able to project (display) as both.
And further, managers often want to see it in a tabular format such as a project/issue status list. If users don't encode (categorize) notes, requests, questions, etc. correctly, it comes out wrong, and it may be difficult to get a hold of the person who did it wrong such that you need some kind of "override" permission tracking so that a back-up person is allowed to fix it. And it helps if it's tied to Active Directory or similar to avoid needing a user account management army.
Somebody with sufficient rank and smarts has to manage the system in a clean way, and have the ability to say "no" when needed without being booted out. Otherwise, it will turn into a sprawling mess the way SharePoint typically ends up. Great technology alone is not enough; it has to be managed and controlled by people with skills, motivation, and sufficient backing and/or power to enforce conventions and keep it clean. That's hard to come by.
Table-ized A.I.
Ok, reading through this, "IT service management" and then the abbreviation "ITSM" clued me in that this is a new buzzword. I looked it up in the Wikipedia to see what this was all about, since I haven't heard this thrown around before:
IT service management (ITSM) refers to the entirety of activities – directed by policies, organized and structured in processes and supporting procedures – that are performed by an organization to plan, design, deliver, operate and control information technology (IT) services offered to customers. It is thus concerned with the implementation of IT services that meet customers' needs, and it is performed by the IT service provider through an appropriate mix of people, process and information technology.
So that's nice. IT service management appears to be what it sounds like, i.e. the management of IT services. It sounds really official when you say that it's "directed by policies, organized and structured in processes and supporting procedures", but really, how else are you going to manage something? Oh, and those things are "performed by an organization to plan, design, deliver, operate and control information technology (IT) services". So... essentially, "IT service management" is when you manage your IT services by using management techniques to deliver IT services? Well aint that somethin.
The article seems similarly meaningless. Surveying people who manage IT finds that they believe, in order to make your IT services run well, you need manage IT services. This is supported with a quote from someone who is selling IT service management software. Is there anything else to this, or is this entirely useless?
Management-speak, HR-speak, PHB-speak, flavour of the month bullshit. The scary thing is that decision-makers will actually try to implement and enforce programs based on this nonsense, and expect the troops to deliver on some hazy, ill-defined vision that some consultants dreamed up to enrich themselves. I'm continually amazed how corporate culture can pretend, so reliably and for so long, that the emperor is indeed wearing a spiffy new suit of clothes and not the ratty, sagging, pock-marked birthday suit he's most likely to be sporting on any given day.
'The Economy' is a giant Ponzi scheme whose most pitiable suckers are the youngest among us and the yet-unborn.
IT Executive.... that's an IT guy with an MBA who went back to school after failing as an Engineer. Or worse- someone with no engineering experience.
As the years have gone by, I've seen executives in tech migrate from "pretty smart" to downright stupid.
Anything an "IT Executive" says is suspect... all the time... every time.
Another consultant who stuck it out.
"We are the Priests, of the Temples of Syrinx..."
Just wanted to touch base and help you web 3.0'rs navigate this open architecture communication feed! This presentation promotes deliverables with minimal time to market by maximizing synergy using the vertical market integration. The convergence of interoperability make it happen in an extensible design-driven way without any NIH issue going forward.
Just thought I'd clear that up! ;)
Anons need not reply. Questions end with a question mark.
Try "IT Executives in the late 1980s", instead.
ITIL (a framework of recommended practices for ITSM) was first published between 1989 and 1996. There really is nothing new under the sun.
Eat the rich.
Even after looking up ITSM on Wikipedia, I still wonder what that stuff means.
The title alone made me want to vomit.
Would you call that a problem or an incident? This will determine if the service delivery team should focus on identifying a root cause or on meeting the Service Level target.
lucm, indeed.