LC: Staff Roster

Please check out this information before this wiki.

• Airtable
• [Something about positions/flowchart]

This should be a one-stop shop for LCs and FTEs to see the current status of any TW staff member. It serves as a way to speed up the scheduling, PDM and training processes, since all records should be maintained and kept up to date at all times.

To this end, there are several categories of fields for each record, as follows.

There are a few categories of fields, each with a different objective.

General Staff Information - Includes information like name, DID, graduation date, status.

Position Status - Information on training status in each space. Each field here has options for every possible training level in that space or role.

Machine Status - Information on training status on each machine. Each field here has options for every possible training level on that machine, so it can be different per space or class of machine.

Record Information - Last edit and who edited.

Specific information can be added as a field, however should be hidden from general views. This would include fields such as “AFL Goal” or if there are any fields related to specific training tracks in each space.

In order to maintain good information in the roster:

• Do NOT add new options to single-select fields that have the same meaning but a different title (check to make sure you’re not adding redundant dropdown options)
• Do NOT let there be any “blank” fields, except for any notes or text box fields

In order to maintain good organization in the roster:

• Keep views organized by including the space/position in the title (for specific spaces, “AFL - Objet500 Connex3” is an example of a good name)
• Keep general views near the top of the views list
• Do NOT change settings of ANY view, unless a new field is added to the sheet and needs to be updated in view configurations
• If a new set of information is desired, CREATE A NEW VIEW instead of modifying something that someone else may be using

Grid views are good for seeing and sorting many staff members at once.

Kanban views are good for seeing proficiency on an advanced machine or training track. In this example, it’s easy to see who are the current users of the Connex, and who we have to train in order to make sure there is no gap in proficiency.

• Whenever any staff member has any updated information (graduation date, status, notes, etc.)
• Whenever any staff member shows interest in training in your space, or trains to a new skill level in your space
• Whenever any staff members learns a new machine or skill in the fields for those skills

This begins to devolve into space-specific workflows, but the roster is a great way to keep track of who is interested in training on certain high-skill level machines, such as the Connex, Nanoscribe or Kern.

Usage of kanban views for each of these machines helps keep track of who is trained at each level.