Child pages (Children Display) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Initial outline combining all suggestions received so far as of Sept 2024
Ready to start fleshing out
On-boarding Process - consolidated notes
Task | Who is responsible - Team or Program | Status |
---|---|---|
Onboarding form? checklist? - some kind of intake form or page for the new person
| ||
Set up Individual Training Plan | ||
Define which PPT the person should be given - separate one for each “Team” with some that is consistent across the Project
| ||
Use Job description and WBS area to define what the person will be doing so both they and their supervisor understand what is expected | ||
Training Schedule - what they are doing to train each week
| ||
Communicate Hire to the Team
|
6 Week Review 1 on 1 - Completing Orientation Period
Task | Who is responsible - Team or Program | Status |
---|---|---|
Review of training - How did we do - what questions do you still have - any suggestions
| ||
ACCESS Manager should check in with staff members supervisor of record
| ||
Address open questions or challenges they are facing. | ||
ACCESS “Mid-term” / trivia quiz | ||
Are they comfortable with the volume of work/meetings they’ve been assigned? |
InBoarding - how can we keep people?
Task | Who is responsible - Team or Program | Status |
---|---|---|
Make sure meetings have stored agendas that are adhered to - make sure when you hold a meeting that it needs to be a meeting - don’t waste people’s time | ||
Make sure all work can be tied back to the PEP - The goal is to have everyone in the team familiar with high-level project activities. | ||
All project members participate in program-level activities to foster career development. | ||
Stay in regular touch via Slack | ||
Have regular team meetings and cross team meetings | ||
Should we create a “human API” where for each project in the program we could identify a point of contact (POC) or subject matter expert(SME) for each track. Having pre-identified POCs for other tracks would help in our work. | ||
Creating and participating in Working Groups is a heavy lift. The EC should empower staff to push decision-making deeper into the levels of the program. | ||
New people find it difficult to speak up during this all hands meetings because they are actively learning while people are sharing their status. Should we have “New Employee parallel sessions” at meetings? | ||
Have the EC provide more coordination for the overall program. More transparency would be beneficial | ||
Summary email after meetings instead of sharing minutes notes | ||
Perhaps a “what’s everyone working on” once a month? | ||
There is some confusion as to who our users are. In Support, our users are the ACCESS users. (separate by Internal Users/Stakeholders and External Stakeholders) | ||
Sharing feedback from our user community would be helpful as well. | ||
Mentorship program, particularly for bridging the gap between a team member and the broader organization | ||
Another potential structural improvement (especially for the Operations’ concierge role) would be having an “embed” (~1-2 weeks or total 40 working hours) within each ACCESS Track to help members network across teams and familiarize with various workflows. | ||
Some of these issues can be identified earlier by performing |
Offboarding - when someone leaves the project
Task | Who is responsible - Team or Program | Status |
---|---|---|
Exit Checklist - what goes on it?
| ||
Exit interview - what do we ask?
| ||