For whatever reason, some people are just anti-documentation. Some people need it more than others. When it comes to documentation, no matter how good or important it is, you’ll never get 100% buy-in. There will always be at least one person who wants to wing it.
If I understand things correctly, you’re the first (and only) UXer at your company. The beauty of being a solo UXer is that you’re (usually) given quite a bit of latitude to do what works for you, regardless of what the rest of the business thinks.
You are the UX expert - and the only one at your company. Do what works for you.
Quite frankly, if you want documentation to make sure that you’re following a consistent practice and addressing all potential problems from a UX perspective, it doesn’t matter a fetid load of dingo’s kidneys what objections your PM/BI guy has.
If it were me, I’d create one of the sheets your referenced - which I love, by the way - as an artifact for my next refinement meeting and send it out to attendees with a note along these lines:
Hi everyone! I wanted to pass along my notes from our last meeting to the group. When I was putting together this summary, I noticed we [hadn’t defined ideal outcomes]/[didn’t discuss risk management]/[hadn’t talked about potential resources for the project]/[whatever other insight you might provide]. We’ll want to make sure that we touch on this in our next discussion on this project. If you have any questions or have anything to add, please let me know.
This works for a couple of reasons:
It shows you were actively participating in the meeting. Hey, you were the only one taking notes - and they were good enough you felt comfortable distributing them to the group.
It adds value by examining the process. More than likely, your group doesn’t really understand what pieces they’re missing. The chances are they’re missing these pieces consistently. By using documentation to point out areas that your team is missing, you’ll help the group as a whole and your users by ensuring that you’re considering all aspects of a project before you start work.
In my most recent article for UXMastery, How to Survive as Your Company’s Solo UXer, I talk a bit about the need to socialize the benefits of UX in your company. This is a great opportunity to do just that.