diff --git a/README.md b/README.md
index 3c4f928..07485f5 100644
--- a/README.md
+++ b/README.md
@@ -8,6 +8,8 @@ Additionally, the planner gives additional documentation for general subjects (b
 
 This project is intended to be collaborative, see [Contribution](#Contribution) for details.
 
+Also, see the [Roadmap](roadmap.md) for a high level overview of our current goals.
+
 ## Cards
 
 Features take the form of **cards**. Each card holds some basic information:
diff --git a/roadmap.md b/roadmap.md
new file mode 100644
index 0000000..dce59fb
--- /dev/null
+++ b/roadmap.md
@@ -0,0 +1,57 @@
+FOSS Events Planner Roadmap
+--
+
+The FOSS events planner is meant to be a tool to help tech community
+leaders successfully build their own flexible events.
+It will highlight the many things that are possible and how to plan 
+them.
+
+There is currently no central place to go for _first-time organisers_
+to learn how to run a conference and get _actionable_ tasks out of it,
+without building a copy of an already existing event.
+The FOSS events planner tries to address this point.
+
+Using the FOSS events planner, people can pick _features_ for their
+conference and then get presented with a set of _tasks_. For example,
+if you want to run a conference with speaker selection, the tasks will
+include "running a call for proposals", "selecting the speakers", etc.
+Some tasks might have dependencies, for example, "determining a ticket price"
+requires that all tasks of the kind "find out what feature X costs" are done.
+
+With this technique, we're trying to get people to both be aware what's possible,
+but also be able to quickly filter by what's relevant for them.
+
+Milestones
+--
+
+## Name
+
+Come up with a catch name for the project.
+
+Tasks:
+- Suggest names
+- Pick a name
+
+## Website
+
+Have a teaser page for the project and register a domain.
+
+Tasks:
+- Register a domain
+- Design Website Content
+- Launch website
+
+## Finding contributors
+
+To make sure that we are not documenting our current conferences only, we should find additional contributors.
+
+Tasks:
+- Find additional writers
+- Find website contributors of all kinds
+
+## Finding users
+
+To make sure that our content is helpful, we need to find first users.
+
+Tasks:
+- Find a first user to collect feedback
\ No newline at end of file