Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Overview

As WARG’s internship program expands and matures, there’s much to pass down from manager to manager about general advice, management, and how to interact with co-op students. Also, ignore the switch to 2nd person tense (lol).

As a lead in WARG, you demonstrated your ability to manage people and projects effectively. Being a co-op manager is an excellent way to hone mentorship skills. Many managers see the same key issues - this doc aims to address this.

General Advice

  • Plan. Plan. Plan.

    • When we first hired interns, Sahil and Shrinjay said “yo, we need people to build stuff, and co-ops are a good resource”. We had the right mentality, but we failed in execution- it lied in not specifying the “stuff” we wanted them to build. To address this, we insisted that every co-op henceforth had a dedicated project to work on, modelling ourselves on internship programs at actual companies. This was further iterated on with the requirement to make a startup guide when hiring: Co-op Admin Process .

    • When planning, remember that your co-op is expected to put in ~40 hours of work per week. In the context of a design team, this is a massive amount of people-hours relative to the rest of your team. Even the most dedicated leads punch a max of 20 hours a week to the team. Thus, a lot of new managers tend to underestimate the amount of work that a co-op can achieve. Be aware of this and plan accordingly when making timelines - don’t hesitate to be a touch on the aggressive side and scale back if needed since your intuition will likely push you to give more time than is needed as it is ‘calibrated’ to those of a regular member.

  • Find people who can mentor them when you’re not around.

    • You are busy. You are a lead, you are their mentor, and you have other stuff to do. Daily 1:1’s are a requirement for co-ops, but it doesn’t mean you’re the only mentor to them. Use the ‘see one, do one, teach one’ model to build up your team member’s mentorship ability and alleviate your workload - win, win. You’ll know you’ve succeded when pings for “how do I do this” for certain matters stop flying your way and go to someone else 😄

    • From Anthony Luo , creating a co-op thread is excellent in giving a self-contained space for specific direction in a public-private manner.

  • Megan Spee ‘s advice for first time co op supervisors: quick tips and tricks to help you not choke on easy management decisions later (thumbs up)

    • Define what days they have off (civic holidays?) and if reading week is off. Also define policy for taking days off (sick days, vacation, whatever. Can just be a ‘ask me, case by case basis' type of thing but specify that).

    • Define purchase protocols

    • Clearly outline expectations, if you can't support them enough for them to stick to these expectations, get help from other leads or re-define expectations

    • Be critical enough of their work that they learn but not critical enough that they get demotivated

      • Big point: they should be learning things whenever possible

    • Get them on confluence (or whatever documentation means you choose) early enough that the documentation is consistent through whole term

    • Safety training is very important get all those certificates + ASK FOR PDFs

  • No labels