# Ohad Perry's Manager Readme

**VP R&D at Bllink**

# Motivation for this document

Hi R&D member. Wrote this document to help in onboarding to bllink. Here, you will find more about me, my expectations, and how you can excel in your role.  

# My role

My role is to lead the R&D and my KPIs are team speed, production stability, planning, and execution of new features. 

What do I value most?

I’m always thinking about what processes can we improve (both organizational and thinking processes), and how to make sure all members are as autonomous as possible. 

# My Expectations

Feature ownership is number one. This means that you care about the task you're working on, and you understand that it’s your sole responsibility to push it forward through all of the steps we’ve defined. I also expect you to ask your teammates and me questions. Use [this](https://jvns.ca/blog/good-questions/) guide to ask the right questions.

Make sure you get everything you need in order to execute: help with figuring out requirements, design, and getting it all the way to production. Set time in advance with people (calendar), ask for clarifications and decisions, etc.

Take a look at the error logs and clean them up from time to time. 

Monitor production after each deploy to make sure you didn’t break anything. 

Be available on slack during your working hours (depending on your time zone). It’s important especially when we have critical bugs in production.

Use [this](https://docs.google.com/document/d/1uTLdNRzokcck_w5p1xlSt7OdUZVsx_CrISY0L_2yb8w/edit) document for more details.

# 1:1s

Please come prepared, these meetings are mostly your time to discuss whatever you want. Possible topics:

- your role and how you feel in it 
- your goals and how you see yourself fulfil them 
- improving processes within the team 
-  R&D in general 
- infrastructure suggestions 
- new business processes 
- company's long term goals

Usually, I’ll split 1:1’s and start with your time and then I’ll the other half to ask you questions about specific tasks you are working on or the last time you broke production and how can we make sure it will happen less and less. 

# Personality quirks

- Feature questions - pls ask inside the ticket. It helps with context and for me to answer faster and not to lose the thread in slack (I get email notifications)
- get push notifications on meetings and approve or decline them. if you approved, I expect you to show up on time and be ready. 
- I think duplicate code is a productivity killer. Please avoid it. 

# Where to focus on your first 90 days?

Glad you asked. All beginnings are hard. You have a complicated code base and a complicated architecture to get into. I’ve created an onboarding process but part of it is solely up to you. You should:

1. Browse our product and ask (a lot of) questions during our 1:1’s
2. Browse our codebase and ask (a lot of) questions during our 1:1’s

You will be able to know if you are on the right track and if you’ll feel more at home when discussing new features. You’ll need help from other developers less and less during the first 90 days. Other developers, and I, won’t surprise you with a new use case you didn’t know. 

# How To Excel in your role

According to your role in the company, you can use [this](https://docs.google.com/spreadsheets/u/0/d/1CPIFwR_iSCQeq8aEebZ0XsBK9IKhah-l_HeDZuavik4/htmlview?fbclid=IwAR3pxVrKea3t8Lg4KixutCNXhjN6xRlk8U-ItDB1r2WMGVSqfCVDkp75HzE#) guide to analyze yourself. If you want feedback from me regarding each and every item, don’t be afraid of asking me.