shoptechs:leads
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| shoptechs:leads [2023/09/12 02:49] – [Duties] smartin015 | shoptechs:leads [2024/10/17 19:39] (current) – [Tech Onboarding] smartin015 | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| The Leads are individuals who have a great amount of skill and experience in at least two major areas of Protohaven and have also demonstrated excellence in teaching, leadership skills, and a commitment to the success of Protohaven (and the Shop Tech program, specifically). | The Leads are individuals who have a great amount of skill and experience in at least two major areas of Protohaven and have also demonstrated excellence in teaching, leadership skills, and a commitment to the success of Protohaven (and the Shop Tech program, specifically). | ||
| - | Leads work directly | + | Leads work closely |
| - | + | ||
| - | * Serve as a mentor to a team of approx 9 techs | + | |
| - | * Get their team trained/ | + | |
| - | * On-board new techs (as needed) | + | |
| - | * Identify & assign shop projects for their team | + | |
| - | * Plan a larger shop project or community project for their team (individually or across teams) to complete | + | |
| + | * Handling/ | ||
| + | * Being a point of resolution for disputes and other things techs don't feel comfortable addressing | ||
| + | * Being available (in shop or discord) to facilitate discussion and decision making | ||
| + | * Mentoring techs & teaching them maintenance/ | ||
| + | * Ensuring shifts are well-staffed and that the shop runs with oversight | ||
| + | * Convening the techs for fun events & orientations | ||
| + | * Getting techs involved in larger, well-defined projects | ||
| + | * Proactively fill gaps in knowledge of techs and other leads | ||
| ===== Duties ===== | ===== Duties ===== | ||
| Line 20: | Line 22: | ||
| - Determine the order of importance of this list. | - Determine the order of importance of this list. | ||
| - | - Unblock techs on the tasks they need to perform to keep tools running smoothly. This includes education. | + | - Unblock techs on the tasks they need to perform to keep tools running smoothly. This includes education |
| - | - Review the Asana tool reports | + | - Review the Asana tool reports, closing |
| - | - ... | + | - Offboard techs that exit the program |
| + | ===== Tech Onboarding ===== | ||
| - | ===== Improvements | + | When a tech comes aboard, they need the following: |
| + | |||
| + | * Shop tech status & an account in NeonOne | ||
| + | * Addition to the " | ||
| + | * Grant August lock access (via August app) | ||
| + | * Discord membership with the #Members and #Techs roles | ||
| + | * Access to the workshop@protohaven.org password | ||
| + | * Access to the relevant Asana projects (Shop & Maintenance Tasks, Purchase Requests) via addition to the Shop team in Asana. | ||
| + | * Filled out profile info for the [[https:// | ||
| + | |||
| + | ===== Tech Offboarding | ||
| + | |||
| + | Periodically audit the above systems to ensure techs that have exited the program no longer have permissions. | ||
| + | |||
| + | * Remove or retire the tech from each of the places above. | ||
| - | * Modify tool report process so it doesn' | ||
| ===== New Lead Onboarding ===== | ===== New Lead Onboarding ===== | ||
| - | TODO | + | When a new lead comes onboard: |
| + | |||
| + | * Admin status in Asana | ||
| + | * A name@protohaven.org user (via admin.google.com) | ||
| + | * Membership in the Protohaven organization in Bitwarden, in the Tech Lead group. | ||
| + | * Granted the TechLeads role in Discord (i.e. access to #tech-leads Discord channel) | ||
shoptechs/leads.1694486951.txt.gz · Last modified: by smartin015
