29 Jul 2010

The Most Powerful Wind Turbine Looks Like the Weirdest Too [Engineering]

In the future, we will look at these 885-foot-wide structures in the middle of the ocean and we won't even blink. But, right now, I'm having a hard time imagining them spinning en masse at 20 revolutions per minute. More »


27 Jul 2010

7 Reasons Why Techies Love Inception

With opening weekend box office receipts of $62.8 million, it’s clear that the film “Inception” appeals to a broad audience, but Silicon Valley in particular is burning with love for this movie. And I can see why: I loved Inception because I am a geek and a techie at heart. Why does being a geek mean that this movie appeals to me?  True to the spirit of the movie, let me address that question on multiple levels. (Don’t worry — I’ll try to do this in a way that doesn’t have too many spoilers).

First, and most superficially, this is a mashup of movie genres that resonate with geeks: The movie combines science fiction, espionage, con games and action movie elements, with requisite car chases and gun battles, spiced up by some excellent special effects (Paris folding in on itself is to die for).

Second, the hero is a good-looking geek — and so is his female colleague. Cobb (Leonardo DiCaprio) works with a team of hackers — including a really smart, beautiful female geek (I am officially in love with Ellen Page) — who together set out to hack wetware, rather than software. He is deeply passionate about his work and unable to draw a line between his personal and professional pursuits. That’s something geeks can all relate to. But it gets better.

Third, they are attempting a hack that no one else has done before — implanting an idea in someone’s brain so that the person truly feels it is his own idea. If you’re the kind of geek who yearns for detailed schematics of the technology behind all of this, you’ll be disappointed – there are none. This is a movie for the Dungeons-and-Dragon crowd, who are prepared to suspend disbelief in the interest of the game.

Fourth, this team of hackers creates designer dreams, defining elaborate settings and choreographing action so that the “players” end up doing things according to plan – well, at least most of the time. Many critics have put down the movie because the dreams are neat and orderly, not messy and chaotic — but that’s the point, these are geek dreams, carefully programmed in advance, like a video game. In fact, these aren’t even really dreams; they’re artificial constructs that have clear rules and complex labyrinths that must be explored in order to progress.

Fifth, these dreams have multiple layers, with clear protocols for moving from one level to the next. Sounds suspiciously like a technology stack.  But like most technology stacks, even the best defined interfaces sometimes yield unexpected ripple effects across the layers – often something happening in one layer of this dream world results in some kind of disturbance in other layers of the stack. Damn it, can’t we eliminate those messy interdependencies?

Sixth, we have a doomed love story. Cobb spends a good part of the movie yearning for his lost wife, regretting and reliving the loss. A key message of the movie, underscored by the Edith Piaf song that repeatedly plays throughout, is that regret is a draining emotion that one must learn to let go.  It is perhaps not coincidental that the lost love’s name is Mal – French for bad. What geek isn’t driven by regret over a lost love or at least a lost opportunity?

Finally, and perhaps most importantly, there are unresolved mysteries. The movie does not neatly wrap everything up in the end.  We are left with major uncertainties that trigger some vigorous debates among those who have seen the movie, with evidence to support very different interpretations of the end. The end very likely may be just a beginning, true to the title of the film. There is much more to be learned. Nothing less would satisfy a geek.

John Hagel heads a research center in Silicon Valley and is the co-author of the recently released The Power of Pull.  His website is www.johnhagel.com.

21 Jul 2010

GTD Times: 10 big ideas from GTD

Josh Kaufman wrote a succinct review of Getting Things Done on his blog, The Personal MBA.  David saw it and commented to Josh, “I’ve run across few people who have “grokked” GTD conceptually as well as you have.”  With Josh’s permission, we’re sharing his complete review here.

~~~~~~~

If you’re ready to stop stressing and start accomplishing your goals, David Allen’s Getting Things Done can help you create a simple, effective personal productivity system.

About David Allen

David Allen is the author of the Personal MBA-recommended book Getting Things Done, as well as Ready For Anything, and Making It All Work. For more information about his work, check out David Allen’s website.

Here are 10 big ideas from David Allen’s Getting Things Done

1. If your day-to-day life is out of control, it’s almost impossible to think strategically or plan effectively.

When you’re feeling overwhelmed about how much you have to do (and who isn’t, really?), it’s difficult to focus on ensuring your life and work is moving in the direction you want to go. That’s why it’s important to get control of your daily tasks before working on your big-picture life planning.

GTD is a “bottom-up” approach to productivity. The goal is to establish a sense of comfort and control over the work that’s on your plate right now, so you can free up some mental energy and space to think about the big stuff.

2. Define what being “done” looks like.

Most of the tasks people keep on their to-do lists are “amorphous blobs of undoability” – commitments without any clear vision of what being “done” looks like. That’s a huge problem – your brain is naturally designed to help you figure out how to do things, but only if you know what the end point looks like.

Everything you’re working on should have a very clear stopping point – a point where you know you’re done. If you don’t know what that point looks like, you’ll find it very difficult to make any progress at all. When you’re having trouble making progress, first clarify what being done looks like.

3. Mental work has five distinct phases: Collect, Process, Organize, Do, and Review

Not all work is the same. There are five separate phases of effective work:

  • Collecting is the act of gathering inputs: resources, knowledge, and tasks. You’ll have a much easier time making use of your available inputs if they’re all in one place before you begin.
  • Processing is the act of examining your inputs: what you can do with the resources at your disposal. This is where you start separating things according to what you’re planning to do next: tasks, projects, future plans, and reference information.
  • Organizing means taking the results of your processing and putting it in a system you trust, so you don’t have to remember it all. Tasks go on your to-do list, projects go on a projects list, future plans go into a tracking system, and reference information goes into a file or database you can access easily.
  • Doing means working through the tasks you can accomplish right now.
  • Reviewing means examining the results of your work, revising your strategy, and improving your systems for better results.

Keep the phases deliberately separate, and you’ll get a lot more done.

4. Get everything out of your head.

Many people try to keep track of everything they need to do in their mind, which is a big mistake. Our brains are optimized for fast decision-making, not storage. Trying to juggle too many things in your head at the same time is a major reason we get stressed out when there’s a lot going on: we’re using the wrong tool for the job.

The best way to stop mentally thrashing and start being productive is to spend a few minutes putting everything on your mind onto paper. You can write or draw – whatever works for you, as long as you can see it when you’re done. Once the information is out of your head, it’s far easier to figure out what to do with it. Even 10 minutes of Externalization can help you feel less freaked out about your workload.

Of course, it’s better not to be freaked out in the first place, so make it easy to capture what you’re thinking on paper. I carry a wallet that has a space for 3×5 index cards and a pen – whenever I have an idea, it’s easy to capture it, even if I don’t have my notebook or computer with me at the time. If you reduce the Friction you experience when capturing ideas, you’ll naturally capture more of them.

5. Projects and tasks are two different things: track them separately.

A major mistake that most people make when keeping track of things to do is conflating tasks and projects. That’s a good way to feel overwhelmed fast – many things can’t be accomplished in one sitting.

For example, I just finished the book I’ve been writing for a little over a year. If I had “write the book” on my to-do list, I’d quickly be overwhelmed – the project was just too big. Instead of “failing” to accomplish that to-do for a year, it’s far better to treat it as a project – something that takes more than one task to accomplish. I can’t “write the book,” but I can complete a small section of the book in one sitting.

Since projects and tasks are two different things, it’s best to keep track of them separately. Personally, I carry a small notebook with me to record active tasks with 3×5 index card inside that lists my active projects. The index card is just the right size to list 4-8 active projects – if I have more than that, I know I’m spreading myself too thin.

6. Focus on the Next Action required to move forward.

Big projects have many steps, and can be overwhelming in their complexity. The key to handling these projects is not to focus on everything that has to be done – that’s a great way to freak yourself out.

Instead, just focus on the very next physical action you need to do to move the project forward. It may be looking up a piece of information, making a phone call, or accomplishing a small task. Whatever it is, it’ll move you closer to completing the project, so don’t worry about everything else – focus only on what you can do right now.

7. Use the “2 Minute Rule” for small tasks.

Don’t worry about tracking small tasks – if you can accomplish the task in less than two minutes, just do it! Writing down every little thing you have to do takes more time than it’s worth – if you need to send a 30-second reminder e-mail to someone, there’s no sense in taking 20 seconds to write it down when you could just get er done.

Personally, I expand this to 5 minutes – the principle is the same. Your goal is to get things done, not to flawlessly capture each and every little thing in your perfectly designed system.

8. Use Reference and Someday/Maybe files for things that have no immediate next actions.

There’s no sense in keeping FYI or long-term dreams in your active daily task tracking system. Reference files are great for storing information you don’t have to act on right now. These files can either be physical or electronic – for example, I keep important paperwork and legal documents in a fire-proof safe, and electronic files and websites in a file on my computer or in Evernote.

Someday/Maybe lists are great for deferring ideas that you’d like to work on someday, but you’re not committing to right now. I have ideas about fun new things do to every day – way more than I have time or energy for. Instead of losing these ideas, it’s far better to capture them in a reference file you can look through later, when you have more capacity. When you’re ready to commit to a new project, the someday/maybe gets promoted to an active project.

9. Build a trusted system that helps you keep track of your commitments.

Your mind keeps things in working memory if it thinks you’ll lose them if it doesn’t. That’s why building a productivity system is important – it helps your mind let go of tracking unnecessary details so you can focus on the task at hand. That’s why Externalization works – when you put something on paper in a place you know you’ll be able to find later, you’re freeing mental resources that can be put to better use elsewhere.

An effective productivity system consists of the following:

  • A list of active tasks – next actions you’ve committed to accomplishing in the next few days.
  • A list of active projects – 4-20 project you’ve committed to accomplishing in the next few weeks.
  • A calendar – commitments to meet with other people in the near future.
  • A someday/maybe list – ideas you’d like to explore, but not right now.
  • Reference files – information or documents you’ll need to refer to in the future.
  • A capture device – some way of capturing ideas or next actions as you think of them.

That’s it, really – you can use any number of tools for the above, as long as they cover those basic needs. Personally, I use a notebook for active tasks, a 3×5 index card in that notebook for projects, the calendar on my computer, someday/maybe and reference files in Backpack and Evernote or physical files, and my 3×5-sized wallet for my capture device.

10. Schedule non-negotiable time for a Weekly Review.

Life moves fast – we often have so much to do that’s it’s difficult to take a step back and examine whether or not we’re getting the results we want. That’s why it’s extremely important to schedule some time each week to do a “Weekly Review.”

Here are a few things you should include in your weekly review:

  • Process and organize – anything you’ve collected but haven’t handled yet.
  • Review your active tasks – are there any to add, delegate, defer, or delete?
  • Review your active projects – are there any to add, delegate, defer, or delete?
  • Review your calendar – are there any meetings to add, delegate, defer, or delete?
  • Someday/Maybe – anything to add or promote to an active project?
  • Reference Files – anything you need soon? Anything to add or update?
  • Goals – are you moving in the right direction? Are you making progress? Are any changes necessary?

Don’t skip this review – it’s extremely important if you want to decrease your stress levels. Personally, I find it best to schedule my review for the end of the week: Friday afternoon or Saturday morning. It’s a great way to wrap up the week, feel good about what you’ve accomplished, plan for the next week, and set yourself up for a relaxing weekend.

BONUS TIP: developing an effective personal productivity system takes time and experimentation.

Many people get frustrated when adopting GTD because it takes so long to get everything under control. Cut yourself some slack: GTD is a collection of habits, and habits take time to develop. Instead of trying to install everything at once, work on improving in one of these areas until it’s effortless, then focus on installing the next habit. In time, you’ll master them all.

Also remember that the goal of GTD is to make it easier to do work that matters – not procrastinating by endlessly improving your system instead of doing productive work. Try to avoid succumbing to “productivity porn” – experiment constantly, but remember that the most effective systems have the same thing in common: they’re usually the simplest thing that could possibly work. When in doubt, err on the side of doing less.

Josh Kaufman is an independent business teacher, education activist, and author of the Personal MBA: A World-Class Business Education in a Single Volume, which will be published by Portfolio on December 30, 2010.

Tags: GTD Times Team - Staff Contributors, Getting Started, Getting Things Done, Implementation, Reviews //
Add Comment »

20 Jul 2010

High Ground Maneuver (iPhone 4 and Steve Jobs)

I'm sure you're all following the iPhone 4 story. If you hold the phone a certain way, it drops calls. 

In a press conference on the subject, Steve Jobs said, "We're not perfect. Phones are not perfect. We all know that But we want to make our users happy." 

Jobs got a lot of heat about his response. Where was the apology? Where was the part where he acknowledged that the buck stops with him, and that Apple made a big mistake that never should have happened? That's public relations 101, right?

I'm a student of how language influences people. Apple's response to the iPhone 4 problem didn't follow the public relations playbook because Jobs decided to rewrite the playbook. (I pause now to insert the necessary phrase Magnificent Bastard.) If you want to know what genius looks like, study Jobs' words: "We're not perfect. Phones are not perfect. We all know that. But we want to make our users happy." 

Jobs changed the entire argument with nineteen words. He was brief. He spoke indisputable truth. And later in his press conference, he offered clear fixes. 

Did it work? Check out the media response. There's lots of talk about whether other smartphones are perfect or not. There's lots of talk about whether Jobs' response was the right one. But the central question that was in everyone's head before the press conference - "Is the iPhone 4 a dud" - has, well, evaporated. Part of the change in attitude is because the fixes Apple offered are adequate. But those fixes easily could have become part of the joke if handled in an apologetic "please kick me" way. 

If Jobs had not changed the context from the iPhone 4 in particular to all smartphones in general, I could make you a hilarious comic strip about a product so poorly made that it won't work if it comes in contact with a human hand. But as soon as the context is changed to "all smartphones have problems," the humor opportunity is gone. Nothing kills humor like a general and boring truth. 

I've wondered for some time if Jobs studied hypnosis, or if he's some sort of freakish natural. And I wonder how much of his language is planned versus off-the-cuff. He speaks and acts like a master hypnotist. (For new readers, I'm a trained hypnotist myself, and it definitely takes one to know one.)

I have long had a name for Jobs' clever move. I call it the "High Ground Maneuver." I first noticed an executive using it years ago, and I've since used it a number of times when the situation called for it. The move involves taking an argument up to a level where you can say something that is absolutely true while changing the context at the same time. Once the move has been executed, the other participants will fear appearing small-minded if they drag the argument back to the detail level. It's an instant game changer.

For example, if a military drone accidentally kills civilians, and there is a public outcry, it would be a mistake for the military to spend too much time talking about what went wrong with that particular mission. The High Ground Maneuver would go something like this: "War is messy. No one wants civilians to die. We will study this situation to see how we can better avoid it in the future."

Notice that the response is succinct, indisputably true, and that the context has been taken to a higher level, about war in general. That's what Jobs did. It's a powerful technique, and you can use it at home.

There's a limit to the method. I don't think that BP could have gotten away with it as a response to the oil spill because the problem was so large and it seemed unique to BP. But if they had tried the High Ground Maneuver, it would have looked like this: "All of the easy sources of oil have been found fifty years ago. If the oil industry stops taking risks, many of you would be out of work in less than a decade. We all want a future of clean energy, but no one sees a way to get there as quickly as we need to. We will do everything we can to clean up the spill, and to make things right with the Gulf economy."

Someday business students will read about Steve Jobs' response to the iPhone 4 issue and they will learn that the High Ground Maneuver (probably by some other name) became the public relations standard for consumer products companies from that day on.

Roel Smelt's Urgency Flow


With a history in consulting and project management, Roel Smelt is specialized in start-ups and turnarounds, realizing ideas and concepts into real-time and virtual organizations with focus and execution power!