I’ve been thinking more about the Kusnetzky-post and my earlier comments posted on ZDNet and as a post on In Max Mind.
What is the vehemence really about?
Is it so that technicians know something about security, availability, consequences that the management level doesn’t know or understand? If so; please tell us. Also tell the cloud technicians so they can build good, secure, reliable and available services.
Is it so that technicians don’t want to kill their darlings? No, or at least I want to think a modern technician don’t have problem doing that. Technicians are normally eager to find the best solution. And todays technician are skilled to give and take help from colleagues, update and read knowledge bases etc to find a fast, good and the best solution to an issue or need.
At the same time; are the management level too eager to save money and doesn’t see the problem integrations and federation might cause, also the talent of orchestration it takes provide services from different sources or vendors. On top of this the concerns about security.
But really, why would companies like IBM and Microsoft go for the cloud if it wasn’t good? Because of Google? Don’t think so. Google is very much a threat to them. But nor Google, Microsoft or IBM are fools, nor the people working there. Of course they will do the very best, like the IT department, to bring good IT-services to their customers. And they are quite competent companies…
I think you as an IT department should think about cloud as one way of delivering good IT services to your business. Not the only way but definitely one way. You have to adopt the ones suiting your business even if you could build it yourself. There will be a break between IT departments and management level if IT departments only plays defense. The management level will always win and might choose the wrong (a non-suitable) cloud service if the IT department doesn’t act as advisors and take responsibility.
As I commented to the Kusnetzky-post; the CIO role is so important. CIO’s should be given a strong position in the C-series. The management group should give the best support to the CIO. Also the IT department should give the very best support to the CIO. Trim the processes to find the best and fastest way to benchmark and qualify services to your solution.
I wouldn’t feel comfortable if letting the management team buy services. The management team know how to make business. The IT department should support them in this and bring IT to the best value (price, quality, availability). Start adopting when it’s good.
Thursday, 5 January 2012
Comment to Ken Hess ZDnet post 'Consumerization: The New Colossus'
3rd of January Ken Hess (@kenhess) published a post named 'Consumerization: The New Colossus' on ZDNet. Worth reading, also the comments. Added this comment to the post today:
I do agree with @aep528 in some cases. Also agree with many of the other comments, concerns and hurrahs. On my blog I'm writing a 3 step story about BYOD where I've published step 1 and 2. I'm really not so in to BYO, I really can't see the point and it will cause an administrative mess. Though my biggest concern is, which my step 3 will be about; when the possibility becomes a demand.
The demand might be a consequence of @aep528's company benefits. What will happen when companies demand you to BYO? I think as Ken say independent contractors will increase and as a dramatic consequence a personal "gold" service agreement attached to your device might be the key to keep your employment or not. And I think this will be a bigger problem than we might think. Why? There are a lot of employers who always try to use laws and systems at a maximum and with a mind set of “is there a possibility – use it”. In Sweden, where I live, there are rigorous rules of how and when you can fire somebody but firing will be easier if having independent contractors. And this will cause disorder in the society. No, I don’t mean BYOD will turn all things upside down but it will make people upset.
Also consider there are a lot of groups who never will afford bring their own. As I say in my part 2 I think BYOD is a possibility for “the cool guys”.
The future employers have to be attractive to attract good people. One way is to allow BYO. But if I was a good prospect to employee I would say “please give me the device” instead of asking “can I bring my own?"
I do agree with @aep528 in some cases. Also agree with many of the other comments, concerns and hurrahs. On my blog I'm writing a 3 step story about BYOD where I've published step 1 and 2. I'm really not so in to BYO, I really can't see the point and it will cause an administrative mess. Though my biggest concern is, which my step 3 will be about; when the possibility becomes a demand.
The demand might be a consequence of @aep528's company benefits. What will happen when companies demand you to BYO? I think as Ken say independent contractors will increase and as a dramatic consequence a personal "gold" service agreement attached to your device might be the key to keep your employment or not. And I think this will be a bigger problem than we might think. Why? There are a lot of employers who always try to use laws and systems at a maximum and with a mind set of “is there a possibility – use it”. In Sweden, where I live, there are rigorous rules of how and when you can fire somebody but firing will be easier if having independent contractors. And this will cause disorder in the society. No, I don’t mean BYOD will turn all things upside down but it will make people upset.
Also consider there are a lot of groups who never will afford bring their own. As I say in my part 2 I think BYOD is a possibility for “the cool guys”.
The future employers have to be attractive to attract good people. One way is to allow BYO. But if I was a good prospect to employee I would say “please give me the device” instead of asking “can I bring my own?"
Tuesday, 3 January 2012
Comment to the last post
Hopefully my comment won't disappear now. If, here you go:
"Thanks for a good read. I so agree.
Reproduced and a bit changed (my first one disappeared):
Of course there are concerns about security, who to blame if it fails etc. And no doubt; cloud services should be secure, reliable and available. But my opinion is that cloud won't get people out of work. It's not like the IT is a decreasing market. Technicians are so needed even if adopting cloud services. We should see it as a possibility to evolve; it might end up in a different direction and role. Companies need to have technical experts, they need policies and trusted advisors, and they need orchestrators to wrap up the complete IT delivery.
It seems like discussions often end up in two teams; the tech team vs the management team. We have to silo and come closer; business to tech and tech to business. Just look at the change of the CIO-role the filter to tech and business. CIOs has an important role, has to be strong and should focus to meet the core business needs to a given budget. Some services will be cloud, and some not.
Cloud is in some way a change in IT delivery and we have to adopt some the services sooner or later, or maybe sooner than later.
Fighting a good reliable, secure and available solution is good. Fighting cloud just because you dont like it or just love the way you designed it might be read like retrogressive.
Also; think about working at a cloud service provider quite techy indeed."
"Thanks for a good read. I so agree.
Reproduced and a bit changed (my first one disappeared):
Of course there are concerns about security, who to blame if it fails etc. And no doubt; cloud services should be secure, reliable and available. But my opinion is that cloud won't get people out of work. It's not like the IT is a decreasing market. Technicians are so needed even if adopting cloud services. We should see it as a possibility to evolve; it might end up in a different direction and role. Companies need to have technical experts, they need policies and trusted advisors, and they need orchestrators to wrap up the complete IT delivery.
It seems like discussions often end up in two teams; the tech team vs the management team. We have to silo and come closer; business to tech and tech to business. Just look at the change of the CIO-role the filter to tech and business. CIOs has an important role, has to be strong and should focus to meet the core business needs to a given budget. Some services will be cloud, and some not.
Cloud is in some way a change in IT delivery and we have to adopt some the services sooner or later, or maybe sooner than later.
Fighting a good reliable, secure and available solution is good. Fighting cloud just because you dont like it or just love the way you designed it might be read like retrogressive.
Also; think about working at a cloud service provider quite techy indeed."
'Cloud computing: why all of the vehemence?' by Dan Kusnetzky
Good read: 'Cloud computing: why all of the vehemence?' by Dan Kusnetzky.
Short break out:
"It would be wise of IT and facilities practitioners to focus on where and how new technology or new approaches can be of use to the organization rather than trying to fight them. Mainframes, minicomputers (now called midrange systems), distributed computing, client/server computing and the like are still found in nearly all medium to large organizations. They didn’t go away when a new approach or a new application was adopted."
I did comment it but it seems like the comment was removed. Really don't know why, it really wasn't controversial. Well, it might appear again later. Sometimes it takes a couple of hours.
Short break out:
"It would be wise of IT and facilities practitioners to focus on where and how new technology or new approaches can be of use to the organization rather than trying to fight them. Mainframes, minicomputers (now called midrange systems), distributed computing, client/server computing and the like are still found in nearly all medium to large organizations. They didn’t go away when a new approach or a new application was adopted."
I did comment it but it seems like the comment was removed. Really don't know why, it really wasn't controversial. Well, it might appear again later. Sometimes it takes a couple of hours.
Subscribe to:
Posts (Atom)