Computer Screen Size, Revisited

Late last year, I wrote that laptop screen size is not itself a requirement, but that the real requirements are on usability and productivity when using the computer. A large screen size is one of the most effective ways of enhancing such usability and productivity. I have always favored laptops with large screen sizes for this reason.

Now, Apple has the results of a study comparing productivity when using its 30-inch external monitor versus using a smaller 17-inch monitor. Among the major conclusions:

Computer displays are a widely overlooked productivity factor of the personal computer, and they can contribute significantly to productivity, efficiency, and overall throughput.
Productivity and efficiency gains documented in these productivity measures are present in not only digital imaging and design applications, but also in office applications as well as in personal productivity of the computing environment.
A larger display area often results in new productivity strategies that make best use of the display in ways that one cannot easily imagine when working on a smaller display.

What is significant about these findings? The main significance is in its exposing how the emphasis on faster processors is misplaced. Instead of just worrying about feature specs, your product manager should be focusing on what really impacts users.

Comments

bob said…

What can we learn? That Apple wisely realized that you can't show faster CPU as easily as you can show Bigger Screen. By quoting "research" that purports to prove the productivity advantages of a large screen, they try to associate business benefit to something that will help them drive the ASP of the iMac line up and up.

Thu Sep 14, 04:23:00 PM 2006

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Cauvin

Search This Blog