Haha, i'd write a thousand pages of documentation before entering ticket hell. I fact I do put a lot of information into the ticket - they still won't read it though and i'll have to repeat myself 15 times to 5 different people.

The solution to this problem. . . I have no idea, but I'm sure they'll appoint another delivery manager who will get hired by the ones who already know fuck-all to know less than them.

I've found that the few managers who want documentation, get documentation, and the others who want tickets and "story points", get tickets and fictional bullshit - in general.___

[–] jj4211@lemmy.world 2 points 10 hours ago

Don't know about solving, but at least can see the signs:

If there's a lot of layers of middle management between you and the head of the company
There are people with oddly narrow scope of responsibilities, a scope that doesn't make any sense to be a dedicated full time job
Excessive numbers of "cute" acronyms to apply to everything and everyone

[–] Kissaki@programming.dev 2 points 13 hours ago (1 children)

The solution to this problem. . .

is that they have to create a support ticket with you, that you then put in progress, and you walk them through your documentation, and then log your time spent onto that ticket. (/s)

[–] naught101@lemmy.world 1 points 9 hours ago (1 children)

The asteroid would have wiped us out before you guys finished this long ass conversation

[–] Kissaki@programming.dev 1 points 8 hours ago

Let's put a story point estimation on that. Then we can extrapolate time range and risk.