[KineticLensman]

> how accruals work

Slightly off-topic but I worked at a UK research organisation that was a privatised entity recently spun-off from a civil-service organisation. The new CEO (who came from a finance background) got a tour of each department. He apparently listened to all of the tech evangelism from the department directors and then asked them how their department's accruals were doing. Those department directors who asked him to clarify what he meant by accruals didn't stay in post very long. Allegedly.

Us lowly engineers just kept our heads down.

[conductr]

This is a bit extreme. I've worked in many industries where the word 'accrual' is kind of internal to the finance/accounting department. I'd estimate over 70% of very good functional department heads I've worked with in the past would ask for clarification too. If they were still confused after further clarification or weren't able to comeback with an answer, then there is a bigger problem potentially with their ability to own a budget/manage spend.

This is kind of like punishing someone for not knowing your preferred buzzword. I've seen dozens of times that when a new high ranking person joins, their language quickly starts to become the defacto language of the org. If they like the "headwind" "tailwind" terminology, then it becomes what people everywhere start writing in the slides and how they discuss items of risk. You shouldn't be punishing people for asking for clarification (and there certainly a whole group of people that like to ask versus sitting silently then looking it up later). Hopefully there was more too it.

[blatantly]

Oh nice. A culture where asking questions is punished. If this was a problem don't fire people. Train them. Make sure everyone does required training. If they refuse then you may have a case for PIP.

Otherwise it is just landmine driven performance

Rant not at comment! But the situation of the comment. Hope it worked out for you!