Meetings are like bitter pills to employees. Most don’t want them, but can’t avoid them, since many organizations, managers, and team leads see meetings as the best way to manage projects, interact with team members, and make critical decisions.
Moreover, it’s almost inevitable for developers, as most software development methodologies depend on meetings for updates, code reviews, software testing, and deployment. Development teams also need to join meetings with product managers to give updates, estimates, and walk-through product requests.
But are meetings always productive? Do they actually help developers execute projects in the pipeline faster, or are they merely time-wasting productivity stealers? Should you clear your team’s schedule or stick with the fully booked calendar to get the best out of them?
As a tech leader or manager, you may find yourself struggling with these questions and debating the point of meetings. Many top managers are not big fans of meetings, but will never openly admit it the way Elon Musk does, for instance. However, as a tech leader, you have to make the right choices for your team, which includes deciding if your developers need to be constantly attending meetings or not.
We recently spoke with Scott Priddy, Chief Technology Officer at B Generous, on our Tech Leaders Hub series. Scott shared some insights on minimizing meetings for technical teams and offered alternative ways to work and collaborate with your team.
If you’d like to save your team members’ time while maximizing your development team’s output and productivity, read on to learn how to keep your team organized and productive without unnecessary meetings.