Very interesting. Key points:
- observe what is actually having an impact with the clients, don’t assume, A/B website, analyze behavior, % that get the service, don’t over-plan or over-engineer on wrong assumptions of what you think ppl want from ur app.
- the issue right now is we’re efficient but in doing smth the clients don’t want! That is the real goal, not making anything.
- optimize this feedback loop to be faster and smoother
- be ready to change direction when it doesn’t happen as planned
- don’t have ppl stuck with too many tasks (long term left behind) or seeing only one part of things (looks like productivity but if nobody uses, what for?)
- try at small scale even if you’re huge company, and test it out in the real world
- train the people, often the root of problems is humans. Put the amount of effort that is proportionate. Issue -> ask why 5 times.
- don’t blame the ppl, blame the system, ppl make mistakes the system should be resilient. Start with a small problem and name someone responsable for the 5 whys to direct the meetings. One problem at a time
- for the big companies splitting into small departments, make them care (shares, fame, give them authority), not only for money
- protect the innovation departments from the company by giving them independance etc, watch indicators though and limited duration, on limited customer base
- let it grow and experiment with more but once it becomes profitable they will try to protect the status quo again
- encourage new ideas but ask for their basis
How to grow once you’re successful? Very interesting and relevant read.
Growth: fidelisation (pepsi) vs viral (hotmail) vs idk
Growth engine is the most important thing, and don’t assume that what you’re doing with new features works because you have growth.
Don’t just cut down development times, make sure the engineers have the proper tools for working smaller and make it clear how things are for the company.