Yesterday I came across an article that pointed out a patent filing by Apple that could possibly be seen as a push to bring iWeb to the iPad. This is an entry level website creation tool for the Mac that is included with the iLife suite.

We are definitey starting to see a trend; Apple is beginning to show their hand. It is becoming more and more obvious that Apple is trying to move the iPad into the hands of content creators instead of focusing simply on the content producers. The post-PC world is changing and Apple is doing what they can to nudge things in the direction they want.

Most users of tablets and even netbook users are content to just consume. However, in a truly post-PC world unchaining the desktop is a necessity. The laptop and even the netbook failed to accomplish this, instead just moving us back to small screens and allowing us to do our spreadsheets in a coffee shop instead of sitting in a stuffy home office. What they failed to do, and what the iPad is right on the cusp of accomplishing, is to fundamentally change the way we interact with our information devices; how we think and work. This is a sea change in the computing landscape.

As long as people stubbornly hold on to their 25 year old workflow patterns and insist that the tablet operate exactly like their desktop PC they will not move forward and be able to truly grasp and take advantage of the tablet and how it can be most effectively leveraged. As long as people continue to view the iPad as simply a platform for convenient content consumption they will be frustrated with perceived limitations and phantom flaws.

Instead of letting ourselves remain hidebound and pretending the iPad is a very thin laptop we need to adjust our own worldview. Just like how the PC revolution fundamentally changed the way we work the tablet has the same possibilities. All we have to do is open up our minds and embrace it.

Welcome to the post-PC world, ladies and gentlemen! You can either ride the train or get run over!

Flexible Expectations

March 25, 2011

Someone mentioned to me recently that they thought the iPad was a pretty nice “toy” but it didn’t help them do real work. I found this sort of stunning, since I push my new iPad pretty heavily and I know I’m not even anywhere remotely close to maxing out the things I can do with it.

While talking with this person, I began to get a better understanding of the underlying issues. It wasn’t necessarily a problem with the iPad, nor with the apps on it. The problem really existed in two major areas. The first area was the fact that their work network is completely locked down and they have no access to it via the iPad, which fundamentally makes it more of a challenge to transfer information back and forth between the iPad and their desktop. The second area was in a fundamental disconnect in how to operate with the iPad as an integral part of the work flow.

Now I certainly can’t do anything about the first point they raised except shake my head and commiserate. However, I can take a pretty good stab at the second part.

We often say that the tools should adapt themselves to how we work, not the other way around. This isn’t really true all the time, though. If a tool enables a more efficient workflow or exposes an inefficiency, we don’t do ourselves any service by stubbornly sticking to how we have done things in the past. Yes, we shouldn’t necessarily have to throw out everything we know when something new comes along but we shouldn’t allow ourselves to become hidebound or stuck in how we accomplish a task either.

One of the things that I’ve discovered about using an iPad in my day-to-day activities is that most people want to imagine it in their heads like it is a laptop, and then when things don’t operate within that paradigm they get angry, frustrated and disappointed. They continue to try and shove it into a laptop box and when it doesn’t fit they perceive it as a limited platform.

In fact, the iPad is an extremely powerful general purpose computer. As a reference point, I am currently writing this on my iPad using a bluetooth keyboard. I have Pages (a spreadsheet application) running with my financial portfolio graphed and outlined. I have some very good news readers (such as pulse) running to keep me up to date on what is happening, my email is here and I am even listening to music as I work. I can bring up a VNC connection and remote desktop into my work computer and check on something if I need to or access a remote server. I can do pretty much anything I normally do day to day except for writing actual programming code and once I jailbreak my iPad (which I will do eventually) I can do quite a bit of that too.

What the iPad is *not* is a laptop. I can’t simply drop my files onto a USB drive and open them up in excel. I can’t fire up Xcode and test a quick algorithm. These aren’t limitations of the system, they are simply artifacts of the fact that the iPad is a tablet computer that operates in a fundamentally different way.

This person complained to me about transferring data back and forth and I understand how it can be different. However, it doesn’t have to be hard or onerous if you change your way of thinking about the workflow. For example, when I need to take notes in a meeting I fire up plaintext, take my notes, and these notes are automatically saved to my dropbox account. When I return to my desk, the notes are already there and synced, waiting for me to integrate them into whatever I need. If I need to share spreadsheets or presentations back and forth, I use my iwork.com account in a very similar fashion, publishing my document to it from one system and retrieving it from another.

Some people might find this hard to do, but in fact once it is integrated into the way you think about your appliance it becomes second nature. The important thing, though, is to realize that whatever you are using is just that… an appliance. You fundamentally use things differently on a laptop, desktop, tablet, or even your phone. You cannot expect your phone to do the same things your desktop does no more than you’d expect your tablet to replace your laptop. Instead, I find these things all work as extensions of each other. This is just a further extension of my entire “right tool for the right job” mentality.

I encourage you to get a tablet and see if you are mentally flexible enough to adjust your own workflow to take advantage of it. Yes, you may run up against limitations when you are learning to use it. Just be sure those limitations are truly platform limitations, though, and not just limitations in your own workflow.

Many times when a company gets overwhelmed with the need to implement a wildly new technology stack they reach for consultants and contractors to do the work. That’s not always the right approach, though. Sure, it can help you bring a new product online quickly and efficiently, but it leaves you high and dry once the project is done.

It is critically important, especially when a company finds itself facing a technology gap, to grow your internal expertise from within. Contractors and consultants can get the job done quickly, but you have to remember they will leave once it is done and they are under no obligation to pass on their expertise to internal staff. Many times they will actively avoid doing this so that you are forced to call them back whenever you need maintenance, upgrades or changes made to it. They have no loyalty to the company and no real impetus to share their knowledge beyond the bare minimum needed to get their contractual obligations fulfilled.

Don’t fall into this trap. Sure, use outside expertise if you need it, but make sure you set up your teams such that there are sufficient internal employees working side-by-side with the contractors. These employees can soak up the knowledge as they roll up their sleeves and work with the outside expertise. Give the internal employees oversight on the project as well and make them responsible for ensuring the expertise gets shared.

It may take a little more time and a lot more effort to do things this way, but six months down the road when you need some changes made you’ll be able to move quickly and leverage this expertise internally. In addition, all that exposure and knowledge will make your staff better educated, more agile and give them even more tools at their fingertips to use on the next big thing you ask them to do. Any respectable development organization thrives on self-reliance and constant exposure to new tech, toolkits and practices. Keep your programmers happy by keeping them current and competitive.

Keep this in mind next time you pick up the phone and call 1-800-help-me and you’ll thank me eventually. Trust me.

It’s not popular to talk about failure, but it’s something we all need to understand and embrace. There’s nothing wrong with occasional failure, and in fact if you never fail at anything you aren’t pushing yourself hard enough.

If you are at a company that is pushing the envelope you can expect the occasional “oops, my bad” along the way. In fact, you need to plan for it and embrace it. Ideally you’ve got a lot of new things to learn and a lot of interesting ground ahead of you. You can go so many different ways that there is no way you are going to get it 100% right the first time. Sorry, but it just doesn’t work that way.

What you do need to do is plan for it, mitigate the bad parts of it and accentuate the learning portions. You need to be able to quickly identify failure before we get dragged too far along the path and you need to encourage your developers to not be afraid to throw something away if it just doesn’t work. We all should encourage experimentation, foster creativity and embrace the possibility of the occasional failure. If nobody is brave enough to drop something on the floor, we will all stagnate.

There’s nothing wrong with throwing failures away. There’s everything wrong with holding on to them and letting them drag you down.