2 ms·
I don't always keep detailed time logs, but would take notes on situations like that, where there were significant delays caused by something outside my control
by mgkimsal 9y ago
I don't always keep detailed time logs, but would take notes on situations like that, where there were significant delays caused by something outside my control. Not showing up on an invoice, but using those notes, I'd have a meeting with someone higher up (if there was no traction from trying to work with the people on the ground).
In most cases, those situations haven't worked out well, but it seems nothing does. There's sometimes some cult of personality - "do it Dave's way", etc. To which the logical question "if Dave's way is so good, why are things broken and people are bringing in outside help to fix things?" If you can't ask that sort of question and get a good feel up front, it may be worth skipping the project (unless they pay is really good - I've usually put up with more crap than I suggest other people do because I wanted/needed the money)
- pjmlp 9y agoI've learned to always keep such logs, in some gigs even down to minutes. They can come really handy if the fire brigade comes in when invoices start getting discussed.
- mgkimsal 9y agoSome projects I do want some product I don't. If I think at the very beginning that I have to do that, I'm already thinking I'm in a potentially bad/adversarial project.
- ethbro 9y agoAlways good to keep notes on things like this (noted at the time each issue appears). Always better that they never have to be formally given to the customer.