What type of agreement needs to be in place regarding the sharing of information among users?
The premise of Learning Labels Team app is to allow team members to: signal and pool their skill sets (represented in a list form), share progress in queued and completed work (Skills Emblem), and provide links to their actual work (links to the learning labels).
The goal is to optimize the team performance by aligning members strengths and weaknesses as well as identifying soft and thinking skills needed to build the collective intelligence of the team.
Some features (defining characteristics):
- Peers suggest learning tasks among each other. Of course, the recipient gets to choose whether to accept and ultimately do the task.
- Peers allow access to their learning and progress in the form of Skills Emblems.
- Teachers (practitioners) might be part of the team. Their tasks (represented as learning labels) are indexed and accessible to the team.
- Openness and trust are meant to strengthen the team
There are ways the app is designed to limit sharing, particularly where there is significant individual competition (getting grades, promotions, etc.):
- Actual achievements are veiled. For example, scores and grades do not appear directly on a Skills Emblem or in the task list that appears in the app. They can be inferred based on the trajectory of tasks completed by a learner, however. Performance determines how a learner moves through a series of tasks. The system and/or practitioner suggests what a learner does next after completing a task: someone getting in the 90 percentile does one task and someone in the 80 percentile does a different task.
- There is grading and quizzes built into the system – pass / fail, pass / progress / fail, and percentiles. A practitioner sets what is required to complete a task.
- Practitioners also create the series by choosing up to ten different scenarios.
- Teams are based on a time constraint, which should be less than a year. By limiting sharing to a semester, onboarding period, or project, learners are more willing to share among each other.
- There is a team size constraint. Team must be no larger than 50 members and the size of the team cannot change after being created.
- Users set their permissions on a team-by-team basis.
- Users can leave the team and remove all connections at any time.
- Joining a team is a two-step process. First, an inviter must establish a connection with users; then, send them an invite to join the team.
Like Learning Labels Search, Learning Labels Team app supports the adoption of the learning labels system by an organization – a school, college, university, or company. Effective use of the app requires a healthy number of learning labels in the system.
For example, to adopt learning labels, a business school might require all professors to create a Skill Syllabus and learning labels for their courses. Generally, learning labels represent tasks and experiences so could be anywhere from 10 to 40 per course. The business school then lets students form cohorts and use the team app through the semester. They access and allocate the resources represented as learning labels. The value proposition is to manage and track the development of skills and use skills to optimize a team’s performance.