examples/company-newsletter.md
3.2 KB查看排版效果| 1 | ## Instructions |
| 2 | You are being asked to write a company-wide newsletter update. You are meant to summarize the past week/month of a company in the form of a newsletter that the entire company will read. It should be maybe ~20-25 bullet points long. It will be sent via Slack and email, so make it consumable for that. |
| 3 | |
| 4 | Ideally it includes the following attributes: |
| 5 | - Lots of links: pulling documents from Google Drive that are very relevant, linking to prominent Slack messages in announce channels and from executives, perhgaps referencing emails that went company-wide, highlighting significant things that have happened in the company. |
| 6 | - Short and to-the-point: each bullet should probably be no longer than ~1-2 sentences |
| 7 | - Use the "we" tense, as you are part of the company. Many of the bullets should say "we did this" or "we did that" |
| 8 | |
| 9 | ## Tools to use |
| 10 | If you have access to the following tools, please try to use them. If not, you can also let the user know directly that their responses would be better if they gave them access. |
| 11 | |
| 12 | - Slack: look for messages in channels with lots of people, with lots of reactions or lots of responses within the thread |
| 13 | - Email: look for things from executives that discuss company-wide announcements |
| 14 | - Calendar: if there were meetings with large attendee lists, particularly things like All-Hands meetings, big company announcements, etc. If there were documents attached to those meetings, those are great links to include. |
| 15 | - Documents: if there were new docs published in the last week or two that got a lot of attention, you can link them. These should be things like company-wide vision docs, plans for the upcoming quarter or half, things authored by critical executives, etc. |
| 16 | - External press: if you see references to articles or press we've received over the past week, that could be really cool too. |
| 17 | |
| 18 | If you don't have access to any of these things, you can ask the user for things they want to cover. In this case, you'll mostly just be polishing up and fitting to this format more directly. |
| 19 | |
| 20 | ## Sections |
| 21 | The company is pretty big: 1000+ people. There are a variety of different teams and initiatives going on across the company. To make sure the update works well, try breaking it into sections of similar things. You might break into clusters like {product development, go to market, finance} or {recruiting, execution, vision}, or {external news, internal news} etc. Try to make sure the different areas of the company are highlighted well. |
| 22 | |
| 23 | ## Prioritization |
| 24 | Focus on: |
| 25 | - Company-wide impact (not team-specific details) |
| 26 | - Announcements from leadership |
| 27 | - Major milestones and achievements |
| 28 | - Information that affects most employees |
| 29 | - External recognition or press |
| 30 | |
| 31 | Avoid: |
| 32 | - Overly granular team updates (save those for 3Ps) |
| 33 | - Information only relevant to small groups |
| 34 | - Duplicate information already communicated |
| 35 | |
| 36 | ## Example Formats |
| 37 | |
| 38 | :megaphone: Company Announcements |
| 39 | - Announcement 1 |
| 40 | - Announcement 2 |
| 41 | - Announcement 3 |
| 42 | |
| 43 | :dart: Progress on Priorities |
| 44 | - Area 1 |
| 45 | - Sub-area 1 |
| 46 | - Sub-area 2 |
| 47 | - Sub-area 3 |
| 48 | - Area 2 |
| 49 | - Sub-area 1 |
| 50 | - Sub-area 2 |
| 51 | - Sub-area 3 |
| 52 | - Area 3 |
| 53 | - Sub-area 1 |
| 54 | - Sub-area 2 |
| 55 | - Sub-area 3 |
| 56 | |
| 57 | :pillar: Leadership Updates |
| 58 | - Post 1 |
| 59 | - Post 2 |
| 60 | - Post 3 |
| 61 | |
| 62 | :thread: Social Updates |
| 63 | - Update 1 |
| 64 | - Update 2 |
| 65 | - Update 3 |
文件内容是平台检查时读出的文本，只供查看。平台不会运行包里的任何脚本或程序。
