diff --git a/src/development/design-doc-research-branch-redux.md b/src/development/design-doc-research-branch-redux.md
new file mode 100644
index 0000000..2083207
--- /dev/null
+++ b/src/development/design-doc-research-branch-redux.md
@@ -0,0 +1,32 @@
+Research Branch Redux
+=====================
+
+This document addresses concerns regarding the upstream implementation of scientific research branches and their contents, and proposes a remodel of this research. 
+This proposal does not alter any current existing mechanics behind research, only restructuring the existing content.
+
+## Proposal
+
+In an attempt to remodel Moffstation's research, it is proposed that research branches should be themed based on the 'type of energy' relevant to each individual research, rather than dividing the researches into silos based on intended target audience.
+As a result, the following new branches would be created to replace the existing research branches:
+- Mechanical, representing researches that function based on kinetic movement.
+- Electical, representing researches that interact with digital systems.
+- Chemical, For researches that power or are powered by chemical interactions.
+- Bluespace, highlighting researches that are cutting edge and more experimental in nature.
+
+In addition, the following criteria are defined for researches within Moffstation:
+- The contents of a research should include technology that serves an intended function.
+- A research should be a new feature or an upgrade from an existing feature.
+
+Finally, research options should be divided into three tiers:
+- Tier one research should focus on technologies that improve the individual player experience, through new tools or small quality of life changes.
+- Tier two expands upon tier one with a larger focus on departments as a whole, augmenting and changing how they function and their gameplay loop.
+- Tier three researches should radically redefine the station experience, affecting multiple departments or large groups of players.
+
+## Reasoning
+
+### Issues with current implementation
+
+### How this proposal will fix this issue
+
+## Considerations
+