I have to evaluate the training impact of a new software change they're making to the system. I do this sort of thing a lot, and it's usually pretty wild guesswork. I mean, the engineering section usually hasn't designed the changes yet, so the documentation people haven't written the manuals yet, so I have no references except maybe a letter someone writes explaining the just-defined problem and guessing about how they'll go about solving it. Not this time.
There's this button.
The purpose of the button is to...well, that's classified.
The change that's driving the need for the button is classified.
It's actually for a system that belongs to another company so the implementation is proprietary data, but we own the system that indicates the status of this other company's system, so it's our responsibility to fully describe the use of the mysterious button.
And the person at that company is unwilling to go into any details over the phone or email and no one's paying me to fly to his office, where I wouldn't have access to his building anyway.
So today, I have learned that 'fuck if I know' is not a professional response to a request for a work estimate. Hey, they didn't like 'that's classified,' either.
All that's left now is the magic dice... Which the probably won't like. I keep yelling 'Yahtzee!' during start of work meetings...