We'll always remember our first real lightbulb idea. For me it was late 2009, I was sitting at my desk, on a course that I soon realised wasn't really going to teach me anything that useful. Not that I knew everything – not at all – but the culture there wasn't exactly one of pushing you to be your best, they were just happy that we turned up.
This day was different though. As I sat there, daydreaming (as I often do), I realised something – I love reading. I really wanted a place to keep tabs on what I'd read, and maybe add a quick review on what I thought. I'd also quite like a way of finding out what my friends were reading and what they recommend reading next.
"Oh! What if there was a Facebook for book readers! That'd be awesome!"
That evening on the train home I rang Mike to chat about the idea. We were both really excited about what it could be. We even came up with a super awesome codename (#blackhawk) so that no eavesdroppers would pick up on our idea and run off into the distance with our millions.
I then spent the next week writing up exactly what the site would do, what each page's purpose was and sketched out roughly how it would look. I had 6 or 7 pages of pure gold, or at least that's what I thought at the time.
With my plan in hand we agreed to meet up at a nearby pub. We sat in the garden next to a quiet stream with a good beer and talked it through. We spent a good couple of hours there going through the notes and discussing what the site would be. When we finished we both left excited about our first real idea, and soon got stuck into the design and development.
After a couple of months, we had an initial design, some code and a clearer view of the path ahead, including how we'd monetise the site. We were making progress, things were taking shape. Remarkably we were still just as excited as that day at the pub by the stream. What happened next definitely wasn't expected.
It goes without saying that when I had the idea, I did a quick Google to see if it already existed. You know, the 'Facebook for reading' search and then look at the top 3 results. But that's about as far as it went. I wasn't looking for a competitor, so I didn't find one. We took this brief research as enough to say it hadn't been done and ploughed on.
But, now a couple months into development, Mike raised the question about whether this really hadn't been done before. We'd spent the last couple months working on this idea, but our initial research was limited at best. I told Mike that I’d done some research and hadn't found anything.
Mike did a quick Google. Oh crap. It's been done.
And there it was. Shelfari. Someone had done this already. We were late to the party. Very late as it turns out. Shelfari had launched 3 years earlier. And not only that, but they'd been acquired by Amazon too. Dammit. This idea was awesome. But we'd missed the boat.
That sucked. We'd dreamed of our idea for months now and invested a good amount of time and effort into it. But it had been done, the dream was over, time to move on.
Looking back on it, there were a number of issues with our approach. First, there was the whole OTT list all the must have launch features. Then there was the locking ourselves away for months on end with our secretive idea, hoping one day we would be ready for the big unveil and that everyone would love it as much as we did. But the biggest issue was the fact that we gave up after finding out it had been done already.
Since then we’ve learnt an important lesson:
New isn’t important. Better is. Significantly better.
When considering a problem to solve, or an idea to work on, we shouldn’t be asking "are we the first to do this?" but “how is this problem currently being solved? How can we solve it better?”
A new twist? A new package? Reworking a successful formula to be more applicable? More frictionless? Easier to access?
For an idea to be worth working on you need to see the core of the problem already being solved, with at least some success. If your idea is going to be successful it will already have been done, somewhere, somehow. Your job is reshaping, repackaging and restarting it to capture a different need than currently applied to, or better capture an existing one.
Seeing other people already working on a similar problem isn’t just a non-issue, it's essential.
The Jobs To Be Done (JTBD) framework forms everything around one question, "what job is our user trying to get done here?". Are they trying to see their notifications so they can make sure they haven’t missed a message about an item they’re selling? It cuts to the core of what’s going on.
The principles behind the JTBD framework can be applied to us when we’re working out whether an idea has legs. We should be looking to boil our core problem down to one key job to be done. Once we have this job, we can search to find out how people are solving this problem already.
For example, if you’re looking to create a new app that scans and stores receipts, then you should be looking at how people are using tools like Evernote to solve this problem already.
How are they using Evernote to keep track? Why are they using Evernote? What steps do they have to take? What’s good about this solution? What’s bad?
Justin Jackson shares one way of finding answers to these questions: searching the places where people will likely be complaining about the issues they find. A great place to start is on Twitter. Searches like "Evernote problem" will give you a great starting point on some of the issues people are facing with Evernote.
If people aren’t trying to solve this problem already, and dissatisfied with their solution, then this isn’t a problem worth solving.
Seth did have this problem, and pointed us to the tool he was currently using. From there we found other similar solutions, also trying to solve the problem of tracking where you’re spending your money.
My initial reaction was "oh it’s been done. Why are we working on this again?".
Ultimately, I still want to be the genius who sweeps in with an amazing solution to a problem that no-one has ever thought of and will totally redefine a whole industry.
Naturally I want to feel like I’m the only one clever enough to have thought about this problem and proposed such an amazing solution. I want a blank space, I don’t want competitors already trying to solve this problem. I want it easy. Glorious.
Thankfully it was at this point I remembered our previous experience with our ‘Facebook for book readers’ idea, and what we’ve learnt since.
The fact that people are already trying to solve this problem isn’t a problem, it’s essential if we’re to have any success.
The only reason to look at completion is to find out 'do people care about this?’. Then go on and solve it better than anyone else for your audience.
So that’s what we’re going to do.