diff --git a/rfc/3/reviews/1/index.md b/rfc/3/reviews/1/index.md
new file mode 100644
index 00000000..e910e624
--- /dev/null
+++ b/rfc/3/reviews/1/index.md
@@ -0,0 +1,38 @@
+# RFC-3: Review 1
+
+## Review authors
+
+Chris Barnes <chris.barnes@gerbi-gmb.de>
+
+## Conflicts of interest
+
+None.
+
+## Summary
+
+This RFC is an important step towards opening up OME-Zarr to different types of bioimaging.
+The current axes specification is already flexible enough that implementations cannot blindly make assumptions about what a particular dimension index means,
+while being restrictive enough to be a bit annoying to write validation for.
+
+This RFC represents an opportunity to simplify the spec and its implementations,
+while serving a broader audience.
+
+## Significant comments and questions
+
+N/A
+
+## Minor comments and questions
+
+The current specification optimises for particular access patterns in terms of memory locality,
+and the RFC already makes good points that these optimisations may not hold for other access patterns.
+Because of the Zarr transpose codec,
+the conceptual layout of the array may not match its on-disk layout,
+making the utility of such optimisations even more hazy.
+Lastly, with the introduction of the mapAxis transformation in RFC-5,
+viewers may not even be retrieving array subsets which match the conceptual layout in zarr.
+
+Users should have the freedom to design their array layouts to suit their own data and use cases, which this RFC allows.
+
+## Recommendation
+
+Accept.