Executive Director: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
(Blanked the page)
No edit summary
Line 1: Line 1:
Role Description of tasks currently taken on by Marcin, ED.
=CEO Required Skills=
'''''Abstract:''''' The CEO sets the Critical Path, defines process for supporting the Critical Path, and dog-foods initial versions of processes.


*Critical Path Narrative - ability to lead the project along a Critical Path - ability to reframe daily tasks within the framework of the greater project vision.
*Technical Literacy - Ability to translate [[OSE Specifications]] into specific product design features of the [[50 GVCS Tools]]
*Fabrication Experience - to understand and direct translation of [[OSE Specifications]] into design-for-fabrication of lifetime design products
*Systems design capacity to define and build a coherent product ecology of the [[50 GVCS Tools]].
*Process Development - Ability to create effective processes for [[Open Source Product Development]], emphasizing strategic clarity, development efficiency, and performance management
*Strategic Planning - ability to execute cost-benefit analysis, risk analysis, review, and effective decision-making ragarding development priorities
*Economic Analysis - Ability to perform economic feasibility analysis and enterprise planning
*Leadership - Ability to generate effective [[Critical Path Narrative]]s and to inspire the team towards excellence
*Ability to [[Work Openly]]
==CEO Duties - Until 2014==
*Prototyping: Directs integrated development of machine prototyping, agricultural, construction, production, and organizational infrastructures. Reviews strategic priorities and critical path with staff.  (25%)
*Production Development: Create and execute process for Collaborative Production and bootstrap funding. (20%)
*Process Development: Continuously create, integrate, and refine Open Source Product Development process - particularly the integration of social and technical aspects of a volunteer/paid process, with on-site and remote collaboration. Develops [[Management Structure]] and [[Financial Controls]] as key processes to support core prototyping. (20%)
*Review: Review product designs for adherence to OSE Specifications and GVCS 50 Product Ecology (10%)
*Hiring: valuate and approve all hires, contracts, bids, and other offers from on-site and remote participants (10%)
*Development Budget: Create a development budget and development timeline (5%)
*Investor Outreach: Engage in speaking engagements and [[Investor]] relations as needed (5%)
*Nonprofit Dev: Oversee strategic effectiveness of nonprofit resource development (5%)
<html><img src="https://docs.google.com/spreadsheet/oimg?key=0Av4ZjQn4DHJHdEU3MkZ5dk81QXVqbnRsVWVINzkzQnc&oid=4&zx=uhw78kkdfi8o" />
</html>
[https://docs.google.com/spreadsheet/ccc?key=0Av4ZjQn4DHJHdEU3MkZ5dk81QXVqbnRsVWVINzkzQnc#gid=0 edit]
==Critical Issues==
The critical milestone for effective leadership of the project is clarifying the requirements of a basic hardware development methodology, as well as producing the supporting documentation for this this method. Presently, we are considering a lean technique with the key point of using simple, widely-available development tools for hardware - wikis, Google Docs, and Sketchup. The next major milestone include:
*Refining the [[Flashy XM]] platform based on recent [[CAD, Remote Collaboration, Replication, and Collaborative Production Learnings]] - in the form of a seminal white paper on a distributed, scalable, open source product development platform.
*Detailing a budget required to execute on each product, with implications for budgets required for scalability

Revision as of 22:51, 4 October 2012

Role Description of tasks currently taken on by Marcin, ED.

CEO Required Skills

Abstract: The CEO sets the Critical Path, defines process for supporting the Critical Path, and dog-foods initial versions of processes.

  • Critical Path Narrative - ability to lead the project along a Critical Path - ability to reframe daily tasks within the framework of the greater project vision.
  • Technical Literacy - Ability to translate OSE Specifications into specific product design features of the 50 GVCS Tools
  • Fabrication Experience - to understand and direct translation of OSE Specifications into design-for-fabrication of lifetime design products
  • Systems design capacity to define and build a coherent product ecology of the 50 GVCS Tools.
  • Process Development - Ability to create effective processes for Open Source Product Development, emphasizing strategic clarity, development efficiency, and performance management
  • Strategic Planning - ability to execute cost-benefit analysis, risk analysis, review, and effective decision-making ragarding development priorities
  • Economic Analysis - Ability to perform economic feasibility analysis and enterprise planning
  • Leadership - Ability to generate effective Critical Path Narratives and to inspire the team towards excellence
  • Ability to Work Openly

CEO Duties - Until 2014

  • Prototyping: Directs integrated development of machine prototyping, agricultural, construction, production, and organizational infrastructures. Reviews strategic priorities and critical path with staff. (25%)
  • Production Development: Create and execute process for Collaborative Production and bootstrap funding. (20%)
  • Process Development: Continuously create, integrate, and refine Open Source Product Development process - particularly the integration of social and technical aspects of a volunteer/paid process, with on-site and remote collaboration. Develops Management Structure and Financial Controls as key processes to support core prototyping. (20%)
  • Review: Review product designs for adherence to OSE Specifications and GVCS 50 Product Ecology (10%)
  • Hiring: valuate and approve all hires, contracts, bids, and other offers from on-site and remote participants (10%)
  • Development Budget: Create a development budget and development timeline (5%)
  • Investor Outreach: Engage in speaking engagements and Investor relations as needed (5%)
  • Nonprofit Dev: Oversee strategic effectiveness of nonprofit resource development (5%)


edit

Critical Issues

The critical milestone for effective leadership of the project is clarifying the requirements of a basic hardware development methodology, as well as producing the supporting documentation for this this method. Presently, we are considering a lean technique with the key point of using simple, widely-available development tools for hardware - wikis, Google Docs, and Sketchup. The next major milestone include: