I'd agree. When looking at systems, the focus is always on the bottle-necks - what is the component that is throttling the whole system. Which is fine, until yo

I'd agree. When looking at systems, the focus is always on the bottle-necks - what is the component that is throttling the whole system. Which is fine, until you replace the next one, and the next one - and eventually you end up with 'success' - or looking at it another way, "everything is the bottle-neck". At this point you're stuck as you've incrementally worked your way into a corner and can't make large changes. If in parallel, you'd put a bit of effort (i.e. time/money) into development of components to try to make them optimal/flexible etc in their own right - you've a decent head-start on creating system v2