Log in

No account? Create an account

Previous Entry | Next Entry

beat up meetings

Goal: next time I'm called into a surprise beat-up meeting over missed deadlines I will...

1) Listen carefully
2) Ask questions about the downstream consequences about not meeting our dates
3) Communicate what can be done
4) Communicate recent successes, both to give everyone a feel for the realistic pace of what's going on, and to make sure the things we have accomplished are what the program really needs
5) Say, "I don't have a great status on X, but with this information you've told me I'd like to check with the team and report back."
6) Brainstorm alternative paths... "what if we just gave you what we have now?"
7) Offer peace amidst the storms

I will not do these things, which seem to be my autopilot brain go-to moves:

1) Get defensive
2) Say nothing
3) Loudly declare that these dates were unachievable crap from the beginning and everybody knew it
4) Stand up and storm out

I know. I've tested all of these. Extensively. I'm awesome.


Recent Posts from This Journal

  • Waller

    The word "waller" is a technical term recognized immediately in Kansas, not as much across the English speaking world. I think it's useful enough…

  • 2017 Resolutions

    It's time to get back to new years resolutions. In 2017 I took a year off, so to speak, January came around and I wasn't feeling it, I was in a haze…

  • idiot proofing

    I really hate the term "idiot proofing". It's on you to make your designs user friendly. If use of your design is ambiguous and fails to predict…


( 11 comments — Leave a comment )
Feb. 9th, 2016 09:04 pm (UTC)
It's very good of you to objectively test methods and report your results.
Feb. 9th, 2016 09:41 pm (UTC)
Those beat-up meetings don't surprise me anymore.

Good luck... I can provide independent confirmation of your test results on most of the second set, although I haven't physically stormed out. Yet.
Feb. 10th, 2016 02:46 am (UTC)
The best is when you can combine it with a dramatic laptop slam.

It's the engineering equivalent of the mic drop.
Feb. 10th, 2016 03:40 pm (UTC)

"We're DONE here!"
Feb. 10th, 2016 12:13 am (UTC)
If you achieve all those things consistently, I want to go work for you. I'm pretty sure lack of knowledge about your field, and absence of a green card, are thingsI can overcome :).
Feb. 10th, 2016 07:13 pm (UTC)
I think #3 on the "Do not" list could be modified to be more effective if there was a mention ofnthe deadline being tight/unrealistic at the start of the project.

Do they habitually run you on crazy, unrealistic deadlines? That would get old pretty fast, especially with the addition of "beat-up" meetings.
Feb. 10th, 2016 07:31 pm (UTC)
Oh good, I'm not alone. ;)
Feb. 10th, 2016 09:28 pm (UTC)
Thank you!
Feb. 10th, 2016 11:17 pm (UTC)
I was familiar with beat up meetings, but they weren't surprises. Having an expectation revealed after not meeting it... ugh.
Feb. 11th, 2016 05:28 pm (UTC)
It can be hart not to get defensive sometimes, depending on how they originally broach the subject. At least you can try to move on from here.
Feb. 12th, 2016 07:51 pm (UTC)
Haha, this is very familiar

Edited at 2016-02-12 07:52 pm (UTC)
( 11 comments — Leave a comment )

Latest Month

January 2018
Powered by LiveJournal.com
Designed by Tiffany Chow