# Writing Weeknotes

### 💡Summary:

In this section, you'll find information on:

* How to optimise your writing for the web
* Resources to help you get started, including templates and timer slides
* The Open Working aned Re-Use Medium Publication

### 🗣Write the way real people talk

Above everything else, you should **always aim for your writing to be understood.** Find your own voice, and use it to interact with your community and peers in the sector. 

### 💭Use sub-headings 

We recommend that you begin with some subheadings, and work from there. By laying out a plan for yourself, you're less likely to get stuck later on. 

### ✍️Write first, edit later

This is not the next great American novel, it's a blog post! Set a timer if you need to, and don't let your inner critic step in until a first draft is ready. 

### 👥 Share your work

Although weeknotes are a great tool for self-reflection, you will get the most out of them by sharing your work! Receiving positive feedback can be a great motivator to keep going. 

Have a look at what others in our network have been sharing: 

🔗[Visit the Open Working and Re-Use Medium Publication](https://medium.com/open-working-reuse) 

<figure><img src="https://images.unsplash.com/photo-1522881451255-f59ad836fdfb?crop=entropy&#x26;cs=srgb&#x26;fm=jpg&#x26;ixid=M3wxOTcwMjR8MHwxfHNlYXJjaHw5fHx3cml0aW5nfGVufDB8fHx8MTY4ODAyODY5MXww&#x26;ixlib=rb-4.0.3&#x26;q=85" alt=""><figcaption></figcaption></figure>

## Getting started

Most importantly, **practice.** The sooner you can make weeknotes part of your routine, the easier they'll be to write.

Try not to overthink what you share. If you're not confident about your writing, ask a colleague to be your beta reader.

## Resources

⏰[ Google slides with timers](https://docs.google.com/presentation/d/1kRTx_3_Fl7t6n3W4F8gbAPLE6q5pFgx0q8oS3cxub5c/edit#slide=id.p)&#x20;

Write and publish your weeknotes in 30 minutes with this guide!

🔗[Visit the Open working blog and weeknotes templates ](https://docs.google.com/document/d/1oHdCJ4MCTOg9-ZTijf-DuD9xFHB1cwI8I4jJEfo8Uls/edit#heading=h.ick16auzx1z9)

{% embed url="<https://docs.google.com/document/d/1oHdCJ4MCTOg9-ZTijf-DuD9xFHB1cwI8I4jJEfo8Uls/edit#heading=h.ick16auzx1z9>" %}

### Further Writing Resources👇

{% embed url="<https://medium.com/wethecatalysts/how-to-write-a-blog-post-without-even-trying-39f31190682b>" %}

{% embed url="<https://www.thecatalyst.org.uk/resource-articles/weeknotes>" %}

{% embed url="<https://agilecommshandbook.com/>" %}

{% embed url="<https://visitmy.website/2020/01/25/blogging-working-open/>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wearecast.gitbook.io/open-working-toolkit/doing-open-working/how-to-do-open-working.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.