Having to go to a meeting really messes with your flow for the whole day, doesn't it?
Having to go to a meeting really messes with your flow for the whole day, doesn't it?
You're viewing a single thread.
Some meetings are for:
-
Project Planning
-
Roadmaps
-
Brainstorming
-
Project-Milestone-Task breakdowns
-
Issue-Triage work
-
Budgetary allocations
-
Priority item tracking
There are many many important meetings to have and to get done. The worst meeting you can have is a status-update call where you mark off items on a checklist. This can be done by automation and status-tracker boards.
No the worst meeting is when the entire team â CEO, CTO, sales, engineering â spend all of Friday (every Friday) divvying up the tabs in a big excel spreadsheet, going and re-going through workflow checklists.
I knew they had no automated tests when I joined. I was promised, when I joined, that Iâd be allowed to spend at least 25% of my time building an automated test suite for our app.
But we never had time to allow me to do that. So instead of spending 25% of my time developing an automated suite, which would steadily reduce the following until it was zero, we spent 20% of the entire companyâs time doing human rspec tests.
One time the CTO asked me âWhy wasnât this caught in testing?â and I said âBecause we donât do any testingâ
Damn sounds too familiar đ
Also, I agreed to only take 2/3 of my salary until a funding round came in. The promise was as soon as that hit, Iâd go to 100% of our agreed salary.
Funding was eventually secured (thanks in no small part to me) and they tried to say âweâll seeâ on the salary increase, so I just quit.
Huh. In theory, at least. In IT I've really only seen the status/blamestorm sessions. If I suggest that meetings aren't a good use of time, it's from that bias.
-