- Look through case studies on the website and pick something you understand and is interesting to you
- Double-check with the Creative Director if it’s a suitable one for the content priorities of the sprint (or ask for some recommendations)
- Find all related documents: Miro board, Figma files, User testing Report(s) any other links that were shared e.g. Loom walk-troughs or product documentation (sometimes they might be in the archived channel on Discord)
- Create a notion page as a card on the Content Calendar (Draft for the week- column). This is where to place all content once you start reading through the case study documents
- Add reference documents in the card - figma files, miro boards, report links etc.
- Familiarize yourself with the project:
- Start with the Miro board and read through the whole first print workshop. Try to get as much context as possible. Understand the product and client goals.
- If you have any specific questions, you can hit up the creative director for that specific project for some clarifications. Try to be on point and only ask things that you couldn’t find answers to anywhere else, use their time as efficiently as possible.
- Once you read through the sprint questions and long-term goal, look through the User journey exercise. Familiarize yourself with the high-level flow - understand why it’s this way.
- Then you can either look through the Figma prototype file or open the Report.
- Pick Interesting Insights - Think about what would be useful for our audience to read, clear universal problems and what impresses you as a writer. You can look for some easy wins, thing you personally understand. Here’s some ideas on types of posts or pointers to potential good content (but don’t feel you should limit yourself to only those):
Try to be clear about what the unique valuable insight is. Some easy sources of content you can directly refer to are: quotes from user research report, highlight sprint goals that were a win from the report, screenshots.
- Unique UI elements that "hit the nail on the head”
- Principles the designers applied that are important for web3
- Insights that came from the user testing - lessons learned (and how we fixed it, or recommended to fix it)
- why does the team choose certain key elements for the user flow
- interesting product strategy
- Double-check for duplicates - review all posts and highlight the most unique ones. (sometimes you’d see the same point in a few places - just pick the best example)
- Add dummy visuals - add screenshots of the product that are directly connected to the point you’re making (either from the figma file or the report). This will hel the designer to orient themselves what type of visuals to add and where to find them
- Add social media tags (name of the client, key words, etc.)
- Create a separate notion page for each insight (and to-be-post) you found and place it in “In Progress”
- Create a title. Make it as clear as possible. Avoid clickbait-y framings (you can find some tips on the tone of voice in “Key principles for external communication”.
- Expand on each point providing a concise message (avoid more than one point per sentence). And format into a complete post.
- Test the copy by putting it in Typefully. This will help to make sure each point/sentence fits in a tweet and the thread doesn’t need to be cut mid-sentence.
- Create a caption with a summary for Instagram (and sometimes for the first tweet in a thread)
- Check if the text fits in Instagram (check in Figma how other visual posts were laid out to get a sense on text capacity.
Structure of the posts: