Lean service development is not a secret code. There are concrete steps you can take to integrate it into your development projects and your organization.
If you decide you want your product development organization or project to be leaner, meaner, more flexible and capable of fast moves, changes have to be made on all levels and in every phase of the development process:
- Recognizing the problem
- Finding a product/market fit and validating it on the market
- Scaling up to create a profitable and growing business Different things drive the various phases of the product development process. Rapid validation is of the essence during the first phase: build cheap and test.
High-quality design and the ability to react quickly to feedback are important in phase two. This phase is about creating a product that users love.
Optimization based on key data and metrics, scaling up the product technically and commercially, and continuously improving internal and external quality are the primary drivers for phase three.
Here some practical tips:
1. Put all your experts in the same room Moving workstations around is a nice, concrete first step to take when making your organization’s product development process leaner. Getting experts from different fields to communicate with each other is vital for the success of digital services. Take your planners, designers, developers, content creators and marketing people, and stick them in the same room.
2. Know your customer and find a problem worth solving Live with your target group. A personal experience with a user’s issues will always leave a stronger mark than reading second hand research reports. In the early phases of the design process, we should look to the users for inspiration and an understanding of what constitutes a problem worth solving, as well as insight into the their everyday lives. Be open and curious, but keep in mind it’s not up to the user to spell out what he or she really wants. Figuring it out is your job.
Here are some excellent tips to help you get closer to the user: http://giffconstable.com/2012/12/12-tips-for-early-customer-development-interviews-revision-3/
Meeting and getting to know the customer is how you find problems worth solving. For the user, a problem worth solving is significant, expensive, common and a source of frustration - a problem the user is willing to pay to have solved. He or she may already have tried to solve it or circumvent it altogether.
3. Design the emotions the user experience evokes Expert organizations have a tendency to view customers as rational agents and underestimate the importance of emotions as a part of the design process. Appealing to the user’s emotions can have a considerable impact on the decision to buy.
Think back on things you’ve bought lately. Were you swayed by a list of specifications and rational argumentation or the fact that you just liked the product? A user experience that evokes emotions doesn’t happen automatically or as a by-product of some other process. It requires design.
Deep design creates a harmonious whole that is more than the sum of its parts. If the product is built by the book, from the ground up, while hewing tightly to a rigid priority list, the end result will probably be quite adequate, but it won’t inspire an emotional reaction.
Lean development processes and design complement each other well. Incremental design requires a strong vision. Otherwise the core idea of the product risks being lost in the compromises that are an integral part of the development process.
4. Validate your business assumptions
In the beginning, all you have are some educated guesses related to how to build a successful business. These assumptions are validated along the way. Honest feedback from outside the project team is essential: users, markets or other stakeholders. From the point of view of creating a successful business, most of the people you need to convince are to be found outside the project team.
Testing is considered a cumbersome part of the process and it strikes fear in people. In 2014 our own Risto Sarvas wrote an article titled You can avoid customer-centeredness, but you can’t run away from the customer (Asiakaskeskeisyyttä voi vältellä, mutta asiakkaita ei voi juosta pakoonin Finnish). In it he listed some of the reasons commonly used to ditch user testing during the early phases of the development process: No time. No money. No need. No use. Never did it before. Apple doesn’t do it.
Don’t buy it. Fight it. Do something. Convince the others. Test the product for five minutes with the first person you run into. Continue fighting for user-centered design.
5. The customer is product development’s crowning achievement
Developing a product and growing its customer base should go hand in hand when building new business. Some questions you need to consider early on in the process: how are you going to identify and find potential customers? How will you pique their interest in your product and get them to commit to buying it?
By putting everyone in the same room, the lean product development process essentially eliminates the artificial division between product development and marketing, allowing for closer consideration of how features under development will impact customer relationships.
- Will they increase the rate at which the product is recommended by users?
- Do any features have the potential to go viral?
- Do they increase engagement with the product?
- Could it cause someone to abandon the product?
Don’t forget to utilize marketing automation and build in the necessary metrics.
6. Get a great product manager ‘The product guy’ is an important role in many Silicon Valley companies. He or she is like a product manager and in a startup, the role is as central to the success of a company as that of the programmer and the designer. The product manager looks at the way the company functions from a product perspective and through the value of the product. It’s the product manager’s job to find the balance between user needs, business demands and technology. The product manager makes the tough choices when prioritizing functionalities. A good product manager is like a junior CEO: influential, good at networking, understands the customer and the markets, sees the big picture and makes good decisions that maximize product ROI.
7. Lightning-fast feedback guarantees quality
In addition to the developers’ know-how, the environment they work with has a critical impact on the cost-effectiveness and quality of a software product. Testing changes should be possible within seconds. Make investing in and building development and testing environments, tools and automation an early priority for your project.
Imagine two professional chefs, both working on a new recipe for a pasta sauce. The first one is allowed to taste the sauce boiling in the pot whenever he wants. The second one has to carefully package a sample, call a courier and send the package to be tested by someone whose taste the chef is in no way familiar with. Which chef do you think will create the better sauce?
8. Don’t build everything yourself
Once your understanding of your customer’s problems is deep enough, it’s easier to find ready-made solutions for those problems among what other technology vendors offer. Building high-quality solutions is expensive. Solutions with a defined scope and a global market are often much more cost-effective than local products with a broader scope, never mind something you built yourself.
If you decide to build it yourself, make sure you do that one core thing that differentiates your product from the rest really well. The rest of the stuff you can buy from the cloud or China. Utilizing open source components and putting your own components out there is worth considering, too. Creating and activating a community of creators takes some resources, though.
9. Kill your bad ideas as early as possible
A lean development model encourages the team to take quick, incremental steps towards the desired end-result. It emphasizes short-term goals. Sometimes this way of working can make it hard for the team to make radical decisions, such as killing the product or changing its place in the value chain.
Sometimes past investments in technology (e.g. a lot of code that does the wrong thing) make radical changes psychologically, financially and technologically difficult.
You can prepare for changes by investing in modularity and high quality tech. But don’t give this kind of thinking too much leeway, because really you should be investing as little as possible and only in what is most important for strategic differentiation.
10. The service launch is the starting point for development, not the goal
The biggest, boldest and most beautiful milestone of a traditional product development process is the launch. The product is thrown out into the market and the team’s focus moves on to other things. The project is over and everyone is reluctant to return to the old stuff.
In service development, this is where the real work starts. Where does the money come from? Using no more than half of your development budget before launch is a good rule of thumb - preferably no more than ten percent, in fact. The launch is when you find out whether there’s demand for the product and if it’s worth investing in.
After the launch, decisions can finally be made based on data. Analytics that measure use and behavior can tell us:
- Did we reach the right users?
- Does the product design work?
- Does the marketing work?
- Does the business model work?
This doesn’t mean you should start adding functionalities after launch, even though expanding a service is rewarding work. Utilizing analytics and feedback to optimize the primary features of service is usually more profitable - just make sure you and the analytics concur on what those features are. This is how we build services people learn to love.