The Future of Work is Service-Oriented
In IT, you used to get all sorts of kudos and accolades if you were responsible for developing and delivering a service oriented architecture. This meant you built services that could be accessed by other services -- an architecture where services could talk to each other, consume whatever the other was offering and, in general, link up in a standards based way. (This is still a good thing, by the way.)
Come up a few thousand feet with me, though, and look at today's landscape. We live in a world where most of us don't necessarily want products. We're more interested in experiences. We don't necessarily crave one-time transactions. We're looking to develop ongoing relationships. For example, we use our smartphones, but what do we do with them? We connect them, via apps, to services on the Internet.
Getting work and getting things done will move in the same direction. To do work, we'll need to connect to different services. We'll expect availability to be constant and never interrupted. We won't want our systems to give us information just one; we'll want our systems to deliver information to us over time. Finally, we'll want our systems to predict what information will be useful to us, at what point that information would be useful, and then push it to us in a useful, non-intrusive way.
Sign up for Computerworld eNewsletters.