OSE Fellowship Performance Development

Intro

OSE Fellows are required to execute a specific number of builds per month once they join the OSE team full time. All of us work together to improve performance - and thus guarantee that we not only meet the required numbers - but also grow with time. The Extreme Builds generate revenue that funds OSE - OSE does not rely on foundation or nonprofit sector funding. We are bootstrapping operations by mission-related revenue streams - which we believe is important for our work to be highly replicable and scalable. Even though we operate in the nonprofit sector, we are an entrepreneurial organization.

Training

OSE provides the training to execute Extreme Manufacuring and Extreme Learning workshops effectively. Such training is the focus of OSE's Immersion Program. During immersion, Fellows-in-Training will be exposed to 6 or more Extreme Builds - which are real-life simulations of the type of work that Fellows will be doing in their own communities once they graduate. The builds during the immersion program serve to both train Fellows - and to provide the actual Extreme Manufacturing/Learning workshop to participants. In every build, Fellows take on additional responsibilities, until they run the build themselves - in pairs - in the 6th or final build. Thus - the typical evolution of responsibility for Fellows may be:

• First workshop - participate in a build of the machine for the first time - to build their own productive machine (3D printer, CNC circuit mill, laser cutter, filament maker, plastic shredder). At this time, Fellows establish contacts with local schools and schedule visits, in pairs, to network with potential clients (schools, libraries)
• Second workshop - repeat of build, and add a second 3D printer to their personal microfactory. Fellows print parts for the second workshop - thereby testing the productivity of their own machine for the first time.
• Third workshop - Fellows participate by sourcing parts for the 3rd build, printing the printed parts, and laser cutting the electronics panel. Fellows participate in teaching a small part of the 3D printer workshop during the actual build.
• Fourth workshop - By this time, Fellows gain a thorough master the design and build of the 3D printer. OSE does the workshop introduction, and the Fellows run the workshop with OSE observing and providing live feedback.
• Fifth workshop - All the Fellows execute the complete workshop by themselves as a group of 4+ Fellows-in-Training, with OSE simply observing and providing feedback.
• Sixth workshop - Fellows pair up and go to 2+ different locations.
• Seventh workshop - (if schedule allows) - Fellows teach an Extreme Learning workshop - which is XM with a day dedicated to teaching design of the 3D printer and of 3D objects in FreeCAD. Includes teaching on how to slice and understand which objects can be printed by following 3D printed object design rules.

Team Development

Fellows are required to be in good standing (see OSE Fellows Good Standing) in order to maintain their position as OSE Fellows. We all work together on performance development. Performance development may include any of these aspects:

• OSE webinars or invited guest lectures over the internet
• Monthly coaching sessions by a professional enterprise coach
• Additional performance development meetings where we work on creative solutions to issues
• Fellows teaching one another during OSE Developer meetings or other sessions.
• Continuing education via addition Immersion Programs every 6 months
• Participation in additional OSE Workshops outside of those the Fellows run themselves.

Team Continuity

The duration of the Fellowship is for one year from the beginning of the Boot Camp, and the Fellow is expect to honor this commitment. Fellows are encouraged to continue with OSE for more than one year as long as they remain in good standing. Fellows can fall out of good standing in several ways, for which a recovery plan must be implemented:

• Not meeting build quotas - needs to be corrected for financial sustainability.
• Incomplete quarterly product release - is needed so we can maintain a predictable schedule and meet annuals goals
• Not investing on one's personal growth - is needed to negotiate the challengest of open source development effectively, and to allow for continuing improvement

Meeting the required quotas is critical. If we are not attracting a sufficient number of clients, then we must:

1. Run more build events
2. Increase the registration numbers by additional, last-minute marketing effort
3. Run build events in more distant, favorable locations
4. Diversify to other products or find a different niche for the Fellow in OSE
5. Identify skill gaps and address them by additional training
6. Diversify the enterprise to enterprise training

Meeting Quotas

We expect that as a startup in each Fellow's location - getting an initial client base may take time - but once developed, things become easier and word of mouth takes over. OSE will leverage its network for marketing, and Fellows will need to visit prospective clients. Fellows are expected to improve their performance as they go through the learning curve.

OSE will not cut the Fellow's stipend if quotas are not met, but instead will make up a deficit from future revenue. We do not believe that it is likely that we will not meet the bare minimum requirement - as we have the opportunity to run additional events or focus more effort on marketing.

Meeting Product Release Goals

If it becomes clear that Fellows are lagging in their product release schedule, possible remedies may include:

1. Putting in additional hours towards completion, and adjusting goals for the next quarter accordingly
2. Outsourcing parts of the work if funds are available
3. Hosting additional Design Sprints or Design Jams for development
4. Spending additional time at OSE headquarters to focus on the development work
5. Leveraging crowd incentive challenges for additional development. To do this, we need to develop a replicable methodology for effective execution of such incentive challenges

If a Fellow is meeting quotas but the R&D work is lagging, then we will look for ways to improve the R&D work. If the Fellow is doing great on R&D work but the numbers of builds are lagging - then we will put more effort into the builds.

Termination

There may be extenuating circumstances under which OSE may be forced to terminate a Fellowship. This may include:

1. Any illegal activities
2. Not showing up for a scheduled workshop, or not preparing materials, printed parts, or other materials for a workshop
3. Disrespecting workshop participants in egregious ways or getting a majority of negative reviews (2.5 or less stars of 5 stars) from workshop participants
4. Not putting in the required hours for R&D work, or producing the required documentation, and not achieving a product release

If Fellows are not making the bare minimum build quota, we will collaborate on improvements and run additional workshops to make up. The Fellow must then spend additional time on build workshops, which may cut into the R&D effort. Ideally, we would like to avoid running extra workshops to keep the development schedule on track.

If a Fellow does not meet the bare minimum build quota - and at the same time does not make visible product release effort - the Fellow may be terminated. Fellows will receive a one month warning in this case, and if no visible improvement takes place