Implementing software is one core aspect of the SRE role. Often this software will be used by multiple teams. SREs need to make sure that what they build is easy to use and understandable by all users. Product Requirement Documents (PRDs) can help collect and prioritize requirements for tooling and other software. But how do you write a good PRD?