I’m pretty sure when most people with tech knowledge use the phrase “Internet protocol”, they don’t usually abbreviate it to IP, so I doubt confusion happens often. Besides, most of the time, we tend to think of specific internet protocol snipets… such as “http” or whatever. And I’m even more sure that “Internet Protocol” is rarely mentioned outside a conversation on using the internet.
(That was longer than necessary, wasn’t it?)
Anyways. The thing with letting a company decide its own fate is that frequently, they DON’T know what they are doing. Not terribly frequently, but it happens enough that one begins to wonder why people are still hiring Micheal Bay.
However, on the other side of the coin, the audience doesn’t know what to do either. What we may think the answer to one problem is might be a different thing to what would be the logical thing to do if you actually have decent knowledge of the problem.
As a relevant example, we probably think the solution that would keep MLP alive is for Hasbro to not be bought by Disney at all. However it could be the case that for legal reasons it could be less of a liability for them to have sections of their company related to Disney’s existing products (Star Wars and what not) moved to one of Disney’s studios through some form of deal, and Hasbro be contracted on to work on them from the outside. Or possibly some other scenario I haven’t thought of.
Still, whatever the case, the problem we see, and the solution are two very different matters.
We can see the problems easily enough, but don’t know the solutions well enough to advise.
The companies know how to make a solution, but find it hard to locate a problem without feedback.
So there is an inherent need to communicate; on some level at least.
(This was all more or less told to me in a games design course, so take with a grain of salt. And I may be remembering this wrong, but I think the unit was literally called “Games Design 101”.)