BTS here - And let me say what a lot of us are too burnt out to keep repeating: Operations doesn’t know sh-t. Requirements come in half-baked, vague, or flat-out wrong. Or you blindly approve BRD’s with incorrect requirements. The amount of rework we do is unreal. I shouldn’t find out during UAT that you wanted a line level denial vs a claim level one. It was in the BRD. It clearly started - APPLY CLAIM LEVEL DENIAL.
And lately? Business leadership is greenlighting massive projects (👋 Duals!) without even engaging health plans. No reviews, no approvals, no UAT sign-off. Just “go configure it like one contract” - like we didn’t all pass 6th grade and know Medicare Medicaid. You still need to generate encounters. You still need to follow state rules. Just because CMS doesn’t deny it doesn’t mean the state won’t. Come on.
But the best part? The same people who can’t write a coherent user story will @ me five times for a story status when you could literally search it yourself. Especially when your request impacts 7 claims a month and somehow you still expects top priority. If I had a dollar for every time someone emailed me about a Jira story they could've just looked up themselves, l'd fund a full-time training program on basic tool usage.
That said - yeah, some POs are trash. People rolling out “modernized” systems with less functionality than what existed before, just because they never bothered to understand the actual need. You don’t need to mimic the old thing - just ask the business what they want tomorrow to look like. Wild concept, I know.
And please… don’t IM me asking where to find a procedure code description. You have Google. Use it.