Skip to content
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

Open
wants to merge 13 commits into
base: main
Choose a base branch
from

Conversation

gemorris
Copy link
Contributor

@gemorris gemorris commented Aug 17, 2022

What are you trying to address

  • Additions to the Envisioning (Now Discovery) section of the playbook, as reviewed with @biancafbmd

Description of new changes

  • Significant content additions to incorporate the process and role of Human Experience within the Discovery stage of a project
  • Renamed the section as part of the edit and review process

@biancafbmd Here are the edits, please let me know if I need to adjust how this is submitted.
@gemorris gemorris marked this pull request as ready for review August 22, 2022 16:39
Copy link
Contributor

@omri374 omri374 left a 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
Copy link
Member

@TessFerrandez TessFerrandez Oct 19, 2022

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.

Copy link
Contributor Author

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

@TessFerrandez
Copy link
Member

@gemorris are you planning on working on this, or should we abandon the PR for now?

@omri374 omri374 removed the request for review from biancafbmd May 29, 2023 18:51
@day-jeff
Copy link
Contributor

@gemorris--would be good to address the reviews and get this merged.

@gemorris gemorris requested a review from shiranr as a code owner April 12, 2024 16:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants