MultiHub Forum

I'm a project manager for a small software team, and we're preparing to release a major update for our productivity app next month. While our developers are thorough with technical changelogs, I'm struggling to write clear, user-friendly patch notes that effectively communicate the value of new features and bug fixes without overwhelming our non-technical user base. For others who write or manage this process, what's your strategy for structuring and drafting effective patch notes? How do you balance detail with readability, decide what merits highlighting versus a simple bullet point, and handle communicating less popular changes like deprecations or pricing adjustments? Are there any tools or templates you've found invaluable for maintaining consistency and ensuring nothing critical is missed between engineering and marketing?