|
|
| (3 intermediate revisions by the same user not shown) |
| Line 28: |
Line 28: |
| *10% bonus per event. | | *10% bonus per event. |
|
| |
|
| =Announcement= | | =STEAM Camp Senior Project Manager Job Announcement= |
|
| |
|
| We are looking for a Senior Project Manager for organizing the Open Source Microfactory STEAM Camps. This is a full time position, reporting to the OSE executive director, and we are offering competitive pay based on experience and skills.
| | See [[STEAM Camp Senior Project Manager Job Announcement]] |
| | |
| Does the open source economy speak to you as the next evolution of human consciousness? Do you want to create a passionate, high performing team to make this happen? Do you believe that global, open collaboration is a prerequisite for getting there? Do you want to solve pressing world issues, and teach others to do so with you? Are you open to rapid learning across boundaries to update your mental models continuously?
| |
| | |
| Currently we are developing the 9-day Open Source Microfactory STEAM Camp as a regularly-scheduled immersion education program to be deployed concurrently in multiple cities around the world. Based on the success of our [https://www.opensourceecology.org/open-source-microfactory-stem-camp/ first STEAM Camp], we felt that we can make a dent in the universe by offering collaborative design training for public development of common products. This program involves the development of open source hardware products, their marketing mix, producer training, certification, and franchising such that we democratize production and bring innovation back to every community. See the [[STEAM Camp Curriculum]] for the program – it’s a powerful 9 days or collaborative design training.
| |
| | |
| We need a Senior Project Manager to help us organize and execute all the steps of successful Camps as we expand this program. We plan to reach 12-24 events in parallel in cities around the world – such that at each parallel event – we have a combined effort of about 500 participants who can work together on collaborative design. Do the STEAM Camps speak to you as something that can do a lot of good, and do you have the management and operations skills to execute such complex events?
| |
| | |
| =Job Description=
| |
| Primary responsibilities include:
| |
| | |
| *Recruitment of instructors for the Open Source Microfactory STEAM Camp
| |
| *Coordinating STEAM Camp instructors in delivering necessary curriculum and related prototypes
| |
| *Scheduling STEAM Camp events, and providing admin, markeing, and logistics support
| |
| *Develop a marketing strategy to fill each camp
| |
| *Facilitating collaboration between STEAM Camps as they are run in multiple locations around the world at the same time
| |
| *Evaluating and improving the [[STEAM Camp Curriculum]]
| |
| *Optimizing the cost structure and budgets for STEAM Camps
| |
| *Refine and document the process for effective delivery of the STEAM Camps
| |
| *Attend the STEAM Camps, learning the STEAM Camp curriculum to the point of being able to serve as an Instructor
| |
| | |
| All of these responsibilities will receive support and involvement from the Executive Director and other STEAM Camp instructors. Expectations for the Senior Project Manager in the first 6 months include:
| |
| | |
| *Recruit at least 6 new instructors per month
| |
| *Reach a minimum of 12 STEAM Camps per month run on a bimonthly basis - that are being run at the same time in population centers around the world
| |
| *Filling each STEAM Camp location with 12 paying participants
| |
| *Publish monthly blog updates on STEAM Camp developments
| |
| *Publish all work openly and update time log on the public work log on a daily basis
| |
| *Attend at least one STEAM Camp as a participant
| |
| | |
| Create an annual budget and submit it for Board approval
| |
| Manage contractors (e.g., infrastructure contractors)
| |
| Organize Board meetings and generally support the Board's activities
| |
| Manage logistics of face-to-face events.
| |
| | |
| We are therefore especially looking for a highly relational applicant, capable of managing complexity, and open to learning new skill sets. Applicants must be fluent in English and and proficient in written communications.
| |
| | |
| Applicants need not be technically proficient in open source hardware, but must have a basic level of hands-on building skills that allow for understanding of a product build process. Applicants should fundamentally understand the open source ethic, is and have some prior knowledge of the field, both technically and culturally.
| |
| | |
| Compensation will be based on experience and skills.
| |
| | |
| OSE has been an all-volunteer organization for over a decade. You should come into this job expecting to have a major impact on OSE and its mission. We want to expand and grow our programs to provide a solid financial base for further growth, with the ultimate goal of creating education campuses that serve as the next evolution of basic and higher education towards the [[Open Source Economy]]. carrying out our mission more effectively: to educate about and advocate for the benefits of open source and to build bridges among different constituencies in the open source community.
| |
| | |
| To apply for this position, please send an email to gm-apply {_AT_} this top level domain. Your email should include a plain text paragraph or two summarizing your interest in and qualifications for the position, with your CV, résumé, or other supporting documents as attachments as needed. All attachments should be in formats commonly used by open source software (e.g., please don't send something in a proprietary word-processor format; PDF is fine, though).
| |
| | |
| To help us avoid spam, and thus be able to see all incoming applications promptly, please do not post the above email address in email-address form (with an @-sign) anywhere on the Internet. Just point people to this page instead. Anyone applying to this position at Open Source Ecology can figure out the actual email address from seeing the above! Thanks.
| |
Average Pay
Revenue Model
- For sustainability, the SPM should bring in more revenue than their pay
- At 24 events per month, monthly net revenue is $120k in the fully developed STEAM Camp
- Flight risk management - (1) candidate is not motivated by money, but by purpose; (2) they are supercooperators, which promotes collaboration over defection; (3) they are themselves interested in learning the content, such that they are in it for the personal growth as well; (4) pay structure reflects their performance.
Why Open Works
We are radically open to enterprise replication by third parties. This is because if others are adopting the curriculum, that means that they are using 100% open source toolchains to engage in open source product development: the whole world wins if this happens. If they don't do this, then they are creating their own proprietary product, which is likely to have less economic distribution associated with it.
The best examples of proprietary collaborative design platforms that work - are unknown. Kickstarter is a good one for projects that are mostly not open source. They are collaboratively funded, but typically not collaboratively developed - and typically the product is not open source. So Kickstarter and other platforms like this already exist. We're aiming for the next level - where the product and process is collaborative and open source. We believe that this is a stronger value proposition than partially collaborative and partially open products.
99 Designs, for example, is plain crowdsourcing. It is not collaborative nor open source. Period. It is essentially about cheaper access to talent, where talent competes, not collaborates.
The best example of collaborative proprietary designs that may work - is OpenDesk. But it is not clear whether anyone there is actually making money.
The perennial problem is always attribution: how do you divide revenue fairly? It's not worth it. That's why the world came up with the open source paradigm: Accounting for proprietary contributions for payment is very hard - so to avoid the difficulty - you attribute without payment - which is what open source does.
Is it possible that a company takes our curriculum and through improved execution takes our market share? If that were to happen, that would be excellent.
Is it possible that a company takes our curriculum - and makes it partially closed - and takes our market share? If that were to happen, that should be ok because we provide a different product, which would likely be better. The 'better' comes from the fact that anyone can start a business. For us to succeed, we should spend as much effort on creating a support infrastructure for new entrepreneurs as possible: turnkey support for building open source microfactories in any community. That is exactly what we are doing, and must be strong on this part. Otherwise, some half-ass company can come in and beat us if our product is sufficiently small. We can win only by having the most ambitious product - and that product is transformative by nature. In summary: we are likely to be more attractive to the producer because we give more wealth away than a proprietary platform.
The practice shall be seen as it emerges...
Pay Structure Options
- $8k/mo regular + annual bonus. 3 month time to first events -
- 10% bonus per event.
STEAM Camp Senior Project Manager Job Announcement
See STEAM Camp Senior Project Manager Job Announcement