From a4c40e8ed568b7fa90b8b130af0c5663c7602c9f Mon Sep 17 00:00:00 2001
From: Nathanael Holliday <100959072+hollidayn@users.noreply.github.com>
Date: Tue, 13 Sep 2022 11:38:50 -0500
Subject: [PATCH] Update README.md (#7724)

This is the update taken from the audible text from the start of chapter 4 in the audio book by Jony Ive (at least as I understood it).
---
 handbook/company/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/handbook/company/README.md b/handbook/company/README.md
index bd6be3e4e2..8e14ac9759 100644
--- a/handbook/company/README.md
+++ b/handbook/company/README.md
@@ -200,6 +200,7 @@ Here's why we use a wireframe-first approach at Fleet.
   - the latest reactions from users
   - all of the motivations and discussions from the previous rounds of wireframe revisions that were thrown away
   - how the UI has evolved in previous releases to better serve the people using and building it
+- Wireframing is important for both maintaining the quality of our work and outlining what work needs to be done.
 - With Figma, thanks to its powerful component and auto-layout features, we can create high-fidelity wireframes - fast. We can iterate quickly without costing more work and less [sunk-cost fallacy](https://dictionary.cambridge.org/dictionary/english/sunk-cost-fallacy).
 
 ### Why do we use one repo?