Feedback Loops: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=Intro= There is a vast array of ways that OSE can facilitate feedback loops to add value and promote developer retention. These can be: #Collaborator surveys - Is a collabor...") |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
There is a vast array of ways that OSE can facilitate feedback loops to add value and promote developer retention. These can be: | There is a vast array of ways that OSE can facilitate feedback loops to add value and promote developer retention. These can be: | ||
#Collaborator surveys - Is a collaborator turning into a developer? How can we facilitate the transition? Surveys on needs such as '''Enterprise Startup Needs Survey''' can help provide clarity to collaborators by asking teleological questions, and facilitate a feedback loop on how we can meet developer needs. | #'''Collaborator surveys''' - Is a collaborator turning into a developer? How can we facilitate the transition? Surveys on needs such as '''Enterprise Startup Needs Survey''' can help provide clarity to collaborators by asking teleological questions, and facilitate a feedback loop on how we can meet developer needs. | ||
#Telemetry - feedback loops for machines, ie, IoT connected to machines. See what Caterpillar does - [https://www.cat.com/en_US/articles/support/telematics.html] | #'''Telemetry''' - feedback loops for machines, ie, IoT connected to machines. See what Caterpillar does - [https://www.cat.com/en_US/articles/support/telematics.html] | ||
#'''Feedback Loop Guidelines''' - provided to all collaborators so that they become familiar with the potential of large-scale, collaborative development - and what conditions/requirements make such development happen - and happen effectively. | |||
#'''User-Generated Maps of Resources''' - these could be of suppliers, resources, marketing and distribution channels, and are made available to the 'competition' so everyone benefits. | |||
Latest revision as of 23:47, 24 January 2021
Intro
There is a vast array of ways that OSE can facilitate feedback loops to add value and promote developer retention. These can be:
- Collaborator surveys - Is a collaborator turning into a developer? How can we facilitate the transition? Surveys on needs such as Enterprise Startup Needs Survey can help provide clarity to collaborators by asking teleological questions, and facilitate a feedback loop on how we can meet developer needs.
- Telemetry - feedback loops for machines, ie, IoT connected to machines. See what Caterpillar does - [1]
- Feedback Loop Guidelines - provided to all collaborators so that they become familiar with the potential of large-scale, collaborative development - and what conditions/requirements make such development happen - and happen effectively.
- User-Generated Maps of Resources - these could be of suppliers, resources, marketing and distribution channels, and are made available to the 'competition' so everyone benefits.