This week, our cohort began working on the first client project, which will run for one week. Each week, a different person will take on the role of the Project Manager. With a total of seven projects lined up, this means that everyone will have the opportunity to be the PM at least once.
As the PM for this first week, I’d like to share some key learnings and important points I’ve observed so far. These insights may resonate with many Data School Consultants, but it never hurts to reflect on them more than once. So, here are my takeaways from the past few days:
Learnings from the Past Week
- Arrive Early: Before the kickoff, ensure that your cohort is prepared to arrive early. While our usual day starts at 9:00 AM, the kickoff meeting begins at the same time. Plan to be there at least 15 minutes early to settle in and be ready.
- Prepare in Advance: If you receive any information about the client beforehand, take the time to prepare a few introductory slides about your cohort. This will help set the tone for the meeting and make a great first impression.
- Follow-Up Emails: After the kickoff meeting and every meeting, it’s essential to send a follow-up email to the client. This email should summarize all the key points and discussions from the call to ensure clarity and alignment.
- Planning Check-ins: The kickoff meeting is the ideal time to schedule your next check-in with the client. Use this opportunity to agree on a date and time, so you wont have the struggle on finding the right time slot afterwards via Mail.
- Delegate Note-Taking: Assign someone the responsibility of writing the meeting minutes. This allows you to focus fully on the client and actively engage in the discussion without being distracted by taking notes.
- Team Debriefs: Take the time to hold quick debriefs with your team. A lot can change in just an hour, and discussing issues together often leads to simple and effective solutions. Regular check-ins help keep everyone aligned and on track.
- Take breaks: It can be difficult to step away when you're in a good workflow, but that's exactly when it's most important to take a break. Stepping back helps you avoid tunnel vision and gain fresh perspective. Be firm about this to ensure the team actually takes breaks—it's easy to forget otherwise!