As long as I've been a manager, I've always built into the team culture a weekly project status meeting. It's not nearly as detailed as the outlined Staff Meeting that MT suggests, but it's one thing that I've recevied feedback from my team about that they hope we keep doing. Since I haven't done 1 on 1s, I think part of the desire to keep those meetings going is that it does provide consistency and it's a great check-in for all of us.
I have a small team of 3 (4 counting me). 2 have the same role (illustrator/animators), and the other is tangentally related (visual designer). So all week, they are interacting with each other, learning from each other, and passing projects around to each other as needed.
I'm nervous that by adding 1 on 1s (which I've bought into and am so excited about), that it's going to change the dynamic of our team meetings. Or, should I keep project status updates out of the 1 on 1s, and just work on relationship building? or, if project status is a part of the 1 on 1, is it not redundant then to also go over project status in the staff meeting?
I haven't started rolling out 1 on 1s just yet (I haven't given the 3-week notice), as I want to have a bit more clarity on how it will impact our already standing team meeting. I've listened to most of the 1 on 1 podcasts, and jumped over and found how to run an effective staff meeting, but I'm still missing the impact these two things can have on one another...
Thanks for any insight, or experience stories you can share!