Review

Introduction

Review refers to any aspect of OSE's work, though primarily to the review of OSE's products. OSE's review process is open to the public, in that all review documents are published online. Review can also occur on other levels - such as organizational learning or development processes.

To enable technical review of product design in particular, we publish a Google Presentation that goes through conceptual design, CAD, or pictures of a machine - and requests feedback on certain specified items. Then, individuals can use the Review Form below to submit all comments and suggestions. The Google presentation is also open for comments on the presentation itself, as well as Pull Requests. Working Team members are usually given edit access to documents.

If you have suggestions, use our Review Form

This applies to technical review of machines, or organizational and process review.

Results

edit

Scope of Review

Review is desired within an open organization - on anything that can lead to organizational learning. The goals are:

1. Providing general feedback
2. Providing mid-course corrections as necessary
3. Identifying key missing resources that prevent goals from being met
4. Assessing proper allocation of resources and shifting resources around if necessary

Key Elements of a Review Submission

1. Clear presentation of results - allow review to happen rapidly. Brevity and clarity are key, without which it is impossible to go through all of a person's materials.
2. Verifiable - results are easily verifiable, increasing the likelihood that the feedback is useful

Organizational Review

Key questions:]

1. Clarity - What is the mission of the company and what is its unique approach? How is that approach implemented? For OSE, it's the Developing an ethical, open source economy.
2. Strategy - does the core work of the company adhere to its core mission?
3. Coherence - is every piece of the company aligned with the core mission? What could be better?
4. Resource allocation - are people matched to their skill set?
5. Projects - are the projects priorities chosen in a way that helps the company grow, while considering constraints and opportinities?
6. Learning - what mechanisms are built in so that the company is a learning organization?

Technical Review

You can use this form to submit technical review. If you want others to submit technical review, use various communication channels to solicit a response.

Implementation

Usually, OSE asks specific subject matter experts (SME) for feedback on specific design points. Formally, Review is item number 33 on OSE's official Development Template.

Organizational/Technical

1. Core contributors maintain a Work Log showing all results and progress.
2. Staff maintains a Project Review framework consisting of a Critical Path Diagram and a spreadsheet of all supporting tasks
3. Staff writes a monthly planning and review in their work log - 1. summary of accomplishments, 2. What worked. 3. What didn't. 4. Plan for next month.
4. Staff meet with ED once a month for the Project Review