Startup building blocks: team and product
I have combined the fourth and fifth startup building blocks in this series (team and product) into one, mainly because either could come first.
At a Startup Weekend, ideas are pitched - usually by the founder - on the first day. Before the evening is over, teams have formed to start researching, validating and executing on the idea, even before the product has been built.
More often, however, some kind of product already exists when team members are added.
It's hard to convince somebody to join you when there is little to show for your idea. Even if nothing is built, being able to show good-looking designs or mockups makes the vision for the product feel real and respresents a reachable goal for the team.
This is very important when hiring new team members.
When the team grows, it's essential to understand that aligning ideas and having a convincing strategy are very different from building a product backed by the entire team.
People may share the same ideas and strategies, but often would not translate them into the same product.
In comparison to the idea, which can usually be explained in a sentence, a product is much harder to explain, especially if the market isn't quite ready for it.
A product has various components such as design, functionality and usability. There is considerable complexity in bringing those parts together to build a product that matches the expectations behind the idea.
So whether the product or the team comes first, things things aren't as important as the team's alignment and fully getting behind the product. If staff don't love the product, customers never will.
If the product has already taken shape and it's clear specific skills are needed to build it further, you can look for team members with prior experience in that skill set.
If the product isn't clearly formed, looking for specific skills while adding new team members is often the wrong approach. In that case, it's better to hire a bright, positive and person wih some startup experience, who has a broader view.
Ask new team members to give lots of feedback on your product - they give fresh eyes on what's been built and are more objective.
So far I've only talked about a product, but what if you're developing a service?
There are significant differences between a product and a service. For instance, software-as-a-service (SaaS) has the word service in it, but I still consider the building process to be very product-like.
In the case of SaaS, you can sell more licenses or scale up by adding more servers. But if you're developing a service such as a specific consulting method, that often requires time and human resources. Those are much harder to scale than if you're just making more products.
The entire team should think of every sold product as a service rendered to the customer.
Ideas should be visionary, but products need to be considered for market readiness. They will have many short and long term iterations.
Following lean startup principles, the strategy of a minimum viable product (MVP) and having regular iterations that fit the validation process are an immense help when building products and services.
One of the best examples out there is @FAKEGRIMLOCK, who has not only applied these principles to products, but even to the creation of his own (fake) online personality.
This video is well worth a watch because of what he says about minimum viable personality - and it's applicable to product development.
While it may be possible to build a team and raise funds based on a big idea, finding great customers and being able to retain them over the longer term without having an exceptional product is impossible. In Grimlock's words, 'it's the product, stupid'.
Toby Ruckert is the founder of Unified Inbox. Read more on his blog: http://tobyruckert.com