Versions Compared

Old Version 33

changes.mady.by.user Faqir Bilal

Saved on

compared with

New Version Current

changes.mady.by.user Jenna Makowski

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Project Acceptance Criteria

A slide deck that succinctly articulates a foundational Open edX Product Narrative. This narrative will be used to guide decisions around the Core Product Offering.

Meetings

Date

Agenda

Action items & decisions

  1. Why are we building the product narrative?

    1. It’ll help us define the core product

    2. It’ll inform the product roadmap

    3. It’ll help us articulate the product vision

  2. What things should we cover in our competitor analysis

    1. Verticals (higher ed, K12, etc.) and use cases (scale, async/sync learning, etc.)

    2. Things that Open edX does really well today (so not functionality and support for on-campus learning)

  3. Areas we feel we should focus on:

    1. Scale

    2. Interoperability - integratation with the existing stack of tools and services (example: MIT is using Instructure to support on-campus learning, they have Open edX-powered MIT residential, and a number of platforms targetting non-matriculated learners

Action items:

Decisions:

  1. Have the final deliverable ready for distribution by November 8, 2022

  1. Key decision: Hold off an a competitor/gap analysis. Focus first on identifying the fundamental needs and associated features required to support the primary Open edX use case - what Open edX was designed to do.

  2. Primary use case we will start with: Deliver online courses asynchronously and at scale, with scale defined as [number of learners total, number of learners at a time, and must also parse edX from rest of ecosystem].

  3. Deliverable: A mindmap/diagram that answers the question: What does each user/persona need in order to accomplish the primary use case? From this we will:

    1. Distill a list of core features that will drive the definition of a Core Product Offering

    2. Enable granular mapping of the Core Product Offering to the Tech Core

    3. Lay the groundwork for writing the product narrative

    4. Lay the ground for gap analyses for secondary use case

  4. Narrative challenge: Open edX is a generic core that can support many broad use cases. Look to similar organizations for inspiration on framing, messaging such as wordpress.org

  5. Reviewed mapping of features created by Marco for edX. (Source)

  •  Complete the primary use case mind map for 3 key personas: https://www.mindmeister.com/map/2385779758?t=FnCLcUqgZ7
    -Define the persona, any sub-personas or related personas (based on team structure of actual organizations)

    -Create an exhaustive list of things/jobs/tasks the said persona needs to do to accomplish the use case successfully.

    - List and organize features related to those tasks

    Faqir Bilal learner
    Santiago Suarez admin
    Jenna Makowski author
    Deadline:

    (Follow-up task: “peer review” each other’s personas and lists)

(Follow-up task: Identify common functionalities and group them on the mind map to visually indicate relationship between different actors/personas)

  •  Anonymize and share notes from discussions with different partners Jenna Makowski

  1. Next steps for the use case diagrams - other use cases, assessing the value/impact, etc. Reference document (Jenna Makowski)

  2. Review progress on the product narrative project (Faqir Bilal)

  3. Align on the path forward - Objectives and timelines (Faqir Bilal)

  4. Elements of the product narrative - review a very early draft (Faqir Bilal)

Action items:

  •  Make a list of use cases that we can work on next (and get input from the wider group) and propose a workflow for working on them. Share it with the rest of the group before the next PWG meeting. Jenna MakowskiFaqir Bilal

Use case list here: Use Cases and MindMaps

  •  Create a draft (sandbox space) for the Product Narrative so that we can start thinking about the end product Jenna Makowski

Decisions:

Sept 20, 2022

  1. Review: Skeletal slide deck https://docs.google.com/presentation/d/1DFl0SQRDse_a-UOcn7nskeQaWxxzZjBgmOPGJEN3sZE/edit#slide=id.g125f71bd1ae_0_1450

  2. Review: Narrative visual draft https://lucid.app/lucidchart/4e5e8a34-4d79-4984-95e8-926d2795023f/edit?beaconFlowId=AC2FD28F9B654946&invitationId=inv_f86fbdb0-f64c-4834-a024-a414a20fbdbb&page=0_0#

  3. Review: Next steps for community feature use survey method

  4. Review: Next steps for building mindmaps for 3 other use cases

Oct 4, 2022

  1. Review: Next steps for building mindmaps for 3 other use cases

  2. Update: Product Narrative work

  3. Input: In-progress Product Core visual https://lucid.app/lucidchart/4e5e8a34-4d79-4984-95e8-926d2795023f/edit?beaconFlowId=AC2FD28F9B654946&invitationId=inv_f86fbdb0-f64c-4834-a024-a414a20fbdbb&page=0_0#

October 25, 2022

  1. Discussion: Questionaire for value prop survey (Faqir Bilal)

  2. Discussion: Next steps for the deck and connecting that to the value prop (Faqir Bilal)

Next steps:

  1. Faqir Bilal to draft survey

  2. Jenna Makowski to share feedback notes from ToC on working ppt slides

November 01, 2022

  1. Discuss the survey design: https://docs.google.com/document/d/1XeL8ChzK1zbALqsjhT8FaVCIwRBzV6f98M4eLNbZQ7E/edit?usp=sharing (Faqir Bilal)

Frameworks for the narrative

What should the narrative include?

Version A

  1. Who is Open edX for? <who is the protagonist of our story>

  2. What problem(s) does it solve for them? <introduce the conflict>

  3. Obstacles to solving the problems

  4. How does Open edX solve these problems

  5. What happens if we don’t solve these problems <the pain of not going ahead with our solution>

  6. Who we are as an organization

  7. Where we've been, where we are, and where we are going

Version B:

  1. Name the enemy

  2. Answer “Why now?”

  3. Show the promised land before explaining how you’ll get there

  4. Identify obstacles—then explain how you’ll overcome them

  5. Present evidence that you’re not just blowing hot air

Version C:

  1. What are the conditions that have led to conflict? For example, has the world changed in some ways but not in others?

  2. What is the conflict?

  3. How can the conflict be resolved?

  4. What can you/your product do to resolve this conflict?

  5. Why are you the right person to resolve this conflict?

Examples:

View file
nameZoura - Turning Customers in Subscribers - bestsalesdeckeverv51-170428122315.pdf

View file
nameleadcrunchaisalesdeck-170102184128.pdf
View file
name235629204-Snapchat-business-deck.pdf
View file
nameirresistible-content070714v3-140806051129-phpapp02.pdf

Other examples:

Wordpress.org: https://wordpress.org/
Similarities to Open edX in that users are presented with a “generic core”, which can be easily customized to nearly endless potential. Open edX as the wordpress of online learning platforms?

Action items

  •  Compile background and context docs
  •  Primary use case mind maps
  •  Competitive analysis with 4-6 top vendors
  •  Share any product narratives that we like
  •  Distill into a product narrative slide deck

Timeline

Project kick-off

Status
colourGreen
titleDone

Deliverable 1

  1. Complete the competitor matrix for higher ed [on hold]

  2. jmakowski@tcril.org to compile all resources related to this competitor research/analysis

Status
colourGreen
titleDone

Deliverable 2:

  1. Mindmaps for learners, course authors, admin

  2. Subpersona definition

  3. Exhaustive list of features required to accomplish primary use case

  4. Peer review

…

Final deliverable

  • Product Narrative Deck

Documents and resources

Open edX

Title

Description

https://docs.google.com/presentation/d/1aEeJjvSES9B6AZUFDLeDfa0rspq4qXBcCjtr3wjrF0I/edit#slide=id.g125f71bd62f_0_0

Slides analyzing the impact and use across sectors/verticals, aggregated at the level of Open edX as an ecosystem:

https://docs.google.com/spreadsheets/d/1uZZT_zcJk_KRZ3m92_yS2tf5Cn0hSQAu9ZdH7yKIlQ4/edit#gid=0

Full list of current features:

https://docs.google.com/document/d/1mNXNmlRG8QYvmMaYlk2fodinU9nDFGsjQnu14tX-Tto/edit

DRAFT: Concept Doc/Gap Analysis - Open edX for On-campus use

https://lucid.app/lucidchart/84a2f62c-2ed9-4f03-8222-42c326a19257/edit?invitationId=inv_98b3a38a-dd5f-49d4-9cf9-9fa816fbb95f&page=0_0#?referringapp=slack

Product Core and Tech Core: tCRIL has been brainstorming about what “core” means, both from a technical perspective and a product/user perspective. This diagram provides a visual representation of possible convergence and divergence between product and tech cores.

Comparison with other LMS providers

Title

Description

https://docs.google.com/document/d/1kNBQTrkWlt9TReuq-ZyGfnoeXEWktPdPAtlLhkt4u4Q/edit

Moodle Docs

https://docs.google.com/spreadsheets/d/1HhKN3H53fmOZZ7tLgpjRq25ato-d5OkyCVrt7n83Rqc/edit#gid=653527801

Competitive Analysis from the Marketing WG (1)

https://miro.com/app/board/o9J_lvIP0Pk=/

Competitive Analysis from the Marketing WG (2)

Authoring flows and LTI flows

Canvas: Authoring flows and LTI flows (course author perspective)

Creating a product narrative

Title

Description

The art of product storytelling: how product teams can balance evidence with empathy

How to write a product narrative

6 Steps for Creating a Well-Crafted Product Story

Epic

https://github.com/openedx/platform-roadmap/issues/174

Project brief

https://openedx.atlassian.net/wiki/spaces/OEPM/pages/3476357132/Idea+Board+Project+Briefs#2.-Build-a-compelling-product-narrative

Meeting

Product Narrative Subgroup meeting link: meet.google.com/bmf-gewb-zbf

10 AM ET every Tuesday

Sub-group members

Jenna Makowski Faqir Bilal Santiago Suarez

Status

Status
colourYellow
titleIn progress

Start date

End date

Contents

Table of Contents