The rationale behind #NewLean and #StartUpHunch
a research PDF and slide-deck
1. The rationale for #NewLean: the two-pager
From the original draft two-pager on the subject of #NewLean’s rationale:
Traditional #lean solves one problem and one problem only: how to invoice the potential or ongoing client ASAP …
Some problems in need of solution can, it is true, even so, be solved by taking a two-dimensional journey of connected pain-points, picking them off one-by-one, in order to make money. But when a real-world problem is solved in this way, it’s a collateral outcome: it’s secondary to the main problem being solved. This being, how to make money out of the potential or ongoing client as speedily as practical.
What’s more, in traditional #lean, the more you code, the more hours you can invoice. There is literally no systemic or built-in incentive for companies to ensure accuracy at the beginning of the software development process: discovery.
Conversely, there is every incentive to essentially “get it wrong”: once the client is captured and in mid-spend, further invoicing becomes much easier.
2. The rationale for #NewLean: the slide-deck
For more information on #NewLean and example applications of the tools in an integrated manner in the domains of law enforcement and counter-terrorism, please click through on the three links below:
gb2earth.com/newlean | gb2earth.com/waste | gb2earth.com/invest-noi