diff --git a/20200723095845-software_development.org b/20200723095845-software_development.org
index a38cec1..735f1b9 100644
--- a/20200723095845-software_development.org
+++ b/20200723095845-software_development.org
@@ -1,5 +1,6 @@
 :PROPERTIES:
 :ID:       9e68d422-cced-4177-96d1-90f777b9a493
+:ROAM_ALIASES: "Developing Software"
 :END:
 #+title: Software Development
 
diff --git a/20210825152445-identifying_product_questions_when_developing_software.org b/20210825152445-identifying_product_questions_when_developing_software.org
new file mode 100644
index 0000000..826a14c
--- /dev/null
+++ b/20210825152445-identifying_product_questions_when_developing_software.org
@@ -0,0 +1,11 @@
+:PROPERTIES:
+:ID:       86e74173-cce7-40ff-9a51-c4a3e817b030
+:END:
+#+title: Identifying product questions when developing software
+
+In the course of [[id:9e68d422-cced-4177-96d1-90f777b9a493][Developing Software]], I find myself making a multitude of
+decisions. Decisions addressing technical aspects of the software (how this gets
+built) are mine to make (and, ideally, [[id:b7c89b7b-5d3a-4cd9-9d26-8107b32ba5a0][document]]), but decisions addressing
+behavioural aspects of the software (how this works) need to be identified and
+raised to the project's stakeholders so that the resulting program doesn't
+conflict with what the stakeholders want it to do.