This section provides light pointers for our internal processes. If you have a guide to add, talk to Sharon.
How to Invo
Reaching Invo-lightenment Checklist
- Made a Friday lunch
- Been to HXR conference
- Printed BIG
- Gave a tech talk
- Published on the website
- Ran my own project
- Mentored another Invo-ite
- Brought in a client
- Brought in a new hire
How to Hire
- Initial communication + resume and portfolio
- Phone conversation with Juhan
- Studio visit + presentation
- Vote on what kind of position if any to offer
- Print resume for all interviewers
- Send out Interview Scorecard to Invo-ites if necessary
- Give visitor a tour of the studio
- Offer tea/coffee
- Help set up in conference room
- Offer Invo apparel and cards to visitor
How to Onboard
Onboarding is driven by a designated Sherpa. As a studio, we are all accountable to make sure each new hire has a Sherpa to help them through their first few weeks. The first day experience is fully impacted by how the Sherpa looks out for new hire, so we take this very seriously. All of the following should be done by the Sherpa.
- Ask “do you have any questions?” X 100
- Be visibly available
- Help newbie manage their time
- If you provide reading for the newbie, follow up and ask about it
- Reach out to see if they have any questions and provide expectations for Day 1
- Set up email @goinvo.com (Juhan, Eric)
- Create accounts for Staffplan, Slack, Dropbox, Github, Basecamp (Juhan, Eric)
- Purchase any additional software licenses: Sketch, Adobe Creative Cloud (Juhan, Eric)
- Find out which project they will be on and who they should talk to on day one
- Figure out their desk options
Prepare care kit and place on desk
- Print First Day checklist
- “Sugar Kills” t-shirt and stickers
- Provide a computer and necessary devices
- Pen, pencil, notepad
- Handwritten note on them joining
- Arrive to the studio before newbie arrives
- Help newbie get set up with devices at their desk while following security protocol
- Help newbie get various accounts set up while following security protocol
- Discuss plan for the day over coffee/tea (Set up digitally, Read & reflect, Learn about your project, Slippers)
- Setup tax(W9/IRS ) and healthcare paperwork(if applicable) (Juhan)
- Check that they are set up on Slack, Github, Dropbox
- Check if they need any design or engineering software installed (see Resources for list)
- Newbie should be reading through parts of the Playbook and setting up security on their devices
- IF they have a project, connect them to the lead who should then assign reading
- IF they don’t have a project, direct them to educational resources if they have time
- Order slippers
- Set up Charlie Card or parking permit if applicable (Jen, Eric)
- Provide studio keys, set up security code (Juhan)
- New staff’s Invo photo (by Juhan), follow up to make sure this happens
- New staff should write a draft bio to be used on the website. Share bio with Juhan to iterate and approve to then post on the website.
- Check in on their mental, social, emotional well-being
- Arrange goal review session with Juhan to track short and long term goals at Invo
- Ask if they have any residual questions/concerns
- Reading material followup (if suggested)
Evolving our Site
So you’ve got a grand idea for the website or playbook? Here are a few practical steps (from the project management perspective) to make the change.
Note: if it’s a minor change like adding a new hire’s bio, fixing a typo, switching out an image - just discuss it in Slack and do it.
- Make a Project in GitHub that lists why the change is important and scopes out basic steps to completion and deadlines. To make a project, open the goinvo.com or playbook repo → navigate to the Projects tab → click New Project (see image above).
- A GitHub Project can help you to manage tasks and clearly state a mission and timeline. Here is an example of how you can set it up (see image above). In the menu, you can copy this template to outline the mission and timeline.
- Mark your name on weekly Techtalk calendar so that you can get the group’s perspective
- Give a short presentation to explain your idea (length 5 - 10 min can depend on how big of a change it would be).
- Give everyone a chance to discuss then take a vote (Ye or Ne).
- If the consensus is Yes, determine who will be a part of the project. Who will lead Engineering, Design, Signoff.
- Use the Github project to keep track of tasks to be completed and deadlines.
- If the project lasts for more than 2 weeks, give short updates every other week during techtalk time.
- Give a talk at the end of the project as well. The website represents all of us, so it’s important that everyone is included.
Suggestions for success:
- Take a “design” approach → understand your users, brainstorm, test ideas and screens.
- Read through this doc Design Principles Invo Site4.0 which holds research about potential client users, potential hire users, and competitor’s sites.
- Design mobile first!
- Rip off the bandaid when it comes to getting feedback. Show your work often!
- Validate your design (via feedback and testing) before valuable time is spent on engineering