What surprised me is that a sizable chunk of a developer’s time is spent on meetings. Up to 20% of their week!
It is not a surprise that most of the time, developers might not be super focused in meetings, and instead using that time to squeeze in a few lines of code.
While it's arguably natural for developers to gravitate towards immediate productivity, such behavior risks long-term clarity and alignment.
What if we could strike a balance? Maintain a level of multitasking, while still fully engaging with the meeting's content?
Ask Wudpecker enables you to ask questions about the meeting’s content, so you can quickly get the gists. Here are a crystalized list of 10 actionable prompts for all your meetings, be it sprint, daily standup, technical review, or project planning.
Prompt 1: "What were the key takeaways from the recent meeting?"
This prompt helps in consolidating the most important aspects of the discussion and ensures that no significant detail goes unnoticed.
- Understanding the performance issues of the existing system that needs to be optimized.
- Identifying new features that need to be incorporated into the software.
- Recognizing potential roadblocks in the project roadmap.
Prompt 2: "What was the client's main concern during the demo?"
This can help identify areas of the software that might require additional attention or improvement from a user's perspective.
- Finding usability issues that might affect the user experience.
- Discovering areas of the application that need better performance.
- Detecting potential security concerns raised by the client.
Prompt 3: "What were the proposed solutions to the problems identified during the technical meeting?"
This helps gather different approaches and solutions proposed to address the problems identified, fostering a collective problem-solving culture.
- Considering various approaches to enhance the system architecture.
- Evaluating different methods for database optimization.
- Comparing strategies to improve code quality.
Prompt 4: "What new learning opportunities emerged from the last retrospective meeting?"
This aids in continuous learning and encourages the adoption of best practices by identifying areas of improvement or new technology trends.
- Realizing the need to learn a new technology or language for upcoming projects.
- Understanding that a different project management tool might be more effective.
- Recognizing areas where the team can improve collaboration or communication.
Prompt 5: "What risks were identified during the project planning meeting, and what mitigation strategies were discussed?"
This provides a clear understanding of potential project risks and helps plan for those contingencies.
- Identifying the risk of scope creep and discussing strategies to keep it under control.
- Pinpointing potential resource allocation issues and solutions.
- Highlighting dependencies that could lead to delays and discussing contingency plans.
Prompt 6: "What feedback was provided by the team during the last demo meeting?"
This enables a healthy feedback loop, encouraging constant improvement and the inclusion of diverse perspectives.
- Discovering improvements in UI/UX suggested by the team.
- Realizing the need for better documentation based on feedback.
- Understanding the need for additional features or modifications based on team suggestions.
Prompt 7: "What were the performance benchmarks set in the recent meeting?"
This helps track progress against goals and keeps everyone focused on meeting these standards.
- Tracking the load times required for the application.
- Setting the target number of bugs or issues to be resolved in the next sprint.
- Establishing the desired code coverage percentage for unit tests.
Prompt 8: "What were the priorities set during the planning meeting?"
This ensures clarity on what tasks are important and should be focused on in the upcoming development phase.
- Setting the development of a critical feature as a priority.
- Identifying that improving system security is a primary concern.
- Recognizing the need for enhancing system performance as a top priority.
Prompt 9: "What were the key decisions made during the last technical meeting?"
This helps to highlight the important decisions made, the reasons behind those decisions, and their potential impact on the project.
- Deciding to refactor a major part of the code for better maintainability.
- Opting to use a particular technology stack for the project.
- Concluding to follow a specific design pattern for software development.
Prompt 10: "What were the action items assigned during the retrospective meeting?"
This helps in ensuring accountability, tracking progress, and understanding what tasks need to be completed before the next meeting.
- Allocating the task of updating the project documentation to a specific team member.
- Assigning the resolution of specific bugs to certain developers.
- Distributing the task of learning a new tool or technology to different team members.
Awesome prompts! But… Where can I even use it?
You can paste the transcript of your meeting into ChatGPT, and then attach the prompts to produce results.
- You can try for free and it works for shorter transcript of 15-minute calls.
- The free version doesn’t have high reasoning capability. So it’s likely you will get answers that make your eyes roll.
- Token limit. If the transcript is from a 30+ minute call, it’s likely that you will get an error that your prompt was too long.
- Might not produce results during peak hours.
Wudpecker.io is an AI meeting tool that records, transcribes, and summarizes your meetings. It is built for you to enter these prompts and extract insights.
- Can extract insights despite the meeting length
- Offers quality summaries and transcripts, making it easy to review meetings and find important insights quickly
- Transcription available in 100+ languages
- Records calls for later reference and sharing with remote team members
- Provides ready-made templates or the option to create custom templates for note-taking
- Allows users to create snippets from recordings, making it easy to share important sections of a meeting with others
- Recognizes speakers during the meeting and separates their dialogue in the transcript, making it easy to follow along and attribute comments to the correct person
No more shall developers live in the dread of incessant meetings, fearing the loss of valuable coding time.
With these strategic prompts, we believe you can draw the fine line between meeting engagement and keeping your fingers dancing on the keyboard.
So, put on your headphones, dive into the world of code, and let the push notifications of a successful git push bring a smile to your face. Meetings? You've got them covered with efficient, actionable insights. After all, we're here to code the future, one line at a time!
Happy coding and happier meeting multitasking to all the software engineers out there!