Apprenticeship Metrics - Revision history

Marcin: Redirected page to OSE Apprenticeship Metrics

2025-05-20T23:56:20Z

Redirected page to OSE Apprenticeship Metrics

← Older revision		Revision as of 23:56, 20 May 2025
Line 1:		Line 1:
	~~=Big Picture=~~		#redirect [[OSE Apprenticeship Metrics]]
	OSE's goal is to level the playing field for prosperity, freedom, and justice for everyone by creating a culture of abundance. We get there by learning self-efficacy towards self-actualization and self-realization as a means to the discipline of open collaboration.

	~~We teach through the~~ Apprenticeship, defining metrics of success and incentibizing for them. We start with asking important questions for the prosperity of the world, and move on to tackle impossible problems. We produce solutions by collaboration, commitment to lifelong learning, and the discipline of abundance. To set a new stage for civilization, where self-determination is key.

	==Metrics==
	*Integrated builder -745 burndown
	*Pay scale - Individual skill burndown
	*Quality of questions proposed by students. List is kept in a wiki page.
	*Time to learn to Count - physical numeracy of all mass physics. Phase 2 is energy physics. Statistics and data analysis. Graphing. Why learn to count. Magnitudes and natural world quantities.
	*Time to learn to read. Both speed/comprehension, and reading tables and data sheets and known information. Why learn to read.
	*Time to learn to collaborate (collaborative literacy) on scalable developmentproject (million people).
	*Time to learn CAD and part libraries.
	*Time to learn 500 mechanisms.
	*Time to learn 500 algorithms
	*Time to learn to design anything.
	*Time to understand common materials and how to produce them. Rocks, sunlight, plants, soil, water.
	*Time to self-efficasize, self-realize, self-actualize.
	*Time to abundance mindset, meaning the theory and practice of global collaboration. This is a philosophy and practice.
	*Time to achieve 50 project teams for [[Distributed Market Substitution]]-scale development. Probably a campus level 240-2400 scale for each.


	~~=Details Overview=~~

	The proof of a 24 person operation building a house in 5 days is unprecedented - and would constitute the first company in the world that builds residential housing on this radical timescale. Thus, this is the experiment worth proving. The key is 24 people working together: unless a high level of coordination exists regarding all the tasks, this would not happen. Skill, coordination, and cross-training are key. In order for a radical speed to happen, each person must handle a wide array of build tasks. Incentives must be created for cooperation, such as everyone helping the slowest guy so that we function as a high performing team, not a team with a few star players. Because few star players are a bad design - more could be attained when each team member is strong, as this is a team sport.

	~~Metrics:~~
	#746 task burndown, with measured time per task. Every time a person performs this task, we take data. To do this, we document by pictures: start and end. Thus, we define the start and end for 746 tasks, and even subtasks. Each person has a stat graph where every task is measured for a burndown: from high time, asymptote to a low value. We may also observe and look out for any U-shape boomeranging - a person gets slower at a task. If that is the case, this is addressed in pay scale. A person must maintain their level of skill, and data is collected passively. For example, in the RLF, automated video capture means that we can capture video from any bay or work station. The facility is heavy in camera bandwidth requirement - but this means that data can be collected passively at any time. Each person contributes to rigorous data collection, which is actually as simple as picture at beginning + picture at end - which documents build time. We must perfect this by clear definition of task breakdown and cut-in + cut-out points. Data collection cannot become a burden. Further, learning and quality control can be added: pictures of unique results etc that serve as learning material.
	#Pairing: best burndown person, at a regular interval, pairs with the slowest person to help them pick up the tricks of learning a task. This way, teachers are made as a result of this process. We can determine whether 'closure of gap' = performance burndown is accelerated for the slower person - by observing if the person burns the skill faster than people who are not pairing up for that skill.

	~~=Dashboard=~~
	*For OSE learning on global intelligence increase - dashboard on all the elements of [[Candidate Assessment]]~~. This is for accepted individuals only who are on the Genius Track.~~
	*Builder Track - burndown of 743 tasks. Translated to pay scale. Burndown of 12 Modules - translated to pay scale.
	*Data Collection transparency - 743 and 12 related to multiple data points, tracking time per over 4 years. Semiannual bonus for tracking time decrease per task - extracting that from their data collection.

Marcin: /* Overview */

2024-08-05T22:10:08Z

Overview

← Older revision		Revision as of 22:10, 5 August 2024
Line 1:		Line 1:
	=Overview=		=Big Picture=
			OSE's goal is to level the playing field for prosperity, freedom, and justice for everyone by creating a culture of abundance. We get there by learning self-efficacy towards self-actualization and self-realization as a means to the discipline of open collaboration.

			We teach through the Apprenticeship, defining metrics of success and incentibizing for them. We start with asking important questions for the prosperity of the world, and move on to tackle impossible problems. We produce solutions by collaboration, commitment to lifelong learning, and the discipline of abundance. To set a new stage for civilization, where self-determination is key.

			==Metrics==
			*Integrated builder -745 burndown
			*Pay scale - Individual skill burndown
			*Quality of questions proposed by students. List is kept in a wiki page.
			*Time to learn to Count - physical numeracy of all mass physics. Phase 2 is energy physics. Statistics and data analysis. Graphing. Why learn to count. Magnitudes and natural world quantities.
			*Time to learn to read. Both speed/comprehension, and reading tables and data sheets and known information. Why learn to read.
			*Time to learn to collaborate (collaborative literacy) on scalable developmentproject (million people).
			*Time to learn CAD and part libraries.
			*Time to learn 500 mechanisms.
			*Time to learn 500 algorithms
			*Time to learn to design anything.
			*Time to understand common materials and how to produce them. Rocks, sunlight, plants, soil, water.
			*Time to self-efficasize, self-realize, self-actualize.
			*Time to abundance mindset, meaning the theory and practice of global collaboration. This is a philosophy and practice.
			*Time to achieve 50 project teams for [[Distributed Market Substitution]]-scale development. Probably a campus level 240-2400 scale for each.


			=Details Overview=

	The proof of a 24 person operation building a house in 5 days is unprecedented - and would constitute the first company in the world that builds residential housing on this radical timescale. Thus, this is the experiment worth proving. The key is 24 people working together: unless a high level of coordination exists regarding all the tasks, this would not happen. Skill, coordination, and cross-training are key. In order for a radical speed to happen, each person must handle a wide array of build tasks. Incentives must be created for cooperation, such as everyone helping the slowest guy so that we function as a high performing team, not a team with a few star players. Because few star players are a bad design - more could be attained when each team member is strong, as this is a team sport.		The proof of a 24 person operation building a house in 5 days is unprecedented - and would constitute the first company in the world that builds residential housing on this radical timescale. Thus, this is the experiment worth proving. The key is 24 people working together: unless a high level of coordination exists regarding all the tasks, this would not happen. Skill, coordination, and cross-training are key. In order for a radical speed to happen, each person must handle a wide array of build tasks. Incentives must be created for cooperation, such as everyone helping the slowest guy so that we function as a high performing team, not a team with a few star players. Because few star players are a bad design - more could be attained when each team member is strong, as this is a team sport.

Marcin: /* Overview */

2024-08-02T05:54:44Z

Overview

← Older revision		Revision as of 05:54, 2 August 2024
Line 5:		Line 5:
	Metrics:		Metrics:
	#746 task burndown, with measured time per task. Every time a person performs this task, we take data. To do this, we document by pictures: start and end. Thus, we define the start and end for 746 tasks, and even subtasks. Each person has a stat graph where every task is measured for a burndown: from high time, asymptote to a low value. We may also observe and look out for any U-shape boomeranging - a person gets slower at a task. If that is the case, this is addressed in pay scale. A person must maintain their level of skill, and data is collected passively. For example, in the RLF, automated video capture means that we can capture video from any bay or work station. The facility is heavy in camera bandwidth requirement - but this means that data can be collected passively at any time. Each person contributes to rigorous data collection, which is actually as simple as picture at beginning + picture at end - which documents build time. We must perfect this by clear definition of task breakdown and cut-in + cut-out points. Data collection cannot become a burden. Further, learning and quality control can be added: pictures of unique results etc that serve as learning material.		#746 task burndown, with measured time per task. Every time a person performs this task, we take data. To do this, we document by pictures: start and end. Thus, we define the start and end for 746 tasks, and even subtasks. Each person has a stat graph where every task is measured for a burndown: from high time, asymptote to a low value. We may also observe and look out for any U-shape boomeranging - a person gets slower at a task. If that is the case, this is addressed in pay scale. A person must maintain their level of skill, and data is collected passively. For example, in the RLF, automated video capture means that we can capture video from any bay or work station. The facility is heavy in camera bandwidth requirement - but this means that data can be collected passively at any time. Each person contributes to rigorous data collection, which is actually as simple as picture at beginning + picture at end - which documents build time. We must perfect this by clear definition of task breakdown and cut-in + cut-out points. Data collection cannot become a burden. Further, learning and quality control can be added: pictures of unique results etc that serve as learning material.
			#Pairing: best burndown person, at a regular interval, pairs with the slowest person to help them pick up the tricks of learning a task. This way, teachers are made as a result of this process. We can determine whether 'closure of gap' = performance burndown is accelerated for the slower person - by observing if the person burns the skill faster than people who are not pairing up for that skill.

	=Dashboard=		=Dashboard=

Marcin: /* Overview */

2024-08-02T05:52:22Z

Overview

← Older revision		Revision as of 05:52, 2 August 2024
Line 2:		Line 2:

	The proof of a 24 person operation building a house in 5 days is unprecedented - and would constitute the first company in the world that builds residential housing on this radical timescale. Thus, this is the experiment worth proving. The key is 24 people working together: unless a high level of coordination exists regarding all the tasks, this would not happen. Skill, coordination, and cross-training are key. In order for a radical speed to happen, each person must handle a wide array of build tasks. Incentives must be created for cooperation, such as everyone helping the slowest guy so that we function as a high performing team, not a team with a few star players. Because few star players are a bad design - more could be attained when each team member is strong, as this is a team sport.		The proof of a 24 person operation building a house in 5 days is unprecedented - and would constitute the first company in the world that builds residential housing on this radical timescale. Thus, this is the experiment worth proving. The key is 24 people working together: unless a high level of coordination exists regarding all the tasks, this would not happen. Skill, coordination, and cross-training are key. In order for a radical speed to happen, each person must handle a wide array of build tasks. Incentives must be created for cooperation, such as everyone helping the slowest guy so that we function as a high performing team, not a team with a few star players. Because few star players are a bad design - more could be attained when each team member is strong, as this is a team sport.

			Metrics:
			#746 task burndown, with measured time per task. Every time a person performs this task, we take data. To do this, we document by pictures: start and end. Thus, we define the start and end for 746 tasks, and even subtasks. Each person has a stat graph where every task is measured for a burndown: from high time, asymptote to a low value. We may also observe and look out for any U-shape boomeranging - a person gets slower at a task. If that is the case, this is addressed in pay scale. A person must maintain their level of skill, and data is collected passively. For example, in the RLF, automated video capture means that we can capture video from any bay or work station. The facility is heavy in camera bandwidth requirement - but this means that data can be collected passively at any time. Each person contributes to rigorous data collection, which is actually as simple as picture at beginning + picture at end - which documents build time. We must perfect this by clear definition of task breakdown and cut-in + cut-out points. Data collection cannot become a burden. Further, learning and quality control can be added: pictures of unique results etc that serve as learning material.

	=Dashboard=		=Dashboard=

Marcin: /* Overview */

2024-08-02T05:45:36Z

Overview

← Older revision		Revision as of 05:45, 2 August 2024
Line 1:		Line 1:
	=Overview=		=Overview=

	The proof of a 24 person operation building a house in 5 days is unprecedented - and would constitute the first company in the world that builds residential housing on this radical timescale. Thus, this is the experiment worth proving. The key is 24 people working together: unless a high level of coordination exists regarding all the tasks, this would not happen. Skill, coordination, and cross-training are key. In order for a radical speed to happen, each person must handle a wide array of build tasks.		The proof of a 24 person operation building a house in 5 days is unprecedented - and would constitute the first company in the world that builds residential housing on this radical timescale. Thus, this is the experiment worth proving. The key is 24 people working together: unless a high level of coordination exists regarding all the tasks, this would not happen. Skill, coordination, and cross-training are key. In order for a radical speed to happen, each person must handle a wide array of build tasks. Incentives must be created for cooperation, such as everyone helping the slowest guy so that we function as a high performing team, not a team with a few star players. Because few star players are a bad design - more could be attained when each team member is strong, as this is a team sport.


	=Dashboard=		=Dashboard=

Marcin at 05:44, 2 August 2024

2024-08-02T05:44:04Z

← Older revision		Revision as of 05:44, 2 August 2024
Line 1:		Line 1:
			=Overview=

			The proof of a 24 person operation building a house in 5 days is unprecedented - and would constitute the first company in the world that builds residential housing on this radical timescale. Thus, this is the experiment worth proving. The key is 24 people working together: unless a high level of coordination exists regarding all the tasks, this would not happen. Skill, coordination, and cross-training are key. In order for a radical speed to happen, each person must handle a wide array of build tasks.


	=Dashboard=		=Dashboard=
	*For OSE learning on global intelligence increase - dashboard on all the elements of [[Candidate Assessment]]. This is for accepted individuals only who are on the Genius Track.		*For OSE learning on global intelligence increase - dashboard on all the elements of [[Candidate Assessment]]. This is for accepted individuals only who are on the Genius Track.
	*Builder Track - burndown of 743 tasks. Translated to pay scale. Burndown of 12 Modules - translated to pay scale.		*Builder Track - burndown of 743 tasks. Translated to pay scale. Burndown of 12 Modules - translated to pay scale.
	*Data Collection transparency - 743 and 12 related to multiple data points, tracking time per over 4 years. Semiannual bonus for tracking time decrease per task - extracting that from their data collection.		*Data Collection transparency - 743 and 12 related to multiple data points, tracking time per over 4 years. Semiannual bonus for tracking time decrease per task - extracting that from their data collection.

Marcin: Created page with "=Dashboard= *For OSE learning on global intelligence increase - dashboard on all the elements of Candidate Assessment. This is for accepted individuals only who are on the..."

2024-04-24T08:11:46Z

Created page with "=Dashboard= *For OSE learning on global intelligence increase - dashboard on all the elements of Candidate Assessment. This is for accepted individuals only who are on the..."

New page

=Dashboard=
*For OSE learning on global intelligence increase - dashboard on all the elements of [[Candidate Assessment]]. This is for accepted individuals only who are on the Genius Track.
*Builder Track - burndown of 743 tasks. Translated to pay scale. Burndown of 12 Modules - translated to pay scale.
*Data Collection transparency - 743 and 12 related to multiple data points, tracking time per over 4 years. Semiannual bonus for tracking time decrease per task - extracting that from their data collection.