diff --git a/proposals/project-management.md b/proposals/project-management.md
new file mode 100644
index 000000000..6542c2c8d
--- /dev/null
+++ b/proposals/project-management.md
@@ -0,0 +1,31 @@
+# Project Management Process
+
+The text below is copied from <https://www.w3.org/WoT/IG/wiki/index.php?title=WG_WoT_Thing_Description_WebConf>.
+
+The main question is "How do we organize the work?". 
+
+## Opinions
+
+- Ege Korkan:
+  - Ideally, we should discuss our requirements and what people want to see. Mandating a mechanism that the moderators like but is disliked by everyone else should be avoided.
+  - The goal is to make it more systematic than "copy-pasting the agenda, look into issues and PRs"
+  - The process for generating features from use cases should be taken into account
+  - We can use a tool like GitHub Projects. A premature example is available at https://github.com/orgs/w3c/projects/31
+- Mahda Noura: Only assigning an issue is not enough, because the number can increase and we can lose oversight/prioritization.
+- Cristiano Aguzzi: Assigning should happen when you know that person can do it in 1-2 weeks.
+- Jan Romann: Splitting issues definitely helps. We should limit the workload of an issue in the beginning or use checkboxes per small item and open a "spinoff" issue.
+- Kazuyuki Ashimura: We should think of what we have been doing so far.
+
+## Proposal
+
+- An MVP is one place to look at the list of "work" to do in a short period. We can make sure to limit the load of a person per 1-2 week timeframe and thus prioritize certain issues/topics.
+- A prioritization should happen and should be aligned with use cases and requirements, i.e. how do we choose the small list of work to do
+
+## Procedure
+
+Concrete procedure text will come here.
+
+## To Do
+
+- We should analyze https://github.com/w3c/strategy/projects/2 and https://github.com/orgs/w3c/projects/13
+- Create issue templates for necessary items