In a few months, my iPhone 3G will be three years old. It’s been a great phone, despite consistently mediocre service from the AT&T voice and data networks. More than a phone, my iPhone was my first truly portable computer and completely changed the way that computers fit into my life. Having been a professional Microsoft server guy for over a decade, the switch to Apple was a radical and tumultuous one. Looking back on my reaction to the original iPhone, I’m amazed at how much I missed the point entirely:

Making a phone with no buttons is brilliant, Steve Jobs. Touch screens never wear out or crack or anything.

The iPhone is bigger than the SLVR and the Chocolate and has no keys. Apple’s track record with battery life on the iPod ranged from shit to OK, but cell phone battery life is much more vital to people day in and day out. And if the touch screens are flaky, this could be a huge flop.

Wow, how wrong I was.

See, I was still thinking of “smartphone” as a phone that does some computer-like things. Steve Jobs and the Apple crew realized that a great smartphone would be a portable computer that had, among other things, a phone application. That idea really did change everything.

I was impressed with the first iPhone, but held out for the second version. I wanted third-party apps, 3G data and a GPS chip and the iPhone 3G delivered on all accounts. And I’ve been happy with my iPhone 3G until now.

Yesterday, Apple released version 4.3 of iOS. It has lots of great new features, including Wi-Fi personal hotspot and a faster version of the Safari web browser. But the new operating system won’t run on my iPhone 3G. After a little over two years, it’s just too old. I’m not upset at Apple. I think this is just the new rate of change in mobile computing. Two years and upgrade.

With only a few months until the iPhone 5 is sure to be released, I’m not about to jump to the iPhone 4 right now. But, I will be pre-ordering the iPhone 5 on Verizon as soon as it’s available.

Posted via email from A Little Slice of Dave

{ 0 comments }

Would you classify this as a design problem or a launch problem?

NASA optimizes for performance. We optimize for cost. They pay five times the cost for the last 5 percent of performance.

- Tom Mueller, Vice President of Propulsion, SpaceX

Everything should be made as simple as possible, but no simpler.

- Albert Einstein

Anybody interested in improving personal or group performance struggles constantly between “Get it Done” and “Get it Perfect”. We want to do our best, and to be proud of the work we do. We also want to get things accomplished and move on to the next important thing.

We make this compromise in two distinct ways. First and most obviously, we do our best up to a point, declare the work “good enough” and then move on. The other way we create “good enough” solutions is to ask a different question, reframe it as a simpler problem and solve that with a simpler solution.

Most of the time, these are good compromises to make, but many times — too often, in fact — they create bigger problems than they solve and can cause a cascade of disasters.

Half-assed is worse than lazy
People at the supermarket who don’t put their shopping carts back annoy me. They make parking spots unusable and make parking lots difficult to navigate for everyone else. One supermarket where I used to shop was on a main highway, and carts would roll out of the parking lots and into oncoming traffic! People create this disorder and mayhem to save themselves about twenty or thirty feet of walking. Seriously, how much lazier can a person be?

But in their laziness, these people have spawned a second solution. Supermarkets hire people to scour the parking lot for carts, gather them together and wheel them back in front of the store. There are downsides. Prices are higher because the market has at least one more salary to pay. Parking lots are still littered with stray carts, but that can be managed to the point of a low-level annoyance that most people don’t even notice anymore. In short, it’s an ugly solution but for the most part it works (even if it does cause a bit of resentment from people who put their carts back themselves).

If we have two working solutions, then why is there a problem?

There is a third group of shoppers who are the actual cause of the shopping cart madness. They push their carts over to the holding stall like group one. But instead of stacking the carts together, they fling them from about six feet away and make a group two style mess inside the holding stall (see pic above).

By committing half-way, they make the holding stall unusable, not only for group one, but for the supermarket employees in group two. They may sort of solve the problem of their individual cart but their “compromise” has broken the entire system of dealing with all carts. To a large degree, they are guilty of creating the hassle that drives people to join group two in the first place.

The worst part, is I’m sure these people think they are making a good compromise. “At least I didn’t leave the cart in the parking lot,” they must think, “It’s not perfect, but it’s good enough.” Nothing could be further from the truth.

  • Think about the effects of your “good enough” compromises and try to see where you may be unintentionally creating “group three” disasters.
  • When giving performance reviews, do you recognize your “group three” employees as negatively affecting your team, or do you fill the box for “Consistently puts shopping cart back in stall” with “Meets expectations”?

Simple is Better than Overly-simple
I’m a big fan of simplification. When we try to tackle a seemingly insurmountable obstacle, the best way forward is often to break it down into simple manageable chunks. If we ask less complex questions, good answers are easier to find.

And if simple is good, simpler is always better, right?

Wrong.

Once a client asked me to design a simple group calendar with some automated workflow through Outlook forms. Because of some inconsistencies with their Outlook deployment, it turned out to be not such a straight-forward endeavor. The forms worked for some people, but not for others.

There were two solutions on the table that would have solved the problem. We could have re-imaged about 50 computers to ensure that everyone in this workgroup had an identical build (i.e., solve the problem by fixing Outlook inconsistencies). Alternately, we could have quickly built a web-based solution that hooked into Exchange server on the backend (i.e., sidestep the Outlook issues altogether).

It was decided that both of these solutions were too complex. We were told to continue to troubleshoot the “simple” Outlook forms solution. Though we spent a little less time than we would have with one of the proposed solutions, ultimately we wound up with a half-working process that was part manual and part automated and wasn’t really any better than the original manual one.

Sure we saved time by removing complexity. But we would have seen a much more worthwhile return if we invested the time in one of the more permanent fixes. We over-simplified the problem to the point that we didn’t solve the original problem. It would have made more sense to scrap the initiative altogether.

  • Think for a moment about past projects that didn’t go to plan. Can you identify an instance when over-simplifying caused you just as much work as tackling the original problem?

{ 0 comments }

iTunes 10: What’s up with the buttons?

September 2, 2010
Thumbnail image for iTunes 10: What’s up with the buttons?

I love the new features of iTunes 10. I love Ping, the new music-centric social network that Apple introduced with the new software. I just have one question: What’s up with the buttons? If there’s one thing that’s Apple’s speciality it’s attention to detail in design leading to excellent consistent user experiences. So, then it […]

Read the full article →

Apple says iOS 4.1 fixes slowness with iPhone 3G

September 1, 2010
Thumbnail image for Apple says iOS 4.1 fixes slowness with iPhone 3G

As a follow-up to my previous post on fixing iPhone 3G slowness after upgrading to iOS 4.0, I’m happy to report that at Apple’s music event today (watch the video here), Steve Jobs announced that iOS 4.1 will permanently fix the bug that caused the iPhone 3G issues. You can check out this post from […]

Read the full article →

Lou Gehrig May Not Have Had Lou Gehrig’s Disease

August 18, 2010

via wired.com The headline reads like something from the Onion, but this article from Wired is an interesting read on the way certain types of brain trauma can be confused for amyotrophic lateral sclerosis (ALS). Maybe we’ll have to start calling it Stephen Hawking’s Disease. Posted via email from A Little Slice of Dave

Read the full article →

I’m a Wikipedia reference (Down the Rabbit Hole)

August 8, 2010

My last blog post is now listed as a reference on the Wikipedia page for the iPhone 3G. So, is that a big deal? I could have just put the link there myself (I didn’t). I feel pretty good about it, because I posted a tip that fixes a fairly widespread problem that people are […]

Read the full article →

3 steps to fix iPhone 3G slowness after iOS4 upgrade

July 27, 2010

If you’re like me, you upgraded your iPhone 3G to iOS4 as soon as it was available. Sure, multitasking wasn’t supported on the 3G, but features like app folders and integrated mailbox were too cool to pass up. Like me (and many others), maybe you also noticed that after the upgrade your iPhone 3G was […]

Read the full article →

Giving Posterous a Try

July 21, 2010

I’ve been looking for a way to consolidate push out messages and links to all of my various social media accounts like Facebook, Twitter, FriendFeed and my personal blog at DaveKawalec.com. It looks like Posterous might fit the bill. It seems to be great for those things that are bit shorter than a blog post […]

Read the full article →

Words are Important: 800-pound Gorilla

June 10, 2010
Thumbnail image for Words are Important: 800-pound Gorilla

Words are Important The business world seems to generate more jargon and buzzwords than goods and services these days. Words are being misused and abused. This is a disaster because words are important. When words can be made to mean anything, they mean nothing. Without precise meaning, we can’t form rational thought and the world […]

Read the full article →

Words are Important: Technically

May 17, 2010
Thumbnail image for Words are Important: Technically

Words are Important The business world seems to generate more jargon and buzzwords than goods and services these days. Words are being misused and abused. This is a disaster because words are important. When words can be made to mean anything, they mean nothing. Without precise meaning, we can’t form rational thought and the world […]

Read the full article →