Skip to main content

Seek Problems, Dream Later

It came to me in a dream. I dreamt I was a bird, soaring above the trees, surfing the wind currents, gliding in for a landing. 


And I realized at that moment that I just had to build a flying machine, and that humans would never naturally fly like a bird because we simply don't have the chest muscles, so we must have something like Wii-controlled, lightweight motorized wing pumps with just enough torque.


Well, none of that's true--for me anyway.

Maybe ideas come from dreams. But most innovation starts at the point of the problem. The concept stage is great because it's like flying in the dream--there's no gravity, no friction, few obstacles.

The real innovation happens when your customers or users try to use what you built on the basis of that concept. You start to learn about friction and gravity, but more importantly, you learn what they really need.

A friend of mine called yesterday to ask if I had ever seen a certain something for websites for small businesses, and I said in fact no, I had not, but it was a great idea. He had dug around the usual spots, and couldn't find anything.

It's one of these things that seems so obvious, but apparently nobody's built  a business. In fact, most of the technology--no--all of the technology already exists. And it's the kind of thing that would likely be broadly adopted, and there could be a real business there.

The only way he discovered that seemingly massive hole was by trying to help customers directly, working with them to help increase their businesses.

And it's not easy--it's work to get enough exposure to the point of the problem in order to innovate.

A founder of  a local started messaged me the other day saying he had made 40 calls with no hits--nobody was interested.

It must have been frustrating, but it made me wonder if he was telling about his solution or learning about what their issues were.

You have great ideas, great concepts, and such great energy that other people nod in agreement when you tell them about it.

But it's only when you immerse yourself in their worlds that you can begin to realize what the real issues are, and what innovations are needed to help them.

Go forth, seek problems--dream later.

Comments

Popular posts from this blog

Beta Signup

I've been working for quite a while on a new search concept, though the further in I get, the closer the rest of the world gets to what we're doing. So today I'm inviting you to sign up for the rather modest beta, which will be ready soon if we can nail down a few difficult  details. Jawaya is a way of navigating the web and getting better results. And that's as much as I can say right now, because we're not a funded startup, and things are moving really fast in this space--it's going to be very competitive. I predict there will be about 10 funded startups in the next 6 months doing something similar. One of them will be mine, and we aim to make it the best. We're raising a round of capital to fund the team, and are shooting for early sustainability. This is my fifth company; my fourth in the tech space, and my third software company. I think it will be the biggest and can possibly have a positive impact on the world by reducing the amount of time it takes

Where Innovation Happens

As I get closer to a go/no-go decision on a project, I've been thinking about the difference about my vision for the project and the supportive innovations to enable the core innovations The vision combines (in unequal parts) product, core innovation as I imagine it, the application of that core innovation, design, marketing,  developer ecosystem, and business development. The core innovation enables everything else, but it's the application of the innovation that makes it meaningful, useful, and in this case, fun. This week we're testing initial approaches to the implementation for our specific application, and that's where we'll develop the enabling innovations, which is basically where the rubber meets the road. The difference is that the enabling innovation happens at the source of real problems only encountered in the making of something, and in a project like this just getting the essence of it right isn't enough; it also has to be safe, the compone

Disqus Digests

This morning my phone dinged with a fresh notification--a new email! What oh what could it be?  I rush over to check while thinking "I need to unsubscribe to a lot of stuff so I get fewer non-urgent dinging notifications." Well shoot, that's disappointing. It's Disqus Digests, one of the biggest wastes of dopamine anticipation ever.  It simply sucks.  Disqus itself is great as a commenting system. I've been there since the beginning and have mostly enjoyed its evolution.  And then they did this interruptive, irrelevant email. Well why does it suck, you say.  Every one of these "Digests" sends a few comments from a blog conversation in which I've already participated. That means it's very, very likely that I've seen the comments before.  So I open the mail, see something I've already read, and curse Daniel and Company for enticing me into wasting my time, and cursing myself for falling for it.  So I unsub