# David Cohen's Manager Readme **VP R&D at Panorays** # 🧭 **Why This Document Exists** **One Sentence:** _Set clear expectations upfront._ **Expanded:** This document provides a brief overview of my approach to work and leadership. If you're new to working with me, it’ll help you understand my mindset and values faster. If we’ve worked together before, it’s a reminder of what I consistently prioritize. Ultimately, it’s here to help us collaborate better, reduce ambiguity, and minimize unnecessary management overhead. Of course, we’ll build stronger mutual understanding over time. # # 👤 **My Role: VP of R&D at Panorays** Here’s how I measure my success and contribution: - **Execution Ownership:** I ensure we deliver what the business needs—with a “default to yes” mindset. We say yes first, and then figure out how to make it work. - **Clarity in Tradeoffs:** I surface and communicate tradeoffs clearly to relevant stakeholders. - **Process Leadership:** I build what’s missing and improve what’s already there—constantly. - **Org Scaling:** I’m focused on growing an R&D organization that leads technologically and attracts top-tier talent. - **Leadership Development:** I mentor managers to lead independently and individuals to grow in their careers. - **Team Design & Capacity:** I make sure we have the right skills and people in place to execute effectively. - **SLA & Quality:** We meet our commitments—uptime, reliability, and product quality are critical. - **Context-Setting:** I bridge business needs and personal development. When people know why they do what they do, they thrive. - **Shared Ownership:** You work for Panorays, not for me. We’re aligned on goals and moving forward together. - **Mutual Accountability:** I’ll support you, and I’ll own my own growth. I am open to and seeking feedback. When I miss something, I expect you to tell me. # # 🧱 **What I Value Most** ## 💡 _“End-to-End Ownership” _ Full accountability. Owning a mission from inception through delivery and support. That’s how we scale, lead, and build trust. **What It Means for You** - **Own Your Work Fully:** Know the big picture and the technical detail. Suggest new tech when needed. Ask for mentorship if you need help “owning.” - **Broaden Your Expertise:** Aim to be strong across several domains. You can choose to go deep in some or rely on experts—just know your responsibilities. - **Team-Based Ownership:** Your team owns domains. Help your team deliver. Collaborate. Share ownership. - **Ownership ≠ Alone:** Don’t try to do everything yourself. If someone else can do it better, delegate, involve, and collaborate. - **Always Accountable:** Your code, your system, your feature—you’re responsible for it in production. Build with quality and scalability in mind. ## ## **📈 Scaling Through Autonomy** We scale by building autonomous individuals and strong team leads. **My Default Mode: High Autonomy** - I trust you. You were hired because you’re capable. - I assume you’ll manage your own work unless you say otherwise. - If something isn’t clear—ask your manager or me. - Update progress frequently. If everyone does it, we reduce overhead significantly. - I work closely with your manager, not instead of them—but I will work with you directly when: If you’re unsure why I’m involved—just ask. ## ## 🚀 **Seek to Improve, Always** Mistakes are fine. Repeating them isn't. Growth is expected. **What This Means for You** - Continuously assess how you can grow. - Ask for support, tools, or mentorship to level up. - Reflect monthly. Track your progress—speed, quality, and complexity. - Welcome feedback. It’s a gift. - Postmortem your mistakes. Learn from them. - Avoid repeating the same mistake. There will be plenty of new ones to make. # # 😟 **What Will Disappoint Me** This isn’t parental. But if you know what’s considered “excellent,” you should also know what’s unacceptable. - **Ignoring Feedback:** Feedback is there to improve you. Use it or explain why you won’t. - **Coming with Problems, Not Solutions:**  Own your domain. Come with ideas, not just issues. - **Disrespecting Others:**  We work together—respect is non-negotiable. - **Poor Communication:** Update, involve the right people, and be respectful of others’ time. Be concise and helpful. ## # 🎭 **Some Personal Quirks** - I’m all-in. Passion isn’t anger. - I may hold unrealistic expectations rooted in nostalgia from my developer days. Be patient. - I repeat myself—usually to reinforce feedback. Sorry in advance. - My written requests (Slack/email) mean action. - I value time. Please respect mine and others'. - I expect meeting agendas and clear communication. - I’m logic-driven. You can ask me anything. I’ll try to help. - If you’re unsure what I’m thinking—ask. You’re an adult. I’ll treat you like one. ## # 📢 **Expectations** **Transparency** - I’ll be open with you about the company, team, and strategy—whenever I can. - I’ll never lie to you. You can ask anything. If I can’t answer, I’ll say so. **Working Hours** - Be aligned with your team’s working hours (generally between 8–10 AM start times). - Work = productive contribution. Socializing is welcome, but focus on delivering. - I support hybrid work. Balance what’s best done in the office vs. remotely. - Over-communicate when remote. Sync with peers and your manager. - I expect availability when something urgent arises—even outside of regular hours. ## # 📅 **How to Work With Me** - **My calendar is open.** Book time when needed. - **Slack for non-urgent, face-to-face for urgent.** - **I can context-switch fast—it’s my job. Don’t assume I’m too busy.** - **Very few things are more important to me than talking with you—if you need me, I’m here.** ## # 📡 **Communication Channels** - **Face-to-face:** Be polite—check if I’m available before jumping in. - **Email:** Expected to check and reply daily. - **Slack:** Direct mentions = response within a few hours. Other messages = async. - **WhatsApp (personal):** Use for post-hours or urgent matters. Blue checkmark = I’ve seen it. - **Phone Call:** For emergencies. I’ll respond ASAP. - On all - I am usually replying in near-realtime. ## # 🕒 **Owning Your Time** - Plan. Take a step back from the day-to-day every two weeks. - You own your time—not me, not your TL. If you need help, ask. - Show me your high-level plan so I can help with alignment. ## # 📋 **Execution Rituals** **Daily:** - Update your personal dashboard (Jira). - Attend the daily meeting and share information. **Every 2 Weeks (Sprint Planning):** - Understand all your user stories. - Break them into tasks. - Estimate effort. - Align with your collaborators. - Finalize planning with your team leader. - Keep everything updated in Jira.