- 2 . Use Zulip - and integrate them with project management tools.
- 3 . Zulip is good for this also
- 4 . Unless you need to share screen and explain things , you don't need meetings for that.
- 5 - Chat please
- 6 - Brainstroming is only place where meetings are needed.
Project management tools are there for the long view and tracking, I don't want to juggle priorities of a JIRA backlog, it basically pushes the burden of PM to me. With a meeting if someone has a blocker thats on me I prefer if they raise it in front of the team and we agree if it should get done now or later. Other than that I share what I am currently focusing on and ignore the rest until I have to deal with it. Multitasking and context switching is a PITA and I will gladly delegate that to PM and hop on a meeting to sync with everyone.
I don't want to be spammed with JIRA updates on dozens of tickets I might be needed on, only to forget about them in 15 mins when something more important comes up.
And written communication takes more effort, it's a tradeoff for sure.
Reductionism is easy, and cheap.
I work with engineers - actual electrical and chemical engineers that design processes and controls - and I make the software side of their ideas happen. They can't do their job without me, and vice-versa. But I'm a SCADA integrator, not an engineer, dammit.
Still if you want to stick to what you know, that’s fine too.
I tend to grab the more interesting issues, which is easy because nobody else wants them. But in general I hate my job and I can't learn much from it.
I have to admit that if I was in a more fulfilling position I'd be happier to collaborate. But I'll never be a "team player". I just don't have this in me.
Similarly I've had so much feedback that people wanted to have a better idea of what everyone else in the department was working on. So various things were tried. Summary emails, brief section in monthly all-hands, yet many of the same people who asked for it didn't pay attention in the meeting and didn't read the email.
* Keeping everyone working on a complex project updated on progress
* Keeping everyone 'aligned' - (horrible corporate word but) essentially all working together effectively towards the same goals (be they short or long term)
* Providing a forum for catching and discussing issues as they arise
* A degree of project management - essentially, making sure that people are doing as they said they would
* Information sharing (note I prefer to cancel meetings if this is the only regular purpose)
* Some form of shared decision-making (depending on the model you have for this) and thus shared ownership
If a meeting 'owner' is sensitive to not wasting people's time and regularly shortens or cancels meetings, it can be done well, I believe.