diff --git a/current-work/README.md b/current-work/README.md
new file mode 100644
index 00000000..99422026
--- /dev/null
+++ b/current-work/README.md
@@ -0,0 +1,48 @@
+# The JSON Schema Organization's areas of focus or interest
+
+## About
+### What is this space?
+
+During an [Open Community Working Meeting](https://github.com/json-schema-org/community/issues/244), it was suggested that we could have a place for the core team (and maybe active community members?) to indicate which areas of their work most require attention from the core team members, in the form of GitHub Issues, Pull Requests, and Discussions.
+
+### Why?
+
+We concluded there was a LOT of activity taking place, and it was hard to get people to respond to the most immediately important things. It is indeed hard to focus on priority items when there are many new GitHub Issues and Discussions each week, especially for those who are community members or not working on JSON Schema full or even part time. It was suggested that by asking for one to three items of priority, we might find it easier to draw attention where we feel it is needed.
+
+### How?
+
+The process will initially be manual and require people to commit to the adjacent file which contains the list.
+The list will be used as it is found on Friday to help assist populate the following Monday's Open Community Working Meeting agenda.
+We may introduce automations to assist in this at a later point, or a medium that isn't storing data in a text file.
+
+#### How should the file be updated?
+
+Initially, it's expected that only those who are actively contributing should look at or add items to the list.
+To add items to the list, make commits directly in this repo.
+If you'd like permission to commit to the repo, please do ask on our [Slack server](https://json-schema.org/slack) in the `#community` channel.
+
+If you're adding to the list for the first time, please copy the below template, and add your GitHub username in alphabetical order.
+
+<details>
+  <summary>Show/hide template</summary>
+
+```md
+  **Link:** [Link to Github Issue, Pull Request, or Discussion]<br/>
+  **What?:** [The most simplest basic explanation of what the thing is about. Think a single tweets length or less.]<br/>
+  **Why does it matter?:** [Pitch why people should care about this too. Why do you care about it?]<br/>
+  **What can we do?:** [What would you like us to do in relation to this thing?]<br/>
+```
+
+</details>
+
+### Show me the details
+
+OK! Great! You want [the-list.md](./the-list.md)
+
+## More?
+
+@relequestual had some ideas on how automation could make this easier to use and encourage engagement, but it lead to a rabbit hole of questions and looking at docs and there wasn't any low-hanging fruit to be had. He intends to write up some suggestions on this soon.
+
+## I have a suggestion on this process...
+
+Great, let's hear it! Create a new [Discussion](https://github.com/json-schema-org/community/discussions) and let's talk.
diff --git a/current-work/the-list.md b/current-work/the-list.md
new file mode 100644
index 00000000..8d01df6b
--- /dev/null
+++ b/current-work/the-list.md
@@ -0,0 +1,14 @@
+# The JSON Schema Organization's areas of focus or interest
+
+## What is this document?
+
+Please see the adjacent [README](./README.md).
+
+## The lists of things
+
+### @relequestual
+
+**Link:** https://github.com/json-schema-org/community/pull/250<br/>
+**What?:** Creating this file and the guide on how to use it<br/>
+**Why does it matter?:** People feel it would be easier to see areas of focus if we highlight them<br/>
+**What can people do?:** Review and approve this PR! =]<br/>