Draft
Template
Build a department newsletter template
Describe the department, cadence, and readers; get a structure that shows the work without the jargon.
The prompt
Build a reusable template for the [department] newsletter.
Context: cadence: [monthly]. Sender: [name or team alias]. Standing sections: [e.g., what we shipped or delivered, what’s next, who’s new, a customer or stakeholder story, requests for help]. Readers outside the department also receive it.
Audience: the department and its internal stakeholders; assume readers don’t know our internal jargon.
Tone: proud but plain; show the work, skip the buzzwords.
Must include:
– A header with the department name, month, and a one-line summary
– Each standing section with a heading, a one-line description of what belongs there, and sample content
– A “how this helps the rest of the company” line in the delivery section
– A “we need your help” section with a clear ask format
– A footer with how to contribute
Constraints: sample content must reference plausible but clearly invented items.
Output: the template with each section in place, sample content marked [like this], and a short note on what changes each issue versus what stays fixed.
Works in
CoAuthorHow to use
The "how this helps the rest of the company" line is the difference between a team bulletin and something other teams read.
The prompt
Build a reusable template for the [department] newsletter.
Context: cadence: [monthly]. Sender: [name or team alias]. Standing sections: [e.g., what we shipped or delivered, what’s next, who’s new, a customer or stakeholder story, requests for help]. Readers outside the department also receive it.
Audience: the department and its internal stakeholders; assume readers don’t know our internal jargon.
Tone: proud but plain; show the work, skip the buzzwords.
Must include:
– A header with the department name, month, and a one-line summary
– Each standing section with a heading, a one-line description of what belongs there, and sample content
– A “how this helps the rest of the company” line in the delivery section
– A “we need your help” section with a clear ask format
– A footer with how to contribute
Constraints: sample content must reference plausible but clearly invented items.
Output: the template with each section in place, sample content marked [like this], and a short note on what changes each issue versus what stays fixed.
