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)
How to evolve GoInvo
So you’ve got a grand idea for Invo?
Here are a few practical steps to make it happen!
Step 1: Prep
- Get your ideas together. It can help to put them into a list or a visual. What's the idea? Why is it important?
Make sure that the idea fits into our company's strategy.
- If the idea is for the website, make sure that the idea fits in to the website structure - check out the Site Map in figma
Step 2: Techtalk
- 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.
Step 3: Execute
Set aside time in Staff Plan!
- Most projects never get completed because other projects pop up, and the internal project isn't handed off effectively.
- If you start falling behind schedule and see that you'll run out of time, figure out who can carry on the project without you, so it doesn't fall between the cracks.
Track progress like a hawk
- Use the Github project or Asana to keep track of tasks to be completed and deadlines.
- A GitHub Project can help you to manage tasks and clearly state a mission and timeline. Here's an example of how you can set it up (see image below). In the menu, you can copy this template to outline the mission and timeline.
Keep the team up to date.
- If the project lasts for more than 2 weeks, give short updates every other week during techtalk time.
Connect with engineering early
- If you aren't the one building the project, make sure to coordinate with the engineer. Show designs and discuss engineering needs. This will help issues come up early so that the project can stay on schedule!
Step 3: Wrap up
- 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.
- 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