-
Notifications
You must be signed in to change notification settings - Fork 593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gemorris / Human Experience Edits (Envisioning/Discovery) #868
base: main
Are you sure you want to change the base?
Conversation
@biancafbmd Here are the edits, please let me know if I need to adjust how this is submitted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! great contribution!
My main question is around the definition of discovery vs. envisioning. Previously, we looked at these as two different activities:
- Discovery is the process of identifying use-cases given a specific business setting (e.g., what kind of insights can we extract from this dataset)
- Envisioning is the process of detailing and framing a specific use case into a clear business and analytical question (e.g., can we identify patients who are likely to have complications).
This is just my own interpretation of the terms. I don't think this is the official definition.
If we do decide to rename envisioning to discovery, I would suggest updating the diagram and text on the top page for ML fundamentals, as it specifies this phase as "envisioning".
|
||
The main goals of the envisioning process are: | ||
The main goals of the discovery process are: | ||
* Establish existing understanding of the problem domain and the underlying business objectives |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The information is great, so thank you for the contribution.
In general, however, this text is a bit heavy to read - can we rewrite this in a bit more "Plain English" (see http://www.plainenglish.co.uk/how-to-write-in-plain-english.html for tips) to make sure our intentions come across correctly?
Examples of a few potential rewordings
- Understand the problem domain, and business objectives
- (? Not completely sure what this sentence means, but perhaps) State the limits of the problem?
- Explain how potential solutions may be used, and how we can measure the performance of the suggested solutions.
- Determine what data is available, and the origin and quality of the data. Take special care to understand if the data may be biased.
- ...
Similar with the rest of the document.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@TessFerrandez Noted, I will be able to get to this around the holidays
Co-authored-by: Omri Mendels <[email protected]>
Co-authored-by: Omri Mendels <[email protected]>
Co-authored-by: Omri Mendels <[email protected]>
Co-authored-by: Omri Mendels <[email protected]>
@gemorris are you planning on working on this, or should we abandon the PR for now? |
@gemorris--would be good to address the reviews and get this merged. |
What are you trying to address
Description of new changes