“-Can you tell me what you would look for in a startup so I can properly build my MVP?” I am at a Meetup where investors (VC’s mostly) sit around the table with Saas startups. Others are nodding at this question, it is the thing they want to know as well.
“-So what do you have now, right this moment?” Another investor asks. The founder, or rather intended founder explains that he is still playing with the idea but before he starts he wants a clear idea of what investors and VC’s in particular would look for in an MVP. He then intends to build an MVP to match these expectations and also wants to know from what point onwards he needs to contact the VC.
“-Does that imply you mean to build one single MVP based on what the investor expects rather than what a customer would want?” I ask the founder. He answers yes, he also does not know what other way there would be to start. In all of the examples he sees online he understands that there is some sort of MVP with which you gain the interest of an investor. He is not the only one. After the meetup another founder connected with me on Linkedin to thank me for the insight; ‘we need to listen to our customers’ rather than build for an investor. The rise in popularity of startups and the seeming ease with which to start one, has peaked the amount of people wanting to start a startup. Thinking that building an MVP is step one and getting investment is step two.
Being a founder is not easy, starting a startup is relatively easy, but proving, with actual customers, that your idea is actually something you can build a business on is hard, and it takes time. It starts by listening to your customers, figuring out what it is they need or want, than prove that your solution is something that really helps them and makes them happy. The next step is to prove that people will pay you for that, and the last is to prove that there is a possibility to scale.
It doesnt make sense to get an investor in if you haven’t proven the viability of your idea yet. You can put your own money in it, or bootstrap, maybe there are friends that want to help you. Ask yourself why you want to have an investor? Is it the goal of your startup? Or is the goal to actually build something that people will buy. An investor will want to see return on her investment, so think about that when and where looking for an investor makes sense for your business, if at all. But always prove your idea has a healthy business model first. Are you looking to build something that is a healthy business but not something you want to scale big, maybe you do not need any investment at all, or just some starting capital from friends or Angels. If you are looking to scale big, than investment makes sense, but only in the phase where you have proven the problem, the solution, and the revenue promises.
The summer is getting near the end, most of you have been on holidays or wel deserved breaks. We have been on a different kind of break. Whilst working with our NEXT Canvas with the startups we help, we were seeing a way to help both startups and companies to actively keep track of what is happening within a startup or innovation team. Right now we use a process of using the canvas to ‘see’ actual progress and interaction with, as well as keeping track of, experiments and validation. It is on the wall with the paper version of both the card and the canvas. While we store experiments and progress over time in a Trello board. We figured it could be made so much clearer if we could get the mental model out of our heads and into a digital tool to guide you. We decided to act upon that and dedicated two weeks in August not going to Bali or Ibiza. Working solely on this online tool during our ‘internal summer hackathon’ ( with just the two of us 😉 ).
As a result a first minimal version is online, based on what we have learned from the paper version of our canvas and experiment board so far. The tool needs to be tested by a few startups right now, so we can learn as much as we can from the start. Things like; How do we convey our mental model to the users and how can you benefit from this. Right now it has a few basic functionalities. You can add a project that contains one or more canvasses. Each segment of the canvas can hold assumptions. To each ‘sticky’ with an assumption you can add one or more experiments. There is an experiment board for an overview of running experiments as well as an experiments inbox.
You are welcome to give it a try, provided you ask us when something is unclear and tell us when something is wrong. We want to learn, learn, learn, so we can continue to integrate and optimize. To be able to build something that will help you build a viable business model.
Why is this such an important part of our thesis? The system as it is right now, we feel, is broken. VC’s are steering startups towards higher valuations and eventually exits or IPO’s in order to make their intended ROI’s within the time set for this (usually 8 to 12 years). This means that a lot of startups are either busy raising money, or looking for exits rather than what we think that they should be focussing on; proving their vision and building a profitable business.
We want to help entrepreneurs in proving their vision and building a working business model. We want them to focus on what customers need and how to create real value. We want them to follow their vision and proof they can build a real business out of it. Success can also be real revenue and a healthy company.
We feel that this should also be reflected in the way we run our fund. Right now we are looking at Indie.vc, an US-based fund that is experimenting with ways to invest in startups that want to become profitable businesses.
They are, like us, working with convertible loans that convert to equity whenever there is a follow up investment. But that loan can also be payed back (times 5) with the profit you start making once you become a company with revenue. Thus creating more value for both the company and the economy. Or as they say;
This is something we strongly believe in as well. For both investors and startup entrepreneurs we are looking for people that belief in this as well, so we can make an impact together.
For the sake of learning and progress it is important to be able to keep track of what happens in terms of the changes and adaptions to your Business Model in every stage of your startup. Every update due to an experiment, the things you have validated or dismissed over time. The closer you get to product market fit, the more likely it is that you can show metrics like traction or retention, but are those the metrics you can account your decisions on, put milestones on or determine your roadmap on? From the very first start you want to be able to account for the decisions made towards building a viable business model, you want to see the progress you are making towards a this. Most likely (in the very first fase of your startup) you will start off with multiple possible options and models. The goal is, over time, to validate and de-risk as much as possible, ending up with one that actually works. Going through the phases, experiment by experiment, means you are making decisions and setting milestones along the way. To account for those, it makes sense to document the learnings in such a way that it gives insight in this learning progress.
At NEXT we are using a Trello board for now. We have changed our approach over time and probably will optimize it when we have learned more. Playing with the structure is easy with a flexible tool like Trello and we don’t have to build anything yet ourselves. Although it misses certain other things, this still gives us a flexible approach towards something workable.
Setting up the Trello board
Create lists that correspond with experiment loops. These are preferably two-week time slots, but sometimes something happens and the timeslot changes to a longer period, so it makes sense to number the lists. Something like ‘Experiment loop #’, but weeks or dates work as well, whatever gives you insight.
Every Trello card within a list corresponds with a Business model canvas that is still in option. Experiment loops at the very beginning of the board can have multiple canvas cards, since there are often a lot of options in play. Some are discarded on gut feeling or research, some on experiments. We use a picture of the business model canvas (lean canvas or our own canvas) as a cover for the card, adding color to the canvas segment that is specifically being tested. This makes the overview more clear. There can be more than one experiment in play on a specific card. Note also that in a two-sided businessmodel, you will need a canvas for each side, each is put on its own card.
Canvas cards
Whenever an experiment is run, we add the experiment to the corresponding canvas card. In a comment we upload a picture of our experiment card, with its unique number. (Make sure that the canvas remains set as cover on the card.) The due date of the experiment is set in the calendar. Once an experiment is finished, the end result (validated or invalidated ) as well as the metrics or documents that proof this, get uploaded or linked to this card as well. The updated Business model (Canvas) is than made into a new card in a new experiment loop.
Stickers and labels
Every card that has an experiment attached to it gets a triangle/exclamation mark sticker. If an experiment fails it gets a thumbs down sticker, if it validates a thumbs up or checkbox sticker (whichever you prefer). Running experiments get a rocket sticker and business models that are still in play but without experiments currently being done get a clock sticker. For experiments that have proven inconclusive or those that need follow up experiments, either more experiments are added to the card, or the card is copied to a new loop and experiments are added there. Sometimes we assign a confused smiley sticker to show this.
Labels are very useful especially for two-sided marketplaces or more complex models that need several canvasses for one option. Colored labels can be assigned to cards indicating the two sides of the market place, or the slices that belong to different users within a certain segment when you are dealing with complex markets/customers that need separation into user, influencer etc.
Progress reports
If you keep updating your board over time this will create a very visual overview of your learnings. Building up from one side, that has many options and assumptions, working towards something that has fewer assumptions and is less risky. It will give you some insight into your learnings and a way to proof your progress. Whenever there are periods of time when you have not been able to take steps in proofing your businessmodel, this will also be visible on the overview, just as pivots or new options.
You can work from left to right or the other way around, the result is the same. A progress over time, validating towards a working businessmodel. With everything that is related to this, the exeriments and their corresponding results attached to it. Thus accounting for decisions and steps made along the way.
We’d love to hear how you keep track of your learnings and if and how you have made adaptions to make this work for your startup? Let us know in the comments!
We have talked about the importance of Continuous Experimenting and working on a sustainable business model, experiment by experiment. Even more important is a way to keep track of these experiments and the progress made. Not only to see what you have learned over time, but also to account for the decisions that are made in the process and why certain things need priority over others. In his book Eric Ries calls this innovation accounting:
To improve entrepreneurial outcomes, and to hold entrepreneurs accountable, we need to focus on the boring stuff: how to measure progress, how to setup milestones, how to prioritize work. This requires a new kind of accounting, specific to startups.
Keeping track of your learnings
Usually, as a startup, you can start tracking as soon as there is a version of your product out there and some metrics are in place. This is why it is important to get an MVP out there. But your much craved hockeystick curve is usually mainly flat in the very beginning. Not because founders are not doing anything, but because looking for a working business model takes time and is hard. You usually get the most valuable insights from the most failed experiments, but this doesn’t show up anywhere in our metrics. How do you keep track of the experiments you have done, and the learnings from these experiments even before having a MVP out there?
How we do innovation accounting at NEXT
Identifying priorities and risks in your businessmodel is hard, setting up and formulating an experiment is even harder. We have found out working with a lot of startups that once you have a framework in place, it is more manageable.
For every experiment sprint or loop, we look at our canvas and decide on the things that are still risky and decide on experiments based on that. At NEXT we like to work very visually so that every team member knows what is going on and why. The starting point is a canvas. We use the Lean Canvas instead of the Business Model Canvas in early stage startups because it helps to focus on the problem and solution rather than strategy and product. We also have developed our own NEXT Canvas, which we will share with you soon.
A physical version of the canvas is always on the wall and gets updated with every single insight from experiments. The canvas helps identify risks and priorities and decide on the next experiment (or set of experiments) to validate assumptions. Once we have decided on an experiment and what it is that needs validating, we formulate an hypotheses or learning goal.
To help us formulate an experiment and to define its succes criteria upfront, we have designed this experiment card:
The card helps us to be scientific about every single experiment. It helps formulate an hypothesis and learning goal, forcing us to think about what it is that we are testing. It also helps being consistent across experiments.
How to use our experiment card
The upper row:
Used to fill in the date of designing the experiment.
A number for this specific experiment. This way you can attach this experiment to a canvas or other events in metrics that this experiment relates to. See it as a unique ID for this experiment
The actual cost of the experiment, this could be time, development time or actual hard cash.
Hypotheses: A falsifiable statement. (What is it that you want tested)
Context: With which segment on the canvas does this experiment correspond. What risky assumption are you trying to validate and why? We put dots in the areas of the canvas to visually mark the segments the experiment is related to.
Learning goal; what is it that you want to learn from this experiment. (If the hypotheses is not really clear, for instance in an exploitative customer interview, this one should be even clearer.
Experiment: It is important to time-box every experiment. Set both a start and end date.
Describe the experiment; Is it an interview? A fake button experiment? Describe how you are testing the hypothesis. In relation to this, which metrics are being monitored to determine succes?
Result: When is the experiment a succes? Write this down before running it. When the experiment is done make sure that the actual numbers are updated.
Next step: Was the hypotheses validated? Did you learn anything? And what does this mean in terms of next steps. Pivot, persevere, or do another experiment because this one wasn’t really testing what you wanted to test?
To do, done
All running experiments are put up on the wall next to the canvas. Once an experiment is finished it is taken from the wall and archived. But not before we have decided on a next step, and updated the canvas or the product from the results of the experiment. The experiment cards are then archived together with the corresponding canvas ( the one just before we updated it with the results of the experiment). In this way we can see which experiments accounted for which decisions and if there are any metrics of importance that relates to them.
Avoid going around in circles; track your progress.
In the next blogpost we will dive into how we use Trello as a tool to keep track of current and past experiments and the changes of the canvases in a ‘timeline’ of sorts.
One of the most important tools, or experiments you can do throughout the search for your business model is the customer interview. Whether you are finding out if there is a problem, or want to know about what it really is that people are trying to do, the customer interview is an important tool in understanding more about the behaviour and needs of your customer. Most startup founders we know tend to be scared by the notion of actually getting out of the building and start talking to strangers. They compile surveys and questionnaires they can conduct online and send out from behind their computers. Easier, far more comfortable, but the outcome will be averages rather than patterns. Talking to real people, listening to the things they say, their expression when saying it, will help you investigate and drill down to the why behind the what. You think they will not tell you? People love to complain about what is not working for them, or to tell you all about their passion, all you have to provide is a listening ear.
Even though customer interviews remain awkward, there is a couple of things to help you feel more at ease. It is not that hard; You do not have to talk about your solution, you do not have to pitch. This is not about you or your product, this is about your customer. All you have to do is listen! Sounds easy enough right? Keep reminding yourself of this, because your first urge is to pitch your obviously brilliant solution. Don’t! Ask what they are doing to solve their problems instead, and why they are doing it. Once you have found a good way to start conversations with potential customers the process will get easier and more and more valuable. We keep conducting customer interviews regularly, even though we are past the customer discovery phase. Sometimes metrics show you a lot of things, but if you want to know the why talking to people is always the most valuable option. Want to grow? Target more customers? Understand what your current customers are doing and why, this will help you learn valuable insights.
How do you turn customer interviews into an experiment?
Box it! In time and in numbers. Be sure to interview as many people as possible in the time of a week. Or the dedicated days within your experiment loop. If you conduct interviews over a longer time, every single interview will slowly influence your overall view slightly. But by considering the whole of interviews as one experiment it will give you a chance to discover patterns and actually move forward from there.
Setting up for the interviews.
First make sure that you know what it is that you want to learn. Define your hypotheses. Personally I’d like to prepare questions that refer to a specific topic that I want to learn more about, related to the hypotheses. No follow up questions, just topic starters. In this way I am able to make sure I tick of all the topics I want to ask questions about, and still be able to drill down if something interesting comes up.
Asking the actual questions.
The other week while giving a workshop, somebody asked me; “I have talked to customers, they have all said they loved what I was doing, but now nobody is actually that enthusiastic about the real product. How do I get actual value out of those interviews because to me it felt they where just lying.”
Since people usually say one thing but do another, this is indeed a very valid question. It is important to try and ask questions that will provide you with answers of high value. Believe it or not, everybody lies to you. Out of disinterest, just to be polite, because they want something else from you, or to not to destroy your dreams. The biggest liar is your biggest fan: Your mom. She will never want to destroy your dreams with telling you your idea sucks. Rob Fitzpatrick came up with a way to get valuable answers knowing that people lie to you. Every single question you ask should be asked in a way that even your mom cannot lie to you. He called this ‘The mom test‘.
The Basics:
Stop fishing for compliments, this is not about you or your product, this is about the world of the customer and how they perceive their problem.
Compliments have no value in validating your business model
Avoid generics or abstracts, this will only lead to guesstimates. Ask about real events and what they did dealing with them.
Actual events rather than abstract averages
Never ask questions that contain would or should,nobody can predict their future. Ask what they are doing to solve their problem right now instead.
Behaviour rather than whishes
What you do want is to know what they perceive as a problem, what they are doing to solve it, and ‘why’ they are doing this.
The Analysis
Now when you have interviewed a good number of customers it is time to analyse data and make decisions from there. Start of by writing every single answer on a separate sticky note. (if it helps jot down a number or initials to refer back to the interviewee) lay the stickies out in a grid. Where the interviewee is played out across columns and the topics across rows. Make sure to leave some room in the row section since there are going to be different and more than one answers available here. Stick answers in the grid. Now start looking for similar answers or problems and group them together.
Can your hypotheses be validated?
Always make sure to take pictures.
See if there are any other patterns emerging.
It feels like a lot of work, but doing this as a team will lead to valuable insights. Your brain is (still) the best patterns recognition system there is in the world, you will ‘see’ patterns sticking out to you. Leaving through the answers that are written down will not give you the insights it will when visualizing it.
The power of visualization
For instance; We interviewed high school students on the use of a calendar. The hypothesis was that high school students have problems with existing calendar apps while no longer using paper calendars because they forget them or find them archaic. By determining a more specific segment we wanted to see if we could see if the problem was different or maybe more prevalent in order to offer more value in our intended solution. I prepared some topics that I wanted to learn more about: Current apps on their phone. Classroom and school digital approach. Paper calendar ( did they use it before , if so how). Context of given homeweork and tests. Their planning and learning rituals ( if any). We validated our hypotheses in a specific group of students we were able to identify. But the real value was the insight that their biggest problem (they all volunteered this information when we saw signed of frustration) was something we didn’t know about. They felt tests and homework seemed to sneak up on them. Tests that only showed up on the actual day, or a day before. They all blamed it on something else, the teacher, yet another crappy calendar app, the system, never themselves. But it was a problem to them because it affected their scores. This ‘job-to-be-done’ became an important part of the new value proposition and the solution. Asking ‘why’ helped us rethink our value proposition. Now, instead of focussingen on a paper calendar replacement, the app gives notifications in advance in three steps before every test. Giving some sense of control back, and help them plan.
In the last post I talked about the importance of validated learning. Trying to validate your way to a working businessmodel. You don’t validate your businessmodel by running one single experiment. Continuously testing risky assumptions is important in every phase of your startup. Helping you to derisk the path to a successful businessmodel.
It sounds easy enough but it is much harder than you think. Your first and foremost urge is to build something really awesome. Show the world your shiny new vision as a brand new product, world domination and everything. Running experiments is something that feels counterintuitive, taking away hours of your precious time and your product. Even when you know it is valuable, even when you realize that learning before building can save much needed time and money and can lead you to more awesome products, it still feels this way. In a way it feels like homework.
You are not building a product (yet) you are building a viable businessmodel.
Experiment design
With each new experiment it is important to remember that you are not testing your product, but rather your businessmodel. Every single experiment is build to learn, not to scale. Ask why. Ask yourself what it is you want to validate. Identify you riskiest assumption and think of how to test this, in the most simple and cost effective way. Do not worry about scale, you are not building your real product yet, you are testing if what you assumed would be the case, actually is the case.
The basic structure for designing experiments looks something like this;
Set a structure and timebox every experiment (1 or 2 week loops for instance)
Decide on what it is you want to learn (this loop) and make this falsifiable. (true/untrue)
Agree on a number that determines succes for this experiment and write it down beforehand.
Design an experiment that will only test what you want to learn.
Build and Run the experiment
Analyse the data.
Update your Businessmodel options with the learnings.
Repeat.
It is important to have a structure of continuous experimenting to show learning progress towards a successful businessmodel. By the time you are ready to scale, you already will have a proven customer base, and a way to grow it into something really big.
The MVP as single proof of concept?
How does the MVP fit into this? Eric Ries talks about the MVP (or Minimum Viable Product) in his book. His definition:
“A Minimum Viable Product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.”
The term has since been used, and also heavily misused, for a lot of different things. Most of the time people wrongly refer to their first release of the product as their MVP. An MVP is not your single proof of concept that will validate your business. Rather, an MVP is an experiment that will help you validate if the solution offer you have in mind, is something that has enough value for your customer segment. I’d rather avoid the term MVP. In a way your MVP is nothing more than a solution experiment. Most probable in a series of solution experiments, that test your value proposition. Is it the first product you build to capture the value you offer to your customer? Or the experiment without a product yet to test your solution? Let’s avoid this discussion and focus on continuous experimenting. Make sure that what you are building delivers value to the customer and iterate from there.
The experiments that you run when you are still validating the problem, and finding customer segments to test with will be different from the ones that you design later on. In the early phases explorative experiments like the customer interview are important. In fact, talking to your customers will remain important throughout the development of your businessmodel. Other useful experiments later on are smoke tests and concierge models. I will explain about these experiments in following posts. Just remember that with every experiment you design, you want to learn something. Think of the easiest way to proof your hypothesis. Don’t worry about scaling. Think simple, if you have to buy customers to test, buy customers. If you have to mail people by had to mimic some algorithm, do it! You are building to learn, not to scale.
In the previous post I introduced the lean startup methodology by Eric Ries. He defines two phases in a startup. There is a Customer Discovery and Customer Validation phase. The first fase is all about proving problem/solution fit. It starts of with exploring the customer segments, validating there is a real problem and deciding on a solution. The second fase starts with validating this solution offer and optimize this into something that a lot of people will actually use, and more important, pay for. If you can also grow the number of those users rapidly, you are ready to scale.
The first phase is all about validating if there is a customer that has a problem at all. Whereas the second phase is concerned with optimizing your solution offer into one that a lot of people will actually pay for to use. Although the experiments are likely to be different depending on the fase that your startup is in, the goal is the same.
The goal is to learn.
As with any new idea, the boxes in your businessmodel or lean canvas are filled with a lot of assumptions and therefor a lot of options. It is all about finding the few that really matter. Test if assumptions are true before building upon it. Not every assumption needs to be tested though. You start of by identifying the riskiest assumptions on the canvas. The one that, if not true, will have your whole idea come tumble down like a house of cards. From there you learn, update that information into your canvas and decide what is most critical to learn next.
Traditional product or service development cycles, look something like this; decide on a product, do research, build the product, put it out there and see how people react to it. The time between the idea and putting something out there is a rather long one. In this period, typically nothing is learned at all. Only when the physical product or service finally hits the market and people interact with it, something happens. By than it is usually to late to fix problems is the product is not working, all the while spending time and money. The lean startup methodology aims to increase learning and decrease risks. The goal is to learn and iterate all the way to something that works.
Business Science But how do we learn? For every assumption that needs to be tested, you design an experiment to test this. Applying a scientific method. Business science that is, a ‘pseudo’ scientific approach optimized for time and money.
The scientific approach lies in the fact that every ‘experiment’ that you run, whether this is a customer interview, an MVP or an A/B test, should validate an hypotheses. The criteria for this hypothesis to fail or succeed should be decided upon by the team and written down before the experiment. The criteria should be based on business value. (Although there are no hard numbers here, it helps to count back from the bigger picture. i.e. What is the amount of people that need to say yes if you look at it from a market segment perspective and the percentage you need to have a viable business.) Build an experiment, Learn, update the information from the experiment on your canvas and make the next step or decision.
Startups exist not to make stuff, make money, or serve customers. They exist to learn how to build a sustainable business. This learning can be validated scientifically, by running experiments that allow us to test each element of our vision -Eric Ries
The startup experience is really a series of experiments. Every single experiment is build to learn. Your Business Model or Lean Canvas is not filled in at once or only once, but is something that you iterate upon. It makes sense to look at your canvas as the product of your startup. Your goal is to learn and iterate this canvas into a working and scalable business model. Experiment by experiment.
The Lean Startup, Running lean, The four steps to epiphany, we have all read the books. We use the Business Model Canvas and build MVP’s. The Lean Startup methodology has become very popular not only within the startup industry worldwide, but also amongst companies that want to enable innovation and change. Allocating time and money as efficient as possible, shorten development cycles and make something people actually want to use.
But what does it really mean to run a lean startup? Why are we doing it in the first place? In this series I will give a short introduction to the lean startup methodology and how to implement this in your startup.
Let’s start at the beginning.
Why do startups need a different approach from all other companies, starting or not. Why did the Lean Startup methodology came to existence in the first place. The use of the word startup is immensely overused and hyped as a marketing term for every single starting company that has something new or is tech related. The term startup however is used specifically to highlight the difference between starting companies and startups. According to Steve Blank:
A Startup is a temporary organization searching for a scalable and repeatable Business model
What does that mean? It simply means that Startups have no Business Model. Yet. Me starting the most beautiful and successful hair salon in the world does not make me a startup. It makes me an entrepreneur, and my entrepreneurial skills and passion can certainly make a successful business out of it, but the Business Model behind hair salons is an existing one. I can roughly calculate the amount of money I need to put into the business, to know what I will be able to get out of it. I can differentiate, target niches, be more exclusive, but still, I am not inventing a new model to change what has been done before in a repeatable and more important scalable way.
The global reset
With the rapid rise of new technologies, easier acces to people all over the world, access to tools not available before, it also became possible to disrupt the way business was done for years and years with only a small team and an innovative idea. The digital revolution demands a global reset. New ways to accommodate the new economy and change in social structures and relations. Startups are searching for those new ways, combining new technologies with business insights. Searching for new ways to make things work using new technologies and new insights.
Lean Startups
Now no two startups are the same, everything they do is new. Paths to succes can not be copied.
What Spotify did for music might work in the world of books, but the path to succes is going to be a very different one. For startups it is important to have a way of minimizing the time and resources in this search for succes. Minimize the risk in every step of the way in order to optimize the chance of succes. You do not want to find out 100K of your savings and 2 years of hard work and no sleep later that you have build something nobody really wants.
This is where the Lean startup comes in. Lean in itself is not new, the concept was coined in the 1980’s when Toyota introduced its minimal waste manufacturing principles. This management system based on making obvious what adds value by reducing everything else has since been introduced in many industries.
Some of the main principles of Lean where taken to accommodate the typical startup search fase for a businessmodel. Be as efficient as possible, reducing both time and money spent as well as minimizing risk along the way:
Respect people (customers and employees)
Solve real problems for real customers
Improve using an iterative, scientific method
Be willing to discover the answer by testing things instead of “knowing” the answer
Do work in small batches and focus on flow and quality
Ask “why” instead of “who” when something goes wrong
With this the Lean Startup methodology was introduced, its main concept being the Build, Measure, Learn loop or validated learning.
Timan's test blog 