(doc): starts communication pipeline

README.md

@@ -78,6 +78,7 @@ Smoke tests coverage should be increased and refined but always managable
 
 Mobile automated E2E tests coverage should be maintained as cypress test are maintained
 - release schedule of mobile app will make e2e testing different from cypress testing but a similar pipeline should be established
+- The Mobile development team currently favors moving our mobile automated E2E tests to [Detox](https://github.com/wix/Detox)
 
 #### New Feature Acceptance Testing
 
@@ -110,6 +111,8 @@ An API testing tool popular with the development team is [Postman](https://www.g
 
 ## Communication Quality Assurance
 
+Our communication pipeline in comparison to our code pipeline needs a lot of work. 
+
 ### Current Process
 
 ### Proposed Modifications

[Bill Ottman]

I think rather than a critical statement like this which doesn't belong in docs, we need a clear and concise process recommendation instead?