diff --git a/docs/next/src/pages/overview/io-managers/io-managers.mdx b/docs/next/src/pages/overview/io-managers/io-managers.mdx
--- a/docs/next/src/pages/overview/io-managers/io-managers.mdx
+++ b/docs/next/src/pages/overview/io-managers/io-managers.mdx
@@ -8,7 +8,7 @@
 
 # IO Managers
 
-Dagster solids have [inputs and outputs](/overview/solids-pipelines/solids#solid-inputs-and-outputs).  When a solid produces an output, what happens to it?  When a solid needs an input value, how is it loaded?  <PyObject module="dagster" object="IOManager" />s, <PyObject module="dagster" object="InputManager" />s, and <PyObject module="dagster" object="OutputManager" />s let the developer decide.
+Dagster solids have [inputs and outputs](/overview/solids-pipelines/solids#solid-inputs-and-outputs).  When a solid produces an output, what happens to it?  When a solid needs an input value, how is it loaded?  <PyObject module="dagster" object="IOManager" />s and <PyObject module="dagster" object="InputManager" />s.
 
 These APIs make it easy separate code that's responsible for logical data transformation from code that's responsible for reading and writing the results.  Solids can focus on business logic, while IO managers handle I/O.  This separation makes it easier to test the business logic and run it in different environments.
 
@@ -28,25 +28,10 @@
 
 IOManagers are [resources](/overview/modes-resources-presets/modes-resources), which means users can supply different IOManagers for the same solid outputs in different situations.  For example, you might use an in-memory IOManager for unit-testing a pipeline and an S3IOManager in production.
 
-## Input managers and output managers
+## Input managers
 
 <PyObject module="dagster" object="RootInputManagers" />s are user-provided objects that are responsible for loading the inputs of solids whose inputs are not hooked up to an upstream solid's output.
 
-<p/>
-
-<PyObject module="dagster" object="OutputManager" />s are for situations where you need to control how outputs are handled independently of how inputs are loaded.  They're useful for handling the outputs at the end of a pipeline.
-
-<p/>
-
-<PyObject module="dagster" object="IOManager" /> is an interface that inherits from both the <PyObject module="dagster" object="InputManager" /> and <PyObject module="dagster" object="OutputManager" /> interfaces:
-
-<p/>
-
-<p align="center">
-  <img src="/assets/images/overview/io-managers/manager-venn-diagram.png" width="600px"/>
-</p>
-
-
 ## Setting a pipeline-wide IO manager
 
 By default, all the inputs and outputs in a pipeline use the same IOManager.  This IOManager is determined by the <PyObject module="dagster" object="ResourceDefinition" /> provided for the `"io_manager"` resource key.  `"io_manager"` is a resource key that Dagster reserves specifically for this purpose.
diff --git a/docs/sections/api/apidocs/io-managers.rst b/docs/sections/api/apidocs/io-managers.rst
--- a/docs/sections/api/apidocs/io-managers.rst
+++ b/docs/sections/api/apidocs/io-managers.rst
@@ -42,20 +42,6 @@
     :members:
 
 
-Output Managers
----------------
-
-Output managers are user-provided objects that specify how to handle step outputs.
-
-.. autodecorator:: output_manager
-
-.. autoclass:: OutputManager
-    :members:
-
-.. autoclass:: OutputManagerDefinition
-    :members:
-
-
 Built-in IO Managers
 ------------------------
 
diff --git a/python_modules/dagster/dagster/__init__.py b/python_modules/dagster/dagster/__init__.py
--- a/python_modules/dagster/dagster/__init__.py
+++ b/python_modules/dagster/dagster/__init__.py
@@ -121,11 +121,6 @@
 from dagster.core.storage.input_manager import InputManager, InputManagerDefinition, input_manager
 from dagster.core.storage.io_manager import IOManager, IOManagerDefinition, io_manager
 from dagster.core.storage.mem_io_manager import mem_io_manager
-from dagster.core.storage.output_manager import (
-    OutputManager,
-    OutputManagerDefinition,
-    output_manager,
-)
 from dagster.core.storage.pipeline_run import PipelineRun
 from dagster.core.storage.system_storage import (
     build_intermediate_storage_from_object_store,
@@ -334,9 +329,6 @@
     "InputManager",
     "InputManagerDefinition",
     "input_manager",
-    "OutputManager",
-    "OutputManagerDefinition",
-    "output_manager",
     "fs_io_manager",
     "mem_io_manager",
     "custom_path_fs_io_manager",
diff --git a/python_modules/dagster/dagster_tests/core_tests/storage_tests/test_output_manager.py b/python_modules/dagster/dagster_tests/core_tests/storage_tests/test_output_manager.py
--- a/python_modules/dagster/dagster_tests/core_tests/storage_tests/test_output_manager.py
+++ b/python_modules/dagster/dagster_tests/core_tests/storage_tests/test_output_manager.py
@@ -13,7 +13,6 @@
     ModeDefinition,
     Output,
     OutputDefinition,
-    OutputManagerDefinition,
     RetryRequested,
     dagster_type_materializer,
     execute_pipeline,
@@ -23,8 +22,7 @@
     solid,
 )
 from dagster.core.instance import InstanceRef
-from dagster.core.storage.input_manager import input_manager
-from dagster.core.storage.output_manager import output_manager
+from dagster.core.storage.output_manager import OutputManagerDefinition, output_manager
 
 
 def test_output_manager():