# Hanokh Aloni's Manager Readme

**RD Manager at NGSOFT**

# Motivation for this Document

I wrote this document to give you clarity on how I operate as a manager and what you can expect from me. My goal is to create a shared understanding of our working relationship, help you succeed in your role, and align our efforts towards shared objectives.

# My Role

As a software development manager and R&D leader, I’m measured by the success of our projects, team growth, and the delivery of high-quality solutions to clients. Key performance indicators (KPIs) include on-time project delivery, client satisfaction, and team efficiency.

To help you grow, I’ll:

- Provide the context and tools needed to excel in your role.

- Facilitate a safe environment for experimentation and learning from mistakes.

- Offer feedback that is actionable and geared toward your professional development.

- Remove roadblocks that hinder your performance.

# What Do I Value Most?

- Core values: Autonomy, Mastery and porpuse. I aim to give teams the freedom to solve problems their way (autonomy), opportunities to grow and improve their skills (mastery), and a clear understanding of how their work impacts the bigger picture (purpose).

- Mistakes are Opportunities: Mistakes will happen. Let’s focus on understanding what went wrong and how we can improve rather than assigning blame. It's better to ask for forgiveness than to ask for permission. Also don’t be afraid to propose bold ideas. I’ll support you.

- Ownership: Take charge of your work. Make sure you understand your impact and take ownership of the tasks.

- Clarity and Communication: If something is unclear, ask. If there’s a problem, let’s talk. Clear communication avoids unnecessary stress.

- Conflict Resolution: Address issues early. If conflicts arise, I encourage direct, respectful conversations. If needed, I’ll mediate to find a solution.

- Clean Code and Sustainable Practices: Strive for simplicity, maintainability, and long-term value in your work. Keep everything clean. Follow the boy-scout rule and write unit test.  

# Weaknesses:

- I tend to get excited about new ideas and might occasionally overextend. Help me prioritize by pointing out resource constraints or competing priorities.

- I’m detail-oriented, which can sometimes make me over-involved. If you feel I’m micromanaging, let me know, and I’ll adjust.

- Sometime I have an aggressive tone. I am working on it. 

# My Expectations

- Mistakes: If something goes wrong, tell me as soon as you can. Come with a clear understanding of the issue and possible solutions. Please do think and implement your safeguards! If it can't be unit-tested, do an integration test, and it that can't be done create a manual test. I hold an extensive library of checklists to avoid mistakes we already did. Please use them and learn from them.

- Definition of Done: Done means the task meets requirements, has been tested, and aligns with our coding and quality standards.

- Availability: Core work hours are  9:00 AM to 5:00 PM. I’m available via chat during these hours and for emergencies outside them. I expect you to be available as well.

- Setting Time with Me: Schedule time with me through our shared calendar. I’m flexible, but it’s best to book in advance for anything requiring focus.

# 1:1s

- Frequency: I hold regular 1:1s, typically weekly or biweekly, depending on team size and workload.

- Focus: These are your sessions to discuss anything—from career growth to current challenges. Bring your agenda; I’ll bring mine if there are organizational updates or feedback to share.

- Ownership: You lead the conversation, but I’ll guide when necessary.

# Personality Quirks

- Excites Me: Clean, well-documented code and clear, organized project documentation.

- Frustrates Me: Avoidable inefficiencies, such as unclear communication or missed deadlines without notice.

- Quick Reactions: I’m passionate about structured approaches. Rapid, unstructured shifts in direction may catch me off guard; a clear rationale helps.

# Where to Focus in Your First 90 Days

## First 30 Days:

- Understand the team structure, ongoing projects, and tools we use (e.g., JIRA, Grafana, etc.).

- Get familiar with our coding standards and workflows.

- Schedule 1:1s with teammates to build relationships.

## Next 30 Days:

- Start contributing to smaller tasks or projects.

- Identify at least one area where you can suggest improvements.

## Final 30 Days:

- Take full ownership of at least one deliverable.

- Present your observations and suggestions for team or process improvement.

By the end of your first 90 days, you should feel confident about your role and responsibilities and have a clear roadmap for your next steps.