Let's be honest: we all like to get a behind the scenes look. We love "making of" videos for great movies. We watch the Discovery Channel to learn how things "really" work. We want to see how the illusionist performs his trick. The bottom line is that we all have a primal curiosity and some part of voyeurism inside of us. We as humans are inherently curious.

The good thing is, your customers are so too.

So here is a great thing you can do when you are working on your product:

Start getting fans for you and your product

Try to start writing a big brother blog. Write the stuff people normally wouldn't do. Blog about your exact every move. Let your visitors take a peak in your kitchen once every one in a while. Your readers will love it and you can turn visitors into fans.

Clarify and communicate your values

Showing off what you do and why you are doing it is also a great way of clarifying your vision. If you are using videos, screenshots, how-to guides or other media with your blog post you can even internalize your vision even more. Because of course, actions, experiment and images speak more than words. Especially when you are still discovering a lot about your customers and what you yourself actually want to achieve with your product.

Start being the best at selling and explaining

Last but certainly important is hour ability to show and explain what you do to other like-minded people. You will be sharing your experiences with the world. Other people wil learn from you or give you feedback and tips to do things differently.

Conclusion

So. Tell everyone in the world about what you are doing, why you do it and how you are doing it when you work on your product and with your customers.

This post is based on a post I read yesterday about the "co-op business model" by Derek Sivers.

In that post Sivers tells the virtues of sharing everything you can think of to create value for other people without direct business value. My previous post about your blog being your first product touches this point as well.

Sivers basically points out three things:

1. You already have something other people need or could use

   For example, you can blog about manual solutions for problems your future product is going to solve for your customers.

   Also. A lot of successful web companies contribute by creating various open source plugins or applications for other software developers.

   As a designer or author you could create e-books or step-by-step videos about how you work and what your process is.

2. Find a way to share it with everyone who needs it.

   It doesn't really matter what you share as long as you can share it with friends, colleagues, competitors or basically because you just like to be a nice guy.

   If you fear that no one needs what you have to offer think about the following:

   If even just one person can benefit by one little thing you product you have already doubled your personal value to the world. This is because not only you as a single person got some value but you scale yourself to 200% for helping one more person. That person can then even help someone else with your solution which means you will have tripled your worth to the world about that single problem.

3. If it takes you some effort to produce something you can charge a little for it.

   Sivers shares some great examples in his post so I won't list them here. But his most important example is the million dollar business that grew out of his way of helping other independent artists to sell music CDs online. He describes a great deal of this in his book Anything you want

Here are three reasons for why I am writing this blog. I think these are great reasons for anyone who is working on a product or running a business. Hope that these reasons will help me practice with inbound marketing and build a path to customers.

1. I want to create the ultimate dashboard for inbound marketing. For the product to succeed I want to build it while I am using it on some of my own projects. My own experience is the multimate test to see if the product works

   I also want to use this blog as a channel for promoting the product, get a change to talk to you guys and post updates with videos and screenshots.

2. I want to see how hard or easy it is to do inbound marketing. I want to become an expert in building a channel for your product. See how hard it is. Experiment with all sorts of content.

   Generally speaking I just want to walk my talk.

3. I want to learn how to write. Knowing how to write is one of the most important things you can practice on as a software developer. Conveying clear messages in an interface, programming code and marketing material is crucial for a great product.

Focusing more time on building your channel and meeting new customers might even be more important than spending a lot of time on figuring out your customers problems, at first.

You can argue that you have no valid reason for existing if you haven't got a good idea of what problems your customers are having. There is a lot of truth in this but I also feel that if you are an entrepreneur you are always able to solve someone's problem any time.

Also, most customers are probably not buying your product for the thing you are trying to sell it to them for. Hence the customer discovery part and not the customer what do you want me to fix for you part. You can only validate your problem and your solution by testing not by just asking.

Building a channel is harder than solving a problem

Building a channel for your product is much harder and takes a lot more effort. It is easier to iterate with a value proposition or a problem hypothesis than it is to iterate with a channel.

You can flip the switch by changing your interview quests or a problem hypothesis but you can't flip over 3000 community members to another subject or marketing channel.

Following this train of thought you might like Ash Maurya's advise of starting with the riskiest part of your business model. In the sense of the arguments given before, your channel might actually be the riskiest part. You can find product/solution fit for your customers in various ways with a small group of people.

But, you can't just build a channel within 3-5 weeks and a bunch of conversations.

Also, The Startup Toolkit has a great post on how he built his channel.

Conclusion

Solving someones problem is always the reason why a product should exist. Either you have consciously solved your customer's problem or they are seeing something in you that you don't know about.

But don't forget the effort it takes to build a channel to your product.

Solving a validated problem is the ultimate goal but it does not make much sense to only do it for 20 people if you can't live off of that.

What are you experiences in balancing building your channel and learning about your customers problems? Where would you focus your efforts on when you are just starting out?

You just started out with working on a new product. Either you began with an idea for a solution or you are going to kick off with an idea of a few problems you are going to solve.

When you are doing customer development you want to learn about the problems of your customers as soon as possible. The ultimate goal at this stage is to get some validation from the people you talk to about these problems.

This will increase your chance of success. Most of all, it will enflame your passion if you get some good positive and negative feedback. Getting people enthusiastic or in brainstorm mode because of your idea is really fun.

Learning about customer problems

Doing interviews is a great and deep qualitative way to reach the validated state. But, there is another way to learn if your problems resonate with the group of customers that you have in mind.

You are building a product that is going to solve problems. And unless your problem is to get someone on the moon and you need to build a spaceshuttle, those problems can already be fixed by alternative or manual solutions.

This is where you can use your knowledge and experience that you already have. And combined with your vision you can get in the heads of those early customers.

Being a product without having a product

You can create a product from your knowledge and experience and solve the problems that your customers already have. You can use the theories and the solution you have in mind for your own final product and start teaching people to get working with those problems right now.

The best way to teach your customers how to solve the problems is by writing posts about you solving those problems on your blog.

How to kick it off

I suggest you write a few blog posts that helps the reader solve each individual problem on their own with alternatives or a process you explain. The great thing about this is that you can test the need for each individual problem you want to fix. This is done looking at the reader activity and incoming traffic to each post.

For example, I still get lots of traffic and the occasional comment I wrote a while ago about something in Android development. Here is the original article. So far it has 43 comments (including my own) and people discussing code samples and such. This can really tell you if you nailed it with a problem.

Conclusion

You want to release a product as soon as possible after defining the problems you are going to solve for your problems. You want to do this because you want to validate if you are on the right track.

Before or while you are building your actual technical product, you can use your knowledge as your first product.

Write blog posts where you describe how your customers dan solve their problems right now on their own by teaching them alternative or manual solutions.

This way you can get a feeling if the problems you are going to solve resonate with these readers.