Blogs

RedMonk

Skip to content

Links for October 6th through October 8th

Stephen J. "Tio" Kleberg

Disclosure: see the RedMonk client list for clients mentioned.

Categories: Links.

My panacea of fantabulousness with Chris Dancy – IT Management & Cloud Podcast #82

Service desks have become a core part of IT Management, but they haven’t moved far since the initial ITIL-driven frenzy of adoption. That’s according to our guest, Chris Dancy, who joins John and I for this episode.

Download the episode directly right here, subscribe to the feed in iTunes or other podcatcher to have episodes downloaded automatically, or just click play below to listen to it right here:

Show Notes

  • Service desk bonanza with Chris Dancy (@ServiceSphere) – ITSM Weekly the Podcast.
  • What’s new in the Service Desk area? Not much, but Chris likes Service Catalogs. ZenDesk, even GetSatisfaction.
  • ITIL killed innovation in Service Desk, says Chris.
  • Adding social into to Service Desk.
  • FlowTone (?) example of finding humans.
  • Some “Hello World” examples for adding social to service desk.
  • What’s up with service desks in the cloud, SaaS ones.
  • The Dolly Parton Strategy for IT Change.
  • Chris’ review of itSMF Fusion next week in Louisville.

Transcript

As usual with these un-sponsored episodes, I haven’t spent time to clean up the transcript. If you see us saying something crazy, check the original audio first. There are time-codes where there were transcription problems.

Michael Coté: Well, hello, everybody. Today is the 4th of October, 2010. And we are really sort of like trying out the tensile strength of the rope, if that’s the right word, by recording two podcast today.

This in the IT Management in Cloud Podcast No. 82 with, as always, one of your co-hosts, Michael Cote, available at peopleoverprocess.com, and I’m joined by the other co-host.

John Willis: [email protected].

Michael Coté: On this episode, or today or however you want to think about it, we’ve got a guest and we actually… you know, I have to apologize because we tried to record an episode with him a couple of weeks ago, and I was using what is otherwise my awesome MacBook Air, or maybe it’s just Mac Air, and the little guy just couldn’t take it. He couldn’t take the awesomeness of our guest here, and it was fragilizing up my voice and everything. So why don’t you introduce yourself?

Chris Dancy: Hey, it’s Chris Dancy, servicesphere.com/blog, and at ServiceSphere on Twitter if you want to hear me rant about my neighbors, @Chris Dancy.

Michael Coté: That’s right (laughing). And so like you have your own podcast as well called the ITSM Weekly, the podcast, if I remember, with a couple of other friends.

Chris Dancy: Yeah. My co-hosts couldn’t even get that right. So I’m like, “You guys don’t even know the name”. They’re not friends, they… we have done this now deliberately for seven months continuously week after week after week, because we actually were inspired by your podcasts.

I put out a call on Twitter and said, “Hey, I want a couple of guys”, and I had this 30-year-old service desk manager — well, he’s good, because they’re fun to snicker at — and then this CIO. And they’re awkward and kind of gangly like teenagers, so I picked them. So, no, I really didn’t know them; they’re just on the show.

Michael Coté: Well, hopefully you’ve gotten to know them over seven months, at least what their day jobs are like.

Chris Dancy: Yeah. Well, they actually talk a lot about their day jobs, which is kind of nice, because I picked them up purpose. I could have done different people, but I just wanted something like your podcast. Your podcast was such an inspiration to me, and Rob England at IT Skeptic when I told him, I said, “I want to do a podcast”; I said, “I am so inspired by Cote”. He told me not to, because he said I could never live up to the awesomeness that is the RedMonk podcast.

Michael Coté: (Laughing.) That’s the other thing about Chris is he’s always very complimentary, which everyone appreciates that. It’s always very nice. But like you’re saying, you go over a lot of service desk stuff and service request things, and a lot of, you know, this is the IT management and cloud podcast and we spent a lot of time of late talking about cloud; but I think the exciting about you is you get a lot of IT management stuff to bring.

We were getting into this when the recording was crackling up, but I kind of asked one of my as usual very broad and unhelpfully broad questions. So when you look at the sort of service desk area, like what are you getting excited about nowadays? Like what’s the kind of stuff that you see that’s like happening and interesting?

Chris Dancy: You know, that was your question. That’s very good. Did you write that down (laughing)?

Michael Coté: No, I’m just so boring that I don’t come up with new stuff.

John Willis: He is a professional.

Chris Dancy: Well, I know; sometimes I live for Core-Mac’s tweets.

As far as service desk, man, there is nothing new. I just kept blog out now called Who Does The Service Desk Service. It’s kind of silly, because when reading it I was thinking “Who do we service? Who does the service desk service?” And it kind of reminded me of that Old Testament guy where He said you only have one God. I thought in IT, we are kind of polytheistic. We have many gods we serve, not just one and that one being the customer.

As far as technology what gets me excited, I’m still kind of a nipple rubber for service catalog. I think that’s kind of sexy. I think that’s about the last sexy thing they have left in traditional enterprise IT. But, man, some of the social support I’m seeing around Zendesk, which was the sponsor on a recent tour I did; so they’re customer-coded disclaimer there.

Also, a company called Get Satisfaction, who doesn’t have the best marketing people; but love their stuff. So Get Satisfaction for social support, and probably service catalog, but I won’t name anyone in particular.

Michael Coté: Yeah, I mean that’s an interesting sort of disruption, if you will, in the service-desk area. Joining together what you were saying there, or putting in my words what you just said to repeat it for the listeners who probably love it when I do this, is there really hasn’t been a tremendous amount of service-desk innovation. Then coming out of the consumer world are like these crazy things like GetSatisfaction and Zendesk.

Zendesk is more directly a helpdesk or a service desk or whatever, whereas something like GetSatisfaction doesn’t really even seem like it’s knowingly trying to get into the same area, if you will. I mean, GetSatisfaction, for people who don’t know, is kind of like a customer-service webpage form thing that’s hosted that companies can come along and sort of add.
(00:05:03)
Like you’ll go to a site, and there’ll be like these little tabs on the side. They’re like, I don’t know, File It — I don’t even remember what it says — but you click on it, it says sort go over to the forum and discuss things.

Chris Dancy: Give Praise is my favorite.

Michael Coté: There you go (laughing).

Chris Dancy: David Buttner says Give Praise; I love that.

Michael Coté: But it is an interesting… like taking it from the experience of one of those gods that IT worships or satisfies, sort of like the end-user, it’s sort of something like GetSatisfaction is kind of taking over what a UI kind of looks like and what the expectations could be. I really have no idea, and I kind of assume they really don’t do stuff inside enterprises like that. But it definitely introduces what you would like the experience within a company to be like when you’re dealing with IT, essentially.

Chris Dancy: You would think. I mean, you said something that I really get tired of people who don’t have any breadth or time in the industry fail to mention or maybe they’ve just brainwashed themselves to forget.

But if you were one of the converts of the ‘99 in the United States, there was innovation on service desk. The minute ITIL came in all the products became identical, all the functionality became the same, and all innovation was dead.

John Willis: Isn’t that brilliant? I mean, it’s brilliant in such a sad way; but, yeah, I never thought about, but you’re exactly right. I was actually in… my career that has kind of dipped in and out of incident problem, change management throughout the years. In the ‘90s, there was a lot of innovation. You had things like, well, IBM was in the game, you have Paragon Systems, you had the Software Artistry. I don’t know if you remember those guys. There was just a lot happening. Then even the Remedy guys, right? Yeah.

Chris Dancy: Another thing that people forget about, John, another thing people forget about the ‘90s, you got to learn from our history — these people just piss me off constantly — was at the end of the ‘90s beginning of this last decade, they were trying to forge. If you look at Numara, what they did with FootPrints when they were owned by Intuit, merging that into CRM.

Then FrontRange did the same thing by merging HEAT into their GoldMine application. We were on the precipice of understanding and delivering both support and customer service, and it all fell apart.

John Willis: Yeah, no doubt. No, you’re so right, because here we are now 20 years or 10 years further, and we’re no closer, you’re exactly right. We were starting to get like the silos of this thing of, like you said, customer relationship and incident-problem change, customer relationship, all that in innovative products. You’re right. ITIL just kind of like forced everybody down this path of just… yeah, it hasn’t — what surprises me, and maybe you can help me out, because I’ve not been in the space at least 10 years, really. I haven’t really paid attention as much. I pay attention from an industry, and I know an ITIL as I run into it when I deal with the enterprise. But to me it’s just mindboggling that there isn’t a whole lot of open-source remedy competitors. You know what I mean?

Chris Dancy: Well, OTRS is.

John Willis: OTRS, yeah, yeah.

Michael Coté: Like as a little parenthetical interjection on there, it’s like looking at the keyword-driven traffic like to the RedMonk site. Like it’s interesting that we get a lot of very consistent traffic for people searching for open-source CMDB, which is somewhat related, right? So they’re sort of interested in that.

Chris Dancy: Well, CMDB has to be open source, because you couldn’t give that shit away.

Michael Coté: There you go (laughing).

John Willis: I think that overtook, if you probably — just going along with what you said, I think that whole focus on CMDB and all that again just pulled away from the more serious discussions of how do we manage customer relationships and how do we manage and how do we integrate all the important things we do with service management.

Chris Dancy: It was so cool, because salespeople, the whole idea was I’m a sales guy and I can log in to one system, and before I call this customer to say “Will you buy my class, will you buy my software, will you buy my consulting”, I could see all the problems they were having with my company. Why is that so freaking hard of a concept?

John Willis: I know, I know. It’s like it’s…

Chris Dancy: Because there’s more money to be made in selling cigarettes than selling freaking cures.
(00:10:00)
John Willis: You know, it’s like this. So I was thinking about when we first started talking. One of the things that we started the conversation last time was I think a comment you made about like if you are like a traditional helpdesk, you should be worried about your job, and I guess part of it was that way. I mean, there is this new dynamic of social helpdesk or whatever, right? So you were just about to get started on that, and then we got cut off.

Chris Dancy: (Laughing.) Well, I think IT folk need to say “Hey, I remember ‘95, I remember sitting up all night with 55 diskettes pushing them in a machine to upgrade my Windows 3.1 box. I remember 2000, I remember adding TCP/IPs, fax; I remember configuring shit. I remember how — I remember 2005, I remember getting my first wireless router. I remember 2010, I remember getting an instant-on tablet machine.

I remember 2015. I didn’t have to call a helpdesk. So I think if anyone is going to own the next 5 to 10 years when it comes to IT period, it’s got to be this new breed of what people are calling community management, because if we leave it to the marketing folks to be the community managers for our company, they don’t know reality. If we leave it to the financial folks, they only know reality. If we leave it to the legal department, they don’t know shit. The only people who could possibly manage us of out of socialness and into something truly inspiring an enterprise is the IT department. But is IT paying attention in the social? No, they are paying attention to the social, because, well, you know, it’s a disruption and it’s just a bump and it’s another tool. It’s all tweets today. It’s just plumbing. Then the tweets said, “Well, try to live without plumbing.”

I wish IT would step up to the plate and say “Okay, we don’t agree with this, we don’t like how disruptive it is; but as an IT department we are going to own this, because the rest of the enterprise doesn’t know what the hell they’re doing with it”.

Michael Coté: So, why —

Chris Dancy: The one and only time — go ahead.

Michael Coté: So why don’t you, like to give us sort of a baseline, you mentioned like Zendesk and Get Satisfaction; but like what is that 2015 socialness added? Like what’s your sense of like what that ends up looking like?

Chris Dancy: I envision some type of software that consists of social objects. So basically if you’ve ever used GetGlue, it’s like a Foursquare for movies, music, books and just silly thoughts. You check into things like I am watching this movie, I am going to sing this song.

Again, if I had an enterprise piece of software it would be wall-enabled, and anyone on any part of the company could browse social objects and check in from them and get updates. I’d want to be able to have people throw out an idea and have the company look at it and then develop it, and I’d let it move fluidly from space to space.

We are all used to working like this. I think if someone wants to make a mint, freaking develop a Facebook enterprise app. Oh, it’s just another tab; put it in there, it will let do everything that you think you are doing now. Everyone knows how Facebook works. Just do it.

But I really like the concept of social objects. I don’t know who is going to do it, I don’t see anybody really talking about it. I’ve done some consulting with a couple of companies about what it looks like and how that works and what it’s like to check into a project or check into a meeting or add your thoughts and then be able to curate that. I like to call it enterprise intuition.

So if you truly had a social wall and a social object-oriented enterprise, you could literally do predictions like they do now with traffic to a lot of these social sites. So wouldn’t it be really cool to predicatively determine outages, changes in people leaving, new hires, changes in your customers’ thoughts and feelings just organically from your enterprise intuition? You could do that. And there is no amount of money that you could pay a consulting company that would be able to give you good information. You put this in place, you’d have information about them.

Michael Coté: So, I mean, if I’m understanding, it sounds like part of what you are saying is that… so, okay. So if IT is doing —

Chris Dancy: Sorry (laughing).

Michael Coté: If IT is doing service delivery based on delivering IT stuff that accomplishes some service that the business need, whatever all those words mean.

Chris Dancy: Right, right.

Michael Coté: Then part of the problem of what they are not doing now is they may be monitoring disc usage and CPU and network traffic and synthetic transactions and they are monitoring the service. But they don’t really monitor the way in which the service is used and sort of take that into account as a way of not only sort of — I mean, the baseline, like you were saying, is like, oh, these people are really using this service, so we need to give it more capacity. We need to make sure it’s working.

But in theory, there is all sorts of other things that you would do if you were actually observing how people were using the service, in the same way that a company might do some ethnography on the way their products and services are being consumed and tweak them so that there are new features and things like that.
(00:14:54)
Chris Dancy: Exactly. I mean, I was aware of hardware and software trending three years ago. As soon as I saw the social stuff, I thought this is the answer, because these machines will evaporate, right? They will get smaller and smaller and smaller, thinner and thinner and thinner. So what’s left but my feelings toward these things?

And you’ve got a lot of companies out there like newScale. newScale is a big service-catalog company.

Michael Coté: Yeah.

Chris Dancy: They have suddenly become cloud freaks.

Michael Coté: Yeah.

Chris Dancy: If I were them, I’d abandon my clouded option, use it for a backbone and develop an app that says this is how I feel about consuming services. If I was a service-management company, I wouldn’t want to send an email to say “Here, this is your ticket and here is your number”. I’d want to let the customer decide. Do you want to follow the updates on your ticket? Let it be push or pull.

These things are really simple. We interacted with our world around this way. I might be in the helpdesk, I might be concerned about the next big round of layoffs. I might want to follow like in SHAtter an opportunity on a big sale. Why aren’t we enabling these things? I’m sorry. I don’t mean it to be the pissed-off podcast.

[Laughter.]

John Willis: A good stop. This is the kind of stuff it brings out early. I mean, I think also I was taken away from like this — what you are saying is that what IT needs to do is look at a kind of a social engine or a social technology to drive the next 10 years of that company, and like it’s all of the above, right?

I mean, what’s happening today is you’ve got the 16:27 departments banging in IT or just giving up and going out of the media consulting companies; they’re getting them on Facebook. Then in some cases you actually have the salesforce.com leg of it going out and maybe grabbing some of your who’s talking about you.

Like I think that… well, I am going to go all over the map here; but in some ways we talk about the cloud of try to get out of technology that’s not your core competency from a technology standpoint. But maybe the message is a core competency should be controlling the social network or the social aspect of your business as a technology.

Chris Dancy: Well, I’d go one step before that and say the core competency needs to starts with understanding. Control the very IT-center thing to say.

John Willis: Right, no, yeah, yeah. Exactly. No, of course, right, yeah, to build that engine, you have to sit back and say, “Okay, what…”

Chris Dancy: Watch it.

John Willis: “… what is it? What do we want to accomplish over the next year from base control?” And this is the way… the world is going to be very much like this, right? If you are in business right now and you’re not figuring out what… a friend of mine works for this company called Digsby, and they do mobile apps.

Chris Dancy: I love Digsby.

John Willis: Yeah. So he is like the VP; he just got the job of VP of Engineering there. They’re talking about the in-store experience and just where they’re going with this technology. You think every business is going to — you know, it’s not just that; it’s going to be the whole social aspect of your business, you know what I mean? What’s your mobile presence, what’s your… what are people saying to you about on Twitter or what are they — and I think you’re right. I think you better have some thought leadership right in your organization right now that’s speaking on how are we going to basically provide a best-of-class solution around all this.

Chris Dancy: I think people — I can’t remember site name; but there was some site I got invited to. It’s kind of like a LinkedIn, but you would only… the whole purpose was you tagged people with a few words. So basically it was metadata for Flash, right? And I thought “Well, that’s kind of cute”. And then I thought, “Why don’t Active Directory have this?”

Again, if you’re planning a social shift, I remember when I was doing service desk, everyone was like “We need to integrate with Active Directory, we need to integrate with Novell,” da-da-da, NDS. Again… have you guys heard of Flowtown?

Michael Coté: No. Flowtown?

Chris Dancy: Flowtown.

Michael Coté: No, what is it?

Chris Dancy: It’s kind of strange. It’s a sales and marketing tool; but again, people often — tools are used for the wrong reasons. A guy named Dan Martell is the CEO. Between Austin and Canada, like everything bright is coming out from those two ends. Another Canadian; but basically the way this works is you give Flowtown your email addresses of your customers, and Flowtown gives you their social profiles.

Michael Coté: Oh, right, right, right. It’s a nice way of pivoting like on an email address.

Chris Dancy: Right. Like if was a helpdesk I would use Flowtown for all of the customers out of Active Directory and help bring them to these spaces. Then the rest of the company two years from now would go, “Gosh, you guys were way ahead of the curve. We liked you IT folks. We’re not going to send you to India.”

Michael Coté: That’s right (laughing). So if we sort of add social into like service-request management and all that, right?

Chris Dancy: Yeah.

Michael Coté: So what’s a good example to kind of walk through what that looks like? I mean, the classic, the Hello World of service desk seems to be the password reset. I mean, does that sort of work as an example of what’s going on there, or does it need to be something more complicated?

Chris Dancy: I kind of like that (laughing). No, you know, to me, there’s something that —

Michael Coté: I guess there is also an employee on-boarding. Those are like the two things that seem to be the biggest service, the drivers.

Chris Dancy: Yeah. Well, that and the whole fact that we’re obsessed with metallurgy when it comes to service-level agreements: it’s gold, it’s bronze.

Michael Coté: That’s right (laughing).

Chris Dancy: … it’s pewter. Pick something out, you know: platinum, you know. So, gosh, a Hello World for social support. You know, the one I see over and over and over again is the one I always tell people, and that’s it’s real simple. Everyone always talks about reducing IT costs. In every company, there is someone in the accounting department, there’s someone in the marketing department, there’s someone in the leadership function who is a wannabe helpdesk person.

So instead of outsourcing level one, in-source it through something social. So say that your service levels don’t change, you can still call the helpdesk for anything; but we are going to post all of your tickets if you opt in out to some social space, and people can answer you.

Michael Coté: Oh, right, I see what you’re saying; and hence, the comparison to things like Get Satisfaction and stuff where part of the nice thing about Get Satisfaction is that it’s a customer-service page for a company, but also other users can answer those questions for you instead of only the company answering it.

So you could actually interact with people —

Chris Dancy: Exactly.

Michael Coté: — within the company, say like “Here is how you reset your password”.

Chris Dancy; Right.

Michael Coté: “You actually click on that thing that says Forgot Password and it sends you an email, and then it resets your password for you.”

Chris Dancy: Right. Another Hello World is the Facebook Like button, right? As soon as that thing crawled out of Facebook, it became more deadly to IT than IT realized, because now you can go to any of your open web-based software — you know, Service-now and the Customer RedMonk, right? — go to any of these things where you have a portal and embed that button, and every single one of your tickets and every single knowledge-based article, people just love that Like button. Someone clicks on that from a knowledge article and, boom, it’s on the wall; 90% of your company who’s friends with you now knows there is a knowledge base. Yesterday they didn’t, today they did. Why? Because you said you liked it.

Michael Coté: Right, right, right. Yeah, it’s kind of like -– oh, go on, John; you’ve been trying to interject here for a while.

John Willis: Well, I was going to say, I mean, that’s the one thing. I mean, should a company today just kind of plan on just kind of building a CMS and just kind of all off of Facebook? I mean, is that… you know, I mean —

Chris Dancy: I like the idea of a human-powered CMS. So keep on tracking everything physically; we have to until it becomes so small and weird. You know, I have a tweet scheduled right now for tomorrow, and I follow some company talking about desktop management. Remember, John, when posting out software was a big deal?

John Willis: Yeah, yeah.

Chris Dancy: You know, compile before me and I will push out software to you. You know, the idea of pushing out software to my app-enabled mobile device is kind of ridiculous, right? So keep tracking all the stuff we’re tracking, but start to enable the human CMS, because we know more about what’s going on and what’s not working and what seems slower today than yesterday. Then why not, you know, when you check in to network slowness, let that be articulated somewhere and look for traffic that way. I totally believe as humans we’re organically more in tune with technology than we give ourselves credit for. There’s almost a nature thing to it.

Michael Coté: Yeah. You know, I mean, that kind of touches on something that I go off on every now and then; I should probably sit down and actually write it up so I can be done with it. But it’s like the idea of… it’s sort of an evolution of what computer literacy means for job requirements, and to put it in the extreme way like, you know, if you can’t manage your own desktop you’re fired. And it seems like some of what you’re saying is sort of that, to use an old Bill Joy quote, right, like, “Innovation happens elsewhere” and it’s sort of like the IT department is not always the best people to solve every single problem, whereas in the rest of the company there’s other people that might be able to help yourself out, including yourself. Like you might just know that you need to install this on your machine or you need to do that.

It’s an interesting thought exercise to think about. If you have the technology to enable that, like what that implies for IT, like if everyone knows that you just go unplug the router and it makes the Internet work again, right, then like what that… I don’t know, I feel like there is a lot of stuff that IT probably does in corporate settings that they don’t really need to do, or they should need to do.

Chris Dancy: Let’s jump to the absurd. Ten years from now we are all Core-Mack as chips somehow; we cybernetically chipped somehow, right? He obtained this information by blinking or slowing down. Let’s just pretend that’s going to happen because it will, right?

So now let’s back up. What happens between now and then, right? We evolve into understanding until we can actually physically mesh with the machine. You guys know what I’m talking about when it comes to machine intuition. You know when stuff is not right.

Michel Cote: Right.
(00:25:14)
Chris Dancy: It’s almost like “The Matrix”: you stare at it and go, “No, this is not right”, right? So what do we do between now and then? The only think we can do until we are chipped is allow people to share their intuition. Sharing their corporate-enterprise intuition is going to make someone a boatload of money, because until we’re chipped in 10, 15 years, that’s where it’s at.

Michael Coté: So what happened with like… I remember you commented, or someone did. I remember —

John Willis: Well, wait a minute. Is that ITIL 5 then?

Michael Coté: Exactly (laughing).

Chris Dancy: No, luckily it will be gone by then (laughing).

Michael Coté: So speaking of do-you-remember stuff, like didn’t those managed-object guys come out with the whole social layer for their service desk and CMDB? Did you check that out at the time, or what’s been going on with that?

Chris Dancy: I did; again, it’s a timing thing, a little too early. But again, I think a year from now it will be a little too late. Everyone will be doing it.

I think it’s really cute. I’ve been working with a few service-desk companies who are working on the ability to be able to pull tweets in the tickets. That’s a good first step. But you know, again, it’s beating the horse.

Michael Coté: Right.

Chris Dancy: Why even bother doing that? So, yeah, I don’t know. I think right now the timing is… timing is everything right now. If I was a service-desk company again, I am betting that we are the key, right, for the next 15 years. I would be betting everything on some type of gigantic enterprise social object and everything having — I mean, maybe you’re the admin of some gigantic server farm; but you care particularly about two different processes. It makes sense to you to Like them or Follow them or check into them. You understand these types of things, because you work and you live it, right?

Michael Coté: Right, right. No, and then —

Chris Dancy: Why aren’t we enabling this? It’s very simple stuff.

Michael Coté: It’s funny, in the previous episode we were talking about cultural change that DevOps needs and all this kind of business. That’s like one of the points you’re getting at, too, is this cultural change of the white-collar worker, if you will, that they actually care about a piece of technology. They kind of know enough what to do with it that they would want to follow it and kind of like keep up with what’s going on.

So there is a certain sense of management spreading outside of the wall — as John would call it, outside of the glass house, if you will, and letting your dirty filthy end users actually come in and like take care of a little bit of their own stuff. I of course say that tongue-in-cheek. But it is like —

Chris Dancy: Yeah. It is more importantly the idea of curation. If I’m an admin, I’m inundated with alerts. Shouldn’t I be able to curate via social Follow, Friend, Like, whatever the heck you want to call it, just the thing that I really care about?

Michael Coté: Yeah, yeah. No, I mean, I think it usually goes under the banner from a few years ago like crowdsourcing or whatever. But for lack of a better term, in many different domains I’ve been seeing the… having this aggregate of… what is it? Having these moderately moderate to huge piles of data that allow you to kind of figure out what the hell is actually going on in some space.

And to the point of what you were saying, if everything had the equivalent of a Like button, and a quarter to half to whatever percentage of the people in a large company were actually Liking the things. And of course, having a Dislike button would be handy as well. But if people could register their interest in some given IT asset, that would be kind of a novel piece of data to have to start determining what you do with it.

Chris Dancy: Yeah, I mean, a company that opens up a Facebook API and says “All my enterprise apps will have some Like functionally so that when you go home or you’re sitting at your desk and you’re looking at your phone, you’re saying ‘Mom just took Junior to the birthday party; Bess is playing FarmVille; the server just hiccupped.’” It makes sense.

Michael Coté: Yeah, yeah. It’s sort of like on the iPhone they have this My Call Just Dropped thing for AT&T. It’s kind of interesting, because they show you other people who have reported dropped calls. So it’s interesting to like open up the map and see like how many dropped calls there are in your area. I mean, that’s not a perfect example or whatever; but because there’s all sorts of —

Chris Dancy: I think it’s a good example, because it also speaks to something that I think is the big hurdle to my panacea of fantabulousness is I know about that app you’re talking about, Cote. And I thought about downloading it; but to take the time to tell them how crappy they are and exactly when and where they were crappy devalues me.

Michael Coté: Yeah, no, I agree completely, and like to some extent I feel like I should get

Chris Dancy: The cultural thing does not like me.

Michael Coté: I feel like I should get maybe a one-percent discount or something like that.

Chris Dancy: Exactly.

Michael Coté: That’s like the dark side of all the crowdsourcing stuff that all the Web 2.0 people didn’t really get into much. There were a couple of snarky people like Mr. Cloud Dude himself, whose name I can’t remember now which is terrible. Then a couple of other people were basically like “Oh, wait, so basically I am doing a bunch of free labor for the company”.
(00:30:10)
I think that’s one of looking at; but the other way is that like there are many situations where I realize self-service should also imply a discount in the pricing that I’m doing because I’m saving a company money, and yet they don’t really have those things in there so much.

So that is the give-and-take of adding social is there needs to be some… if you already have the expectation that stuff should be working and then you’re doing work to make something you’re paying for work, something is a little wacky as far as the expectation settings there.

John Willis: Yeah, it’s a fine line in scale, right? I mean, like to me one of the great social-network applications, if you’ve ever gone to Disney World, right, they got the iPhone app that tells you how long the lines are, how long you are going to wait, right?

Michael Coté: Yeah (laughing).

John Willis: If you like are worrying about like what like you are going to go on and stuff, right, I mean, that’s really (laughing)… So people, while they are waiting in line, even though they are pissed, they are taking the time to go ahead and answer the social…

Michael Coté: Right.

John Willis: … that benefits, and why would anybody bother saying “20 minutes, god dog it. I am going to put it into this app”?

Michael Coté: Right, right.

John Willis: So I don’t know.

Chris Dancy: I was at Disney a few months ago, exactly what you are talking about with these lines. And I said to the guy, I wanted to get on this ride. I had to get out of the park in the next half an hour. I said, “Dude, I’ve got my ticket, my” — you need to pay a FASTPASS ticket. I said, “It’s for an hour from now.” I said, “I’ll give 20 bucks; just let me in there and out.” He said, “No, everybody at Disney is equal. If we took money from you, it would mean other guests would be less important than you.” And like not five minutes later somebody walks up with an entourage and goes right in the line. And I said, “So I guess he is just as equal as I am, too, right?” It comes down to a real —

John Willis: That’s a bunch of crap, being equal, because we bought Disney Time thing and they gave us — so I was told they never do this. There’s 32:04 something divert on Disney. They give you like these token, they are like all-day FASTPASS.

So the sales guy gives these things out all the time when people are trying — when they are to sell Disney properties. It’s like an unlimited — it’s a FASTPASS you can use at any time during the day, and they’ll give you — they gave use like 30 or 40 for our extended family.

Chris Dancy: I mean, someone ought to make it an app for your iPhone and your Droid to let you get, you and your partner or whoever you are you at Disney with, all get FASTPASSes. Then stand for two or three rides, and then you all check into some app and then you trade them with other families who are wanting to get in your line and then you go get back in their line. I mean, it’s real simple stuff.

But it takes me back to this whole idea of micro payments, right? I don’t know, we have a Walgreens here in Denver. I am not from the East, I am not used to Walgreens. Last winter I had to go, because I wasn’t feeling well. Well, they had a machine and I had swiped my credit card, swiped my insurance and fed everything in; nobody, no nurse or anything. Then it said to me, “Would you like to pay $10 extra to move to the head of the queue?”

So there were like eight old women in there. So I said, “Of course. They are going to be forever”. So it swiped away 10 bucks. Then they are like “Would you like to pay an extra $10 to have your prescription ready if you need a prescription before you come out of the door?” as if they already know what you have, right? I’m thinking, “Well, of course.” So I sat there just super-sizing my illness, and my time was worth it.

So, again, people have — you know, they lose their bowels when I say this; but in service management, I don’t think it’s beyond the grasp of most people once we get some micro payments to say “Here is a dollar, move me to the front”. Make IT a profit center.

Michael Coté: No, no. I mean, what’s interesting there is, not to be all like topical plug news guy, but like Service-now came out with a recent thing and one of the things they had was cost management and stuff like that, which… so I have had a few discussions with reporters about what is it, what is all this cost-management stuff and everything mean.

I never get the sense that IT departments have had a really good grasp on exactly how much it costs to do things, or they can come up with a grasp; but at some point you usually have someone sitting in a spreadsheet and they kind of insert a number into a column, and then you’ve got your costs. It does seem like the more you can sort of cost out what any given service means.

The dark side of that is it means you are going to start charging people what they really should be paying, which can be bad. But there is a more interesting sort of, I don’t know, positive thing that you can do, which is exactly what you started saying. Like one person might say “Well, Walgreens is just fleecing me.”

But on the other hand, they are also giving you more decisions to like get the kind of service that you want, right? Like so if you don’t want to pay a lot, you can wait, which is fine. But if you’re sick of waiting, then at least they give you the option of a way to speed it up, kind of comparing to the Disney thing.
(00:34:59)
I feel like the way that a lot of IT is delivered, they don’t really have that grasp on how much a service is going to cost someone, such that they could say, “Well, if you give us $5 more” — it’s probably more like $5,000 more — “we can do this and do that”. I mean, it’s kind of like a game, a sleight-of-hand game usually when you’re budgeting out how much something is going to cost, which makes it very difficult to give people maximal decision based on what they want to pay.

Chris Dancy: Yep.

John Willis: Yeah, I mean, that’s why people love… some of the things people really love about the public cloud, right, is for the first time if you know once you go down that route, you know exactly what your costs are. I mean not route; there are still other management issues, but for the first time you’re not guessing on… there is a specific price that you’re paying for computer power, and it’s a bottom line.

Michael Coté: Yeah. It reminds me of another quote someone told me a while ago from some CIO they were talking to, and it was something like — and this is something you said many times about, for example, the budget that big banks have for IT where it’s like cost isn’t really the issue. It’s sort of like the certainty of spending something. Like if I went to the Board and I told them, “You give me $5 million and we’ll make 20% more profit”, then they would give me $5 million right there in that meeting if they trusted that that would happen; but it seems like the controls and trust isn’t necessarily there in service being provided to enable that kind of conversation. So instead, you just turn IT into a bunch of offshore skeletons, basically.

Chris Dancy: But that’s kind of silly, because saying “You give me $20 million or $5 more, we’ll give you 20% better”, that’s like saying to somebody who’s about to knife you to death, “Scream softer and I won’t stab you as hard”.

Michael Coté: Exactly (laughing).

Chris Dancy: I mean, you’re in control of the thrust and speed, for gosh sake. The motion of the ocean has already taken over, all right?

Michael Coté: That’s right, that’s right.

Chris Dancy: I could go places with that one.

Michael Coté: That’s right. Well, I mean, to switch to sort of a tangential topic, so this is something I’m curious to hear you talk about a little bit is with like — so I mentioned Service-now a while back, and like I had noticed in the past year or so a lot of the service desk people have kind of — and we’ve talked about this offline; but a lot of the service desk people have come out with SaaS options, or On Demand as they seem to like to call them, which I always think is kind of funny.

But, I don’t know, what do you think of this whole thing of like service desk moving to the cloud or as a SaaS thing? Is that sort of good or bad? What are you seeing play out in that area?

Chris Dancy: I like what John said, that the cloud has really given us as consumers of IT, whether we be in IT or not, a real idea of what we’re spending. I know I just got an email saying QuickBooks 2011 is out and I can upgrade for $200, and I thought about converting my software and buying the software and all that stuff, or I could pay $39 a month and just move to their online solution, which is crap and it looks like crap. But I wouldn’t have had to install anything, I can get to it anywhere.

Michael Coté: Yeah.

Chris Dancy: As far as service, so obviously I mean, my whole mind has shifted. I mean, being a small business, I’m thinking everything I do is in a cloud, a cloud service or SaaS some way. I don’t have time and I want to know right away at the end of the month if something has to go, which light in the house — not all the lights, but which light, right?

For service desk, I think it’s moving that way. Unfortunately, again, if I was… I think a lot of these vendors are just cloud-washing is what Rick likes to call it. They’re service desk and saying that they are SaaS or On Demand. You can call it whatever you want; it’s good marketing. If it sells the more six-month extensions on the cancerous life of service management, then you’ve got a SaaS operation.

Michael Coté: Right. This is kind of like the Oracle/Larry Ellison-like strategy for cloud computing. It’s like “Hey, if you give me money if I call it cloud computing, I’ll call it cloud computing. Can I have your money now?” So that does happen.

Chris Dancy: Yeah. I think it’s all a little too late. Again, unfortunately, I don’t think anyone is saying “What does service-management software look like” — let’s just be real conservative — “two years from now?” and go on from that. You look at all the vendors to these major revamps at the end of the ‘90s, beginning of the 2000s, create the uber-service management pantheon, which was parent-child relationships, because then anything could be related to anything: a problem to a change, a change to a release. They could spend all day linking things together.

Then that time you take Service-now, and they said “Well, we’ll just do this whole web-based thing.” But the thing, that wasn’t new. I mean, FootPrints by Numara was doing that. What made it new was they were saying, “And we will take the half part of you doing it, and we’ll make it easy for you to understand.” I think now that people get that, I think a lot of companies will be successful moving in that direction.
(00:40:00)

But, again it’s just like Keynote’s: it’s not going to make it last, and I really have no good comment for you on it. I think people are…

Michael Coté: And it sounds like, definitely. So, I mean, does a service desk seem like the kind of thing that should be a SaaS versus on premise, or does it not really even matter?

Chris Dancy: I mean the fact we’re asking the question doesn’t mean we understand what the term “service desk” means.

Michael Coté: Right, right, right, right.

Chris Dancy: The fact that we’re considering a tools delivery in service management means we don’t understand service management.

Michael Coté: Right. Well, that’s exciting.

[Laughter.]

Michael Coté: But that is like — like I remember sitting at –-

Chris Dancy: I won’t get all cocky.

Michael Coté: No, no, no, no.

Chris Dancy: I worked on a helpdesk for years. I was a helpdesk tier level. I mean, I was still 41:00, right?

Michael Coté: Yeah.

Chris Dancy: And then I managed that same helpdesk. Then I installed them for FrontRange. Then I consulted from the end desk, and then I did something else that touched on it. I’ve worn all these hats, right? So trust me when I say I have sold service-desk software and I still feel sorry for it, because there was no service in it.

I remember — and I’m sure, John, you do, too — back when someone had a problem in service and support was, “You have a problem? What’s your problem? This is what you do. Are you happy? Good.” That was it.

But what happens, tons of money came in and said “You need metrics to measure that, and you can’t get metrics unless you know how quickly you’re talking to these people and how often they’re calling” and da-da-da, and we spent more time worrying about all the things we had to do to prove we were doing it than doing it.

Michael Coté: Yeah. No, like and what I was trying to recall is I was at CA World — that’s where I was — and I remember I saw that there was a session that was like the… I don’t remember what it was called; but it was basically like do you use our service desktop software? Come complain at it, it was that kind of session.

So I thought it would be interesting to go sit in there and see what users and customers were saying. And I remember… well, what happened was there was a lot of questions of — you know how these things go. It’s basically “When are you going to do X?” where “X” is a collection of really complex, weird and esoteric ways of assigning a ticket and then reporting to it. And everyone was kind of obsessed, because this is what their expectation was for how they were going to run is like “Well, if we have got a team of 50 people and then one of them is out on vacation and then we do the assignment here and that person is overloaded, how do we figure out who gets assigned a ticket?” And this is just one example of — it’s very complicated, weird stuff. And I remember sitting there and thinking like, kind of to the point I think you were making, is like it’s sort of the wrong question to be asking of like…

Chris Dancy: Exactly.

Michael Coté: You don’t sort of ask like “How can I sink faster into this quicksand?”

Male: Yeah.

Michael Coté: Like I feel like I am moving a little too slow. It’s more like “How do I just get out of the quicksand in the first place?” It was one of those enlightening and also depressing moments where it’s… you know, that’s one of my poster child for what I always call the sort of Stockholm syndrome in enterprise software, where the people actually paying the money and the user management, they have just been conditioned to want the wrong thing and they get upset when you try to give them something new and interesting or useful.

Chris Dancy: Well, it’s rude to ask a young couple “When are you going to have another kid”, right? You just can’t ask that. You don’t ask young girls “When are you going to get married?” unless you’re Mormon or Catholic, and then it’s perfectly fine; you’re expected to have it and, you know, there are certain things we do as an enterprise we wouldn’t do as a family or as a friend.

Michael Coté: Right.

Chris Dancy: And I just think if we go to an enterprise and just like pretend we weren’t brainwashed by craziness for years and just say, “Would I ask my mom this, would I ask my wife this”, right? So you said, “When are you going to add this new thing?” That’s like saying to your husband that drinks, “When are you going to stop drinking when you come home from work?” “Well, when I don’t have to go to work to support the fact you over-shop.” This is real simple stuff, people. We should also be in psychology class, not ITIL 3 foundations.

John Willis: Right, well, I mean that’s the whole — I know we talk about the DevOps. We just did a podcast before this and, I mean, I think that’s part of like you know what you are talking about, like somebody to be able to start thinking about social objects, right? These are the kind of rip-it-apart thinking that the enterprise is going to have to do, right? It’s no longer just to buy a mainframe because IBM sells one, you know what I mean? That may or may not be the right choice, and just because they’ll sell you one and you bought one last time, you’re going to get the new one this time, and we’re going to go with AIX again next time. You know what I mean? I think again it goes back to the whole economic side there that your competitor may not exist yet, you know what I mean, and they are not going to have -– this is what’s happening in the whole WebOps world, right? Theses companies that they don’t have all these preconceived notions of the way you have to run a business, right, or the way IT has to be, right?

And I think DevOps is part of that, too. Like if you went right out of college and you went right to work for a large corporation, you would think there should be a wall between developers and operations.
(00:45:15)
Like, wow, I don’t get it but… 45:24 now. They’ve been doing it for 15 or 20 years, so they must know what they are doing, And 5 years later you are like “Well, that’s just the way it is”. I mean, that’s — when you are training the new guys that are coming in, “No, no, that’s the way it always worked”.

Michael Coté: So the upshot is anyone who has access to a service desk, they should probably file a ticket to ask why they run the service desk the way they do, right? Can we get a little like self-referential stuff here? Like everyone needs to start sending in tickets requesting that they evaluate the way that they send in tickets.

John Willis: Yeah, but nobody ever looked at it; they’ll never get close, so…

Michael Coté: (Laughing.) That’s right, the system will defeat them. Fantastic.

Chris Dancy: I think if you wanted to learn about IT in 2010, all you need to do is go back and watch “9 to 5” with Dolly Parton and Lily Tomlin. You need to smoke a little bud, you need to get rid of the boss, tie him up in his mansion and you need to allow people to work when they want, where they want, how they want, any which way, and forget about everything else. Watch profits soar, let the boss back in, let him take credit for everything, and you are a little bit more mellow and things have gotten back.

John Willis: I love it. Yeah.

Michael Coté: Yeah. You know, I re-watched that movie recently, and I think you are right.

John Willis: That’s great.

Michael Coté: I think using upward promotion to get rid of troublemakers is a… it’s not that it’s underappreciated because it happens a lot. Well, it’s like The Peter Principle or whatever; but it definitely is a nice tactic to send them to the —

John Willis: Well, that’s another podcast.

Chris Dancy: I don’t even remember that movie, it’s been so many years; but, I mean, it’s —

John Willis: Oh, come on.

Chris Dancy: Honestly. When I watched that, in the ‘70s I think is the last time I watched that movie. So…

But anyway, yeah. The thing is is that that is kind of what’s happening is people that are having this kind of attitude of do not ask if you get in the slave attitude, the if I build it, they will come. And I think that’s to me some of the exciting stuff for the people that aren’t waiting for the CIOs.

I mean, I think I’ve told this story on here, but the Best Buy story to me is like the greatest do not ask forgiveness later where the guys who built the Blue Shirt Nation stuff, right, they just decided to do it, and they even — like I saw an interview with them where they said if they would have asked permission, they would have gotten shot down. Their success in building a content-management system for all the store employees, they could start sharing their knowledge about the business made its way into the Board where the Board decisions were “Have we checked with the Blue Shirt Nation on this one yet” from guerrilla to like where the Board was actually asking “Should we do this without checking with them first?”

I think that that’s part of the culture that’s changing is people are just figuring out, “Hey, I can fix this now”. It is the Dolly Parton thing; it’s like “I am not going to ask, I am just going to do it”.

Chris Dancy: Yeah, because we need more stories. We need people sharing more stories of success like you just defined. The problem is when I hear those stories, they are treated as like sightings of the Loch Ness Monster or the Chupacabra. They happen more often than we give them credit; but, again, there would not be a whole of happy unemployed IT people if we allowed everyone to do this free thinking. You said, “If we build it, will they come?” I often tell people social networking, social objects and social media is all about letting someone else build it and then be there because they built it.

You know, the community we have around my organization, you know, we didn’t set out to do what we did; we let the community build us and decide who we were and what we were doing and what we were selling. Why is that such a bad idea? Why do I need a plan? I’m sorry, Mom and Dad, you were wrong.

John Willis: Yeah. Well, I mean, that is the Blue Shirt Nation. I mean, what happened was they were just trying to solve a simple problem, like they didn’t want to travel to all the stores to get all the feedback. So but before long they had a database of knowledge about their business that it turns out this Blue Shirt people that were in the stores were they’re sweet spot or we’re basically their demographic for sales. They were all 18- to 25-year-olds who liked to buy geeky stuff, and they all started talking about “Well, I would never buy this” or “When we put this on this shelf, it went like hotcakes”.

Michael Coté: Yeah. I mean, it’s that same thing. One of those things I always come back to is no one expects the IT department to be helpful (laughing). So they don’t even think like we need to figure out what all of our — I mean, the Blue Shirt one highlights this as a counter-example, right? But we need to figure out like what people’s reaction will be to this. Maybe the IT department could tell us what to do — or not tell us what to do, but maybe they could help facilitate doing something.
(00:50:11)
John Willis: Well, I think that’s where the IT department have to be the guys that either — you know, again, I see a lot of this whether it’s right or not is that they are just going to build it and they see it working in other places — and the cloud has been a classic story of just guys going out and getting cloud resources and then just saying “Heck, I am just going to do this because there’s no other way to do this”.

What happens, how many times have you guys seen where you talk to a guy and he’s talking about some project and he’s put in a phenomenally impossible position? “We want this in four weeks, but we are only going to give you enough resources to get it done in eight weeks”, and “They’ve only given me 10,000, but it’s going to cost 20,000, but who cares? Get it done. It’s your job’s on the line”, right?

I mean, people are faced with these kind of things all the time, and I hear from people like “My management has told me I have to do this; they have no clue, they are telling me I have to have it done by this date”. And so these people are finally just throwing their hands up and saying “All right, they want me to do it, I’ll do it; here’s how I am going to do it. I am going to go out, I am going to get some cloud, and I am going to do this and I am going to do that”, and almost nine out of ten times they don’t get fired because they are successful, and everybody looks at it and says “Ooh, you probably should ask; but, wow, that’s pretty cool”.

John Willis: (Laughing.)

Michael Coté: Yeah. Earlier this morning I had a little… I don’t know what you would call it, a sort of relationship epiphany where I realized if you are going to ask your partner or spouse or whatever you want to say to like do something, just like a good manager would do, you have to make sure to give them time to accomplish that task. And I feel like that that little bit of giving time or being realistic in what you assign to people is always… an effective manager does that; but even like normal managers usually to your point, they don’t really realize, they don’t take into account the time and resources needed to accomplish what they want. They just want things accomplished.

John Willis: Oh, because their managers are giving them unrealistic expectations (laughing).

Michael Coté: Yeah, yeah (laughing). There you go, the unrealistic-ness rolls downhill, as it were.

Chris Dancy: But again, you’d have a more successful project if you had more people playing in it, and you’d have more people playing in it if it was open for anyone to play in.

Michael Coté: Yeah, I know. I think that’s what’s interesting about layering this social level is it breaks down the downhill/uphill pattern and has like some other avenues for unsatisfactory and for whatever things to run around is that… I don’t know; like I feel like in these kind of situations when IT is asked to do something unrealistic in isolation from the rest of the company knowing about it, then it’s easier to fail because you don’t really have that community backing you up, right?

And to be totally tangential, right, like I remember one of my old philosophy teachers said one of the problems we have in society nowadays to be that kind of guy is that shame isn’t really used as much as it used to be. Like shame, you could put someone in stocks in the middle of the town, and it was very shameful. So you could use shame as a very nonviolent tool to get things done. And whenever you are acting in isolation, like the shame of being unrealistic doesn’t occur to someone who is asking you to do something unrealistic because no one knows they are asking, whereas if you had this more social thing, then hopefully that would be one avenue in which you could realize that just crazy stuff is happening and maybe you should poison the boss and tie him up, as it were.

[Laughter.]

Male: [Singing.]

Michael Coté: Well, see, I’ve had a real issue with this episode, because you have given me so many great titles that I can use. I mean, we have got My Panacea of Fantabulousness, and we have basically got like The Dolly Parton Strategy for IT Change. And there’s a few more, so it’s going to be very difficult to pick out which one to use.

[Laughter.]

John Willis: Well, hold on, now.

Chris Dancy: We are going to split it down the middle, buddy. I was planning on taking a few of those myself, so… .

[Laughter.]

Michael Coté: We’ll have to dole them out.

Chris Dancy: Yeah, yeah; no, yeah.

Michael Coté: We don’t really want to do this doling out in isolation, because then there might be some shenanigans with it. When you do it, I’ll —

John Willis: I think your Fantabulousness, I want the Dolly Parton “9 to 5”.

[Laughter.]

Chris Dancy: You can’t wrap up yet. Michael I met you, I missed my Cote-versary because I met you last year in person at itSMF.

Michael Coté: That’s right, up at the lovely Gaylord Houston — no, in Dallas, right, which I fly over frequently when I am flying into DFW to make a connection; so it’s funny that I see that so often. But, yeah. So I was actually — and we talked about this in the podcast — I guess this is one of those… well, I don’t know what it is. But the itSMF thing that I went to in Dallas, it exceeded my expectations, which I don’t know what that means necessarily. But I thought it was a lot better than I thought it was going to be. And you know it’s kind of a bummer I missed the one this year. But what happened with this one this year that was in Orlando — or was it with Louisville? That’s right, Louisville.

Male Speaker: Louisville.

Michael Coté: Isn’t that what I said? How was it? Did they have a Gartner guy come in and talk about the need for transformation and things like that like last year?

Chris Dancy: Oh, yeah, yeah; yeah. You know what I was amazed at the meeting was they used “Gartner” and “Maturity Model” in the same sentence. But basically the vendor hall was —

John Willis: I love you. I love you, dude.

Chris Dancy: Thank you, dude. So basically the vendor hall — well, it was really funny — by David Coyle from Gartner walked past me, and I obviously over the 18 months I have been in business have become more visible to him. So he looked at me and shook my hand and goes, “Hey, how you doing?” like he knows my name. It’s like “Hey, it’s Chris Dancy.” “Oh, yeah, yeah, I know, I know.” And I said, “Shouldn’t we soak?” He said, “Why?” I said, “We just shook hands” and he just kind of left me.

[Laughter.]

Michael Coté: Always courteous.

Chris Dancy: Yeah, I am always courteous. Well, you know, they are not going to — I asked him, I said, “Dave, when are you guys going to start tweeting or doing something?” “We are working on our strategy.” “That’s what you said last year. You have a 12-month strategy for social media, and you are supposed to be a leading analyst? Shouldn’t you be doing?” Wax on, wax off there, David Coyle.

Two things I thought were interesting about this year’s conference, one, the vendor hall basically had no one in it, which kind of leads me to think the days of these big tech conferences are officially dead, almost, you know, it’s product-centric. Service-now seems to be doing okay with the conference for their folks — and getting their own customers to pay to come to their own conference, which blows my mind.

The other thing I thought was amazing was HDI, which is kind of like the traditionally thought of — it’s not true, whatever — thought of as the helpdesk people, announced that they were merging the two fall conferences. So instead of there being one HDI conference and one itSMF conference, itSMF basically threw their hands up and said “Ah, we can’t do this any more. There will just be one conference run by HDI”, which to you guys probably isn’t a big deal; but people in my little space, I don’t think they realize the major shift in power that just happened. So it’s going to be an interesting two years, because that’s the length of the agreement.

And then today itSMF USA and a secret closed-door meeting that was tweeted about and then deleted but I saved the screenshot of the tweet, you know, laid off three of their staff, and they have only got a staff of five.

Michael Coté: Right.

Chris Dancy: So you look at ITIL’s Flagship Fan Club Foundation, itSMF, and you see what’s going on with it and go “Well… .” But still I don’t get how people just spend bucket-loads of money on ITIL training and — oh, well. So that’s good.

I got an award, I wanted to mention that; that was nice. The president of itSMF USA gave me the President’s Award. I don’t know, I think it’s because I called them out on tweets and offered something. But, no, it’s a big deal, and I am very, very honored and look forward to getting an award next year from HDI/itSMF/whatever the big conglomerate will be.

Michael Coté: Yeah. Well, you know, I mean, like I remember going and thinking this is like one of the only conferences I have been to where they are actually talking about… for better or worse, where they are actually talking about like doing service management and things like that. And it is like… I don’t know, it’s like with as much like fabulous like, you know, The Panacea of Fantabulousness that we have, as it were.

Chris Dancy: Yeah.

Michael Coté: It is still difficult to kind of track down. There is only a handful of people who kind of talk about that on a regular basis. I mean, there is folks like yourself and the IT Skeptic and like people here and there; but there is not… I don’t know, I don’t feel like for all the talkers of cloud —

Chris Dancy: Well, we don’t get invited, we don’t get invited to your fun conferences, right? I think the only service-management guru you are going to get at Oracle World is somebody who is like an Oracle person. At CA, you are going to get a CA person, maybe Meghan Stabler, who is also from Austin. You know, you don’t get these kind of independent freethinkers, which leads me to the question that I asked you on my podcast: When do we get our RedMonk Conference?

Michael Coté: That’s right (laughing). We should do one of those. You know, the issue is — and I have probably explained it at that time, too — is we can barely like handle like getting ourselves dressed in the morning, and so we definitely… we are continually looking for someone who can kind of take on the actual helping us get dressed in the morning when it comes to conferences and doing stuff, which that’s my excuse and I am sticking to it. But you know, it would be nice to like bring together… I mean, the thing in this podcast that we come across again and again is like there is new ways of doing IT, and there is just this like big hair ball of crap preventing people from even thinking about doing it that way.
(00:60:08)
And, you know, we won’t go into a lot of nice detail here in this episode on it; but it’s just frustrating, because I don’t think people necessarily are very excited about the way like service management is being done at moment, despite the fact that it may be compliant and you’re following process and things like that; but there is not a… I don’t know. There needs to be some sort of more better driving force of change, the driving change and innovation in the area.

John Willis: I was just going to say you said you went to the conference, and that was one of the few places where you saw people talking about doing IT service management. I always tell people you don’t kind of do IT service management, like you don’t do library. You go to a library and you perform an activity, and you leave, right?

So service management is something, it’s not a destination or a journey; it’s a roundtrip ticket, all right? It’s a relationship between you and someone who needs or desires you or your services and what that little mini-quick date looks like, right? Real simple stuff, you know.

Michael Coté: Yeah.

John Willis: Take speed dating, right, and apply it to -– again, I’ve got another tweet scheduled to go off; I’ll start deleting all these, now I’ve been on the podcast. I think service and every service should think of themselves as an app that’s going to be rated or passed over based on cost and whether it’s useful or not.

Michael Coté: Right, right, instead of an essential cemented-in thing, essentially, right? I mean, it kind of gets back, or at least it seems to get back, to something you were talking about. You were saying earlier that ITIL kill the innovation in the service desk, right? And what that seems to implies is so here is the way IT is run, and if you run it that way you’re done. You don’t ever have to think about it again (laughing). And then that probably —

John Willis: Well, the thinking, they put a framework around — they put a framework of inflexibility around something very fluid.

Michael Coté: Right, right, right. I mean, I don’t know if it’s in there somewhere; but they forgot there is Orwell’s famous Rules of Writing, right? And it gets duplicated any sort of like polemic ruliness stuff. And the last rule is always like feel free to not do any of these rules if it makes sense. and I always feel like whether it’s like Agile or ITEL or the Rational Unified Process or anything, like that rule is usually in there somewhere; but it usually is the first thing to go, which is kind of not very wise.

Chris Dancy: Well, dude, it’s profit motive. I mean, I don’t know why we all beat around the bush. Service management is nothing more than profit motive. It’s like Wall Street run amok, right?

Michael Coté: Oh, yeah.

Chris Dancy: There’s too much money to be made in teaching classes, putting in software and managing infrastructure for it to die. I mean, it’s dead; it’s basically a zombie that can’t be killed unless you cut off its head, and what is its head? The CIO. So what do we need to do? We just need to flush the CIO. I don’t know. I mean, I’m just being over the top; but again, you know it’s never going to get fixed. We could have a million podcasts all day long. The only time it is going to be fixed is once Core-Mac is chipped and he can get what he wants when he wants from the best provider by thinking about it.

Michael Coté: Yeah, yeah. We just need to have to some good old-fashioned disintermediation.

Chris Dancy: Yeah.

Michael Coté: That’s exciting. Well, I think that’s a good place to wrap up. Speaking of Core-Mac, I think I’m supposed to go get his passport before the post office. Talk about a system that you need to fix up, man, getting a passport? Not cloud-enabled, I’ll tell you that right now.

Chris Dancy: How do you get a passport for a baby?

Michael Coté: Well, you just bring sort of proof of parenthood-ship and you take a couple of pictures of him, and then you go to the post office and that’s it, and then you wait.

Chris Dancy: You’re kidding.

Michael Coté: That’s kind of how it works out. Yeah, it’s pretty simple.

Chris Dancy: Hmm. Okay.

Michael Coté: Yeah, the funny thing is like a lot of these processes, there’s sort of a minimal amount of paperwork that you need to do; but there is a whole lot of waiting and uncertainty and unhelpful websites telling you what you need to do. But what are you going to do? There is no way to Like or Dislike a passport-service thing.

Chris Dancy: Not yet.

Michael Coté: That’s right (laughing). Well, on that note, thanks for -– I really appreciate you being on the episode here and putting up with the trying technical difficulties we had before. I tried to file some service-desk ticket with the RedMonk service desk, but I’m still hunting down where that is exactly. But, yeah, it was great. I think we had a fine episode here. And why don’t you tell people where the ITSM Weekly, the podcast, can be had if people want to see that or listen to it?

Chris Dancy: Yeah, so you can catch my podcast on iTunes. You can just search for ITSM or ITSM Weekly. You can get it at my blog, servicesphere.com/blog; we’ve got it there. We just launched a Rest of the World Edition, which is recorded out of Europe, which is always interesting; but they think they are the rest of the world. So, yeah, those are the two places to check it out.

And by the way, I said it before, I’m going to suck up again; I love what you guys do. You guys are inspiring to be kind of radical thinking, and I appreciate that.

John Wills: Well, for me, it was a blast. You know, I took about a page worth of notes with the guest; I know I had a good time. So it’s good stuff.

Michael Coté: So there you go. Go subscribe to Chris’ podcast. It’s good stuff, I listen to it myself, and we’ll see everyone next time.

Disclosure: see the RedMonk client list for clients mentioned and relevant folks.

Categories: Cloud, Enterprise Software, IT Management Podcast, Systems Management.

Tags:

"What's hot right now?" 3 Tech Picks

Eggs

I’m often asked “what’s hot now?” And why the hell not? I was asked most recently by Issac Roth at Makara at the Rackspace SaaS Summit during lunch yesterday. My focus tends to be more enterprise-y than consumer (I don’t spend too much on the cadre of “some dot com will buys us” business models).

Here’s what I generally tell people, expanded out beyond what my mouth can usually produce:

  • Cloud Computing – I spend a lot of time talking about this with folks, both on the buy side and the sell side (vendors). Vendors are all trying to ride the wave of cloud interest (cheaper, faster, more agile) and have either come up with genuine offerings or shimmied what they have (virtualization, management, etc.) into that category. Cloud is mostly understood to be “public” (Amazon, Rackspace, and the rest) or “private” (using cloud-inspired methods and technologies to run behind-the-firewall data centers). Most vendors recognize that the easier money and (more importantly) customer retention is in private cloud. Folks universally agree that Amazon is ahead of anyone else the public cloud space, and there’s some uncertainty about how much of the private cloud elephant companies can eat in 12 month transformation project chunks. Another thing I should write-up is the huge interest telcos are having in IaaS cloud technologies: these guys have piles of infrastructure they need to protect from Amazon & co. and seem to be going crazy buying IaaS clouds. For example, see the recent moves by KT with involvement from both Cloud.com and CloudScaling. And there’s starting to be action on the other end of the dumb pipes.
  • Mobile app development – developers I talk with are obsessed with the iPhone/iPad, or “iOS” as Apple has mercifully re-labeled their category. They’d love to develop for Android, which they feel is more open and “right” than iOS, but the gold rush is in Apple-land. While Hacker News might vote up a story every quarter pointing out the actual pennies on the dollar revenue in the Great App Game, developers still see the chance to cash in. These desires drive interest in mobile web (using web technologies for native apps or delivering mobile web apps), and a wider acceptance of the app store idea in (completely) different domains. Apple and Android dominate here: little is said (aside from a few snickers here and there) of Nokia, Samsung, MeeGo, Adobe, Microsoft, RIM, etc.
  • Elder Companies go Cocoon – the big tech companies like IBM, Oracle, HP, Microsoft, Cisco, and even “young folks” like VMWare are going bonkers with consolidation, portfolio shake-ups (“hey, we’re Cisco, wanna buy some servers?”), and otherwise doing something beyond collecting their tasty revenue streams. These companies used to have their ecosystems staked out, and then Cisco came along and started eating from HP, IBM, Dell, and other hardware folks’ buffets. Throw in Oracle buying Sun and recasting their story as Oracle vs. IBM along with Tennis-buddy-gate, some Java custody battles, and there’s just hijinks aplenty. The question here is where everyone will land, and what parts of the market each vendor will carve out for the next 10 years of boring but highly profitable revenue streams (for example, Dell has a window of opportunity to move into high-end servers). Scrappy youngin’s are hoping the new age of cloud and SaaS will just eat all the old folks lunch, and I sure like their optimism. It’s adorable.

Others

These are just the top three, at the moment. There are other longer-term hotnesses out there, and ones deeper in the stack, to pick a few:

  • Big Data/Analytics is a huge ice-berg floating out there. NoSQL is a sort of sibling here.
  • The possible demotion of the desktop/laptop as the primary computer device in favor of smart phones, tablets, and even Internet-connected TVs can piss away of hours of day-dreaming.
  • Figuring out sales and marketing automation to start using the web as a core store-front (or “point of customer engagement,” if you prefer) is taking over ISV go-to-market, and even getting some traction outside of tech. If you Google for everything, don’t you think your customers do too?
  • The great on-prem to SaaS rewrite is a bundle of cash, time, and fun waiting to happen if buyers can get over cloud-FUD and ISVs can figure out the business models behind it beyond those “we have to do it” imperatives that don’t quiet work in spreadsheet columns.
  • If you’re into this kind of thing, the open source world is oddly rudderless at the moment. Many of the same parties are still there, doing The Lords Work, but all this cloud and mobile business has shifted attention – and, more importantly, open source has gone mainstream, it’s how software is done. (And don’t even start on standards bodies. OAuth anyone?)

While that’s what I see at the moment, what are you, dear readers seeing? What do you spend your time thinking about?

Disclosure: IBM, Microsoft, Dell, Cloud.com, CloudScaling, Adobe, and VMWare are clients.

Categories: Cloud, Enterprise Software, Marketing, Open Source, The New Thing.

Tags: , , ,

AppMatcher.com – Rackspace SaaS Summit

AppMatcher: Poultry Slaughtering and Processing

Rackspace got into the app store/marketplace space today with the launch of it’s AppMatcher service. You fill out some corporate demographics – type of company, number of employees, budget, and features needed – and AppMatcher tries to suggest SaaS applications to you. The fact that eHarmony was one of the presenters today gives you ample metaphor to understand the app-matching Rackspace is trying to do.

The idea is nice, for sure: as Rackspace’s Andy Schroepfer said during the announcement, getting found is key to the (now) crowded SaaS and web app landscape. This problem exists in spades in the iTunes App Store, where app developers carp like 49’ers who can’t find their claim among the crowded creeks. At the moment, AppMatcher claims to be serving up 1,000 apps, which is a lot to whack through. While it’d be easy to restrict the apps to ones running on Rackspace, it looks like they’re going to open submitting apps to anyone, no doubt following the “grow the pie, and our slice is bigger” strategy made famous by Google and all it’s Internet freebies.

In the pre-iPhone era, I would come across market places like this a lot (folks like JackBe and JamCracker come to mind, if only tangentially). It was always a tough row to hoe, but the iTunes App Store has changed that perception.

Success Elsewhere

To add in some context, one of RedMonk‘s clients MindQuilt was recently featured in the Google Apps Marketplace, resulting in 15% sign-up growth over a few weeks (for a 30 day free trial). Their CEO Dan Kim also pointed out the quality of the leads and, thus, feedback they received too:

…the google apps sign-ups are coming in with a particular use-case and problems in mind, so they been very vocal re: feedback… something that’s really valuable to a Startup trying to evolve and pivot and find market fit.

Over half of those companies have given very in depth question and feedback as opposed to the general group which only about a fifth of them bother to send us feedback.

Clearly, it pays to be on the endcaps of the cloud.

More

Disclosure: Rackspace is a client, and, as mentioned, so is MindQuilt.

Categories: Cloud, Marketing.

Tags: , , , , ,

Links for October 3rd through October 6th

Happening right now

Disclosure: see the RedMonk client list for clients mentioned.

Categories: Links.

Telco clouds, dev/ops, Andrew Shafer guests – IT Management & Cloud Podcast #81

We get all dev/ops crazy when Andrew Shafer joins John and I for this episode of the IT Management & Cloud podcast, #81.

Download the episode directly right here, subscribe to the feed in iTunes or other podcatcher to have episodes downloaded automatically, or just click play below to listen to it right here:

Show Notes

  • Andrew at CloudScaling.
  • We talk about telcos and service providers wanting cloud stuff. As a quick example, see CloudScaling’s work with KT.
  • What are telcos looking for from cloud?
  • Andrew: “we need to automate the bottom.” What do the “commodity boxes” look like, though?
  • James Hamilton talk at Velocity (video or audio only) goes over how he handles this stuff.
  • Optimizing to the meat-level – “it’s all about the math.”
  • Andrew: if you want to do cloud, you need commodity hardware, open source [cloud] software, and a WebOps culture. What’s the software used here.
  • Why is open source so important here? Flexibility, adapting to change – having to re-write your stack as things scale.
  • John’s been going to a lot of dev/ops days – how’ve those been going? Check out the round-up of videos from devops days US from Damon Edwards..
  • Web Operations book, mentioned by John several times.

Transcript

As usual with these un-sponsored episodes, I haven’t spent time to clean up the transcript. If you see us saying something crazy, check the original audio first. There are time-codes where there were transcription problems.

Michael Coté: Well, hello everybody it’s the 4th of October 2010 and this is IT Management & Cloud Podcast, number 81. While John was away I slipped in a number 80 with a special guest. So, now we don’t have to worry about the awesomeness of 20 X 4 as it were.

So with that, silliness aside, this is one of your co-host as always Michael Coté available at peopleoverprocess.com.

Andrew Shafer: I think the proper nomenclature is for Four Score Cote.

Michael Coté: Oh, Four Score that’s right. And as you can tell, we’re joined by a guest, old long time listeners may recognize his voice, but do you want to introduce yourself before the other co-host?

Andrew Shafer: I suppose. This is Andrew Shafer and I have been on this show. I missed the transition, when did you add & Cloud to the podcast?

Michael Coté: Well, it just seemed appropriate, because we spend a lot of time talking about that.

Andrew Shafer: Because IT Management & Cloud, those are way different topics.

Michael Coté: Totally. Well, you know what we’re going to get into some of that, but first, let’s introduce the co-host.

John Willis: The unannounced co-host guest disagrees. My name is John Willis at [email protected] and can be found also and at [email protected].

Andrew Shafer: Can we make the IT Management & Cloud Comedy Hour?

Michael Coté: That’s a lot of pressure to be funny.

Andrew Shafer: Yeah, it’s better not to say you are funny people, think you are funny, but —

Michael Coté: It’s all, you know, that there is —

Andrew Shafer: We will go understated.

Michael Coté: You know, while we’re on the meta conversation here, there is a lot of lessons I’ve learned in doing podcasts over the years. And the number one lesson is, never put anything that implies regularity in the title of your podcast, like weekly or daily or something like that.

And I think, another one — it’s a little further down the list, but you definitely don’t want to have a conceit that you are funny, because then you have to try to be funny. I think that’s a good one John.

John Willis: Well, are we funny? I didn’t even think we were funny.

Michael Coté: No, no. This is a very serious podcast dealing with things like —

John Willis: From now on, we’re very serious, sorry.

Michael Coté: You know, it’s dealing with things like ITIL and the process and basically what we’re dealing with here John and Andrew is aligning IT with business and there is nothing funny about that.

John Willis: Well Cloud is pretty serious stuff, and particularly when you marry it with IT Management.

Michael Coté: Exactly I mean —

John Willis: It’s not a laughing matter, it’s not a laughing matter.

Michael Coté: So speaking of things that aren’t a laughing matter. Andrew, so you know, I think since last time we — I don’t know talked on some recordings and you’ve been working at a new place Cloudscaling, you want to just give us a quick overview of what’s going on there?

Andrew Shafer: Cloudscaling is helping service providers and Telco’s transition to the cloud service model for their businesses.

Michael Coté: And so you know, how my predilection is to always get like the most basic things to find. And so, like I think — well I don’t know like, tell us what exactly like, what are Telco’s and service providers? What does that mean in this context exactly?

Andrew Shafer: Well Telco’s, we can pull up the Wikipedia article, but you basically have a bunch of companies that have businesses built around providing landlines, mobile, these networks for the 3G, 4G, all these services that have been provided for the last — I don’t call that space as much as I probably should now, but they’ve been packaging, hosting, you know, every little Telco has a web hosting package, I think. I mean when I usually see them, I don’t consider them for my personal business, but you see lots of these all over the place.

John Willis: Well Andrew, could you explain for our listeners just since we’re doing this what 3G and 4G means as well?

Andrew Shafer: When you look at your iPhone and it says edge you’re doing it wrong. Okay, there you go. Sorry.

Michael Coté: I think to pull out the sometimes less than obvious point of Telco’s is that, there is a kind of, there is all the consumer based Telco stuff. I mean everyone knows about AT&T. So I think, the somewhat less than obvious point of Telco’s, especially in the context of cloud stuff. Like you were saying, they all have like websites and they’re all like doing a lot of — providing services to business and stuff.

So, most people of course encounter Telco’s on the consumer end when they’re using their Internet and their voice connection and all that crap, but there’s a whole bunch of — they make plenty of money just providing Internet and data and voice and all sorts of other stuff to businesses and then more importantly running web stuff for them.

So, there’s a lot of stuff going on, the service provider or a managed service provider or a Telco or a carrier, however you want to say it, where they’re basically trying to kind of scrambling to get the software that allows them and basically get their own clouds, so that they can continue providing these services rather than that stuff going off to Amazon or Rackspace or other people.

Andrew Shafer: So, if we back up and just sort of think about this space and the evolution and you guys have been watching this real time for the last few years. There is a class of businesses and services that are being for lack of a better word, is the word I would use is, disrupted. And people that are in those businesses are highly motivated to find some other way to provide value, to create value.

Michael Coté: Yeah, definitely. And anecdotally there are several cloud people that I’ve been talking with recently and they’re seeing a lot of — they’re getting a lot of sign ups through Telco’s if you will.

So there’s a lot of interesting stuff going on there and one of the funny things that I think is, kind of, I guess cloud counterintuitive about it is, originally there was this idea there is one, maybe two or three clouds or whatever, but if you think about what’s going on here, all of the existing Telco’s are trying to make sure that there is hundreds if not thousands of different clouds out there, which is kind of a subtle, but big shift of kind original cloud thing, but we’ll, I don’t know we’ll see how this stuff sorts out, it will be — for people who get excited about the words like Telco’s and service providers it’ll be interesting to see how that disruption plays out over the next few years so.

John Willis: Well you guys from an age that you might have a perspective on this, but imagine if there was only one telephone company.

Michael Coté: Yeah. There used to be a long time ago. I mean you could get like getting a pink phone was considered a feature.

John Willis: Those were good days.

Michael Coté: That’s right, yeah. No, I mean there is a — that is like the idea of monopolistic effects on technology innovation is something that is kind of a bird in the UniCloud theory.

Andrew Shafer: Well, the other thing I think is, what I’ve been seeing from the — and I don’t have as much experience in a Telco, but is that their whole playground is some much huger, right, because of all the web apps that are now mobile apps, right. So like I remember talking to one of the big Telco’s about like, they were just building their clouds so that partners could develop their apps and test them and get them to production, kind of like a pre-built app store, for their particular brand. So I think that even drives more so why they need some type of kind of private cloud infrastructure.

Michael Coté: Yeah and along those lines so like in —

Andrew Shafer: They’re public, I mean really what you’d like as a Telco I think is to be able to package these things that’s the — the Telco space right now, you’re not competing, minutes or minutes, you’re competing on the way you could package things. So if you could put together a package where you could give someone their business, their phones, their Internet connection and also oh, yeah here’s this thing it is sort of like Google App Engine or Heroku or whatever and you can power your mobile apps with that, like that’s a pretty good package or compelling service maybe.

Michael Coté: And like are there other — I mean is that — what are kind of like the requirements you’re seeing Telco’s and service providers have for their cloud software. Like what is it they are looking for? Like obviously, like you just said, there is that ability to package, to bundle things up right. So the technology has to be vulnerable.

Andrew Shafer: So there’s the actual — there’s the story and the narrative and the packages and the pricing and then there is the technology. And I think that there is a lot of people in this space, because cloud is so undefined and people can define it however they like. For example, the Oracle World Keynote, you get up and you say everything, nothing is new, there is no such thing as cloud, oh yeah everything we do is cloud and that’s put people in a position where it’s very difficult for them to be able to make good decision about things.

Michael Coté: Right.

John Willis: And I think right now for the Telco space, the service provider space, there is a little bit of a danger, because — and this also applies to some degree to the private cloud space, but if you think you’re just going to install cloud and then run it in your data center like you do your switches, then you’re setting yourself up for a little bit of a hurt.

Michael Coté: Yeah. No I mean this is like completely like off the top of my head theoretics or whatever right, but I always — I get the sense that it’s almost like running your own private cloud is just as much hassle as running what you already had. And so, like if you’re really going to like run your own — if you’re going to do this big transformation where you’re running your own private cloud, you have to really be certain about what it is you’re getting after all of that trouble.

Andrew Shafer: In some ways it my actually be worse, because you still have all of the overhead of managing the separate services, plus you managed to create yourself a nice little distribute single point of failure if you don’t do it right.

Michael Coté: Yeah. Well do you guys — have you been seeing any exciting Telco stuff John?

John Willis: No, not really. No I mean that’s the high end of our —

Michael Coté: Yeah, I mean and you guys are a little higher up the stack of needs if you will over at Opscode. So probably you spend your time doing things more in the application and like —

John Willis: Yeah, I mean we don’t see more of the media companies or bioinformatics, those types of things. It can be leading edge service oriented service, e-tailer type companies.

Andrew Shafer: So, I think some of this has to do with culture and we can certainly talk more about the impact of that in both directions, but I think it’s a ways off before the Telco’s and we’ll see how it goes and John and those guys can you know, try to prove this wrong, but I think it’s a long ways off before they’re going to be willing to let their infrastructure be managed and configured from something else, either a firewall.

John Willis: Yeah, I mean that’s another lengthy, lengthy discussion. I think one of the maturity things is to happen is, like you know if you think about private cloud, right. So private cloud pretty much — I mean I’m sorry, public cloud people buy into the — very easily buy into the you know, the kind of managing your infrastructure or configuration management from the cloud right, like which is what Opscode does, right.

And because you’re in the cloud already and I think and it’s more then that, the public cloud is more mature right, in terms of its delivery and all that. So, I think what’s happening now is the private cloud is still on that infant stage, right you know in other words, well they’re just trying to get the meat and potato stuff right, you know get instances doled out properly and allocated and managed with the infrastructure hardware.

They are not even ready to discuss how you might mange you know, end-to-end configuration and system integration. I think there is still another year or two of maturity in the private cloud space when they can lift their head up and say yeah, we do the whole provisioning thing really well now, all right. Now let’s look at what we have to do next or to make the higher layers of the stack, wouldn’t you agree Andrew?

Andrew Shafer: Well, I would agree. I think that everything you said is true, but for the stuff we’re building now, we need to automate the lower layers. We need to automate the bottom and cloud, you know, the promise of cloud and the magic of cloud notwithstanding there’s got to be metal at the bottom.

John Willis: Right, no. I think we’re saying the same thing, right. I’m saying there is still a maturity level of just getting the basics of what we would consider a pure cloud delivery.

Andrew Shafer: The majority of the problems that we solve with configuration management now are not on instances learning —

John Willis: Right, that’s what I said.

Andrew Shafer: It’s actual metal — configuring metal machines

John Willis: Yeah.

Michael Coté: And how is that bottom metal layer like working out, like is it — are you able to just like use like commodity boxes or do you need to get specialized boxes or like, you know, and this is another interesting kind of like counterintuitive cloud thing, because you know way back when it was supposed to be like you just use really cheap boxes and they are commodity boxes and you replace them and everything and then you learn that Google has their boxes custom made and people are having shipping containers of boxes.

And it seems like, nowadays like the public cloud storage you hear about, maybe their hardware is cheap, but it’s definitely not like I just go down to Best Buy and buy a bunch of servers, like there’s kind of like specialized boxes that people are getting to operate like this. And so like, what is the metal looking like when you’re building these clouds?

Andrew Shafer: That’s a very interesting question and one we’ve been giving a lot of thought to. Our strategy is to build on commodity, commodity hardware and the question you were just asking; we talk about the way Google and Amazon are building servers or Facebook or whatever, it depends on where you’re thinking the commodity lies.

So they’re putting together specialized for their needs, you know, configurations, opinionated configurations of hardware, at the same time, the building blocks that they’re using, they are not that different from what you would buy and consider commodity, it’s just of question what relationships do you have with your suppliers, with the manufactures and what leverage do you have.

If you go look at some of the stuff, James Hamilton’s talk from Velocity Conference for example. He at this point is analyzing and optimizing for every voltage drop from when power comes into the data center on the macro scale down to that the chips and the boards.

Michael Coté: Right. Yeah, I know. As an analyst, like, nowadays it’s very popular when you go to an Analyst Summit or Conference or whatever, to have the person come, it’s always been a guy I guess. So they always have the guy come out who is like the — who just like bombards you with data center optimization awesomeness. And there’s always lots of things like heat flow and like the environmental conditions and energy things like that.

And so, you know, I’ve seen this talk from Microsoft folks and IBM folks and pretty much all of the big industry people trot out the — we have that the data center guy sort of talk, which is kind of interesting to — I don’t know I mean it’s get back to this point of like, a lot of — to use one of my favorite old quotes like a lot of effort to went into making this effortless. And it doesn’t seem like it’s always like such a snap of an easy thing to do.

Andrew Shafer: So that brings up an interesting point. Some of the things you mentioned, the difference between Microsoft trotting out the data center guy versus Amazon, is Amazon runs a service and Microsoft runs some services too, but they’re not necessarily optimizing the same way James Hamilton is. Because he is looking at his own bottom line in optimizing for his service, where Microsoft has it’s — I can’t remember the quote, I’m sure I’m going to butcher it, but James said something to the effect of if you don’t know something exists and you’re not measuring it, then there is no motive for the manufactures to optimize that anymore than kind of like the crappiest level that they can to get by. So, he’s talking about in that comment I think he was making, talking about the power supplies sort of at the board and server level.

Michael Coté: Right. And is that, I mean that’s another question for you guys. I mean do you see a lot of people obsessing about power usage and things like that, because I certainly like — I certainly hear vendors claiming that everyone is obsessed with like power consumption and things like that, but I don’t always hear a tremendous amount and it’s probably just because I don’t listen to the right places but, on this topic, but I don’t know always hear a tremendous amount of people like you know saying that’s top of their mind or things they’re worried about.

Andrew Shafer: Well, we’ll just keep talking and I don’t pretend to have the perspective on this that someone like James Hamilton does, but at the end of the day he pretty convincingly proved that the big cost is actually servers, it’s actually the hardware and the power, once you get all this stuff setup on a day-to-day operating cost, that’s a smaller percentage. The servers are more like 50% to 60% of your cost and power is more like 20.

Michael Coté: Right.

Andrew Shafer: So while you — go ahead.

John Willis: No, I recently saw that I think it was probably was another survey not from him, but it was the same thing where the — it’s almost exactly what you just said, less than 20% release power and more like in the 30’s or 40’s as servers.

Andrew Shafer: I think the reason that people have the perception of power as the biggest cost is, because their server is already some cost and they’re looking at their monthly bill to pay the power, but if you take the server purchases and amortize them properly and do the actual accounting, then the server costs are significant.

Michael Coté: You know, maybe it’s also like virtualization and consolidation where — and you were kind of getting at this right, like if you don’t measure something vendors aren’t going to optimize it or no one will optimize it, because you know if you’re wasting power in the forest and no one knows then you’re not really, not wasting power.

Andrew Shafer: Well, the only other thing is — the only thing if you look at like an IBM’s perspective, right where they try to sell products to monitor power usage, you know they might be tool schools of implementation right. The James Hamilton school of implementation is, we run overall 80% of — you know we run 80% utility on the power and 20% SAP, whereas I think that a company that hasn’t address their power concerns could be just the opposite. So I don’t know if that’s in the play too, right.

Michael Coté: Yeah I mean and I think that’s what I was getting to, it’s like it seems like, like I was in Raleigh in one of the IBM cloud locations or whatever. They’ve got you know lots of crazy gold lead certified data centers and all this stuff you know, this was another instance where they trotted out, it was the data center guys in this case, you know they’ve got the heat maps and there’s all of these words I could spin out that I really know what they mean, like there are crack units for cooling air and all sorts of stuff and it seemed like basically what you do, is there is a bunch of wasteful dumb stuff that you’re doing with energy and then you kind of fix it.

And then to Andrew’s point, it’s kind of like that cost is controlled and there’s a just lot of waste that you can take care of. And so, to the point that once you solve that waste problem just like once you consolidate your servers with virtualization then, then there is other costs that become expensive, but it does seem like there’s just a bunch of waste happening to say that again.

Adam Shafer: So that’s a nice segue into another interesting point that I already — I pointed out in previous conversations maybe not with you guys, but certainly on Cloudscaling’s blog. When you look at James Hamilton’s analysis of cost, he has no mention whatsoever of the human cost, the headcount and I think that for the scale that he is familiar with and what he is dealing with then that cost becomes fairly close to negligible, but for most of these organizations they don’t have the same kind of WebOps culture, they don’t have the same kind of approach to automation that Amazon does and the headcount costs are actually significant.

And I think if you look at the cloud story and you really want to put this in perspective, that the advantage that Amazon has in this game, is not that they’ve figured out how to put a web service in front of a hypervisor, that’s trivial. Amazon’s advantage is that they have over a decade of experience managing a massive web infrastructure.

John Willis: Absolutely, totally, yeah.

Michael Coté: Yeah, it would also be, along those lines it would be interesting to compare the like, the total overhead and cost for an average employee between like Amazon and various Telco’s, right, because I mean not to get all like this guy, but like it would seem like with a lot of Telco’s they also have like pensions and benefits and all sorts of like historic things to deal with their employees where I would wager at Amazon.

They probably love that 401(k) business where you kind of like are cutting out a bunch of stuff that you have to pay for people and it seems like, I think coupled with the fact that they’re not automating stuff, so that older companies probably have a lot more employees. It seems like your cost do become — the human side becomes a pretty big cost and as a human myself, I always bemoan you know cutting out humans, but it does seem like that’s the kind of competitive environment you are in.

Adam Shafer: Well, I’m not — I think it a lot it has to do with the time when those companies were born, right. You try to optimize given the conditions that you have and certainly the notion, and I don’t want to get too financial or clerical here, but there has certainly been a transformation in the way that things like pensions and the way that employee corporation relationships have evolved in the last 20 years.

Michael Coté: Yeah. No I mean that kind of stuff is like the ultimate leaky abstraction that drives how much you have to charge for things and therefore like the availability of the technology that you can provide and it’s kind of interesting to track down to that level of things.

Andrew Shafer: Well, what’s interesting too, I mean last week I was in Seattle and I went over to Amazon had an open house at their new office or whatever and 00:23:18 gave us kind of history of Amazon, the business not just the cloud, but included it, it’s interesting because — you know I’ve got that Cambrian explosion presentation I gave where I talk about how Google kind of came to realization that they were, you know that where they were like when they were doing 15 million Euros a day and they saw the growth pattern and they knew that they had to drastically change the game, right. It just — the math didn’t work out the way they — you know there was no mainframe or super computer big enough to handle where they were going, so they basically kind of punted and went with, distributed CAP Theorem all the things we’ve seen from Google File System and Big Data or Big Table and I think Amazon —

John Willis: It’s all about the math.

Andrew Shafer: Yeah it is. Well I think that was the same things that, when you talk about Amazon doing this for ten years, you talked about kind of four phases of Amazon and first phase was a very kind of coupled stack, web database and then second phase was a service oriented architecture and then their third phase was WebOps, Webscale, what did call the Webscale infrastructure and now they are Cloudscale infrastructure, right.

So, I think that like at certain points when he was giving that representation, he didn’t say they used the math, but it was, you know they looked and they said. “gosh where we’re going, we’re going to have to do something completely different”. And they are the ones that kind of took a lot of the Google ideas with the Dynamo White Paper and all that and you kind of further push that eventual consistency of all the CAP not to get too nutty technical, not that I am even that nutty technical, but what they did is, you know if you look at Google had to change the game to deal with the math, Amazon changed the game to deal the math, you know what I mean, or drove that one step further and I think that —

John Willis: You choice is either to do that or to get crushed?

Andrew Shafer: Yeah and I think that’s the — I mean that’s the reality like again I think that’s every company now and like you’re saying the Telco’s right, in their own way they are doing the math, right and we’ve all had this conservation offline a hundred times. I say simply that there is ships sailing to the left and there are ships sailing to the right, which ship is your company on, right. And you better deal with the reality — you know you better do the math, how are you going to be able to do the kind of growth that your competitors may or may not be able to do?

John Willis: So to that ,point if you want be building a public cloud infrastructure and be competitive as a service provider, if you’re not going to build on commodity hardware, open source software and have a deep commitment to WebOps in your culture, then you might as well just fold your hand.

Andrew Shafer: I agree. I couldn’t agree with you more sir.

Michael Coté: And on that point like we talked about the commodity boxes like a little bit, but like what is the open source software that you’re looking at and seeing used, like what fills that slot, that bucket?

Andrew Shafer: Well, if you start at the bottom and you think about the evolution of the cloud again, going back to the story of the cloud, which I think we all sort of agree starts with Amazon —

John Willis: The story of the cloud.

Andrew Shafer: Yeah, there would be no cloud, there would be no cloud computing if it wasn’t for Linux. If it wasn’t for Linux, if it wasn’t for open source, hypervisors all this kind of stuff they would not be easy too. And then you just have complexity moving up the stack, right you look at all the — what is the — I mean outside of Microsoft and if you went to Velocity two years ago. There was a guy giving a conversation, I think I actually mentioned this on a podcast with you guys before, there was a guy giving a lecture on doing profiling on the .Net stack and he asked everyone in the room if they are running .Net and only one —

Michael Coté: Oh, yeah that’s right.

Andrew Shafer: And only one guy raised his hand. So up and down the stack, if you are looking at PHP, Java, Ruby, Python, all these things are open source. All these things, everything you need to build whatever you want at the bottom is open source software and then the complexity of managing, doing system management there is Puppet, there is Shaft, there is CF Engine all those, that’s open source, that’s basically an open source lineage of configuration management frameworks. There is monitoring, monitoring is the kind of bastard stepchild of web operations, but who is running 00:28:03 Open Source software.

John Willis: Is it monitoring management, Andrew?

Andrew Shafer: We’ve been through this, monitoring is not management.

John Willis: Couldn’t resist. Well it’s interesting this might be a little be segue, I’ve been kind of fighting my way through the – either fighting my way, I just don’t see that a whole lot of time, but I’ve been reading the WebOps kind of chapter by chapter and I just read the Eric Ries Continuous Deployment or Continuous Delivery chapter, that’s pretty freaking fascinating that whole process, so —

Michael Coté: Well, let me ask you —

Andrew Shafer: Actually let me — I want to continue the line of thought I had a just minute ago about open source.

Michael Coté: Yeah, well let me ask you along that line, like is it the fact that it’s open source that makes that stuff work or it is just the software happens to be open source and the software is what you want. Like, I mean you see what I’m saying, like does it matter that it’s open source or like what or is it feature side of the software that happens to be open source?

Andrew Shafer: I think it really, really that it’s open source.

Michael Coté: And so why is that?

Andrew Shafer: Well, that’s the line I want to pursue, I think not only does it have to be open source, there’s a spectrum of openness with respect to how the different projects interact with their potential community, with respect to how people can get patches accepted upstream, with respect, if you look at all the different Linux distributions, they all have slightly different motives and they have slightly different mechanisms for how they handle this.

And if you look at the evolution right now there is just — I mean without being too bias, there is a big difference between a open source project that you know if you submit a reasonable patch it will get accepted and that you know that you can go to the mailing list and you know you can go to the IRC and get answers and there is people there that want to see that project succeed and open source where you know, it’s VC funded out the gate and they have the open source, but you can’t really — it’s not really setup to build or accept patches or there is not a community so to speak, it’s what I’ve been — I said this a few times in other contexts, but I think of it as ornamental source where you can sort of see the source and it’s sort of there, but there is not not really the true commitment to that spirit of open source, it’s open in name alone.

Michael Coté: So, if I can pull out what I think you’re saying there, like one of the reasons open source is so important for a cloud stack if you will is that the sort of needs that any given cloud might have are different, not all clouds need the same thing or more importantly, the software you are using is going to have to change per sort of like use of it. So you sort of need a community you can go to that helps support and evolve the software you’re using to fit into what you’re doing and then even —

Andrew Shafer: It goes in both directions, you need a community but you also need to have your own ability to understand what’s going on. If you kind of go back to the story John just told about the transition. If you look at all these web services and cloud is let’s not kid ourselves, cloud computing is basically a big web application.

Every single one of them went through transitions where in order to scale to meet the demand, we basically had to rewrite their whole stack. I can’t think of one example where that’s not true. Amazon, Twitter, Facebook, everyone, Google or whatever, when you get to a certain point that the scale is the limitation and you have to rethink how you approach the problem or you’re not going to be able to provide that service at that scale.

John Willis: I’ll go one step further and I think you know I agree open source, I think it’s in general open right and you could argue the difference between just being open or open sources that I think the one thing we’ve learned over the last three years is if you’re going to be a company that relies on technology which is just about every company that exists now, you need to be nimble and you can’t be restricted in terms of the changes and your ability to change, right.

And so, the technologies that you choose have to be flexible, so you can’t like wait on a vendor, you know what you need to do is you need to adopt a base of technology that doesn’t block you, you know and then there is no guarantees but you need to put yourself, because you don’t know — I mean if you look how much has changed in three years and imagine you know what could happen in the next three to five years.

So I think that part of what you are explaining about the best possible scenario for me if I was going to build a private cloud I’d want to work on commodity hardware, I’d want to make sure the operating system is as open as I can get. I’d want to make sure the stack as I build on top of it, is as open as possible. So it gives me the most flexibility to adapt to change and different things that are you know it’s the unforeseen and the potential growth you know to control my own destiny and if I have to —

Andrew Shafer: I think it’s a question of what you are going to take responsibility for and I think what’s happened in the enterprise culture is they’ve sort of accepted a level of mediocrity and advocated their own responsibility for their infrastructure and for their applications to their vendors. And if you’re going to do that, if you’re willing to do that then you know, by all means go ahead, but if you’re actually going to try to deliver value as a web service, it’s one thing if your business is selling tractors and you’re going to build a private cloud or whatever and you know God bless you, but if you’re going to deliver a cloud service and you think you’re going to go build it with kind of enterprise mindset, then you first of all, do the math, you are not going to make any money. And second of all, you’re in for a lot of heartache.

Michael Coté: A nice tractor ride.

Andrew Shafer: Yeah, and the tractors are awesome by the way.

Michael Coté: Yeah, I think this has been exciting times recently, because there is all this cloud hype that’s been going around, people are actually like trying to compile it as it were and that’s when the you know like I was chainsawing this weekend and every now and then your chainsaw hit something and sparks fly out of it, and that’s fun stuff. That’s when the good stuff happens and if you don’t end up sawing your leg off then you know you get that tree cut and it’s good stuff.

But I really like all the — you know as the — I think you were using this metaphor before we were recording Andrew about the whole when the rubber hits the road or whatever and that’s what I’ve been seeing a lot recently so it’s nice.

Andrew Shafer: Yeah, I think you’re going to go or there has been like you know the DevOps stuff, DevOps days in the U.S. There’s one coming up in Hamburg, coming what is it a week, two weeks from now, yeah I lost track of that calendar.

John Willis: It’s two weeks from this week, it’s a week from this weekend, so it’s the following Saturday. I’m actually going to be there.

Andrew Shafer: So I think it would be great to be there, but I’m actually going to be in Africa. So I’ll have to live vicariously through all my DevOps buddies over there.

Michael Coté: Well so you’ve been going to a lot of DevOps stuff recently right John, you want to tell us what’s going on with those, with the DevOps days and things like that.

John Willis: Yeah. It’s you know, I mean as Andrew knows, Andrew is kind of, you know him and Patrick, I think you know got pretty much a lot of this stuff started and then you know, we had the DevOps days after Velocity — right there was DevOps in Belgium or in Brussels last year and I was fortunate enough to attend that and then we ran the DevOps in — after Velocity, which was amazing and I know we’ve talked about that and then they’ve got the other one coming up here.

Michael Coté: There is like videos for all those sessions right, I’ve watched a couple of those.

Andrew Shafer: There’s also one in between that Lindsey did in Australia.

John Willis: Yeah, that’s right there was one in Australia. Now what’s happening is through a lot of what you know Andrew and myself here in the States and what happened was like a lot of guys left that one last year in Brussels, Belgium sorry, and everybody basically came back at it just — you know their heads exploding with my God this is great and like you know Lindsey went to Australia, the guys in England started going nuts, Andrew and I were doing a lot of stuff in the US to get stuff going and now what we’re starting to see is all these regional ones I think pop up, so I was in Chicago two weeks ago, I went to Orbitz and gave a presentation there and then we did the first Chicago DevOps at dotWorks and then there was Morningstar had that little thing too and then there’s one coming up in New York in a few weeks.

The guys out in the Valley have had a couple of ones already. I went to — I was fortunate enough also to go to the SoCal, Los Angeles they’re pulling 100 to 125 people on a Thursday night, Tuesday or Thursday night under the label of DevOps Meetup. So, it’s pretty interesting. I mean the emotion and the passion around and you know — Andrew said this and my CTO Adam Jacob says it’s a cultural movement, it’s a cultural and professional movement and that’s what we’re seeing, we’re just seeing a lot of passion in this, kind of, cultural movement or trying to figure out, you know, some people have already got it, some people don’t have a clue, right, not the people that are coming to these meetings, but enterprises and whatnot and I think when people see the ideas of just the DevOps, it’s one of those things, you don’t have to see it twice, it doesn’t have to be explained to you more than once, you know, you pretty much get it right from the get-go, if you’ve worked more than a week in IT, you know so.

Michael Coté: And so, I mean is there — what’s the explosive device that blows peoples heads up? Like is it kind of the stuff that we and other people have been talking about for a while or is it sort of like some tweaking that’s been going on that like blows heads up better?

John Willis: Well there’s a secret and we can’t let you in unless you join the cloud.

Andrew Shafer: You got to get the secret handshake.

Michael Coté: There you go.

John Willis: Well let me — go ahead Andrew.

Andrew Shafer: So I guess there’s a couple of things there that I want to at least touch on. On this notion of having to explain to you and you understand it, I went to the AGEL 00:39:04 conference that was in —

Michael Coté: Nashville. No that wasn’t right.

Andrew Shafer: Moved to Orlando. And at the — there was an analyst panel and they mentioned DevOps about five times on that panel and there was you know the Gartner guy and the Forrester guy and what have you and then afterwards because I think I might have a little bit of knowledge and a little bit of an opinion about DevOps, I went up and I tried to explain to those guys where I thought their DevOps coverage was a little bit off what I thought was actually happening.

And then I follow up by writing some email to them and encouraging them to reach out to me and have a conversation and I didn’t get responses and I don’t know about you, but I never forget when somebody doesn’t respond to my email. So if you’re listening to this Gartner & Forrester, someone should send me an email.

John Willis: So what was he missing, what was like you —

Andrew Shafer: Well I just think they have — everyone has a perspective, everyone has an opinion. And at this point there is, you know there is DevOps and there is me and there is Patrick and there’s a bunch of people building stuff and you know I got to consider all the puppet people and the chef people and sort of this community practice and the amazing infrastructures and the things they are building and the things they are doing on both a technical and a cultural level.

And there is vendors, that want to sort of attach themselves to the movement, to sell the product or whatever their strategy is and those things aren’t always 100% aligned. And just like cloud is an ambiguous undefined term that creates confusion and opportunity, I think you have the same sort of thing with DevOps and I think that it actually — it tends to weaken the potential for what could be accomplished in a lot of organizations when that message gets muddied and diluted.

John Willis: Well I, you know when I present on a DevOps thing, the first thing when I say is that you know I use the line that Adam used that Velocity, which is DevOps is a culture and professional movement. Right and then I say, you know if a vendor is coming to you and saying they’re DevOps compliant or they have a DevOps product or you know they’re implying that DevOps is anything other than a cultural and professional movement as a general discussion run. You know, they are evil, you know because it’s exactly what you said, is that there is the cultural aspect to it and which is you know and as I say that if me and David we’ve kind of come up with thing called CAMS, so you know cultural automation, measurement, and sharing. You know unless somebody else comes up with a better way to describe it I’m sticking with it. And I would say if you don’t have — if you’re not dealing with the cultural, you don’t even understand the culture.

Andrew Shafer: So let me put it in perspective, all right. As an engineer I have opinions and perspectives about technology and how some of this stuff works and how the culture works and I express them and sometimes I have ideas that other people don’t have or other people have ideas that I don’t have and that’s is fine. But when I read something that makes me roll my eyes, when it exceeds the eye-roll threshold, then that’s sort of — you know that’s my BS detector. And all I really wanted Gartner & Forrester to do is write articles that don’t make me roll my eyes. Like I don’t think that’s too much to ask. It’ll help you, it’ll them and then —

John Willis: Well and I think there is technicians that make the same mistake too, right, I mean that really don’t have an agenda and they pierce in that DevOps is you know, continuous integration. You know the whole article is what is DevOps and then the whole thing is just describing some really, you know fascinating continuing integration model, you know what I mean and I think that’s just as probably not — I mean I agree with you that I think then —

Andrew Shafer: That’s the trunk of the elephant, you know, it’s the lineman on the offense.

John Willis: Oh I agree. I think the vendors that are trying to write — but you know that’s business and that’s what happens. We saw that happen with the cloud. I think the people in the movement are pretty darn smart. You know, the truth of matter is the Forrester’s and the Gartner’s, they are never the guys that get it on the first run anyway right. I mean they were pretty much convinced the cloud didn’t exist until a good year into it, you know before they even started mentioning the cloud right.

So I think DevOps is the same thing. I think that right now their view of it is from their big clients and their big clients are driven by their thought process is mostly driven by large vendors. So they’re going to get whatever they are kind of minor, oh don’t worry about that or that’s something we can solve in Version 2 of our product.

Andrew Shafer: Clearly.

Michael Coté: You know it’s also an opportunity.

Andrew Shafer: I’m here to help that all I’m trying to say, I’m here to help.

Michael Coté: It’s also an opportune time to plug your other podcast John, the DevOps Cafe, where you guys spend a lot of time talking about the finer points of what DevOps is. And if I remember in the first episode, you have a nice little what DevOps means to me moment, which is fun. But like — I think that’s part of the issue people have is they definitely — you know and it’s kind of getting back to the point of why it’s sort of easy to explode people’s heads, is there is not — you know there is not a lot of like easy things to point to, like you can’t buy the O’Reilly DevOps book if you will and so —

Andrew Shafer: So that was the other point I wanted to make when you guys touched on it is, this exploring people’s heads the outcomes, because so many people their idea of IT best practices is such a disaster, it’s a minefield of Jenga setups where everything that they’ve ever experienced is broken, fundamentally broken where you had you’re under resourced, extreme time pressure, extreme up time pressure and it’s just — there are a bunch of people with post-traumatic stress syndrome.

John Willis: Well maybe that’s the thing I think now taking it back to where it was earlier is I think the web operations book, which I know you’re an author of one of the chapters Andrew. A very good chapter actually and — but the — you know I think that to me is hand this book out not that it like solves DevOps, but it’s clearly — you know like Adam says right, Adams says that I know you said this and others said this too, that web operations is now becoming or is the dominate culture for IT right.

So the dominate model for IT processing, this is — you know what we’ve learned over the last what five, maybe ten years about web operations is the right way, unless somebody else comes up with a better way, is the way that we need to start assuming our best practices for building IT and which includes, you know this is very much where the DevOps mindset came out of, you know, because it was less of a barrier in WebOps blog and I think that book is a great — I mean everybody should read that if they are thinking about what IT is going to look like for the next ten years, that book, you know I think you would agree is a great starting place.

Michael Coté: And I think that’s a nice concise way of putting it this 00:46:39 instant. We’ve, sort of, ironically been moaning the fact that people talk about DevOps without knowing what they’re talking about and yet we haven’t really said what it is, but which is exciting other than some top line stuff, but like, in the same way that it can be said that consumer technology drives what happens in enterprise technology now.

Like basically the point you’re making there kind of is — it kind of dips your toe into more specifics here is that rather than thinking about enterprise IT management where a lot of the innovation is happening and coming from is how high scale public websites run their operations and that’s like what the big switches you know, from Andrew’s Jenga towers or whatever it is, like there is a whole different way of running or not a whole different way, there is a much different way of running IT that comes from a different source than like what you’re used to being taught in your enterprise IT stuff.

John Willis: So back to this point, I think that the present is not evenly distributed. In every sense of the word and while I do think that there is — there are some very colorful and powerful personalities that are involved in doing WebOps I don’t think it’s the dominant paradigm and I think that you know like I love Adam, don’t get me wrong, but I think he might have a little sampling bias, because he has done a lot of WebOps and if you go — I mean I don’t know what your experience is at Opscode, but I can speak to my experience at Reductive Labs and looking at the way a lot of these enterprise IT shops run, they could learn a lot from all of the lessons in that WebOps book. They could learn a lot from the lessons and the things people do at Velocity conference or Surge conference. But at the end of the day, when they go back they’re still — it’s still a bunch of Jenga and they got a lot —

Andrew Shafer: That’s the point. I think they’re the ship sailing to the left, you know what I mean. I mean I think that in all honesty that enterprise — there is a lot that WebOps can learn from enterprise and I think I’ve had discussion with you. I mean I remember sitting and watching John Allspaw talk about incident and change. And I remember you know J.P. Morgan or Chase Bank doing that 20 years ago, you know what I mean and having it nutted on the mainframe, right.

So and that’s kind of not that it came from the banking industry in the US, but 00:48:59 came out of people that were figuring out how to get incident and problem and change in a process that everybody could share.

John Willis: I could probably articulate this a little bit more effectively but I feel like —

Andrew Shafer: Are you saying I’m dumb?

John Willis: No, no, to reinforce your point. I feel like cloud computing is really just client server coming back full circle and relearning all the lessons that people learned about how to build reliable systems in mainframe and implementing it in distributed architectures.

Michael Coté: And that answers how you’re going to get rid of all that legacy IT, you’re not —

Andrew Shafer: Yeah you’re not. And okay so that’s a great point. There are still people building mainframes or —

John Willis: There are all right. But all right, so again I’ve got a bad sampling rate to sample set as well because, I’m so immersed in world right now. But I think that when you look, it goes back to what you were saying early, I think today all things being equal, and that’s a pretty gigantic statement, but if your decision is to pay $15 million for an IBM mainframe or build a commodity infrastructure based on commodity hardware, Linux, Xen Hypervisor, possibly one of the open clouds as it matures.

Andrew Shafer: You could buy a lot of CPU and disk for 15 million.

John Willis: That’s what I’m saying — well you know yeah, I mean my point is that yeah there are still people buying mainframes, but I’m not sure they’re on the right ship, you know what I mean? I’ve never been one to bank against IBM or bet against IBM, but the point is I think that I don’t — I think if you are not picking up some major lessons from web operations, if you’re not looking at DevOps as something that should be game changing your enterprise.

Now the chances are like you said can we, will we, would we; yeah, well they will eventually. I mean eventually they’ll get a CIO that’s basically out of college that you know that’s coming out of college right now that will actually be their CIO and he’ll have no other way except WebOps, DevOps and cloud right. And — but I think that the people that are going to hold on to dear life to their Jenga infrastructure, as you would say it or I mangle it, I think they’re headed for — you know they are sailing in the wrong direction.

Andrew Shafer: Well, it’s just they’re always going to have the cost center, because they always treated it like a cost center. I don’t think —

John Willis: Let’s take it out of business right. I mean the question is, is there somebody out there going to start a business. I mean the one thing we should have learned over last 15 years and certainly within the last five, is that when the Internet boom came out companies like Barnes & Noble and Borders thought they were safe and then all of a sudden this Amazon basically shocked their world right. But the banks and the insurance companies they were like that’s never going to happen to us, right.

Well guess what’s happened in the last three to five years, right, cloud is in a struggle. So I mean your competitor, I mean there’s a bank called Simple Bank, I mean these guys are ex, I think B of A guys, right that are building commodity infrastructure, one of the interviews we did was this company called Ka-Ching on our DevOps Cafe.

Andrew Shafer: Ishe Smith, he was at DevOps days.

John Willis: Okay, I mean they blow your mind if you look what they are doing and people say well you can’t use cloud if you’re in the financial credibility. Well these guys are kind of like a mini e-trade and there are 15 guys, I called them a garage band of startups, they actually —

Andrew Shafer: They are like garage band mutual fund.

John Willis: Yeah, and they’re doing it all on commodity infrastructure, they’re doing continuous, to hold continuous deployment Eric Ries continuous delivery or whatever, Continuous Deployment. It will blow your mind what they’re doing, and I would bet, this is what I say like what they had built, I could picture going to B of A and say he tried to replicate this.

So they are probably about a $2 million investment, they’re up to like 15 guys, they’re working out of what looks like a garage and if you went to B of A and said replicate this, it probably cost them $5 million to $10 million, it will probably take them a-year-and-a-half to develop it and it wouldn’t be as half as efficient. And so, you could stick with your mainframe and AIX and DV2 and Oracle and keep going down that path and somebody is going to put you out of business.

Andrew Shafer: Disruption.

John Willis: There, I’ve said it.

Michael Coté: Oh, you closed the circle back to the beginning of Telco’s being disrupted off of one word.

John Willis: But they get it obviously, they have no choice but to get it, right, because the mobile is killing — is totally ripping them apart.

Andrew Shafer: I mean you’re obviously in a better position if you know your business model is being disrupted and if you —

John Willis: Or you are somebody like Amazon and Google who have really smart guys that do the math, right. And they figure it out ahead of time.

Andrew Shafer: Right. I mean everyone has always done some math, it’s just a matter of as you get more insight into where your costs are and how do you’re going to be able to spend things, until people see things then they’re not obvious and once they do then it’s de facto standard.

Michael Coté: Well, and also to use your metaphor again right, if you’re dealing with bunch of Jenga towers. Really the thing that usually happens is they fall down in a big catastrophe, it’s a little difficult to carefully unassemble them.

Andrew Shafer: Or you are hiring a bunch of guys to hold the little pieces up and they run around and they keep them. If you just had a bunch of Jenga all by itself and no one ever touched it, then it shouldn’t really have a problem, but you have users, you have new features, whatever page you can deliver them and then that’s why they fall, not because they’re sitting there and they’re unstable, but because that you changed them.

John Willis: Well, the other thing, are you a type of company that are willing to take the Amazon like or Google like risk to make that kind of change that’s so disrupted to yourself, right and to do that right. And that’s — and unfortunately a lot of these companies, for all sorts of historical reasons and reasons that I’m not even qualified to comprehend, but what it takes is some company to have a risk taker to basically say you know what we got to change the game.

I always think about like when I worked at the Federal Reserve doing consulting, the food always suck and what they do is every few years when the contract come up, the lowest bidder got the contract, whoever was the lowest bidder on the food services for the cafeteria got the contract. So the food always suck, right I mean it was never going to work, right.

Andrew Shafer: So, that was the result of someone doing the math and I think so let’s talk about and I think this goes back to culture. We’re making lots of little loops here, but Zappos was purchased not because they were beating Amazon on price, Amazon’s core competency is beating or winning the price battle.

Zappos was winning on culture. They had a great culture of people who loved their stuff and if you think that your differentiator is all about running the numbers and at the bottom you find the lowest one, that’s not the math I want to do. There’s the bottom line and there’s the top line and if you can build relationships with people, in 2010 you have amazing, amazing infrastructure for reaching out and interacting with your customer on any level business-to-business, consumer-to-consumer and that is another thing that’s changing the game right now.

Michael Coté: Yeah, and I think maybe the point, the thing that I encounter a lot is, it gets back to the cultural thing of CAMS or whatever just like you alluded to, is that businesses aren’t used to taking risks with IT or using IT to take risk or taking risk in the first place of course, but I think the wider thing is people don’t expect IT to be helpful or to actually help them do anything, as you were saying.

Andrew Shafer: So, yes —

Michael Coté: I think there’s little expectation that like —

Andrew Shafer: Exactly.

Michael Coté: That like you could do something interesting with your customers, because you have some new piece of technology, they just assume that any technology stuff you get involved in is going to be a swamp.

Andrew Shafer: Exactly. So to make my point more explicitly, it’s about treating people like people and it could be your outward facing customers and the culture this app was built to leverage that or it could be your colleagues and your co-workers. So if you think about the IT mindset where the guys in the data center we think they’re all a bunch of chimpanzees and they can’t do anything right, then don’t expect to get great IT out of them, right.

If you want people to solve problems, if you want real DevOps you can’t just slap a little DevOps label and say we got some automation now, basically you need to treat people like people, you need to give people interesting hard problems to solve and let them solve them.

John Willis: Well, what I’ve been seeing and kind of now circling, circling 00:58:31 that is you asked me what I’m seeing from DevOps, what kind of — there’s nothing genius about this, but I’m finding that when I interview or talk to people, the most effective DevOps culture it plays is where somebody at the top, the CIO, somebody up there gets it completely and then it just kind of, you either want to work there, because you get it or you don’t want to work there, because you don’t get it.

I mean and it’s like anything else, we say this all the time, unless you have a kind of top level commitment or something, but when you’re talking about like we always talk about top level commitment to maybe a road process or a technology, but when you start thinking in terms of like top level commitment to understanding your culture and how it affects your business, if you’ve got that, then everything falls downhill in a positive way, you know what I mean.

I think that when people ask me what’s the most effective thing about DevOps, I was like, like again if you don’t have cult, if you don’t understand like, I believe like the visible ops guy, the Gene Kim and all, you can’t change culture, you could change behavior, but you got to understand your behavior and you got to think about, well how do I change behavior to affect a positive flow of anything we do, because if we don’t understand our behavior or our culture, then throwing a whole bunch of automation and process and trying to formfit everybody into something is just going to be a waste of time.

Michael Coté: Yeah that’s why usually like it helps to have executives, giving permission to do all this stuff, because it seems like the way most businesses run, if not all of those. Basically you figure out one work flow that makes you money and if your employees deviate from that, you punish them and you basically want to do the one work flow that generates profit. So you sort of have the —

Andrew Shafer: You want a positive feedback, not a negative feedback.

Michael Coté: Exactly. And so, first you have to give — you have the employees that can innovate and then you have to kind of give them the context in which to innovate. And then finally of course, you have to give them permission to do it, and then hook it up to actually transforming things, but I mean I would wager for all the innovation talk and all that kind of whiz bangery that most companies are not really, the business side is not really interested in doing new things, they’re interested in squeezing as much cash out of their current 01:01:00 as they can.

And so, that’s why, and then the same sort of thing would happen in Agile world where you sort of acculturize all these programmers to develop software in one way and you can’t really expect them to be able to take it fully bottom up all the way until you get executive leadership that says, all right you’re allowed to do this. It’s sort of — part of business culture that you don’t do what the boss tells you not to do or wait, you only do what the boss tells you to do.

Andrew Shafer: And what has to happen is again, I think that business leaders have to come to the conclusion that DevOps ultimately is trying to mature, the principles of DevOps if there are any, will actually make you more money, right. The same conclusion that I guess the Opscode guys came to that hey there was a reason why this is going to work, we are not just doing it because it sounds cool, there was grassroots efforts where people did it and said, I’ll build it and they were calm and then there’s executive level people that got it and said, “Oh My God” or they read about their competitor doing it and I think that’s what DevOps is going to have it’s traction is that —

John Willis: It’s not about a name, it’s not about DevOps, it’s not about —

Andrew Shafer: It’s about creating value, it’s about creative capitalism, it’s about creating more value than you capture, I think that’s the bottom line.

John Willis: But yeah.

Andrew Shafer: DevOps is this idea focused on one particular slice of how you’re going to run your business. How you’re going to trade your —

John Willis: But I think that’s just like the cloud and just like Agile names are affective, right. I mean I agree that DevOps is just a place, a stakeholder in the ground right, but it’s an affective stakeholder, because it allows you to rally around it and have the kind of discussions that could affect business, positive business changes.

Andrew Shafer: I agree. And I’ve said all those words; DevOps, cloud, Agile yes, but at the end of the day it’s not about the word it’s about the action.

John Willis: Totally. No we always kind of say the same things but —

Michael Coté: Well, I think on that note it’s good time to wrap up. We got the Web Operations Book, that’s by O’Reilly right John?

John Willis: O’Reilly, yeah.

Michael Coté: You know a willingness to change, to do something with them Jenga towers and also yeah you know if the audience, you guys — do your listeners really like this kind of DevOps talk, like I said John and Damon Edwards have a great podcast series where it’s basically all they talk about all the time, which is good stuff. So, hey thanks for being on this week Andrew, it was a pleasure as always.

Andrew Shafer: I’m started to think my core competency is meandering editorialization, but thanks for having me.

Michael Coté: Well, it’s true meandering editorialization works for podcast.

John Willis: Well, he is Little I Dare on Twitter, but he’s got some Big I Dare in the clouds.

Michael Coté: Send that guy to the marketing department. And with that–

Andrew Shafer: We’ll see how the 01:03:55 or we’ll measure them over the next few years to see how it turns out.

Michael Coté: There you go and with that we’ll see everyone next time.

Andrew Shafer: Cheers.

Disclosure: CloudScaling is (new) client of RedMonk, as is OpsCode where John works. Many other companies of interest are clients as well, see the RedMonk client list if you’re interested.

Categories: Cloud, IT Management Podcast, Programming, Systems Management.

Tags:

Liferay, portals, & social product marketing – Interview with Liferay's Paul Hinz

The demand for closer engagement with customers and users is driving companies to use portals in new and interesting ways. Throw in all of the social networking sites like Facebook and Twitter, crossed with sales & marketing automation practices and technologies, and the opportunities for companies to use the web as one of their main “store fronts” are huge.

In this interview with Liferay‘s Paul Hinz, we talk about this use of portals, of course, involving Liferay. He spends some time talking about social product marketing, but also goes over the “good, old fashioned” portal features in the most recent Liferay offering, 6EE.

Also, I wrote up more on Liferay right after their West Coast Symposium, where this video was shot.

In addition to watching the video above, you can download the video directly or subscribe to the RedMonk podcast feed.

Disclosure: Liferay is a client, and sponsored this video.

Categories: Conferences, Enterprise Software, Java, RedMonkTV.

Tags: , , , , , ,

HP's New CEO – Press Pass

Chair in the backyard

I talk with the press frequently. They thankfully whack down my ramblings into concise quotes. For those who prefer to see more, here’s a new category of posts: Press Pass.

I IM’ed with IDG’s Chris Kanaracus about HP hiring Léo Apotheker for CEO. Here’s what I said:

Recent History

I’m loath to theorize on executive hires like this, but here’s the obvious stuff:

  1. Leo oversaw one of the worst enterprise software bungles of the year, raising maintenance pricing during a recession.
  2. SAP’s continually inability to deliver a SaaS offering didn’t start under Apotheker, but it didn’t end either. Ideally, leadership would be installed that knew how to do the technology behind a SaaS, market it, and more importantly, believed in it. Perhaps those things exist at SAP, but the outcomes – a wildly successful SaaS enterprise software offering, if only part of the overall pie, a la SalesForce – haven’t occured.

All of that said, hindsight criticism of SAP is fraught with problems for us Yankees. I’ve followed SAP for several years now, and I don’t totally understand the different incumbent power brokers, German labor unions, and other stuff that doesn’t exist for American based technology companies. Like most elder technology companies, SAP is an organism all of it’s own beyond the complete control of any one individual.

HP Software

Looking at HP: most everyone I talk to agrees that HP needs to get their software act together. While they have great assets (as one example, most every QA department uses HP testing software, another example: OpsWare, or whatever they call it now), there isn’t a sense of a unified software strategy like you have with, say, IBM.

And, thus, Leo being “a software guy,” you’d hope he’d pay more attention to that than “a hardware guy.” Having a good software portfolio helps drive so much else – be it hardware, services, etc.

And then the speculation of HP buying SAP.

Chris asks me about getting enterprise apps vs. following a more middleware focus, as with IBM Software.

The idea of exactly duplicating IBM is a bit misleading. The more important thing in “duplicating” someone you think is successful is duplicating their tactics, not the exact things they do. And, IBM just say they don’t do applications. And then there’s that whole Lotus division. Not to mention the analytics stuff they’re getting into, e.g., Sterling Commerce, etc.

The thing with HP is that, as a company, they make a tremendous amount of money: in that billions and billions that you can’t really fully comprehend [as Chris put in his story, “HP generates north of $100 billion in revenue each year”]. But they’re not really known for or as anything at the moment other than charging a lot for printer ink (a barrel costs more than a barrel of oil, right?), decent servers (they do well here), and niche software products that seem to work in isolation (their QA success, HP Orchestrator/OpsWare).

If you wanted to be an “HP CIO,” there’s not much of an ethos, road-map, or sort of “brand” to sign up for. There’s not much to identify with to motivate you to stay with or buy from HP vs. IBM, Microsoft, Oracle, SAP, etc.

All that said, those stupendous revenue numbers seem to make that not much of a problem at the moment.

Also, see James’ piece on Apotheker leaving SAP from back in Feb, 2010.

Disclosure: SAP is a client, as is IBM. HP has been a client in the past.

Categories: Enterprise Software, Press Pass.

Links for September 30th through October 2nd

Goat Rack

Disclosure: see the RedMonk client list for clients mentioned.

Categories: Links.

Tivoli Live Update with Phil Fritz

Before having a few beers at the local pub simulucrum, IBM’s Phil Fritz tells us what’s been happing with Tivoli Live, the IT Management as SaaS offering IBM put out earlier at the end of last year.

Phil and I last spoke with him when Tivoli Live first came out – with an interview and demo – so it was nice to grab him for a quick update on features, customers, and the way people are using Tivoli Live. Of note, there’s an interesting group of customers who’re providing their own SaaSes that are looking towards IT Management tools that are SaaSes as well.

Disclosure: IBM is a client, but this video is not a sponsored video.

Categories: Cloud, Enterprise Software, RedMonkTV, Systems Management.

Tags: , , , , ,