| | SEPTEMBER 20219Seventh, take very short small steps. Milestones are not effective, and long projects have low success rates. Instead, try to implement something very small but useful every 2-4 weeks, so even if the overall project fails, you still have some parts that add value. Avoid milestones based on the success of the overall project; these are worthless. Focus on small useful steps along the way.Eighth, if you find success, don't be afraid to add more resources and double down on your winners. Alternatively, have a "kill switch" every few weeks for projects that are failing. In general, once two steps or deliverables are missed in a row, the chances of project success are very low. Walk away fast, don't wait to kill it.Ninth, if you start to see successful projects, only then begin to train others to also implement innovation. If you are the only one doing it, it makes for slow work.Tenth, enjoy the successes when they come. Even with a good method, a lot of projects will fail, just kill them fast so they don't cost you much, and you will still have time and resources left to others. Don't aim to "fail fast;" fail cheap and fail forward. It is best if you set the goal in relation to the cost/benefit involved to allow it to scale more easily (remember, you or your team might want solutions that are cheap, fast, and good, but you should pick two). What you want is not the biggest return, but the biggest return per dollar/effort spentRobert Neivert
< Page 8 | Page 10 >