<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jonah Greenberger on Medium]]></title>
        <description><![CDATA[Stories by Jonah Greenberger on Medium]]></description>
        <link>https://medium.com/@jonahgreenberger?source=rss-73733e1b30ad------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1iYoWx7Sd8sD-dxFq9KYug.jpeg</url>
            <title>Stories by Jonah Greenberger on Medium</title>
            <link>https://medium.com/@jonahgreenberger?source=rss-73733e1b30ad------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 15 Nov 2026 09:03:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jonahgreenberger/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Getting an advanced degree]]></title>
            <link>https://jonahgreenberger.medium.com/masters-as-a-stepping-stone-c36270f24752?source=rss-73733e1b30ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/c36270f24752</guid>
            <dc:creator><![CDATA[Jonah Greenberger]]></dc:creator>
            <pubDate>Wed, 05 May 2021 01:40:29 GMT</pubDate>
            <atom:updated>2021-05-05T02:01:01.677Z</atom:updated>
            <content:encoded><![CDATA[<p>Many times we’ll hire a great employee and they’ve received advice their whole life to work first, then get a masters once you have that experience and perspective, and then go back into the work force and you’ll have a “leg up.” The logic behind getting real world work experience is dead on. But the part of this logic I’d challenge in today’s world (and especially in a tech focused job) is that getting a masters helps you learn faster than just staying at a good job and learning there. In fact, I would argue many parts of college could likely be learned faster and better on the job. As CEO of Bright, most of what I’ve learned that helps me on a day to day basis I’ve learned by doing. The calculus classes, chemistry, and definitely fluid dynamics etc I rarely ever use. And if needed I can find an expert’s blog, youtube channel, etc (and perhaps even message them) to give a much faster answer than if I were to dust out my old books and refresh myself.</p><p>Where this is not true is in highly specialized fields (thermodynamics, gene editing, etc). Then advanced study is critical and mostly because the knowledge is not readily available or taught online. Instead it’s in the minds of other experts and knowledge transfer is more person to person. But in most other fields today, knowledge is so readily available on the internet or by connecting to someone else over the internet that a “face to face” school is far less useful than it used to be.</p><p>This paradigm shift happened somewhere between our parents generation and ours, and is likely highly correlated to the rise of computers and the internet. This phenomenon has had two affects:</p><ul><li>knowledge is far more accessible and comprehensive than it used to be</li><li>the best practices our parents know and worked well for them is highly outdated.</li></ul><p>If you’re thinking you may need a masters because you’ll look better, it’s likely you’ll get a higher paying job, or folks will trust you more, it may be worth examining if this advice still applies in your situation. If you’re going to advanced study to become a world expert in that field and advance it, you’re likely on a good path.</p><p>Hope this is helpful and good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c36270f24752" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to end convos if dragging on…]]></title>
            <link>https://jonahgreenberger.medium.com/how-to-end-convos-if-dragging-on-fabbbbad2f11?source=rss-73733e1b30ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/fabbbbad2f11</guid>
            <dc:creator><![CDATA[Jonah Greenberger]]></dc:creator>
            <pubDate>Sat, 13 Feb 2021 20:09:59 GMT</pubDate>
            <atom:updated>2021-06-01T16:14:05.738Z</atom:updated>
            <content:encoded><![CDATA[<p>(How to get off calls that go on and on)</p><p>Tips on how to end calls / meetings:</p><p><strong>The ‘heads up strategy’</strong></p><ul><li>If the convo is trailing, mention “I have to run in 5 minutes but to answer your specific question…” or “Hey I’ve got to prepare for my next call — I’m happy to meet again if needed.”</li><li>The heads up gives you permission to then follow up and let them know you have to run without being rude</li><li>Then follow up with “I’m SO sorry I have to run but I’m happy to schedule an additional call — can you whatsapp me with a couple additional times that work for you.”</li><li>Then they will only follow up if very important, but 90% wont likely which could save you meaningful time</li></ul><p><strong>The ‘let me get back to you strategy’</strong></p><ul><li>if they’re explaining a situation and going on about it, mention “I actually don’t have the full context or answer yet to get a solution, but I can make sure I do get more info and circle back by 5pm today — would that work?”</li><li>This should decrease the motivation to explain the situation more since you’re not the right person to get this info</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fabbbbad2f11" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Performance Improvement Plans (PIPs) at Bright]]></title>
            <link>https://jonahgreenberger.medium.com/performance-improvement-plans-pips-at-bright-a237e197f795?source=rss-73733e1b30ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/a237e197f795</guid>
            <dc:creator><![CDATA[Jonah Greenberger]]></dc:creator>
            <pubDate>Sat, 13 Feb 2021 20:05:33 GMT</pubDate>
            <atom:updated>2021-03-06T22:37:05.866Z</atom:updated>
            <content:encoded><![CDATA[<p>At Bright, we want to continuously provide feedback, some times it’s hard to do so this a quick process guide in which you can execute an ideal Performance Improvement Plan (PIP) plan with your team member. One important thing to clarify — <strong>the goal of PiPs is to help employees improve their work so that we can keep them — it is a tool to help employees succeed.</strong> A lot of people think the goal of PiPs is to help people leave, but in reality the goal is to help us be able to justify them to stay! <strong>Usually we find 50% of people on PiPs end up improving and being able to stay and 50% don’t and have to leave.</strong></p><p>Here’s the process:</p><ol><li>Evaluate if someone should be put on a PiP. Give them time to ramp and if they don’t perform after average ramp time it may be time for a PiP. Make sure to have a standard for how to define underperformance that you stick to — at Bright, if they don’t reach at least 80% of their goals this means they’re underperforming.</li><li>Identify his/her main areas that they could work on to achieve better results and quantify where they are today versus where they need to be</li><li>Fill this <a href="https://docs.google.com/spreadsheets/d/1nxt8pinoRBCD3anwyrctdC0Zr1D4BCByWw-Ohoz916g/edit#gid=0">template</a> (and work to provide very specific examples). Send to People Ops and CEO to get feedback before sharing with your employee since an extreme level of specificity is necessary that’s not always intuitive. A couple additional thoughts for those interested — in our experience, a majority of employees almost have no idea they’re not performing to expectations unless given a document beyond clear that spells it out with clear metrics. Note that this may feel a bit too honest but it’s actually mean to not give honest feedback to someone that could really help them perform. Also remember to establish which will be the consequence if this requirements are not full-filled.</li><li>Schedule a PIP session with your team member cc People Ops — People Ops will run this meeting (important because they know all the best practices)</li><li>Execute PIP session providing the specific feedback and make clear the deadline to achieve this plan and the consequences if they do not. Note that People Ops must run this session 1) to ensure best practices are being used and 2) to limit liability if the employee sues.</li><li>Get signature as a commitment for your team member that he/she understand the provided feedback and deadline.</li><li>Make sure to do a mid-review PIP, to check in with him/her. This is a great time to repeat expectations and consequences.</li><li>When reviewing PIP, People Ops will lead the meeting and leading next steps with the back up of performance review data from the manager.</li></ol><p>Last word</p><p>Remember at Bright we are looking for a top performers culture. If we encourage a culture in which we accept low performance we won´t let future good talent join Bright.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a237e197f795" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One on one best practices]]></title>
            <link>https://jonahgreenberger.medium.com/one-on-one-best-practices-91880af972d0?source=rss-73733e1b30ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/91880af972d0</guid>
            <dc:creator><![CDATA[Jonah Greenberger]]></dc:creator>
            <pubDate>Sat, 13 Feb 2021 19:10:07 GMT</pubDate>
            <atom:updated>2021-04-20T13:12:40.815Z</atom:updated>
            <content:encoded><![CDATA[<p>Suggested template <a href="https://docs.google.com/document/d/16PRyCv9GPQnSGCIqyllIo67F2qKHEcx4arGsS3Zi8qU/edit?usp=sharing">here</a>!</p><p>It’s a fundamental rule of management that to lead others you need to practice frequent and open communication. The general wisdom is that managers can best accomplish this by holding regular one-on-one meetings with directs reports, usually weekly or close to it. It’s certainly a simple idea that sounds good, but yet so many managers and directs alike complain that these meetings are unhelpful — or worse, don’t actually happen at all.</p><p>Why is having a half-hour meeting once a week so hard?</p><p>First, we know we’re supposed to have them, but aren’t always sure what makes them productive. We may err on the side of being too unstructured and loose, or have so much on our own plates that it’s a one-way delegation session. We may find that they unearth some simmering conflict or complaints, and prefer to avoid the sensitive topics, or blow off the meeting entirely.</p><p>So, in the spirit of bettering these less-than-satisfying conversations that do take up quite a bit of real estate on our calendars, here are some ways to be sure that you and your direct reports are getting the most out of them:</p><p><strong>1. Have a schedule and stick to it.</strong></p><p>Although it’s a nice idea to think you can catch up with your direct reports on the fly, that’s harder to do in reality. By making a commitment to a schedule, whether once a week or once a month, both parties will better prepare and take the meeting more seriously. This is often the prime time for work to be discussed and advanced, so this time on the front end saves you dearly on the back end.</p><p>It’s natural that other work may come up that causes you to reschedule, but beware. I can’t count the number of complaints I’ve heard from employees that their managers never stick to their one-on-ones — sending the message that the employee is the most expendable action item on the schedule. Try to stick with the meetings and have cancellations be the exception.</p><p><strong>2. Share the air.</strong></p><p>Structure your meetings so it’s partly about what you need to discuss, and also about what your direct report needs to raise. It shouldn’t be just a one-way delegation of tasks.</p><p>Good one-on-ones are a conversation, and for that to be successful you need to be receptive, as this article in Harvard <a href="http://www.forbes.com/business/">Business</a> Review <a href="http://blogs.hbr.org/2008/02/communicating-strategically-wi/">points out</a>. I suggest starting with what the direct report needs to discuss, and then moving to your own list (which you’ve prepared ahead of time). Your employee will take your lead — so if you come with thoughts ready to go, they will as well.</p><p>It’s also important to leave time to discuss open issues. This is a great chance to cover those less urgent items, like a promotion path or difficulty with a colleague, that get in the way of productivity and retention. Better to know early, as it may be a problem that’s easily resolved, and can give you insight into ways to keep your team more productive.</p><p><strong>3. Be present.</strong></p><p>So many of us struggle with how to get it, and keep it, amidst so much distraction. Giving someone our full, uninterrupted presence is a gift that makes a big impact. It’s so rare, and I believe is a large part of what people mean when they say someone has “presence.”</p><p>The one-on-one meeting is a perfect time to practice being present and free from distraction. It’s not easy, but it is <a href="http://www.forbes.com/sites/work-in-progress/2013/09/19/the-multitaskers-guide-to-being-more-present/">possible</a> with intention. Come to the meeting focused and committed — don’t schedule between back-to-back meetings so you come late and have to cut out on the dot. (One trick: schedule meetings for 25 minutes rather than a half hour.) Keep off your phone and email, and close your door to limit interruptions.</p><p>When you’re truly engaging with a co-worker or direct report, you’re not only showing them respect; you’re also able to really take in what they’re saying and use everyone’s valuable time wisely.</p><p><strong>4. Manage accountabilities.</strong></p><p>As with any good meeting, it should wrap with accountabilities and a path for follow up. We all know it’s easy to listen and absorb ideas when you’re in the moment, and then to forget them when your attention is inevitably diverted.</p><p>Make sure to schedule the last few minutes of the meeting for each of you to go through and say what you’re committing to and by when. For best results this should also be followed up with an email from your direct to you, restating what’s supposed to happen. Depending on the project, it also may be useful to set up a milestone to update each other.</p><p><strong>5. Manage to a structure.</strong></p><p>Of course all meetings are different, and you need to work with a style that’s doable for you. That said, if you can find a structure and manage to it, you’ll find that the conversations will naturally fit into those expectations. It’s your job as the manager to honor the time and facilitate the discussion.</p><p>Following all of the above, a good structure for a 30-minute, weekly one-on-one meeting is <a href="https://docs.google.com/document/d/16PRyCv9GPQnSGCIqyllIo67F2qKHEcx4arGsS3Zi8qU/edit?usp=sharing">here</a>.</p><p>As a side benefit, you’ll find that when you follow this type of format, it becomes easier to provide constructive feedback and to address issues before they become big problems as there’s a space set aside for it. It also supports proactivity and strategic thinking because everyone knows that they are expected to come to the table ready to share.</p><p><strong>6. Principles to Remember</strong></p><p><strong><em>Do:</em></strong></p><ul><li><em>Begin each meeting by sharing a win. It creates positive energy.</em></li><li><em>Notify your employee in advance if you plan to touch on professional development — those conversations require reflection and thought.</em></li><li><em>Be curious. Listen to your colleague’s concerns and provide feedback and ideas on how she might solve problems.</em></li><li><em>Make sure pre-reads use full sentences</em></li></ul><p><strong><em>Don’t:</em></strong></p><ul><li><em>Cancel. Demonstrate to your employee that s/he takes priority by arriving on time.</em></li><li><em>Be rigid. While it’s wise to have an agenda, it’s also important to be flexible.</em></li><li><em>Forget to say “thank you.” It’s important to show your colleague that you value him/her</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91880af972d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Repeating yourself is actually an important leadership skill]]></title>
            <link>https://jonahgreenberger.medium.com/repeating-yourself-is-actually-an-important-leadership-skill-290467c53d16?source=rss-73733e1b30ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/290467c53d16</guid>
            <dc:creator><![CDATA[Jonah Greenberger]]></dc:creator>
            <pubDate>Mon, 04 Jan 2021 18:56:19 GMT</pubDate>
            <atom:updated>2021-01-04T18:56:19.382Z</atom:updated>
            <content:encoded><![CDATA[<p>It took me years, but I think I’ve finally accepted that as a leader it’s very important (and necessary) to repeat yourself often. This is because this is how an organization learns what is important and is able to sift through all the noise to find where they really need to focus.</p><p>The challenge is that it takes so much time to have to repeat yourself to every employee at Bright. This is why I actually think documentation is actually so critical. By writing a blog (like this!) or creating documentation for your processes, you’re able to just send a well thought out and clear document vs. take time to repeat yourself over and over again. Plus something truly beautiful happens when you do this, you take the time to explain something very clearly since you only have to write it once. Versus if you actually are not documenting but just verbally repeating yourself, you won’t likely take the time to explain clearly and you’ll leave many confused. And once you do document, you can get feedback and continue to iterate and make it better indefinitely.</p><p>Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=290467c53d16" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should someone be a manager?]]></title>
            <link>https://jonahgreenberger.medium.com/should-someone-be-a-manager-5e34caed574f?source=rss-73733e1b30ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e34caed574f</guid>
            <dc:creator><![CDATA[Jonah Greenberger]]></dc:creator>
            <pubDate>Mon, 04 Jan 2021 18:54:31 GMT</pubDate>
            <atom:updated>2021-04-19T13:52:36.546Z</atom:updated>
            <content:encoded><![CDATA[<p>There are many early pitfalls with the decision to make a top performer a manager and no one avoids them all. A very common one is many folks misunderstand what management is. Many people don’t grasp that managing is a totally different set of muscles. For instance, managing is not just being deeply knowledgeable about what the team does, it is all of the follow things as well (and check that these are true when you’re thinking about whether someone should be a manager):</p><ul><li>the ability to delegate tasks they don’t need to do or say no to them in the spirit of focusing</li><li>the ability to communicate concisely and in written and verbal form (they are exemplary slack and google doc users)</li><li>the ability to make sounds business decisions</li><li>the ability to share feedback in written and verbal form and have it be understood</li><li>the ability to prioritize (and say no to things that aren’t a priority)</li><li>the ability to set clear and measurable goals and hold other accountable</li><li>the ability to provide clarity and generally understand how each individual contributes to the success of the whole team.</li><li>the ability to create pre-reads and start meetings on time</li></ul><p>These are not the things you had to worry about as an IC (individual contributor).</p><p>When people tell you they want to move into management, ask them why. Ask them to tell you what they like about management and what they think they might be good at. If it becomes clear that the person doesn’t understand what their actual duties will be as a manager, steer them away from it or tell them to go have a think (or in some cases read a book). Great managers are people who are intrinsically interested in the responsibilities above and get energy from exploring team dynamics, hiring and developing people.</p><p>It’s useful to help new managers understand the impact of keeping all of the work vs. delegating and developing the team. For instance, there will never be a chance for them to expand their role if they don’t groom their team to take over their responsibilities they usually get it. When you put it in terms of the impact to their own career progression it gets their attention. It’s also hard to let go of doing the things that made you successful to begin with so helping them understand and accept that the transition to manager will be both uncomfortable and scary at times. — This is completely normal, it is change after all.</p><p>To add a bit more color, I’ve also outlined below things folks generally wish they knew as a manager:</p><p><strong>First — how you’re evaluated fundamentally changes</strong></p><ul><li>It’s about the output of the individuals on your team.</li><li>You only have full control over two things that affect team output: hiring the right people and keeping them motivated.</li><li>You’re now a coach in addition to a player. You will be evaluated on the basis of your ability to hire, develop, and amplify talent.</li><li>Sometimes, motivating your team will mean leaning on <em>your</em> manager to motivate in ways you can’t. This says nothing about your capabilities. Your ability to identify when you need help and to team-up with your manager to keep people motivated does.</li></ul><p><strong>Second, it’s always your fault. Always.</strong></p><ul><li>If your team fails, it’s your fault.</li><li>When things go wrong, always start by looking at yourself first and asking what context you failed to set, what resources you failed to provide, or what guidance you failed to articulate clearly.</li><li>You exist to serve your team. Study <a href="http://toservefirst.com/definition-of-servant-leadership.html">servant leadership</a>.</li></ul><p><strong>Third, objective-setting, the context and guidance you provide, and your framing is 10x more important</strong></p><ul><li>Your team (and others) will repeat the words you use. Choose your words carefully.</li><li>Similarly, your team (and others) will emulate your behavior. The way you behave implicitly indicates the behavior you consider acceptable for others on the team. Choose your behavior even more carefully than your words.</li><li>By nature of your positional authority, your opinions and words carry more weight. Be aware of that weight and exercise restraint appropriately. <a href="http://www.edbatista.com/2017/02/leadership-decision-making-and-emotion-management.html">Study this decision-making framework</a>.</li><li>When in doubt, over-plan for important discussions.</li><li>Understand <a href="https://getlighthouse.com/blog/management-concept/">task maturity</a> and provide more hands-on guidance appropriately.</li></ul><p>I hope this is helpful and good luck!!</p><p>Jonah</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e34caed574f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Team morale is all about “winning”]]></title>
            <link>https://jonahgreenberger.medium.com/team-morale-is-all-about-winning-54a36f15cbfe?source=rss-73733e1b30ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/54a36f15cbfe</guid>
            <dc:creator><![CDATA[Jonah Greenberger]]></dc:creator>
            <pubDate>Mon, 04 Jan 2021 18:51:31 GMT</pubDate>
            <atom:updated>2021-01-04T18:51:31.712Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve found that teams that consistently win over a week period (measuring over a week vs day is the right frequency here since anyone can have a bad day) are happy teams. And teams that consistently loose over a week period have low morale and are bound to have high turnover.</p><p>Why do teams win or lose concisely? It’s all about these three things:</p><ul><li>Focus — do they only have one or two ambitious goals or more which is probably too many?</li><li>Team talent vs challenge — are the challenges given to the team allow them to be “in the zone” or are they too challenged or too bored?</li><li>Motivation — are the individuals on the team doing things that give them energy &gt;50% of the time?</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54a36f15cbfe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The outline principle]]></title>
            <link>https://jonahgreenberger.medium.com/the-outline-principle-3ed35a618d43?source=rss-73733e1b30ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ed35a618d43</guid>
            <dc:creator><![CDATA[Jonah Greenberger]]></dc:creator>
            <pubDate>Mon, 04 Jan 2021 18:48:14 GMT</pubDate>
            <atom:updated>2021-01-04T18:48:14.188Z</atom:updated>
            <content:encoded><![CDATA[<p>Many times when you are starting a big project (say that takes &gt;5 hrs), it’s impossible to know exactly what your audience wants beforehand without really asking a lot of questions. But knowing what questions to ask is hard and also your audience may also not know what you don’t know and what to tell you. So I’ve found it’s often super useful when starting a big project to outline just in one page what the project is before you do the work. To help you, we’ve created <a href="https://docs.google.com/document/d/1b4L5yoltCOcII5BCmyWWruiMAeLbUen1LcXvhtO8HtY/edit">this template</a>. Try using it and provide feedback on what could be made better!</p><p>Good luck!</p><p>Jonah</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ed35a618d43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Process]]></title>
            <link>https://jonahgreenberger.medium.com/process-98572ac052c9?source=rss-73733e1b30ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/98572ac052c9</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[process]]></category>
            <dc:creator><![CDATA[Jonah Greenberger]]></dc:creator>
            <pubDate>Fri, 02 Oct 2020 01:16:30 GMT</pubDate>
            <atom:updated>2020-10-02T01:16:30.102Z</atom:updated>
            <content:encoded><![CDATA[<p>A lot of process in companies just exists to ensure mental processing happens (i.e. understanding what’s happening and why, what affect you’re having on the employees around you, why customers are happy or unhappy etc).</p><p>The reason we create processes to ensure this happens is that many people don’t process unless forced to, and even if they do, they often only process part of what they need to. And even if they do process a lot, they don’t have many experiences to help them make the quality decisions that are needed. And so processes exist to solve this. They structure in time to think about important questions and to get perspectives needed to make good decisions. A relevant example — we create processes to approve a new hire because it forces people to understand what types of hires are good investments and why, whether the company can afford this hire, and what the right structure is to bring them on. It may feel like extra work, but if it does, the person assuming so may believe they’re already doing all the mental processing to understand all these questions and if you really lay out all the considerations and questions that need to be asked to make a good decision, they may realize why the processes is actually necessary.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=98572ac052c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meetings at Bright — distributed work best practices]]></title>
            <link>https://jonahgreenberger.medium.com/meetings-at-bright-distributed-work-best-practices-b615cc412bc5?source=rss-73733e1b30ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/b615cc412bc5</guid>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Jonah Greenberger]]></dc:creator>
            <pubDate>Thu, 14 Mar 2019 18:51:47 GMT</pubDate>
            <atom:updated>2019-03-14T18:51:47.596Z</atom:updated>
            <content:encoded><![CDATA[<h3>Meetings at Bright — distributed work best practices</h3><p>Working on a distributed team is hard. But with the right best practices it can become incredibly effective. Below I outline some of Bright’s top best practices:</p><ul><li><strong>all meeting should be over zoom</strong>, even if you’re in the same location. Counterintuitive I know but easiest to always follow a practice than just do it sometimes</li><li>all meetings should have folks <strong>connect on their own computers and everyone should use headphones</strong>. If not, you get weird feedback and have the alternate muting and unmuting. Plus all folks can then be seen so its more personal</li><li><strong>video should be turned on</strong> ideally all the time — that way you can see your coworkers and get to know them!</li><li>make sure you have <strong>a good internet connection </strong>— obvious perhaps but sometimes hard in certain locations</li></ul><p>Good luck!</p><p>Jonah</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b615cc412bc5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>