Update NN-notebook-v7/notebook-v7.md

Co-authored-by: Brian E. Granger <[email protected]>

NN-notebook-v7/notebook-v7.md

@@ -97,7 +97,21 @@ These user stories are guiding principles for the experience of using Notebook v
     - As a user, I want Jupyter Desktop to let me open my Jupyter editor (with any extensions I may have installed) as a single application and the Jupyter Console.
     - As a user, I can use other Jupyter-based tools in the native desktop experience, such as Consoles attached to Notebooks, in their own Native window.
     - As a user, I want Jupyter Desktop to be able to authenticate to and connect to any local or remote Jupyter Server, so I can have the same native Desktop experience against remote resources.
-
+## Decision making principles
+
+As we move forward with this plan and begin to make decisions about how to handle the visual design, functionality, and UX of Notebook V7 (how elements are styled, how do they behave, etc.) there will be tension between two paths:
+
+* **Option A**: Making Notebook V7 work and look exactly like Notebook v6
+* **Option B**: Making Notebook V7 work and look exactly like JupyterLab V4
+
+There will always be tradeoffs between these two options. To help us make these tradeoffs, we propose to look at the following questions:
+
+1. Is Option A or Option B be more accessible?
+2. If we were to design this from scratch today, would our design work and look more like Option A or Option B?
+3. Is Option A or Option B more maintainable?
+4. Is Option A or Option B be more secure?
+5. Will Option A confuse or cause friction Jupyter users who work in both Notebook V7 and JupyterLab v4?
+6. What is best for future Jupyter users who have never used either any version of Notebook or JupyterLab?
 
 ## Links and resources