Translation: you want a fleet of people to do the hard work of adding new capabilities to the system, with all the man-hours that comes with doing that work (and its testing and refinement), but you don't want to pay for any of that.
"Were's the grit, the smarts" - indeed.
No. I want less people doing the work-to which I would be willing to pay. These must be motivated individuals up to the challenge.
This is a quote from a piece in HBR from 2019
Why Constraints Are Good for Innovation
"...As a simple illustration of the principle, consider GE Healthcare’s MAC 400 Electrocardiograph (ECG), which
revolutionized rural access to medical care. The product was the outcome of a formidable set of constraints imposed on GE engineers: develop an
ECG device that boasts the latest technology, costs no more than $1 per scan, is ultra portable to reach rural communities (i.e, should be lightweight and fit into a backpack), and is battery operated. The engineers
were given just
18 months and
a budget of $500,000 – a very modest budget by GE’s standards, given that development of its predecessor cost $5.4 million. Our research suggests that GE engineers were not successful despite these constraints, but
because of them. Constraints can foster innovation when they represent a motivating challenge and focus efforts on a more narrowly defined way forward...."
Now with this thread we are only talking about software....