Observations Feature Guide

Streamline Experimentation from Insight to Action: Capture, Test, and Archive Ideas with the Observations Feature

THIS ARTICLE WILL HELP YOU:

• Understand the Observations feature
• Get an overview of the feature
• Know the key technical features of Observations
• Use the Feature - Step-by-step guide
  • Add an Observation
  • Manage Observations
  • Convert Observations to Hypothesis
• Understand Hypothesis management and its status tracking
  • Move hypothesis to Knowledge Base
• Use Knowledge Base

Introduction

The Observations feature in the Convert app enables users to document insights, manage experiment ideas, and convert those ideas into actionable hypotheses. Designed to create a seamless flow from observation to hypothesis and finally to a comprehensive Knowledge Base, this feature helps teams visualize the life cycle of an idea and archive valuable insights.

Accessible through the Convert app, the Observations feature is a powerful tool to ensure that insights are captured and systematically developed into testable hypotheses.

Feature Overview

The Observations feature includes three main components within the Compass section:

1. Observations - Document initial insights directly.
2. Hypothesis - Convert observations into hypotheses for testing, adding various statuses for experiment outcomes. Note that you will still be able to add a hypothesis without this.
3. Knowledge Base - Convert proven hypotheses to serve as a historical record and knowledge resource.

Each of these stages is designed to guide users in recording, testing, and tracking valuable insights, ultimately strengthening experiment strategies.

Key Technical Features of Observations

• Adding Observations: Observations can be added either within the app. Each observation can include a name, description, URL, author, tags, and optional attachments (screenshots or other image files).
• Convert to Hypothesis: Observations can be transitioned into hypotheses, which marks them as ready for testing.
• Status Management: Hypotheses can be marked with statuses such as "Proven" or "Disproven," while observations include statuses for easier tracking.
• Notification: A toast message confirms the creation of observations visible for 5 seconds.
• Knowledge Base: Proven hypotheses can be moved to the Knowledge Base, creating a structured repository of experiment results.

Using the Observations Feature: Step-by-Step Guide

The following instructions will guide you through using the Observations feature, from capturing initial insights to archiving successful experiments.

1. Adding an Observation

Observations serve as the starting point in documenting insights. You can add an observation directly in the Convert app.

In the Convert App:

1. Go to the Compass section and click on Observations.
2. Click New Observation.
3. Fill out the observation details:
   • Name: Title of the observation.
   • Description (optional): Additional information or context.
   • Web Page URL: Reference URL.
   • Attachments (optional): Upload screenshots or relevant images.
   • Tags (optional): Tag/Label to identify the observation
4. Click Save to complete. 

2. Managing Observations

All saved observations appear under the Observations tab, where you can view and manage them easily. Each entry includes essential details like:

• Author: The creator of the observation.
• Date Added: When the observation was created.
• Status: Current state of the observation.
• Actions: Edit, tag, or convert the observation to a hypothesis.

To efficiently manage observations, you can:

• Use search and filter tools to sort observations by tags, author, or date.
• Hovering will change the background color to light purple and tags to white for visibility.

---

3. Converting an Observation to a Hypothesis

When an observation holds potential, it can be converted into a hypothesis for testing:

1. Open the observation you want to transition.
2. Click Convert to Hypothesis.
3. Confirm the conversion in the pop-up.

Once converted, hypotheses become available in the Hypothesis tab for testing.

Hypothesis Management and Status Tracking

In the Hypothesis tab, hypotheses can be managed and tracked. Additional statuses allow users to mark experiment outcomes clearly:

• Proven: Indicates successful hypotheses.
• Disproven: For hypotheses that did not meet success criteria.

To update the status, open the hypothesis and choose Proven or Disproven based on test results. Proven hypotheses can then be moved to the Knowledge Base, ensuring valuable insights are stored for future reference.

4. Moving Hypothesis to the Knowledge Base

The Knowledge Base stores successful hypothesis, turning them into accessible knowledge assets. Here’s how to move a hypothesis to the Knowledge Base:

1. Go to the Hypothesis tab.
2. Select the Move to Knowledge Base action.
3. The hypothesis will now be in the Knowledge Base with its name, creator, last update date, and summary.

The Knowledge Base entry provides a quick-reference resource for the results of previous tests.

Knowledge Base Usage

In the Knowledge Base tab, users can access the history of proven hypotheses. Each entry includes:

• Name: Title of the hypothesis.
• Creator: Person who created the hypothesis.
• Last Updated: Date of the last update.

The Knowledge Base serves as a valuable archive for experiment results, helping teams build on successful insights over time.