Tentatively unassigned since it doesn't look like there's been progress on this. Please feel free to reassign yourself if you have been working on it.
Try and understand why someone drops out of an exploration, so that the exploration can be improved.
An idea that came up in a conversation I had recently was: when a student exits an exploration midway, offer them a way to give feedback on why, so that the creator can improve the exploration. For example, we could show a short feedback box, with messaging along the lines of: sorry about the bad experience; if you could let us know what we could do better, we'd really appreciate it and will try to improve the lesson based on your feedback.
There are two parts to this: (a) figure out when to show the box, (b) design the UX for the experience.
Note that, for (a), some users may just be browsing, and it's reasonable for them to leave after the first card -- so we do need to figure out when to show the box. One possible filter is to do so only when the learner has made a significant attempt to engage with the exploration by submitting some answers -- or, alternatively, we could restrict it initially to cases which are definitely problematic, e.g. the learner has just submitted a whole bunch of answers in a row to the same card. The exact criteria for this needs to be thought through carefully.
Also, from the implementation point of view, it would be nice to tag the feedback as "feedback that led to a drop-out" so that creators are aware of this.
- weixin_39752352 5月前点赞 评论 复制链接分享
I'm out of town until after Christmas -- will reassign myself when I'm back to work on it.
On Mon, Dec 12, 2016 at 11:19 AM, Ben Henning wrote:
Tentatively unassigned https://github.com/rachelwchen since it doesn't look like there's been progress on this. Please feel free to reassign yourself if you have been working on it.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/oppia/oppia/issues/2744#issuecomment-266524526, or mute the thread https://github.com/notifications/unsubscribe-auth/ALmJ24GyCPLgCwAvVrYO4S9Eu2qr4XK3ks5rHZ4qgaJpZM4K3hOp .
-- Rachel Chen
Design Lab at UC San Diego x SAP www.rachelwchen.com点赞 评论 复制链接分享
Update: is investigating this, and we had a chat this morning. I'll summarize next steps here (but, Rachel, please feel free to correct me if I've written anything wrongly!)
We are looking to tackle this in two ways:
Remove factors that cause students to leave in the middle of a lesson. This may be due to things like:
- insufficient feedback or overly-stringent checks, so the student is stuck and doesn't know how to continue
- lack of interest in the topic
but we don't really know. Next step: spec out and implement a survey to get more data about students' reasons for dropping out in the middle of a lesson, so that we don't end up fixing the wrong thing.
点赞 评论 复制链接分享
- Make it easier for students to return to a lesson. This can be done by saving progress for logged-in users who leave in the middle of a lesson, and showing them their unfinished explorations when they return. Next step: figure out the user experience for this flow, and create mocks for it.
Hi , how is this going?点赞 评论 复制链接分享
Sean and I explored this in 2 directions. First: remove factors that cause students to leave in the middle of a lesson: I interviewed 4 users and asked them to think out loud while completing an exploration. This helped us understand their thought process & evaluate things that may have led to frustrations and dropout. You can read more about it here: https://docs.google.com/document/d/1aP5YwugM-UtKovdOOgH22VApp6TZErDtyHEWR-lkoKU/edit
As next steps, 1. Sean and I are thinking about compiling a "creator doc" where we outline things that creators should follow/avoid, so that their explorations may have lower dropout rates due to learner frustration. We still need to flesh out the actual design specs, ex: where do we place this? How can we get creators to read it? 2. Add some feature to the exploration editor so that it automatically reminds creators of things to avoid (ex: issue #3074) 3. Help learners get "unstuck." The GSoC project -- replace fallbacks with hints -- will help with this. 4. Do more user testing on younger kids. So far, our user testing participants are mostly HS/college students. We should test with younger students to see how their responses might differ.
Second: Make it easier for learners to return to a lesson. Distractions, lack of time, etc... can lead to dropouts; we can't prevent them, but we can make it easier for learners to re-engage with an exploration again. This will probably get implemented in the learner dashboard for GSoC.
Thanks!点赞 评论 复制链接分享
That's very interesting; please let me know when the "creator doc" is ready. It sounds like that is a good thing to start with, insofar as we are currently exercising creative oversite of the explorations. Building guidance into the editor itself represents a second level of difficulty, but would be very valuable indeed.点赞 评论 复制链接分享
Hey , here's a draft: https://docs.google.com/document/d/1WcO4uNznFejkQZ2nq320zzpSaNRQ8aqYZz5MGMQuEoY/edit
It's not super thorough yet -- feel free to add/edit more things. Thank you!点赞 评论 复制链接分享
Thanks for the link; I made a few comments. There are some existing documents giving advice to content-creators here: https://docs.google.com/document/d/1Ffx_nJsZ8k-aJyPRlFu2HWDJPIkfTAyUBxyUbtcEe2Y/edit https://docs.google.com/document/d/1u4WErMBSRR7TQPAZ9Kd1rGJ6U4V9EQZJx462gCxyrYk/edit https://docs.google.com/document/d/1h8jDHduAOgMOkpssiDMduCdP9TYfTOsS0UQ_VhwWa-k/edit#
It would be great if we could work towards a synthesis of these that we can link to from the Oppia navbar and/or editor.
On Sat, Mar 18, 2017 at 1:52 AM, Rachel Chen wrote:
Hey https://github.com/jacobdavis11, here's a draft: https://docs.google.com/document/d/1WcO4uNznFejkQZ2nq320zzpSaNRQ8 aqYZz5MGMQuEoY/edit
It's not super thorough yet -- feel free to add/edit more things. Thank you!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/oppia/oppia/issues/2744#issuecomment-287504204, or mute the thread https://github.com/notifications/unsubscribe-auth/ANF0TC-xQTa9VuzcXpQm4WTE2x3zOQmTks5rmyq9gaJpZM4K3hOp .点赞 评论 复制链接分享
- weixin_39716510 5月前
Friendly ping. Are there any updates on this?点赞 评论 复制链接分享
Hi , thanks for the ping! Haven't worked on a synthesis yet; we've been making changes to the explorations themselves. -- I'll start a draft so we can get that guidance page ready!点赞 评论 复制链接分享
- weixin_39704727 5月前
Hi -- how is this going?点赞 评论 复制链接分享
Here's a draft: https://docs.google.com/document/d/1UQ-wyDcAngR_xloWxmtWZ5SB2_Trl5Y-1qzN8bsyvuI/edit. I selected a few tips that stood out as really useful to me (from the 4 existing documents on creating explorations -- links are included in the draft). Please feel free to make edits!点赞 评论 复制链接分享
Hi , this is great, thanks! Think we could put it on the GitHub wiki (under References, perhaps)? Easier to edit and reference that way, I think.点赞 评论 复制链接分享
Here it is! Advice on creating explorations. I've also placed it in the sidebar menu under References.点赞 评论 复制链接分享
Thanks, , for starting this! I've pointed Mark to it, so that he can develop it further as well.
With regards to this issue thread in general, what are the next steps? Should we leave it open or close it?点赞 评论 复制链接分享
I think we can close it for now, since we can file individual issues for specific things that should be fixed with each exploration!
On Thu, Jun 15, 2017 at 8:06 PM Sean Lip wrote:
Thanks, https://github.com/rachelwchen, for starting this! I've pointed Mark to it, so that he can develop it further as well.
With regards to this issue thread in general, what are the next steps? Should we leave it open or close it?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/oppia/oppia/issues/2744#issuecomment-308920830, or mute the thread https://github.com/notifications/unsubscribe-auth/ALmJ2zdgPZOJM04qcaEhFEHOoi58_xQ-ks5sEfFPgaJpZM4K3hOp .
-- Rachel Chen Sent from mobile.点赞 评论 复制链接分享
OK, thanks ! Closing.点赞 评论 复制链接分享
- weixin_39663258 5月前
Hi how is this going?点赞 评论 复制链接分享