diff --git a/helm/README.md b/helm/README.md
index 6604aff56..b1483c6f4 100644
--- a/helm/README.md
+++ b/helm/README.md
@@ -1,73 +1,93 @@
-# Dagster
+# Dagster Helm
 
-[Dagster](https://github.com/dagster-io/dagster) is a Python library for building data applications.
+## TL;DR
 
-## Install Chart
+### Installing from remote
+```bash
+helm repo add dagster https://dagster-io.github.io/helm
 
-To install the Dagster chart into your Kubernetes cluster:
+helm install my-release dagster/dagster \
+    --namespace dagster \
+    --create-namespace
+```
 
+### Installing from source
 ```bash
-helm install --namespace "dagster" dagster /helm/dagster/
+helm install my-release . \
+    --namespace dagster \
+    --create-namespace
 ```
+## Introduction
+[Dagster](https://github.com/dagster-io/dagster) is a Python library for building data applications. This chart will bootstrap a Dagit web server deployment on a Kubernetes cluster using the Helm package manager.
 
-After installation succeeds, you can get the chart status with:
+In addition, our helm chart allows for Dagster configuration such as:
+ - Deploying user code containers separately from Dagster system components
+ - Specifying the Dagster run launcher
+ - Specifying the Dagster scheduler to handle recurring pipeline runs
 
-```bash
-helm status dagster
-```
+## Prerequisites
+### Setup a Kubernetes Cluster
+Please refer to the Kubernetes [getting started guide](https://kubernetes.io/docs/setup/) to set up and run a Kubernetes cluster.
 
-To remove Dagster:
+### Installing Helm
+We use Helm to manage our Kubernetes application in a configurable, replicable, and sharable way. Helm can be installed by following the [Helm installation guide](https://helm.sh/docs/intro/install/).
+
+### Adding the Dagster Repo
+To download and install the Dagster charts, use the following command:
 
 ```bash
-helm delete dagster
+helm repo add dagster https://dagster-io.github.io/helm
 ```
 
-The Dagster chart configures a Dagit web host Deployment/Service, Celery worker Deployment, and
-various other Kubernetes objects to support executing Dagster pipelines within a Kubernetes cluster.
-
-Currently, this chart also installs RabbitMQ and PostgreSQL Helm charts as dependencies; a future
-update of this chart will support "bring your own database/queue" configuration.
+### Using Helm
+We can now use the Helm client to install the Dagster chart! Refer to the guide on [Using Helm](https://helm.sh/docs/intro/using_helm/) for an explanation of useful Helm concepts.
 
-## Helm Chart Configuration
+Here, we install a release of the Dagster chart named `my-release`, under the Kubernetes namespace `dagster`:
 
-Full and up-to-date documentation can always be found in the comments of the `values.yaml` file.
+```bash
+helm install my-release dagster/dagster \
+    --namespace dagster \
+    --create-namespace
+```
 
-See more detailed notes on configuring environment variables in the section below.
+### Customizing the Release
+[Settings can configured](https://helm.sh/docs/intro/using_helm/#customizing-the-chart-before-installing) to customize the Dagster release.
 
+To see the full list of configurable settings, check out the `values.yaml` file. Documentation can be found in the comments.
 ## Environment Variables
 
 We support two ways of setting environment variables: either directly add them to `values.yaml`, or
 provide an external ConfigMap/Secret object to mount using `envFrom:` in the chart pods:
 
 - `job_runner.env.SOME_ENV_VAR`: Set `SOME_ENV_VAR` in the Celery Worker and Job pods
 - `dagit.env.SOME_ENV_VAR`: Set `SOME_ENV_VAR` in the Dagit pod
 - `job_runner.env_config_maps`: names of ConfigMaps to use for environment variables in the
   Celery Worker and Job pods
 - `job_runner.env_secrets`: names of Secrets to use for environment variables in the
   Celery Worker and Job pods
 - `dagit.env_config_maps`: names of ConfigMaps to use for environment variables in the Dagit pod
 - `dagit.env_secrets`: names of Secrets to use for environment variables in the Dagit pod
 
 These will be loaded in the following order, and in the case of conflicts, subsequent loads will
 take priority:
 
 1. Base environment; custom env vars specified in `values.yaml`
 2. ConfigMap environment variables, loaded in order of the ConfigMaps specified
 3. Secret environment variables, loaded in order of the Secrets specified
 
 Thus, for example, if `CUSTOM_ENV_VAR` appears in `values.yaml`, a ConfigMap, and two secrets, the
 last secret loaded will be the value of `CUSTOM_ENV_VAR` at runtime.
 
 ### Implementation Notes
 
 This chart installs a base pair of Kubernetes ConfigMap objects for environment variables. These
 are:
 
 - `dagster-job-runner-env`: Environment variables for the Celery workers and the spawned Job pod
 - `dagster-dagit-env`: Environment variables for the Dagit Deployment pod
 
 Each of these ConfigMaps set `DAGSTER_HOME` by default, and also enable user-specification of
 additional environment variables directly in `values.yaml`.
 
 Additionally, this Helm chart supports pulling in other external environment variables from external
 Kubernetes ConfigMaps and Secrets.