The Product Owner is accountable for maximising the value of the product and for the Product Backlog. You are not a junior PO, a ghost-writer of stories, or the person who 'translates the business.' You are the coach who keeps the backlog in a state the team can plan from.
Backlog health is the relationship
A healthy backlog is ordered, refined enough at the top to plan a Sprint, and honest about what will never happen. Your interest in that health is selfish in the good way: Planning collapses without it, and collapsed Planning becomes your impediment list. Offer techniques — story slicing, acceptance criteria, a Definition of Ready the team agrees — rather than taking the keyboard.
Refinement is a standing habit, not a rescue the day before Planning. Facilitate the conversation between the Product Owner and the Developers. The Developers say what they need to forecast. The Product Owner says why the item is next. You watch for epics wearing story costumes and for 'ready' items that still have an open legal question in the middle.
Stakeholder noise is a backlog problem. When five departments want five different next items, the Product Owner must order. You can facilitate the room, surface cost of delay, and stop the meeting from becoming a promise factory. You cannot order the backlog for them because a director frowned. If you do, you now own the product and they own the alibi.
Do not do the Product Owner's job
Writing the entire backlog because 'they are busy' trains them to stay busy elsewhere. Pair on the first ten items, then hand it back. If the organisation has not given the Product Owner time or authority, that is an organisational impediment. Name it. A proxy Product Owner who is actually you is how Scrum becomes a delivery team with a project manager and a part-time customer.
Do not become the decision-laundering service. 'The SM said the team cannot do that' is a sentence that should not exist. The Developers forecast. The Product Owner orders. You coach both. If a stakeholder wants a date for a scope that has never been refined, facilitate the trade-off: thinner slice, later date, or more capacity. Do not invent a date to end the meeting.
Keep the accountabilities visible in the Review. The Product Owner invites stakeholders and decides what the feedback does to the backlog. You facilitate time, turn-taking, and the difference between an opinion and a decision. Stealing the demo because you are better at slides is a compliment you should refuse.
Course complete — what's next
Partner on backlog health: ordered, refined at the top, honest in the tail. Facilitate refinement and stakeholder rooms. Do not write the backlog, launder decisions, or steal the Review. Shared outcome, separate accountabilities.
You now have the Scrum Master craft: the role, the events, impediments, coaching, and the Product Owner relationship. Use it on a live team this Sprint — pick one event to run for its actual job, and one impediment to write as cause, goal impact, and owner.