XS✔ ◾ changes from Adam (#6717)

* Structure changes

* Add files via upload

* Update rule.md

* Delete rules/ask-clients-approval/MJ-signature-mockup.jpg

too low quality

* remove low quality image

rules/ask-clients-approval/rule.md

@@ -25,31 +25,46 @@ A person's signature is extremely valuable. Getting a signature is hard work. Sa
 
 Requesting a **signature** (or just an initial) on non-contractual type documents (especially screenshots, mockups, or data-schemas) is very beneficial.
 
+## The Signature Dance
+
+There are 3 steps
+1. Ask for a signature
+2. Get the requirements in writing
+3. Get the signature in writing
+
+### 1. Ask for a signature
+
 Getting paper signed is the “Dinosaur Method”. These days there are 2 main scenarios:
 - The "Checked by {{ NAME }}" system for when you are with the person or sharing screens with the person as per the ['Checked by'](/checked-by-xxx) rule 
 - The "Test Please" system for when it's a big job or it needs to be done asynchronously as per the ["Test Please" rule](/conduct-a-test-please) rule
 
-### Is a signature required?
-
-::: greybox
-
-Requesting a client's initials is encouraged for all projects, but **required** for fixed-price projects as their initials on the original specifications would show that everyone was aligned and approved the specifications.
+### 2. Get the requirements in writing
 
-- If the client pushes back _"Why am I signing it?"_ reply with:  
-  _"This is not a legal document but a good practice to do before we start coding. It is cheaper to change the mockups now. Fixing changes with the UI now, can save a lot of money later."_
+You shouldn't rely on links to a mockup because the design can change... same problem as linking to Terms and Conditions. Therefore the better version is create an email with screenshots/content and add "Checked by {{ PRODUCT OWNER NAME }}"
 
-:::
+### 3. Get the signature in writing
 
 When you ask a client to review a mockup for example, they will generally take a cursory glance, perhaps make a comment or two and then move on to something else. 
 
 Asking them to initial/sign the document/file always makes them take a second or third look, ask someone else, or at least spend a few more minutes working out whether it's correct or not.
 
-**Note:** Please make sure you have a documented “Test Pass”. A verbal "Test Pass" is not sufficient and an implied "Test Pass" because you actioned their feedback is also not sufficient.
+Make sure you have a documented “Test Pass”. A verbal "Test Pass" is not sufficient and an implied "Test Pass" because you actioned their feedback is also not sufficient.
+
+::: greybox
+
+#### Explaining to the client why they need to sign
+
+The best scenario is to give the client plenty of warning, explain the engagement process and how you will work together to develop the specs. Once, you're both in agreement, you'll both sign. Aim to make it a nice "co-signing" experience. 
+
+Requesting a client's initials is encouraged for all projects, but **required** for fixed-price projects as their initials on the original specifications would show that everyone was aligned and approved the specifications.
+
+- If the client pushes back _"Why am I signing it?"_ reply with:  
+  _"This is not a legal document but a good practice to do before we start coding. It is cheaper to change the mockups now. Fixing changes with the UI now, can save a lot of money later."_
 
-::: info
-**Warning:** You shouldn't rely on links to a mockup because the design can change... same problem as linking to Terms and Conditions. Therefore the better version is create an email with screenshots/content and add "Checked by {{ PRODUCT OWNER NAME }}"
 :::
 
 Training clients to review the work carefully leads to better quality projects.
 
+![Figure: Getting the client's signature ensures more accurate requirements](/MJ-rule-UI-mockup.jpg)
+
 ![Figure: A signature from Michael Jackson is very valuable but hard to obtain](SuccessfulProjects\_Signature.jpg)