Troubleshooting Two Issues in Project Planning Meetings
When working on a project, meetings can be just as important as writing code. But meetings often bring along unexpected problems. 🤦♀️
This post is not about technical matters—it’s about the soft skills needed for teamwork. I’ll share two issues we faced during project planning meetings and how we solved them.
1. ✂️ When the Boundaries of Task Distribution Became Unclear
Original Approach
In our team meetings, we assigned roles such as timekeeper, decision-maker, facilitator (to redirect when off-topic), meeting leader, and scribe. Each day, the roles rotated so everyone got a chance to try different responsibilities.
Problem
Over time, issues began to surface:
- The boundaries between roles became blurry,
- Responsibility was scattered,
- Confusion arose about who should make the final decision.
As a result, discussions often drifted without reaching a clear conclusion. 😶🌫️
Solution
Instead of rotating, we decided to assign each role permanently to the person who had performed it most effectively. With team consensus, we locked in roles, and I took on the position of “decision-maker.”
Outcome
This significantly improved the meeting flow. Previously, we often wavered in the middle of planning, but now with responsibilities clearly defined, conclusions became much sharper.
2. ⛰️ When Discussions Drifted Away from the Topic
Original Approach
We documented meeting agendas in Notion. 📋
Problem
During meetings, the atmosphere became scattered, and unrelated topics frequently surfaced. Because Notion wasn’t always visible unless someone actively opened it, our focus often strayed.
Solution
A simple but powerful fix: writing the day’s topic in large letters on a whiteboard visible to everyone. 🧑🏫
Outcome
The tendency for discussions to drift almost disappeared. Whenever someone veered off-topic, eyes naturally returned to the whiteboard, keeping the group on track.
It was surprisingly simple, yet highly effective—a reminder that “the simplest solutions can be the strongest.”
Conclusion
Just as we debug code, meetings also require troubleshooting. From this experience, I learned:
- Assign roles clearly, to the people best suited for them.
- Keep the agenda visible and simple for everyone.
These small changes greatly boosted our team’s planning efficiency. Going forward, I hope to continue finding small yet impactful ways to improve collaboration. 🚀
