I've trouble trusting any development that is done undercover and with no level of transparency to the public. It's a sure way to hide any troubles that may come with the new product, or hide features that are objectionable by any standard.
Most often than not, doing development like this is an easy way to hide something from the users. And if someone says something, he's usually hushed or sued in order to keep the information from any interested party or getting it fixed. Mainly because they are more interested in meeting the needs, or wants, of a small circle of people rather than the needs and wants of the actual users. Or even those who would be affected in other way by the product itself.
This makes it relevant to our interests to back those companies, or groups, that develop their products openly.
Any interested party should be able to check any part of the development process, and ask for changes. Even better would be for ways for changes to be proposed by anyone interested in bringing one forward.
Open collaboration in development processes should be the norm, since this way the interest of most of the people interested would be meet the first time around. Collaborating should be easy, and inactivated in order to bring people to bring proposals to the table.
It's important to take into account no one has all the answers, and other people can bring valuable skill sets, knowledge, and experience to the table. By closing the door to them, we are in fact wasting those valuable resources. And by extension, not giving our product the possibility to reach its full potential.
Not all proposals should be used, but they should be at least heard.
We all benefit from such collaboration. There is far more to win, than there is to lose.
Comments
Post a Comment