TL;DR
Let’s take a look at how a problem interview script could look like as well as some resources you might find interesting when building your own script. As usual the example is with BARconWIFI.com

fortunecookie_understand.jpg

The problem interview script

So you figured out you are going to go talk to people in order to find out if your idea has some future. Once you decide on running your experiment, you want to be prepared. It would be a waste of time and resources if you forget to ask something, or if all the interviewees answer different and unrelated things, because that would make it hard to get useful information out of it.

In order to have some consistency in the context and way in which the interviews are performed it is a good start if you have a script for the interview.

Now, there have been several articles on the subject of customer interviews. I particularly like the series from Justin Wilcox of custdevlab on most of the aspects of running successful interviews: like what to ask and how to get people to interview using cold emails. You should definitely check them out.

Ash Maurya (the author of Running Lean) talks in this post about his view on doing problem interviews and the structure he follows to do this.
Problem-Script-Deconstructed_White.png
I use this same structure also, with some small modifications. However for the notes I am using Matthieu Garde’s customer development interview sheet and it has worked pretty well so far. I still have a printed copy of the script at hand, but for dissecting the interview and summarizing everything it works.

When I don’t have a printed copy I just write down the note on the computer.

The script.


As promised this is the script for the first BARconWIFI.com problem interview with annotations.

- Hi, thanks for your time and agreeing to meet me. I appreciate it.
- Did you have trouble finding the place?
- [How are you feeling or some other genuine question about how they are doing].
(The objective of this is to make them feel at ease and comfortable. This will also alert you of their state? Are they in a hurry? Worried? Even make them aware of their state. etc.)

- Like I mentioned before on [previous channel of communication], I am looking to interview "[profile]" to understand better if some of the things I have in mind are really a problem for them.

- [Insert heartfelt compliment or referral reference]
For instance: I know you have been in the industry/sector for some time and  I am hoping that with your experience you could shed some new insights  with your point of view on some of the situations that I am going to present to you.

Another example: [Mutual friend or colleague] mentioned that it would be interesting to hear your point of view on some of the topics I’d like to talk about.

- Before we start, I would like to ask you a few general questions really quick if that is okay with you. They are mostly demographics.

- Usual demographics like name, email, phone, etc. (in case you don’t already know them)
- How long have you been a [profile/persona]? (You can use whatever name you think they will understand. This is to establish maturity of the business and potential experience.)
- Do you have an office? (Based on my assumptions about early adopters, they don’t, that is one of the reasons they meet in other places)
- Which language do you usually use? (Again, if you want to make them feel comfortable and can speak that language, you could ask if they would prefer to continue the interview in that language. Also, to understand target language for communication. In my case maybe a better question or accompanying question would have been: Which language do you usually use to look information up. Google, etc. )
- Do you travel for business?
(This could be interesting, since when you are traveling you usually don’t know in depth the locations)

Thanks. That part is over. :)

Now, 8 years ago, when I first moved to Barcelona I was sharing a flat. Like many young people do, but the flat that I was sharing did not have internet, so I used to spend a lot of time in close by places getting online.
(Possible problem context)

A few years later also I faced this problem again only a little different. When I was starting to work as a freelance and wanted to meet clients or collaborators, since I didn't have an office, we would usually meet somewhere.

Other times I just needed to get work done, or eat while working but wasn't feeling like being at home because of the distractions.
(Problem context)

Three months ago I had a similar problem, when I moved. For some inexplicable reason the phone company wouldn’t change the line in time and I ended up not having internet at home for almost a month. So, I did some of my work elsewhere.
(Problem context)

(Telling a story to present the context in which I believe the problem arises without specifically guiding the person into what you may think the solution is.)

Does any of these things resonate with you? Do you feel identified with any of these situations? Whichones? (Are they familiar with the context? Do they see themselves identified with it? Have they had problem themselves?)

Have has any of these happened to you in the last 4 month? (Are these my customers according to the experiment criterias?).

Tell me about the last time. (Asking to tell a story)

When was it? (Last happened.)
How often does this happen? (Frequency)
What was the hardest part about it? (Pains)
How do you solve this problem now? (Current solutions if any)
Are you satisfied with your current solution? (Also pains and wording for UVP)

If you had to order by priority each of the situations described, which one would you say is the most important to you? Second? Third? (Prioritize them)

Can you rate them in a scale from 1 to 10, where 1 means I don’t ever think about it and 10 means I am constantly worrying about this. (Rate pain)

When you are looking for a place to do any of the things we mentioned, what do you look for? Could you order them by importance to you. (What do they look for? What’s important for them.)

Can you tell me some of these places? (Getting content, and also to get an idea of the kinds of places)

Would you mind if I follow up with you in the future in case I need more information? (Permission to follow up, in case you need to. If yes, this is probably an early adopter and by the end of the problem solution fit, he could be using your solution.)

Is there anyone else you think it would be interesting for me to talk to, regarding this topic? Maybe a friend or a colleague? (Ask for referral.)

Thank you for your time. It’s been very helpful.
(Again, be thankful. I sometimes pay for the drinks. After all they are doing me a favour. :)

5 things to remember.


Don’t talk about your product, service, etc. The objective is to understand how they think about the problem, and if they even see it as a problem, not pitching. So don’t, even if they ask. If they ask you can hook them up for the solution interview.

Smile and be empathic.

If the interviewee start’s talking about other unrelated stuff try and keep him in track with the script. Even if he goes into MVP or solution territory, it’s fine to have the feedback but remember you are not there. Besides, most of the times people don’t know what they need. It’s your job to find out.

If the interviewee is in a hurry, stick to the core questions. That way you can have a quick interview and at the same time get some useful information.

Use BARconWIFI.com to find nice places to meet with your interviewees (see what I did there.. ;)

As usual, leave a comment and share the article. I would love to know more about how do you conduct your interviews and if you have other insights you may want to share. Until next time!


TL;DR

Once you decide you want to run an experiment everyone is faced with the question: where do I get the people to run the experiments with. These are some of the methods I have tried to solve this dilemma.


1st: Your address book.

The first place you want to start looking at is your address book. Thats a simple yet very overlooked place to start. Figure out who in your contacts fits some of the criterias you defined for your early adopters and shoot them an email asking them if they would like to help you out by giving you 15 minutes of their time. If you are afraid of interviewing your own contacts, or for some reason you don’t know anyone who fits your defined criterias, then the next solution is for you.

2nd: Referrals.

Asking for referrals to your contacts or during interviews is a must. Because asking the interviewee for referrals or introductions is a good way to meet new candidates for the experiment but also a way to break out of the “cold email” situation. In fact, referrals have the highest probability of a close, the lowest cost, and all you have to do is ask for them.

If you are being introduced by someone you have a much higher chance that the person would agree to meet with you.


3rd: Go to the places where these people meet or go.

Sounds simple, isn’t it? This is very overlooked also. Most of the times there is a good chance that the kind of customers you described for your experiment, are already meeting somewhere else. Let me give you some examples.

For instance, if you targets are parents or people with kids, there is a good chance you will find them at schools either dropping or picking up their kids, or at football practice, etc. If they are runners, there are particular locations in your city that are very well known by runners as great places to go practice, you could go there. If its people looking for a place to work with their computer, you can go to coworking spaces, starbucks, libraries, etc. You get the idea.

In general there is a really good chance they are already going to a particular place easy to find and get to. Just show up and ask.


4th: Find communities where these people engage.

If it exists, there is a community about it. How else would you explain this and this.

Online communities are a great way to get to know your customers and how they think about the problem you are trying to solve. It is a good way to understand them and to find information and early adopters since people who join and engage in online communities are usually very motivated and passionate about it so they will probably be happy to help you understand.

The moral of the story being, you just need to find those communities, or create them! Although that last part is very demanding and time consuming.

Also, lurking or posting in communities is not a replacement for actually talking to your customers.

These are just a few places you could look for them: meetup.com, mailing lists, google groups, reddit, linkedin, facebook, etc.

5th: Paid advertisement + Landing Page

This is a very well known method. If you have heard Eric Ries’ talk or read The Lean Startup, you probably know about it. However, the times where you could do this for $5 a day are over.

Competition for certain keywords in most Adwords campaigns is pretty high nowadays. Meaning you need to spend more. Not something you want to try if you are on a tight budget.

6th: Your current product or service.

If you already have an existing customer base, you can take advantage of that by A/B testing some of your assumptions with them.

There are several tools that will allow you to do that with little or no effort. Google Analytics Experiments is one of them.

Just be careful not to end being booed like Facebook.

7th: UX testing sites.

You can run your own user experience tests, either by A/B testing or by interviewing people directly. However there are ways to do that in an easier way and in some cases for free.

Sites like UsabilityHub, UserTest and others allow you to submit your questionnaire and mockups, chose a segmentation criteria and run a number of experiments to test some of your assumptions regarding the user experience of your site.

Don’t underestimate the power of user experience testing. You can find real gold nuggets there.

8th: Cold emails.

Cold emails are hard to write for most people. When you are trying to contact someone you don’t know and get the to pay attention to you it is not so simple, especially if they are busy people. But is it available, if you know how to do it.

Here are some a good articles with some practical advice on how to use cold emails to build relationships with the press or others.

9th: Message boards. (like craigslist)

By posting a real or fake ad, you can get people to give you the feedback you need.

10th: Twitter, Facebook and LinkedIn

Although this could be considered some kind of “cold” communication, a very good ways to find people that fit some of your profile characteristics are to use the already established social networks that exist.

By searching and filtering results on these networks by demographics etc. you can find potential people to interview. I use socialbro.com to segment and find people to follow, or just monitor what people are saying.

11th: Amazon Mechanical Turk or similar.

I have a friend who hates the whole concept of the Turk Machine. But like this article explains it can be very helpful if used right.

That’s all for now!

Which other ways do you use to find your customers? I would love to hear about them. Remember to share this article or comment I would really appreciate the feedback!


TL;DR

After the initial Lean Canvas it is easy to get lost on what to do next when you have so many assumptions so I use some techniques to help me keep on track. 
I will take you through my train of thought with BARconWIFI.com as an example.


Picking up where we left it...

In my previous post I talked about how I use the Lean Canvas in order to analyse and better visualise what I know or don't know about how I think my business model will work. But, a problem for me, specially at the beginning, is determining what to do next.

The thing is, once I have done the canvas, I am faced with so much uncertainty and possibilities that deciding what to do next is not trivial. Maybe you have had the same problem, where you find yourself asking: What should I go for next? Better yet: What am I trying to accomplish with it so that I learn the most out of it?

Well, Lean Startup, is about constantly performing a ruthless exercise on prioritisation and waste prevention. Taking the riskiest core assumptions, and learning as much as I can about them, as cheap as I can. That way I try to diminish the uncertainty about the whole business but at the same time move forward. This is what the whole MVP strategy is about.




Like Eric Ries likes to say, you are taking market risk (is someone going to buy my stuff) and turning it into technical risk (will I be able to build other stuff to test that and learn from it the answer?)

At the core of all this is the Build-Measure-Learn cycle. You build and experiment (or MVP) to test the market assumptions you are making. You then measure the response, and finally based on the data you can decide what you want to explore or build next. So... in order to start learning we need to start building.

Now, selecting what you want to build, requires you to have some idea of what you want to learn about. This is where the phrase that is often used to describe why startups fail comes in.

Paraphrasing Steve Blank: Most startups don't fail because they didn't build their products, they fail because they didn't build a product people wanted in the first place. So, the biggest risk one faces when starting a startup, is actually building the wrong thing and that is what the first step in the customer development process is about: customer discovery.

In customer discovery we are trying to find out if we are building the right thing. We want to validate that we know who our customers are, that we know which problem they have and that we are able to, not only give them a solution for that problem, but also that we are able to explain to them what that solution is, in an effective way.

However with so much information out there where do you go first?

Here is what I do to find out and organize that first wave of thoughts. I'm hoping it will be helpful to you.


Down the rabbit hole.



Like I mentioned at the end of the last article I not only filled in the boxes for the BARconWIFI.com's Lean Canvas, but also had a section for questions that would come up as I was thinking and filling in each section of the canvas. This is definitively not by chance.

While I am filling in each box, I ask myself the questions that someone who would have to do the job, would ask me, or questions that would help me understand the way the business would work.

For instance, if I say that my customers are freelancers and I know I will want to communicate with them some natural questions follow. For example for customers:
  • Are these really my customers?
    (Remember, biggest risk, not building the right thing for these people)
  • What similarities do they share?
    (Everyone is different, but there needs to be a pattern if you plan on selling to them in a consistent manner)
  • Which ones are going to be my early adopters?
  • How many of them are there? (Market size)
  • ...
In the case of the channels. If I say that I assume will use Twitter to deliver some of the value and to communicate with them, then:
  • Are they even on Twitter?
  • How will I get them to listen?
  • How will I get them to spread the word?
  • ...
Or when filling in the problem:
  • Do my customers have this problem?
  • How often do they have it?
  • How painful is it?
  • ...
The list goes on and on... It is long. Yes. 

There is a lot of stuff I don't know and that is exciting!




Prioritising

To prioritize I first write down the assumptions one by one on post-it notes. Then I distribute them in two axes.

The horizontal axis with how much would it take to execute the experiment. This is based on my own notion of what "risk" is. For me its a combination of the cost in time and money I think I would have to invest.

As an example, a round of interviews would be easier to do than let's say, build a twitter account with 100 followers in two weeks, or write down piece of software. Also, some experiments are easier to run if you have money to throw at them. So some times you could have the same experiment rank differently on the same axis depending on your resources (time, money, team, software...).

The vertical axis represents how much I think I would learn. Again based on my own notion of "learning". Again you will have your own set of learning priorities, but for me at this stage knowing that my customers really have this problem is more important that knowing if twitter is the channel to reach them, or if they will use my yet incipient solution the way I think they will.


By doing this I am already forcing me to think about how I would test each assumption and I write down the ideas for tests also. Once I do this, I usually start with the ones that that give me the most learning and at the same time are easier to test.

Again, you can use whatever method to prioritise y usually assign numbers and do a quotient. From here on I start taking them and clustering them around the experiments that I think would validate them. With that prioritised list in mind you can now chose which experiments to run.

But before running the experiment,  I rephrase the questions in the experiment into testable hypotheses. By that I mean, you can determine if its true or false. Otherwise you don't know what it is that you are testing or if you found it or not.




For instance the questions: Are these really my customers? Is not clear enough for it to be testable.

In an effort to make it testable, I would change it to: Do they have the problem or problems I am describing? Ok that's better, but still not specific enough for me. I ended up with: I know they are my customers if they have had the problem in the past 4 months.

Now that we have a specific assumption that we are making, I set an acceptance criteria. You know, the line in the sand. Where in the sand? That, again, depends.

Trevor Owens from the lean startup machine describes it in his explanation of the validation board as the minimum criteria that needs to hold in order for you to be satisfied that the assumption (hypothesis) is true.

Since we really don't have any idea of what we are going to find in most cases, this is usually an educated guess. I like not to be too optimistic. If I do better than random, I'm fine with that. To me it means I am on to something.

Now the experiment I selected for this question is a set of problem interviews. The acceptance criteria I chose is that at least 6 out of 10 people that I interview say that they have had this problem in the last 4 months.

Once you have done that, you go and execute the experiment. Of course, you can run more than one experiment at the same time if you wish.


First round of experiments.

Ok, so based on the assumptions I am making I decided to run a couple of experiments in parallel. If you have some comments I would love to hear them.

What I chose to do was:

Problem Interview: Easy to do when your customers base is so approachable, and I know some people who fit the profiles. It yields the greatest learning for this part.

Landing Page stating UVP and sign up form to start collecting leads: Easy to do since I am using instapage.com (free) and lets you customise your landing easily as well as connect it to Google Analytics. You can read my other post if you want to know about other free tools I am using to build BARconWIFI.com.

Data Research of various kinds:

  1. Research on the Twitter channel to check on assumptions like: can I reach them, how can I deliver some of the value, are they even on twitter, etc. 
  2. Estimate market size from the INE statistics and other sources. 
  3. Find out if we can get the content to curate in sufficient amounts and quality. 

This is all due to the fact that I am already paying for socialbro.com which allows me to easily run this experiments and research on twitter without much hassle and that I know how to use some other free tools to automate most of the process.

If that were not the case, I am not sure I would have gone this way.

Results.

In upcoming posts I will talk about some of the results for these experiments as well as some other details about executing the experiments. Until then, remember to share this article or leave a comment. :D


TL;DR
Lean canvas has a lot of advantages compared to a traditional business plan document but there are three reasons why I think doing anything else at the beginning, is a waste of time.
Lean canvas for me, is an iterative tool. You need to apply it over and over.
This is what I use it for: Analyzing, dissecting and communicating my business idea and follow its evolution, identifying blind spots, identifying assumptions.
Some personal tips.
This is how the initial lean canvas for BARconWIFI.com looked like.

The problems with tradition business model documentation


A couple of years ago when some friends and I started the now defunct Social Fund It, one of the screw ups we did (among many), was to write down an almost 60 pages long business plan.

Isn't that what one is supposed to do, you ask? Well... Now, I don't think so.

Here are some of the reasons why I now think that was a total waste of time:

It was almost "all" fake: Most of the stuff that was supposed to be there, we didn't still have any data about it, so we just made it all up. The cash flows up to 5 years, the marketing strategy, the operations strategy, costs structures, etc. The only thing in that document that was not fake, was the team.

It took far too long to write and maintain: It took us about two weeks to write it, and once we did, we seriously couldn't be bothered with updating it often enough as for it to be of any use. Time is money, even more when you are an entrepreneur.

It took far to long to read: Be real, most people wont read your 10 lines email completely, so why on earth would they read 60 pages of... potentially boring stuff.

In a few words, it was a waste of time and resources with close to 0 return on investment.

The only reason that I would consider doing something like that again is, if its required to get funding and only if based on actual data.

There is another important point here. Although in general I believe it wasn't a good idea. It did get us thinking about the business instead just ignoring important details. However I now know there are better ways to "get myself thinking" about the important stuff and they don't involve hours in front of a Microsoft Word screen.

Enter the dragon



Now, one of the first things I do when I get an idea for a business, or when I am consulting with a client, is to ether write the idea down using the Lean Canvas tool or ask them to walk me through each of the points described in it.

I do this because it helps me decompose and analyse the business model behind the idea, into the pieces that I find the most important at the beginning of the process, fast.

This last part is particularly important. Lean canvas, or it's close relative the business model canvas are in essence a one page overview of your business model. One page you can write down an explain in just a few minutes.

But while small and laconic, I find that it focuses on the key aspects I want to understand and analyse about the business model and therefore, is a good exercise to prevent the idea from changing without noticing, while it is in my head, a way of getting it out there and pinning it to the table.

It also works beautifully when I want to communicate with others what is going through my mind.

Now, there is one catch I find when I talks to people who also use this tool or entrepreneurs who are starting their own thing and are trying this tool out. What I often hear is: "This is fine. I get it. I have done it before and I thought about it a lot, but it is still not helping me."

Well, I think they are missing an important point and that point is: What did you do as a result of what you learned using the tool, and how did that affect your initial canvas? If you answer is... nothing. Well.. you didn't use it right.



Lean Canvas is not supposed to be the tool that tells you what to do next or to help you track which assumptions you already validated. For that you have other tools, like the lean startup machine's validation board. Lean Canvas is more of a pair of goggles through which to look at your business from a different perspective.

In order for you to be able to extract the most value out of it, you need to ask yourself questions. Questions that stir the Martini you had in your mind about how things are supposed to work. Questions to show you what is really happening, out there. The lean canvas helps you finding these questions and then, by answering them, you can actually learn about your business.

To explain what I am trying to say here. If you look at your canvas and don't test the assumptions that you are making, you will not get the value you were aiming for. It will stay as it is, assumptions.

The only way that picture is going to change is, if you learn anything new about the reality you are trying to describe with it. Then, you can use the tool to analyse, learn and adapt based on what you learned. Rinse, and repeat. Build-measure-learn. Inspect and adapt. This mantra is as old as humanity itself and it didn't start with Customer Development or Lean Startup.

Personal do's and don'ts.

The first time you sit down and start filling up the canvas, chances are you are going to be making stuff up.

That is fine. If you feel like you are not sure about something you are putting on paper, well, that's a good sign. It is a sign telling you where you can start learning. So don't sweat it if you don't know everything on each aspect, that just means you are now aware of the stuff you know you don't know. But... don't stop there. Get out of the building and start learning.

Something that I see often also, is that, as masters of self deception that we are. We tend to avoid difficult questions. What do I mean by that?

Well, if we have a two sided market, we would start developing the canvas for one side, usually the one we know about, while the greatest potential risk is somewhere else... (in the part we don't know about!)

For instance, if we are creating a marketplace for handmade artistic products, and we know a lot of craftsmen/craftswomen it's easy to start thinking about getting them on board, and doing that canvas first, while neglecting to pay attention to the people looking for the crafted products, or vice versa.

But why does this happen? I think this happens because we feel bad about not knowing, so we avoid feeling uncomfortable. This is a big red flag. If you don't like reality hitting you in the face, don't use customer development or lean startup, or agile software development for that matter.

Somehow we have ingrained this idea that "If you build it... they will come". Do not engage on wishful thinking.



Last but not least. Don't forget about the questions. For me this tool is mostly about the questions. What I usually do once I am "comfortable" with what I wrote or while filling it in, is to make notes of which assumptions I am making.  I do that in form of questions. Once I have those assumptions, I can start exploring and finding out the answer.

Then, after you go out and learn something new, come back and revisit the canvas. Better yet, fill in another one and keep the previous as a measure of how the landscape has shifted. You can then start getting the most out of the tool, and then I'll believe you if you tell me it didn't work for you.

The BARconWIFI.com initial canvas.

The initial canvas for BARconWIFI.com for one of the potential customer bases looked something like this. I filled in each of the boxes there, since this is the first iteration these are all assumptions... Next step is to start learning. In other posts we are going to be talking about what to do once you have all this questions and assumptions identified.

That's enough!

With this first exercise I now have some idea of where to start looking next and which courses of action I could start to explore in order to build the business. As always I am very interested in your thoughts so don't be shy and leave a comment or share the article!


I you don't want to read the whole post here is the TL;DR version.

  • The originality or uniqueness of idea matters, but not that much and in particular contexts.
  • Some characteristics that in my opinion good ideas for startups need to have: 
    • they have practical value for your customers
    • they are something that you (the entrepreneur) believe in and feel passionate about.
  • Be aware of your own biases and plan on that so you don't allow yourself to cloud your judgment. 
  • Some example and stories while developing the BARconWIFI.com experiment.


Flashbacks

When I was 16 years old back in Cuba, around 2001. I remember being talking to my good friend Nelson about what would it take for us to "hit the jackpot" and make tons of money. I remember in that particular occasion Google (which was something new back then) came up in the conversation and the whole story of how the Page Rank algorithm came to be and how these two guys had just, made it.

The conclusion we arrived to back then was that we needed to "invent" something. We didn't know exactly what, but in any case, it needed to be good. It needed to be unique. We needed a "great" idea.

If we have that, the path to fame and glory is set.

Years after that, I think back to that day, and realise that if current me could talk to past me, the conversation would have gone a lot different.


How much is an idea worth?

You see, I now know, that having a great idea is not everything. In fact, I now believe that having a great idea, alone, is worth nothing. An idea alone is worth nothing without its execution. I believe having an average idea with great execution triumphs any idea with poor execution no matter how great it is.

History is full of good ideas that went nowhere, and average ideas that made it all the way to the top.

Before Facebook, there where other social network sites like MySpace or Friendster. When Google showed up, the search engine market seemed to be such a crowded space that it was unimaginable to think about competing with Yahoo! or Altavista. Today, Google's search engine market share, accounts for  68.11% worldwide. Something similar can be said about Chrome vs Firefox, IE and Opera.

Now, knowing wether something is a good idea or not, depends on who you ask. However the fact remains that, the innovative aspect of the idea or being first, doesn't seem to matter that much, unless you are in some specific contexts like: developing a totally new market.

And by new market I mean that your idea is really a ground-breaking, earth-shattering, drop-a-bombshell kind of thing. In that case, it matters because the market you are focusing on affects everything else in your business in a substantial way. You are asking your customers to do something they haven't or couldn't do before. It affects the way you position your product, the way you market your product, your customer adoption and acceptance rates, the money you are going to need, etc, etc, etc.

This is how I like to assess my ideas.

All that being said, here is what I think good ideas for a startup need to have as a must. This is my own personal point of view, and it may be different from yours.  If so, I invite you to share it in the comments.

Is it of practical value to your potential customer?

By that I mean it needs to provide actual value to whomever you decide your customers are going to be. In which way does it improve your customer's life? Which problem does it solve?

This is tricky because, in the beginning you don't really know who your customers are or even if they have the problem you are trying to solve. You may have some ideas. You may have talked some friends or colleagues. But chances are, you won't know anything about them just yet. These are all hypotheses.

Usually there is no other way of knowing but to try it out. This is the main reason why I use customer development and lean startup. I use it in order to assess the "practicality" of it all. Most of the time, by acting and avoiding paralysis by analysis.

















In other words I need to try it out and find out. Like Eric Ries likes to say: convert market risk into technical risk. There are lots of tools and techniques that can be used: interviews, mockups, landing pages, paid ads, fake ads... you name it. And while I am answering those questions I keep one thing in mind, always: Is this the cheapest quickest way to find out if my hypothesis is true?

Do you feel passionate about it?

The second question I ask myself is this: Is it something I feel passionate about? Is it something I am willing to spent countless hours working on, without getting any money, and without any kind of security that it will indeed succeed.

For me this is important, because when things get though THAT is going to be the energy that is going to keep things running. That is what is going to make the difference between making it or not.

This is sort of a Damocles sword. It is great to have this energy and passion when things don't go as expected, but they also act as a reality distortion field. We human beings have an almost infinite capacity for self deception, but with entrepreneurs, the chances of that happening are 100%. The question is if you are going to be able to stop it in time.

There is no spoon.


The thing is, we love self deception. There is nothing better than having an idea in your head you can toy with without having to put it down and seeing it for what it is. It is that fear of finding out if it may not work. It is the feeling we get stepping out of out confort zone and doing the things that minimize the most risk first, the one where you learn the most, not the most rewarding, not the one we know how to do. That is how we fall in the trap of subconsciously avoiding it, sometimes by procrastinating others by simply avoiding it completely.

For instance, with BARconWIFI.com my first instinct was to start writing code. I come from a technical background. So it came natural for me to enter "product development mode" and start asking away: How am I going to build it? Which frameworks am I going to use to develop? Where should I host it?

You see, these questions, although important, don't shed any light on the riskiest assumptions that I was making like: How am I going to make money out it? How am I going to find and curate the contents? How do I get people to find and use the platform? Are there even enough people interested in this to be worth the time and effort?

What the first group of questions has that the second doesn't is that I already knew I could answer those. I felt comfortable there in the known-knowns zone. It took some cold showers and some inner reflection to see that I was being a victim of my own eagerness and biases.

Know yourself. It goes along way fighting your own worst enemy. Follow the signals. Read about cognitive biases and how to break them.

Eating your own dog food.



Where do you find an idea then. Well... anywhere, but I particularly like to start by looking at my every day life.

When I first moved to Barcelona eight years ago, I didn't have wifi at home so I was constantly looking for bars where I could just sit down and do my thing.

Then three months ago, it started happening again. I changed flats and while I was getting internet installed at home (which took ages for one reason or another) I had to make due with whatever I could find. Same thing has happened before when I wanted to meet clients and didn't have an office, or simply wanted to get things done outside the house to avoid distractions.

There you have it! Finding a nice, tranquil location, with free wifi has always being a problem (for me).

The whole scratch your own itch is not as weird as it sounds. When Ash Maurya talks about how CloudFire came to be, or his book, or workshops, etc. They all came naturally from a need he had. Same thing with 37signals and BaseCamp. The list goes on and on...

Flashforward

A lot of water has passed under the bridge since that time almost 14 years ago. There are no silver bullets for success, but sitting around waiting for a "great" idea to show up is not going to stop me from taking action.

What do you think? Tell me in the comments.




I don't like to think in terms of tools, because I believe tools are just a means to an end. That being said, here are 10 tools I am using right now to develop BARconWIFI.com and that you could benefit from.

The best part... they are all free to use.

  1. InstaPages: Generate landing pages for conversion. Free trial. Integrates with GA and allows for A/B testing. Tried  LaunchRock also, but I liked this one better because of the functionalities. LeadPages' policy of give me your credit card before I show you anything scared me off, although it seems to have a more complete feature set.
  2. Name Checker: Find out if your name is taken (twitter, facebook, others..)
  3. SumoMe Tools and small plugins to improve CRO, signups, virality of your content, etc.
  4. Google Analytics: Googles Analytics tool for websites and other kinds of products. A must to track conversion and other useful statistics.
  5. SocialBro: Analyse twitter social network accounts, hashtags, etc. Get best times to tweet etc.
  6. BufferApp:  Buffer your tweets and other message you want to send to your social network.
  7. Canvanizer:  Create your own business canvas online, share it and collaboratively edit it.
  8. Mail Chimp: Email marketing with analytics. Free. Lets you A/B test.
  9. Rapportive: Gather information about people through social networks and their emails. Check this article to find out more about how you can use it to develop contacts and do PR.
  10. If This Then That: Automate the internet. Make it work for you. Create triggers for when you do certain things like posting to Twitter, or publishing and article in your blog.

This is all folks!

Stay tuned and again, if you have your own favorite tools or suggestions feel free to share them in the comments!


There are a few things that bother me in life, but there are three in particular that provide me with the energy to finally start writing this blog.


Knowing. 
It's a never ending marathon of discovery and resilience.

Forgetting.
I have a really bad memory, so I'll forget if I don't write it down.

Sharing.
I want to share more what I know, so that others can benefit and contribute to it. Not from a theoretical, but from a practical and pragmatic point of view.

In this blog I'm going to keep track of the failures and learning opportunities that I'll find while playing around with Customer Development, Lean Startup, BARconWIFI.com among many other things. 

Feel free to join me and stay tuned.


Popular Posts

Powered by Blogger.