Startup ideas

This post is about startup ideas and why sharing yours is a good idea!

I am active in the young startup community here in Denmark and one of the things I have been seeing lately is people searching for brilliant tech people, but they will not tell anything about their idea for their new startup.
I think this is downright wrong and here is why.
I am not suggesting that you share your entire business model, but share enough to get your crowd listening.

Your Startup – Your team
When you run a startup you want the best people possible to join your team, because this will give you the biggest chance of success.
However, the best people don’t come easy, they can be hard to find, and they need to be conceived that your startup will succeed or at least have a very high chance of success and reward.
No one wants to join business which is dead from the get go.
Your idea is what started it all, and what made you believe in a startup, so tell it to the crowd, and tell it loud.
Don’t just tell it to a few people at a time, tell it in the forums where the brilliant tech engineers are.
Most people have a sence that they have lost their idea and someone will steal it when they tell it.
However, as I see it, they just got a ton of feedback saving them valuable time to market.
Furthermore, it can help you hook partners and investors because you make them believe in your idea as well.
When working in a startup you have scares resources and little time, don’t waste it telling your idea to one person at a time.

Execution and timing is everything

If we listen to Bill Gross execution and timing are the two most deciding factors when it comes to success for a startup.
The idea only gets an 3th place.

And when you are the founder of a startup your most definitely want your startup to have the best probability for success.

Furthermore, we are in a time where the product starts to beat marketing.
It is more important to create a product which your customers want than telling them that it is what they want.
In these times it is fairly easy switching companies for the best product in the market.

Your followers
Lastly you will have the early access effect.
This is something very popular in the game scene right now where you give out early access to a few people such that they will tell all their friends that your game is awesome!
You have the possibility of getting followers which will tell their friends that your product is awesome and they should join as well.
Having such followers or fans is crucial for making it in today’s markets from my perspective.

The conclusion is spread your idea, be ready for it to morph into something even better, be challenged by people and make your product better!
Share your idea with the world and share it loud!

Understanding the domain

In software engineering understanding the domain is key to providing business value.

“The design of good houses requires an understanding of both the construction materials & the behavior of real humans” — Peter Morville

To develop good, comprehensive software we, as software developers, need not only to understand the technology and architecture behind a given solution.
But we need to understand the business domain including the customers needs.
Many great projects have been discarded because of poor domain knowledge even though the solution is a shining master piece with all the bells and whistles.
A correction; the solution is not a master piece until it can support the customers business.

The business domain is of highest importance when developing a software solution.
Customers will often happily purchase minimum viable products, if it support their business needs.
I.e. if it do not it is of no value to them, even with all the bells and whistles.
Providing business value to the customer is a tough nut to crack and it can never be considered trivial.

“Customer collaboration over contract negotiation” – Agile Manifesto 2001 Kent Beck et. al.
The manifesto describes how it is important to understand the customer which we are creating software for, and that is not done by writing comprehensive contracts.
Software is one of the business areas where everybody on the team needs an understanding the domain, it is hard to define everything beforehand and therefore, we use techniques which let us do a little at a time to comprehend what we are building.
It requires understanding of the materials used and behavior of real humans!

Does the customer know it all?
Certainly not, when having a successful product the strategy changes and it can be good not to listening to customers and instead focus on disruptive innovation to stay competitive in the market.
However, this will be left for another blog post.

Everybody on the team need to care!

This post springs from something i see very often in projects I am involved with, namely that if everybody cares the team will reach a higher state and produce better products.

Caring – a long and painful road
This may sound simple and easily overcome but the reality is quite different from my observation.

If everybody on a team cares about whats being produced I promise you the projects goals will be fulfilled, and provide greater business value.

However getting there is a very long, and sometimes painful, road.
If team members do not care and let something slip it risks the hole project – and risk is something to be mitigated not created.
The team members not caring about the product is essentially dead weight.
Weight which the other members of the team needs to carry to reach goal – namely provide an amazing product!

Caring about something is a very powerful emotion, it makes people persuade others about politic views, religions, or apple products!
Image a team that cares so much about their product that they just want to tell everybody about how amazing its gonna be when it hits the streets.
If the product hits a road bump everybody will care so much about fixing the problem that they will use all of their knowledge, time, and resources in collaboration to get the product in that amazing state once again.

This team will also be the most beneficial seen from a business stand point.
The management behind the team can be 100% certain that the product will be produced with all the love and nurturing a software project needs!
And god help the individual which hurts the project, because the team will fight with tooth and claw to protect and ensure the product well-being.

If everyone in the team cares about every important aspect of it has a much higher probability of become a success and hereby becoming a profitable business.

Creating the caring team
First of all you need to ensure that you have team members able of caring.
If the team can work together and have the needed knowledge, skills, and resource coupled with caring they are likely to going the extra mile for the project.
For this to happen the team needs to have a clear view of the goals of the project – namely a vision.

Furthermore the team needs transparency, everyone in the team needs to know that each team member is caring there own weight and not just wasting their time waiting for the clock to reach 5pm.
If this transparency is not ensured it can be hard for team members to feel that everybody is doing their absolutely best possible to make this product amazing.

To create this transparency it is important to match expectations within the team.
This ensures the team have the same goals for the product and what the product needs to stand for.
This also highlights if some team members thinks it is okay to go for mediocre and not awesome.
Matching of expectations should be one of the first actions done within a team and should be a reoccurring event.

Caring dangerously
Caring, if not managed the right way, can lead to gold plating, analysis paralysis, and over designing.
However this can be minimized by ensuring transparency of the business aspects, because the product is not going to be amazing, from the customers view point, if it is not on time and within budget.

Everybody on the team needs to care about the product under construction.
A caring team, with the right knowledge, skill, and resources, will produce amazing products.
Amazing products which provides business value for the customer will inevitably generate profit.

So can you afford not to have a caring team?

Software Innovation and Business Modeling

Currently I am writing my master thesis as a Software engineer. The subject I am working on is Software Innovation and Business Modeling.
We choose to call the project Software as a Business.
In this thesis Essence, by Ivan Aaen, a software innovation methodology is used as well as Business Model Generation coined by Alexander Ostewalder & Yves Pigneur.
The project looks into the intertwinements of these two methodologies and also with the look at works from Saras Sarasvathy in form of her work in Effectuaion and Causation, and the Blue Ocean Strategy.

The usage of the Business Model Canvas combination with Essence is really inspiring and makes it more clear what innovation is and is all about – creating new products which can produce revenues.
I think that the last is often forgot by innovative developers.
Mostly articals talks about inventions but there are more things to innovation that just an invention; it also needs exploitation and diffusion.
This definition is subject to discussion and I recon that it will soon see a change, my guess is that an innovation can be said to be; invention and diffusion.

Nevertheless diffusion is an important part and can, from my perspective, be helped by using the Business Model Canvas.
Software as a Business tries looking at the diffusion part from an entrepreneur perspective, in our case with software educations, by doing a case study in a new started business in need of an innovative electronic payment solution.

This case study have showed me and my partner that innovative software is no trip to candyland and is a lot of hard work. Within the iterations for finding a design for the technical solution the business model also needs to be assessed to secure that a profitable business can be created from the technical solution.
I think that this approach is valuable for other developers making innovative software which needs to generate funds but also for software entrepenuers wanting their solution see the sunlight.
Also for developers to have some knowledge about business models will help the communication with “business people” as they often are called in developer terms.

This project is still ongoing and as of now the team are working on implementing the business and technical design which was the fruit from the first half of the thesis.