Media

You are currently browsing the archive for the Media category.

Does location matter? Or, put another way, is the world no longer flat? Many cloud and SaaS providers work under the assumption that where we store data where it is most efficient from an application performance point of view, ignoring political considerations. This runs counter to many company and governments who care greatly where their data is stored. Have we entered a time where location does matter, not for technical reasons, but for political reasons? Is globalisation (as a political thing) finally starting to impact IT architecture and strategy?

Just who is taking your order?

Just who is taking your order?

Thomas Friedman’s book, The World is Flat, contained a number of stories which where real eye openers. The one I remember the most was the McDonald’s drive through. The idea was simple: once you’ve removed direct physical contact from the ordering process, then it’s more efficient to accept orders from a contact centre than from within the restaurant itself. We could event locate that contact centre in a cheaper geography such as another state, or even another country.

Telecommunications made the world flat, as cheap telecommunications allows us to locate work wherever it is cheapest. The opportunity for labour arbitrage this created drove offshoring through the late nineties and into the new millenium. Everything from call centres to tax returns and medical image diagnosis started to migrate to cheaper geographies. Competition to be the cheapest and most efficient service provider, rather than location, determines who does the work. The entire world would compete on a level playing field.

In the background, whilst this was happening, enterprise applications went from common to ubiquitous. Adoption was driven by the productivity benefits the applications brought, which started of as a source of differentiation, but has now become one of the many requirements of being in business. SaaS and cloud are the most recent step in this evolution, leveraging the global market to create solutions operating at such a massive scale that they can provide price points and service levels which are hard, if not impossible, for most companies to achieve internally.

The growth of the U.S. enterprise application market

The growth of the U.S. enterprise application market (via INPUT)

Despite the world being laser levelled within an inch of its life, many companies are finding it difficult to move their operations to the cost-effective nirvana that is cloud and SaaS services. Location matters, it seems. Not for technical reasons, but for political ones.

Where we store our assets is important. Organisations want to put their assets somewhere safe, because without assets these the organisations don’t amount to much. Companies want to keep their information — their confidential trade secrets — hidden from prying eyes. Governments need to ensure they have the trust of their citizens by respecting their privacy. (Not to mention the skullduggery this is international relations.) While communications technology has made it incredibly easy to move this information around and keep it secure, it has yet to solve the political problem of ensuring that we can trust the people responsible for safeguarding our assets. And all these applications we have created — both the traditional on-premesis, hosted or SaaS and cloud versions — are really just asset management tools.

We’re reached a point where one of the a larger hidden assumptions of enterprise applications has been exposed. Each application was designed to live and operate within a single organisation. This organisation might be a company, or it might be a country, or it might be some combination of the two. The application you select to manage your data determines the political boundary it lives within. If you use any U.S. SaaS or cloud solution provider to manage your data, then your data falls under U.S. judicial discovery laws, irregardless of where you yourself are located. If your data transits through the U.S., then assume that the U.S. government has a copy. The world might be flat, but where you store your assets and where you send them still matters.

Country-specific regulations governing privacy and data protection vary greatly.

Global data protection heat map (via Forrester)

We can already see some moves by the vendors to address this problem. Microsoft, for example, has developed a dedicated cloud for the U.S. government, known as BPOS Federal, which is designed to meet the government’s stringent security and privacy standards. Amazon has also taken a portion of the cloud it runs and dedicated it to, and located it in, the EU, for similar reasons.

If we consider enterprise applications to be asset management tools rather than productivity tools, then ideas like private clouds start to make a lot of sense. Cloud technology reifies a lot of the knowledge required to configure and manage a virtualised environment in software, eliminating the data centre voodoo and empowering the development teams to manage the solutions themselves. This makes cloud technology simply a better asset management tool, but we need to freedom to locate the data (and therefore the application) where it makes the most sense from an asset management point of view. Sometimes this might imply a large, location agnostic, public cloud. Other times it might require a much smaller private cloud located within a specific political boundary. (And the need to prevent some data even transiting through a few specific geographies – requiring us to move the code to the data, rather than the data to the code – might be the killer application that mobile agents have been waiting for.)

What we really need are meta-clouds: clouds created by aggregating a number of different clouds, just as the Internet is a network of separate networks. While the clouds would all be technically similar, each would be located in a different political geography. This might be inside vs. outside the organisation, or in different states, or even different countries. The data would be stored and maintained where it made the most sense from an asset management point of view, with few technical considerations, the meta-cloud providing a consistent approach to locating and moving our assets within and across individual clouds as we see fit.

Tags: , , , , , , , ,

Another week and another collection of interesting ideas from around the internet.

As always, thoughts and/or comments are greatly appreciated.

Tags: , , , , ,

I stumbled onto a somewhat interesting post over at HBR, which talks Garry Kasparov’s ideas in the business world. This is actually quite a relevant pairing, though an old one in the tradition of human-computer augmentation.

The idea a simple one, which takes far fewer words to express than the article took.

Use information technology to augment users, rather than replace them.

IT is good at lot of tasks, and less good at others. People, too, have their strengths and weaknesses. What’s interesting is that computers are weak where people are strong, and vice-versa. Computers excel as appliers of algorithms with huge memories and an attention to detail; people are powerful, creative problem solvers who have trouble thinking of four things at once and like coffee breaks. Why not pair the two, and get the best of both worlds.

Rather than replace the users, why don’t we use technology to automate the easy (for technology) 80% of what they do. (This is something I’ve written about before.) In the chess example, the easy 80% is providing the user with a chess computer for the commoditized solution space search, allowing them to focus on strategy. The performance improvement this approach provides can create an significant competitive advantage. As Garry Kasparov found, even a weak user with a chess computer can be impossible to defeat, by human or computer.

This then provides us with two options:

  1. Take the improvement as a saving by reducing head count.
  2. Reinvest the improvement by providing our users with more time to focus on the hard 20%.

(I must admit, i much prefer the later.)

If we continue to focus on automating the next easy 80%, we’ve created a platform and process for continual business optimisation. (Improvements in search efficiency would simply be harvested when appropriate to maintain parity.) Interestingly, this is one of only two sources of a sustainable competitive advantage available to us today.

The competative advantage with this approach rests with the user, in the commonplaces, the strategies, they use to solve problems. By reifying the easy 80% these strategies in software (processes and rules) we are moving some of the competitive advantage into the organisation with it can leveraged by other users. By continually attacking the easy 80% of what the users are doing, we are continually improving our competitive position. We could even sell our IT platform (but not the reified problem solving strategies) to our competitors — commoditzing the platform to realise a cost saving — without endangering our competitive position, as they would need to go through the same improvement and learning process that we did, while we continue to race ahead.

Now that’s scary: as long as we keep improving our process, our competitors will never be able to catch us.

Posted via web from PEG @ Posterous

I’ve already written about why I think private clouds can be a good idea. Similar arguments can be made for SaaS, and then some. A friend and I did the email-ping-pong thing and ended up with a (shortish) list of reasons why to go with a SaaS solution over an traditional on-premises solution.

  • OPEX rather than CAPEX cost. The CAPEX gulp is minimised, and the ongoing costs are tied to your own operational cost (head count, etc).
  • Faster provisioning. SaaS is can be up to 90% faster to deploy than on-premises solutions. (Weeks/months rather than months/years.)
  • No more upgrades. You’re always on the latest version, and new features are roll out organically rather than every few years as part of a change management process.
  • More focused vendor and community support. As there is only a single version in play, support efforts from the vendor and user community are focused on the version that you’re using. This also avoids the problem of getting left behind on a stale and unsupported platform (been there, done that, and have the scars to prove it).
  • SaaS provides a platform that scales organically with our organization. You’re not required to invest in additional hardware, software, and provisioning processes, letting your business focus on the business.
  • Reduced IT involvement. IT resources can focus on specific business problems rather than the care and feeding of the system.
  • Try before you buy. Instead of a traditional big license gulp at risk, sign up for a handful of SaaS seats for a few weeks and try it out. (From @shermo1.)

Any more?

Posted via web from PEG @ Posterous

Tags:

Death, taxes, and now, change, are the eternal verities. As I said in another post:

The pace of change has accelerated to the point that everyone’s challenge, from Pre-Boomers and Baby Boomers through Generation Y to Generation Z, is how to cope with significant change over the next ten years. If we are, as some predict, moving to an innovation economy, then it is the ability to adapt that is most important. Those betting their organisation on a generational change will be sadly disappointed as no generation has a monopoly on coping with change.

While the youngest generation (whichever that is at a particular point in time) might have the advantage of coming unencumbered to the new ways of working, every generation has a unfortunate habit of treating what they learnt in their formative years (~24) as dogma once they hit their late 20s. Social research has shown that most people’s interest in novel ideas or experiences peaks around the mid to late 20s. (Tell me your favourite band and cuisine, and I’ll tell you what decade you grew up in.) Or, put another way, 24–28 might have the advantage in a rapidly changing world, but once you grow out the top of that age bracket you’ll find yourself at the disadvantage.

However, as with all gross generalisations, and the exceptions are more interesting than the rule; in this case the commonalities between groups are usually stronger than the differences between them. Research like Forrest’s Groundswell show that its more productive to think in terms of personality types.

I prefer to focus on getting stuff done, and ensuring that each and every stakeholder has the tools and support they need to get their job done. This is not a static thing either, something we do once for each stakeholder, as someone’s needs and preferences can change month-by-month, week-by-week, day-by-day or even minute-by-minute.

And this is probably the most important mega-trend we’re seeing emerge at the moment: the drive to continually personalise communication/products/services/tools for each and every individual, rather than trying to divide people into coarse-grained, and increasingly unproductive, demographic groups with predefined needs. If you’re managing change, then you’re still thinking in terms of a static work/home environment that needs to be transformed (however regularly). If you’re managing personalisation, then you’re focused on creating a continually optimised environment for all your stakeholders, ensuring that they have the information and tools they need at that moment. Change isn’t an enemy that should be managed—its a tool to help you achieve, and sustain, peak performance.

Posted via web from PEG @ Posterous

There’s a quite a bit of noise in the blogsphere about the coming entrepreneurship boom, generating yet another pointless debate about the distinction between generations. What is really going to drive this new boom is the ability to find new white spaces, not access resources or connections (people forget that Sergy & Larry had a good idea and connections into the VC network in the Bay Area).

Twitpic is a case in point. Started on a spare server to scratch an itch, Twitpic is a poster child on how to build something new with little or no resources or connections.

  • In terms of traffic, Alexa says Twitpic is a top 100 site.
  • In 2009, the site did over $1.5 million in ad sales.
  • For every million in sales, the company keeps $700,000.
  • The site has about 6.5 million registered users.
  • Noah, the founder, was recently offered 8 figures for the business.
  • There are only 4 people working on the site (including Noah’s parents).

The common point with services like Twitpic and Craig’s List is that this new generation of businesses are creating new white spaces, and that the cost and accessibility of attacking these white spaces is now very very low.

Posted via web from Business-Technology

Tags: ,

Another week and another collection of interesting ideas from around the internet.

As always, thoughts and/or comments are greatly appreciated.

Tags: , , , , , , ,

Google (well, James Hamilton) has weighted in on the question of private clouds. As expected from a large cloud provider, James takes the position that private clouds make no sense. His reasoning is straight forward: private clouds will never have the scale of public clouds, therefore private clouds can never achieve the same price point as their public brethren. Ergo, there’s no point in building private clouds.

As I’ve pointed out before, there’s a lot more to cloud than simply reducing costs. The biggest benefit is probably the agility that cloud can bring to your IT estate, leveraging a cloud platform’s ability to codify and automate many of the management practices and create a target platform that can work across a range of deployment options, as well as streamlining hardware provisioning. Companies are also increasingly having to deal with the realities of political boundaries, a situation where the best technical solution might not be acceptable due to legal requirements (such as privacy legislation). Developing a private cloud can be a sensible move in this context.

Of course, if you want to compete purely on cost then private cloud will never hit the same price point as public cloud. But this misses the point that for many companies IT flexibility/agility is more important than cost.

Note: I was going to post this as a comment on James’ post, but comments appear to be broken.

Posted via web from PEG @ Posterous

Tags: , ,

Have we managed to design agility out of enterprise IT? Are the two now incompatible? Our decision to measure IT purely in terms of cost (ROI) or stability (SLAs) means that we have put aside other desirable characteristics like responsiveness, making our IT estates more like the lumbering airships of the 1920s. While efficient and reliable (once we got the hydrogen out of them), they are neither exciting or responsive to the business. The business ends up going elsewhere for their thrills. What to do?

LZ-127 Graf Zeppelin

LZ-127 Graf Zeppelin

An interesting post on jugaad over at the Capgemini CTO blog got me thinking. The tension between the managed chaos that jugaad seems to represent and the stability we strive for in IT seems to nicely capture the current tensions between business and IT. Business finds that opportunities are blinking in and out of existence faster than ever before, providing dramatically reduced windows of opportunity leaving IT departments unable to respond in time, prompting the business to look outside the organisation for solutions.

The first rule of CIOs is “you only have a seat at the strategy table if you’re keeping the lights on”. The pressure is on to keep the transactions flowing, and we spend a lot of time and money (usually the vast majority of our budget) ensuring that transactions do indeed flow. We often complain that our entire focus seems to be on cost and operations, when there is so much more we can bring to the leadership team. We forget that all departments labour under a similar rule, and all these rules are really just localised versions of a single overarching rule: the first rule of business, which is to be in business (i.e. remain solvent). Sales needs to sell, manufacturing needs to manufacture, … By devoting so much of our energy on cost and stability, we seems to have dug ourselves into a bit of a hole.

There’s another rule that I like to quote from time-to-time: management is not the art of making the perfect decision, but making a timely decision and then making it work. This seems to be something we’ve forgotten in the West, and particularly in IT. Perfection is an unattainable ideal in the real world, and agility requires a little chaos/instability. What’s interesting about jugaad is the concept’s ability to embrace the chaos required to succeed when resource constraints prevent you for using the perfect (or even simply the best) solution.

Vickers F.B. 5 Gunbus

Vickers F.B.5. Gunbus

Consider a fighter plane. The other day I was watching a documentary on the history of aircraft which showed how the evolution of fighters is a progression from stability to instability The first fighters (and we’re talking the start of WWI here–all fabric and glue) were designed to float above the battlefield where the pilots could shoot down at soldiers, or even lob bombs at them. They were designed to be very stable, so stable that the pilot could ignore the controls for a while and the plane would fly itself. Or you could shoot out most of the control surfaces and still land safely. (Sounds a bit like a modern, bullet proof, IT application, eh?)

The Red Baron: NAME

The Red Baron: Manfred von Richthofen

The problem with these planes is that they are very stable. It’s hard to make them turn and dance about, and this makes them easy to shoot down. They needed to be more agile, harder to shoot down, and the solution was to make them less stable. The result, by the end of WWI, was the fairly unstable tri-planes we associate with the Red Baron. Yes, this made them harder to fly, and even harder to land, but it also made them harder to hit.

Wizz forward to the modern day, and we find that all modern fighters are unstable by design. They’re so unstable that they’re unflyable without modern fly-by-wire systems. Forget about landing: you couldn’t even get them off the ground without their fancy control systems. The governance of the fly-by-wire systems lets the pilot control the uncontrollable.

The problem with modern IT is that it is too stable. Not the parts, the individual applications, but the IT estate as a whole. We’ve designed agility out of it, focusing on creating a stable and efficient platform for lobbing bombs onto the enemy below. This is great is the landscape below us doesn’t change, and the enemy promises not to move or shoot back, but not so good in today’s rapidly changing business environment. We need to be able to rapidly turn and dance about, both to dodge bullets and pounce on opportunities. We need some instability as instability means that we’re poised for change.

Jugaad points out that we need to allow in a bit of chaos if we want to bring the agility back in. The chaos jugaad provides is the instability we need. This will require us to update our governance processes, evolving them beyond simply being a tool to stop the bad happening, transforming governance into a tool for harvesting the jugaad where it occurs. After all, the role of enterprise IT is to capture good ideas and automate them, allowing them to be leveraged across the entire enterprise.

Managing chaos has become something of a science in the aircraft world. Tools like Energy-Maneuverability theory are used during aircraft design to make informed tradeoffs between weight, weapons load, amount of wing (i.e. ability to turn), and so on. This goes well beyond most efforts to map and score business processes, which is inherently a static pieces/parts and cost driven approach. Our focus should be on using different technologies and delivery approaches to modify how our IT estate responds to business change; optimising our IT estate’s dynamic, change-driven characteristics as well as its cost-driven static characteristics.

This might be the root of some of the problems we’re seeing between business and IT. IT’s tendency to measure value in terms of cost and/or stability leads us to create IT estates optimised for a static environment, which are at odds with the dynamic nature of the modern business environment. We should be focusing on the overall dynamic business performance of the IT estate, its energy-maneuverability profile.

Tags: , , , , , ,

Garther have suggested that by 2012, 20% of companies will own no IT assets. At the same time we have Forrester predicting a boom in IT. I think both of them are right, and what we’re seeing is a breaking of the old covenant between business and the IT services industry (which includes internal IT departments). The old relationship was founded on the development and maintenance of IT assets (networks, applications, desktops …). The new one will be founded on something different. The new IT industry is going to be a different beast (i.e. no more strategic transformation or infrastructure projects), and we’ll need to radically reconfigure our organisations if we want to play a part.

Posted via web from PEG @ Posterous

Tags: , , ,

« Older entries