by Brian Prentice | January 16, 2015 | Comments Off
Here’s a prediction. By 2017, the single biggest way in which digital technology will annoy people is through thoughtless, intrusive and annoying algorithmic automation.
Let’s call it Over-engineering 2.0.
Over-engineering 1.0 has been all about feature bloat. It’s the result of an approach to system design that thinks the more things we can give people in technology, the happier we’ll all be.
Over-engineering 2.0 will emerge as the result of an approach to system design that thinks the more things technology can take away from us, the happier we’ll all be.
Over-engineering 1.0 had a strong appeal to the “power user” – the person who delighted in engaging with technology for technology’s sake. Finding new things the technology could do was as important as the technology getting something meaningful done at all.
Over-engineering 2.0 will have a strong appeal to what I’ll call the “idle user” – this will be the individual who delights in technology doing “stuff” for him or her for no other reason than technology being able to do it.
The thing is that the power user and the idle user are outliers – they’re not indicative of what most people seek and expect from technology. Yet, these two archetypes often exert tremendous influence on those system designers whose own bias of technology is towards perpetual expansion of functional or automation capabilities. This connects to a broader level of confirmation bias.
Decades ago, software engineering practices were designed to add functionality as efficiently as possible for the simple fact that most software didn’t do much. Every new feature added was largely met with a positive reaction.
“Hey, my word processor v3.0 now has bullet points…thank goodness, it’s about time.”
But eventually we hit an inflection point, where the next feature really didn’t matter to most people.”
“My word processor v14.0 can now adjust the text distance for an in-margin drop cap? Ah, I don’t think I’ll ever need that.”
This inflection point is where we move into the realm of over-engineering. But by this stage there’s too much momentum in the design process to stop the train…it’s geared to add functionality and that’s what you’re going to get, like it or not.
And it could end up be the same for algorithmic automation systems.
In the past, it’s been “Cool, Facebook automates a recommended friends list.” Now we’re moving to a place of “What in the heck is this ‘Year in Review’ thing that just popped up in my News Feed.” Or, perhaps into a place called “algorithmic cruelty.”
As we continue to be propelled into a world of massive global-class computational power, vast expanses of mineable data, an increasingly inter-connected global population, and a mind-numbing array of digital access points, the temptation for system designers to piece these together into systems of algorithmic automation will be enormous. Without doubt, many of these systems will be wonderful. Without doubt, some of these systems will be scary bad.
The challenges with algorithmic automation will have broad implications. Whether it’s the newfound ability of the beautiful but talentless to achieve music frame through auto-tune technology. Or the impact that “automation addiction” has in the world of avionics systems.
So we must be asking ourselves today how we create an environment where systems of algorithmic automation are created in a considered rather than reflexively fashion. Because once the momentum starts building, systems designers will be hard pressed to temper the desire to over-engineer. And that’s what will lead to the inevitable creation of thoughtless, intrusive and annoying systems of algorithmic automation.
It’s my view that one of the prime factors that has propelled the growth of user experience (UX) design has been as a way to tackle technology made incompressible though incessant feature bloat. UX design will still be needed in the world of algorithmic automation. But I believe it UX design needs to sit alongside a broader philosophy that we refer to as digital humanism. This is a specific intent amongst everyone involved in system design to put the interests and values of people at the center of everything they do.
With that in mind, I’ll offer the digital humanist’s laws of algorithmic automation:
- Empowerment always trumps automation.
- Never take something away from people that they enjoy doing for themselves.
- Automation should never startle – surprises that delight people are welcome. Surprises that bewilder people are infuriating and, sometimes, dangerous
- Don’t automate something for everyone that only some people want automated – technology will never advance to the point where system designers are relieved from the responsibility of understanding the nuances in people’s goals and behaviors.
Category: Uncategorized Tags:
by Brian Prentice | November 27, 2014 | Comments Off
Last month, at Gartner Symposium, we introduced the concept of digital humanism. This concept emerged after reflecting on the profound philosophical considerations that will be driven in an era of digital business.
Digital business will require us to orchestrate a vast array of sensors, data, and devices into impactful new systems. The manner in which we conduct this orchestration will ultimately be value-driven. And we believe there are two value systems that we must choose from.
The first is digital machinism. In this value system, people and organisations are seen to benefit from technology through automation. That is the ongoing dilution or removal of peoples’ direct involvement in activities and processes. The other value system is digital humanism. Digital humanists specifically seek opportunities, through technology, to redefine the way people can achieve their goals or to enable people to achieve things they didn’t previously believe possible.
Examples are ultimately the best way to illustrate a point. So, let me turn your attention to a recent presentation by Prasad Setty, Vice President of People Analytics & Compensation at Google.
In the presentation, Setty talks about one of his department’s first efforts at a applying a data and analytics approach to HR decision making. Their target was the process used to determine the bi-annual promotions of its engineers. After very careful analysis, they developed an algorithm that resulted in what he claims had a 90% accuracy rate for 30% of promotion cases.
This is a perfect example of digital machinism. The very purpose of this project was to automate the promotion process by dramatically reducing people’s role in it. The exchange for the loss of individual control was a reportedly higher level of decision accuracy.
Now, if ever there was an audience you think would warmly embrace an algorithmic approach to HR decisions it would be the very Google engineers whose professional lives are absorbed turning the world into a mass of algorithms.
The result? Google engineers hated it.
Sweet irony? If that were the end of the story, it would be. But to Setty, and Google’s credit they looked further and discovered that engineers:
“…didn’t want to use the model to make decisions for them. They wanted to use it to examine their own decision making process.”
This is precisely the perspective of digital humanism. Rather than removing people as part of a broader system, we seek to enable them to be a more effective part of it. As Setty pointed out, his “doh” moment was realizing that his team should be letting people make people decisions.
That realisation, as I see it, can be extended. Let people make decisions. This doesn’t mean that we cease automating. In fact, the digital humanist embraces automation as an important tool to enable people to achieve their goals. But note – automation is a tool. It is not the goal.
Category: Uncategorized Tags:
by Brian Prentice | January 29, 2014 | 1 Comment
Let’s face it. Enterprise software is the land that UX design forgot.
Whether it’s an internal enterprise application development team, or the R&D department of an enterprise software vendor, the practices commonly found in UX design agencies the world over are poorly understood and rarely implemented. Pre-development ethnographic research is almost never conducted. Personas seem confusing and if ever applied are done so incorrectly. The opportunity to collect data that can be used to refine UX design specifications is regularly missed.
And yet, the stewards of enterprise software are honestly perplexed at the negative feedback they get from “users” (a semi-affectionate term developers apply to human beings).
From the perspective of a UX designer, the solution is simple. Implement UX design processes undertaken by UX design professionals. Based on my conversations with many in the UX design community, most are just as perplexed why something so obvious is so rarely acted on.
Generally speaking, the diagnosis of the UX design community is that enterprise software suffers serious usability problems due to mass ignorance. If application architects, development team leaders, and vendor product managers in the enterprise space could only be made aware of UX design then they would logically seek to apply this to create successful outcomes.
Unfortunately, the problem isn’t one of mass ignorance. The problem is one of mass delusion. Application architects, development team leaders, and vendor product managers already believe they’re people-centric. They would argue that an application project is largely a culmination of features users asked for themselves. In fact, over many years they’ve perfected processes to collect and prioritise feature requests, figure out how many you can get completed within a time frame users define, create a version, and deploy it.
This is why these people commonly conflate graphic design and UX design. If users are unhappy with a system delivered as specified, it must be the way the specifications are presented.
It’s akin to the dilemma of the indulgent parent. Such parents think that giving children everything they want is the best way to make them happy. When the child remains unhappy the parent thinks the problem is that they aren’t giving them enough, or fast enough, or nice enough. A vicious cycle of repeat behaviour emerges that results in a bad outcome for both parent and child. The effective parent, on the other hand, provides for their children based on a deep understanding of who they are as people and their actual needs at the moment.
This is the basis of the UX disconnect in the enterprise. There are competing world views for what being people-centric means.
UX design is the effective parenting method for software development. But a bridge between these competing world views needs to built in order for the enterprise software community to move to the other side. The onus lies largely on the UX design community. They need to put as much emphasis on their communication strategy as they do on their design methodology. And the language they use needs to resonate with their intended audience. Here are a couple suggestions:
- Start with the baseline perspective that everyone wants delighted users. The question is what the best approach is.
- Don’t challenge the enterprise software community on their understanding of UX – challenge them on measurable outcomes they understand. For example, what is the impact on a project’s ROI for features written but rarely used? How does under-utilised functionality impact the overall productivity of the application development team? Can a project be measured on the extent to which users stop using alternative software applications, hence supporting application rationalisation initiatives?
- Push the enterprise community to acknowledge emerging work patterns. Therefore, a software system that enables a particular business process can only be considered successful if it also reflects the way people are conducting themselves in relationship to the business process.
- Avoid semantics. Focus on success stories.
- Be a matchmaker. UX design will create better outcomes that line-of-business managers will be happy with. Find ways to let the enterprise software community share in the success.
I’d welcome your additional suggestions.
Category: Uncategorized Tags:
by Brian Prentice | June 18, 2013 | Comments Off
The series of tubes we affectionately know as the internet has been abuzz over the last week with talk of Apple’s flat design detour with iOS7. As with anything aesthetic, there’s bound to be be the highly positive views and the highly critical. We’ve seen psuedo-conspiracy theories emerge along with some trending memes.
So does all this discussion of colour palettes and iconography point to an appreciation of UX design by IT’s digerati?
Nope! Not as I see it.
In fact, I’d argue the week’s icon madness indicates that too much of the IT world is still entrenched in the view that great UX is synonymous with great graphic design.
The man himself, Steve Jobs, once said, “Design is not just what it looks and feels like. Design is how it works.” Missing from most of the post-WWDC conversation has been much insight into the way these design changes fundamentally make individual apps, collection of apps, or the devices they operate on work better.
I’ve been spending a bit of time going through the presentations from the WWDC. I must say, there is some impressive stuff that Apple is doing for the design and developer community. The new system font is beautiful and the dynamic type capability in UIKit is some serious goodness. There’s the new App Switcher and it’s relationship with the improved multitasking capabilities. The motion effects, in my opinion, are a marvel of engineering.
What’s much less clear is how Apple’s new objectives of clarity, deference (which Microsoft describes with their Modern UI as “content over chrome”), and depth – design themes that the new UIKit is being engineered to support – enable a new style of app experience. Experience, mind you, in the how it works sense…not the look and feel sense.
When I search for clues in Apple’s own apps, the feeling I get is that the upholstery on the furniture has changed, but the room’s purpose and layout is the same as it always was. Adding depth as a new dimension to app design seems to me to have profound long term potential. But if it’s primarily demonstrated at the top level of the operating system by floating icons above your wallpaper, then we have something which will rapidly descend into ho-hum ornamentation. Maybe Calendar and Notes isn’t the right place to highlight this stuff…but surely there’s something that can.
My intention is not to be critical of Apple. After all, Microsoft is having the same issues with Windows 8.
Their Modern UI pre-dates Apple’s drive towards a typographic experience. It’s one thing to tell designers and developers to clear out the chrome. It’s another thing to articulate how content itself becomes the engaging, interactive raison d’être of an app. Here again, when we look to compelling examples from Microsoft’s own apps, we’re left wanting. Semantic zoom is a great UX innovation. But isolated in a handful of included apps it’s difficult to sense it’s potential.
As a result of all this, the conversation about Microsoft’s new design language has been derailed. Like Apple, it’s largely about icons, which in Microsoft’s case are their Live Tiles…along with how users must lurch back-and-forth between the new Start screen and old desktop.
The point is that UX is too easily seen as the look and feel stuff. And the more time we spend on colour palettes and icons the less nuanced our understanding of what these design languages can and should do to software and services. Ultimately, the onus is on all mobile operating platform providers to offer some steak along with the sizzle. They need to show us how their UX vision translates into a new experience with practical examples. In Microsoft’s case, they need a much bigger commitment by their own product groups outside the Windows team to embrace and deliver solutions that take full advantage of their Modern UI. In Apple’s case, I’d love it if they’d apply clarity, deference and depth as one part of a strategy to re-inflate their cloud service offerings.
Ultimately, I’m hoping that we can all shift gears and ignore the icons for a while and think about what will happen when we tap on them.
To paraphrase William Shakespeare, “what’s in an icon, that an app by any other should work as well.” Indeed!
Category: Uncategorized Tags:
by Brian Prentice | September 14, 2012 | 2 Comments
There, I said it.
Actually, I was toying with two other titles; “iPhone 5, The Emperor Has No Clothes,” or “iPhone 5, What’s In A Name That A Phone By Another Other Would Operate The Same.”
Look, I’ve been going through the same rationalization process I think a lot of other people have. Is it fair to expect Apple to move Heaven and Earth with every announcement? Why fret, the really cool stuff is in iOS6, not so much the phone. Try as I might, I can’t shake the feeling that with all the build up, the iPhone 5 announcement had all the impact of being hit by a wet noodle.
Now, I’m not stating this as a Gartner analyst but as a dedicated Apple customer. And I’m definitely no Apple-hater looking for a reason to knock the company. I’ve spent my own cash for my iPhone 4 in spite of the fact Gartner would fully fund the cost of the latest Blackberry. I parked my company ThinkPad in a dusty spot under my desk and bought my own MacBook Air to use at work , much to the consternation of our IT department. Heck, I even lined up in front of the Sydney Apple Store on the day of the new iPad announcement for my 64gb, white, wi-fi model. I have enough of the company’s products in my house that with an Apple logo on my mailbox and a blue t-shirt I could open an Apple store.
I’ll be perfectly honest with you. My disappointment is directly related to the fact that I’ve been spending a little time with Windows 8. The new Metro/WinRT design language is a design innovation of the highest order. Nor am I the only one taking notice. Add to that the new Lumia 920 and 820 smartphones which are evolving an alternative industrial design perspective. Microsoft and its partners are beginning to offer a compelling alternative vision for the smartphone.
My gripe…no, my concern…with the iPhone 5 is not that Apple made it. It’s that Apple has diluted the value of their well-crafted product launch strategy. Apple has earned my continued attention because these big productions have been used to announce big changes in the way we experience and interact with digital technology. They are a celebration of what a company driven by a deeply ingrained design ethos can accomplish as compared to those that prefer to market the incremental technical achievements of their engineers.
What is Apple ultimately offering with the iPhone 5? Speeds and feeds. New processor, larger screen, different connector, LTE support. thinner form factor. Don’t get me wrong – these things are important. And they constitute some fantastic engineering work to hang it all together. But is it fundamentally changing my experience with a smartphone? No, not really. So why does this new product need a new version number? Why rent out the Yerba Buena Center? They could have called this “the new iPhone 4S” and just rolled it into the retail channel without the hoopla and fanfare. It would still be a great, competitive phone. On September 12, Apple became the company that I would prefer to ignore. The type of company that tells me that another processor core, a couple of gigs more of storage, even the casing materials, are things that I really need to get excited about.
There are, of course, many people that will rave about the iPhone 5 because that’s what you’re supposed to do when Apple launches any new product. At one level, it can be quite funny as Jimmy Kimmel recently exposed. They handed people an existing iPhone 4S, told them it was a new iPhone 5 and then listened to them rave about how much lighter, faster and clearer it was – even from people that owned an iPhone 4S.
I haven’t lost my passion for Apple products. While I’m gobsmacked at what Microsoft has accomplished with the Metro design language I’m not converted as yet. But I can’t help but feel that Apple used the iPhone 5 launch for marketing over substance. And for the first time ever a word has, only for a brief moment, crossed my mind in relationship to Apple.
Category: Uncategorized Tags:
by Brian Prentice | May 1, 2012 | 1 Comment
I guess I should be delighted to hear that the Australian Parliament is going to start examining the reasons why Australian businesses and consumers are paying huge mark ups on on technology products compared to US customers. But I’m not.
See, I don’t really care whether my apps, my songs, my video games, and my ebooks carry a steep premium here in Australia. Apple, Microsoft and all the others can charge whatever they want.
What I care about is why I’m prohibited from shopping outside Australia to get a better price. Shopping for digital products is like being asked for your ID before you enter a department store and if you don’t live in the right location you’re barred entry. Or, they’ll let you in to browse all the great prices but your credit card will be declined at checkout.
If there’s a reason to uplift pricing in Australia then I’m fine with that happening. But it should be the right of the consumer to determine whether those prices warrant the added value, if such value actually exists. If not, they should be allowed to take their business where they please. See, what I want to do to Apple, Microsoft, Adobe is the same thing I’m doing to local retailers. If it costs $110 for a pair of Levi’s 501 jeans at major departments stores in Sydney (yes, that’s the actual price), then consumer should be welcome to take their business to Macy’s online and get them for roughly half the price.
The problem is not high prices. And I believe the Government is wasting all our time exploring that topic. The problem is restraint of trade. And we all know the tricks of the trade that are used to achieve those aims. Things like funnelling non-US customers into local app stores. Disallowing the use of credit cards with non-US mailing addresses. And let’s not forget about the ever-popular region coding system (no, it’s not just a system to control piracy). All, I’m assuming, perfectly legal – a fascinating situation which should again give us pause to think about what we signed up for with the US-Australia free trade agreement.
While the terms of reference for this investigation are yet to be decided, I’m betting that the issue of restricted trade won’t be up for discussion. Why? First, I think it’s impossible to examine this issue without going well beyond the scope of the IT industry. Second, and more important, I don’t think the government seriously wants to wade into the fetid cesspool of inefficient and exclusive distribution agreements, corporate taxation policy, and political influence peddling that makes restraining the free flow of goods such an attractive option for businesses across the Australian economy. Additionally, the Government will find themselves uncomfortably having to consider some of it’s own decisions and political relationships:
- The Australian Government fluffed the opportunity to allow the parallel importation of books, as advised by the Productivity Commission. The higher local prices surely must impact eBook pricing, particularly with Apple’s iBooks, where the publishers set the list price.
- If the Australian Government can demonstrated a willingness to take on multinational tobacco companies and their claims of of IP rights by enforcing plain packaging, why haven’t we seen similar action taken in tackling region coding – a practice that the Australian Competition and Consumer Commission has long identified as a system of biased distribution.
- A big component of this problem is content related. That means taking on the powerful and politically-connected movie, music and publishing industries.
If the Australian government really wants to put some pressure on the high prices we pay for technology products and digital content then Parliament is not the place to do it. Instead, let the Australian public do it through unrestricted markets.
Category: Uncategorized Tags:
by Brian Prentice | April 10, 2012 | Comments Off
One BILLION dollars!
It’s hard to fathom that type of money without putting my pinky to the corner of my mouth.
I’m prepared to give Facebook’s management the benefit of the doubt. I think they have some very good reasons for paying the type of money they are for Instagram. So I won’t be spilling any more digital ink over new investment bubbles and crazy valuations.
But consider this – Instagram is a singularly focused app. It is designed to do one thing well. It allows people to apply a digital filter to pictures they take on their mobile devices and to share them. That’s it. Additionally, Instagram chose to go for native mobile development.
The fact that a simple, focused mobile application can create the disruptive potential to garner even a quarter of Instagram’s purchase price should be ringing alarm bells with application developers the world over.
This, ladies and gentlemen, is a paradigm shift!
Category: Uncategorized Tags:
by Brian Prentice | March 15, 2012 | 2 Comments
Daddy’s got a new iPad! I just got it home.
Since I live in Australia, I guess I’m one of the first. And the experience I had getting it was a lesson in retail done right. Heck, it was an example of capitalism done right! There were five keys to making my purchase a great purchase experience.
- Honesty – Unfortunately, I couldn’t pre-order my iPad because of my travel schedule. So I had no choice but to brave the Apple Store on launch day. I thought I’d avoid any queues but coming at the nonchalant, but early-enough time of 10:30am. No luck, there was still a queue. I asked the staff running up and down the line how long I’d have to wait. They said 30-45 minutes. I was heading back home with my iPad in 40 minutes.
- Efficiency – As I got into the queue, an Apple staff member asked me what model I was looking for. I told them the it was the white 64gb WiFi version. She dug into her bag and gave me a coupon which secured my purchase. The point here is that the Apple Store matched every unit in stock with a coupon. So, if they didn’t have what I wanted I could either pick something else or leave the queue and wait another day. What I didn’t have to do was waste my time to find out what was in stock.
- Courtesy – when I got into the Apple Store I realised why there was a queue. It kept the store from being a mad house. What they were doing was managing the foot traffic so I didn’t end up jostling and fighting people for available product.
- Commitment – I know it seems trite to say this, but the people working at the Apple Store are on some higher plane of retail existence. They are polite in a way that can only come from the sincerest appreciation for what they’re selling. Add to that knowledge of what they’re selling that can only come from people who use what they’re selling. That was evident by the casual conversations staff were having with waiting customers on what they were doing with their iPads.
- The Extra Mile – The Apple Store was prepared to unbox your new iPad and work with you to get it set up. For free! Here in Australia that type of effort would be deemed by other retailers as being a paid-for service…probably one you’d need to book a week in advance.
None of these things happen by accident. Each of these things requires meticulous planning and a sustained effort at maintaining a high performance culture. In a recent interview with Jonathan Ive, Apple’s Senior Vice President of Industrial Design, he said;
“I think that people’s emotional connection to our products is that they sense our care…”
Well, I certainly felt Apple cared about me as they designed an experience to make acquiring a highly popular product on launch day – one where demand is outstripping supply – a pleasurable one.
Why do I feel compelled to write about this? Two reasons.
The first is to point out to vendors hoping to compete with Apple that this is what you’re up against. Your challenge is how you create the same type of experience with retailers who see your products as just another SKU at aisle 6, floor 4, electronics section.
The second reason is to point out how incredibly hard it will be to achieve that. In a case of ironic serendipity, the National Retail Association in Australia has released an inquiry claiming that 118,000 jobs will be lost to online shopping over the next three years and that 33,000 jobs will vanish because of the GST exemption on imported goods bought online under $1000. Australian retailers (and I’m assuming many other around the world) are obsessed with what everyone else is doing to them rather than focusing on what they need to do to compete in a global digital economy.
What they need to learn from Apple is two critical lessons. The first is to make sure that you have a well-designed and integrated retail experience. One where your customers are not penalised (unavailability of some stock, limited access to specials, etc.) if they chose one over the other.
The more important lesson is price consistency. No amount of experience design can entice people into your shop when your asking price is vastly overpriced compared to online oversees alternatives. If I remove the GST from my new iPad purchase, for comparison purposes, then I’m actually getting my iPad slightly cheaper than I could in the US. That’s online, or in store. Now, locally Apple faces the same real estate and staff costs and the same legal obligations as local retailers. How come they can do all this and the local companies can’t?
So, Apple, thanks for the pleasurable experience.
So, Apple competitors, best of luck.
So, Australian retailers, stop whining and pick up your game.
Now, if you’ll excuse me, I have a new iPad to set up.
Category: Uncategorized Tags:
by Brian Prentice | December 11, 2011 | 20 Comments
There’s been a lot of discussion lately about Atos’ CEO Theirry Breton’s plan to implement a zero email policy for internal communications. According to Breton, only 10% of emails received per day are useful. 18% of all email is spam.
I’m curious – what percentage of emails generated internally are deemed as being useless by the people sending them? I’m guessing that would be something closer to 0%.
I’m not being flippant. I think it’s the crux of the problem. While I applaud Breton’s desire to increase productivity and to reduce the encroachment of work into people’s personal lives, I’m afraid he’s misdiagnosed the problem.
The problem with email today is not an ever-decreasing signal-to-noise ratio. Spam filters are doing a pretty good job. And while I concede that I certainly get a lot of unimportant emails every day, I find it takes me no more than 30 minutes to clear the rubbish out. I’d rather spend my 30 minutes doing that than waste it sitting in a meeting room getting nothing done at all. And, prior to the world of email that’s what we spent our time doing. The most common phrase uttered in the 90’s across work cubicles the world over was – “skip the meeting, send an email.” Email emerged as the centerpiece of collaboration and workflow for good reason.
The problem with email is not the volume we see each morning, it’s the stuff left over after it’s been cleared out. It’s the list of things we can’t avoid doing. And that list keeps getting bigger. That’s the true essence of most people’s complaints about email. It’s not a volume problem. It’s an obligation problem. Email “inboxes” have become a misnomer. What we have are email “to do lists.” Woe unto the person that doesn’t stay on top of their email – whether it’s on holidays, at dinner, or on a date. For that person faces a stress-inducing mountain of obligations when they eventually have the heart to log onto their email account(s).
The essence of the email problem is that a global asynchronous one-to-one/one-to-many communication system radically increases the ability of people to seek assistance, create and delegate tasks, update colleagues and coordinate activities.
There is no technology solution to this problem. You can try to parse this out into different applications but the problem remains – as I believe Atos will soon find out.
The only solution, IMO, is to tackle the ballooning administration and bureaucracy overhead in organizations that is fuelling the number of emails being generated. Specifically, our criticism of email as a collaboration tool needs to shift towards the unchecked growth of bureaucracy it enables. And in this context, it is but one piece of IT that is driving the problem. Ask sales reps what they think of CRM. It doesn’t increase their productivity – it drains it as they have to spend increasing amounts of time filling in the system which, in turn, generates more email requests. BPM can standardize best practices – it can also spin out a set of obligations which land in people’s inbox. Every exception to these practices requires streams of emails to associated cc lists, forwards and reply-to-alls.
There are parallels with the argument “guns don’t kill people, people kill people.” Email doesn’t erode productivity and encroaches work into our personal lives, bureaucracy does.”
So don’t fault the tool. Fault what it enables.
Category: Uncategorized Tags:
by Brian Prentice | June 9, 2011 | 1 Comment
Personally, I think Apple’s new iCloud service is brilliant. Personally, I’ll be making heavy use of it. Personally, I like the idea of being able to synchronise contacts across devices. Personally, being able to coordinate documents across all my Apple devices will probably push me to buy an iPad as my primary travel computer.
I’m sure that a lot you, personally, like iCloud for similar reasons.
Personally, I’m also quite sure iCloud will send a huge number of enterprise IT managers into a state of apoplexy.
For all the cool things that this well designed solution will provide you, as an individual, I can assure you that many, many IT departments will fixate on one single fact. iCloud creates a potential situation where corporate IP will find it’s way into people’s personal clouds thus out of reach and control by the company.
Does iCloud create IP headaches that IT organizations will have to deal with? Yes. Does iCloud provide opportunities for IT organizations in delivering innovative solutions to staff. Yes. But when it comes to Apple, the glass is half empty for many IT departments. It’s easier, and more satisfying, to hit the “ban it” button then to look for creative ways to take advantage of the new solution.
So here’s my prediction. Because iCloud is provided as an automatic and free service with iOS 5 we will see IT departments, fixated on this problem, seek to prohibit staff from upgrading their iPhones and iPads. Whether they can enforce this or not is immaterial. Whether a whole lot of other tools that create the same potential risks will be left unnoticed will also be immaterial. We’re talking about those IT organizations with an inbuilt dislike for Apple getting a taste of blood. If you’re currently working for a company that has blocked access to Facebook and Twitter because they fear a loss of IP, you can count on this happening. If you’re a sales rep working for a company that demands all your client’s contact details are entered the corporate CRM system then prepare yourself for the email telling you that iOS 5 upgrades are banned.
And of course all new iPad and iPhone acquisitions, once they start getting shipped with iOS 5, will need to be put on hold. It doesn’t matter whether they’re company or employee funded or made available through agreements with the mobile provider.
For a whole lot of organizations out there, the battle between corporate users and their IT departments is about to escalate.
And that will be a shame. Because at the end of the day this will just delay the inevitable.
Apple’s vision of personal computing has unleashed a massive, pent up demand amongst people. That is undeniable. But they are just one of many companies having success in reaching out directly to the user rather than granting to the enterprise IT department the status of rightful proxy to these people’s requirements. It is also clear that people are no longer prepared to separate their personal and professional digital lives in the way the IT department would like. These two intersecting trends are challenging underlying assumptions of what enterprise computing is all about. Enterprise IT departments can rage all they want about these providers. The thing is they won’t change for you. Nor will the users. Ultimately the enterprise IT department can, should and will probably be the ones having to change.
I am not advocating that IT governance controls simply melt away to make room these consumer-oriented providers. But I am suggesting that some creative thinking might yield innovative solutions that can integrate this very different class of provider into the fabric of the IT environment. Consider something like PC fleet management. How can this process be adapted to deal with a range of devices that will be acquired directly by the employee (there is no such thing as a global iPad rollout driven by the IT department)? How should software version control be governed when some systems will be updated automatically by the supplier through the cloud? You get the picture.
It has been my observation that enterprise IT organizations are some of the most resistant departments to change. Conversely, when change becomes absolutely unavoidable they display an amazing ability to craft intelligent, finely-tuned governance controls to deal with the new reality.
I’d like to suggest to all of you in enterprise IT organizations that changing to adapt to a world of what I call DTTU providers (that’s “direct to the user”) has become absolutely unavoidable.
You might as well start adapting with iCloud.
Category: Uncategorized Tags: