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

Describe assessment differently #18

Open
kallewesterling opened this issue Jun 17, 2020 · 0 comments
Open

Describe assessment differently #18

kallewesterling opened this issue Jun 17, 2020 · 0 comments
Assignees
Labels
Milestone

Comments

@kallewesterling
Copy link
Member

Draws on #8, specifically Lisa's comment:

"self-assessment" doesn't really describe it. So, for example, the self-assessment "quantitative" questions are really just multiple choice questions, but they're as much for us as they are for the user. However, assessing whether or not the user understands what a work plan is... that's a different kind of assessment.

So, what I'm thinking is that we need to maybe look at all the different types of questions, and maybe describe them differently-- maybe even making it obvious what we want to assess.

For example, one is about how valuable the workshop was for the person. Another question is about information retention. Another is about the lesson value, etc. etc. I think we could probably find better headings for these... but I'm glad we've got the process started.

And Kalle's follow-up comment:

Thinking beyond this particular workshop and for the project as a whole:

Maybe we should keep calling them exit slips? Do we need to rename them? I kind of like the idea of seeing us use the language that we have, as exit slips emphasizes that the "assessment" is not something impersonal that happens after you are "done" but rather when "leaving the room"... so, if we could contextualize that for the user on the website, perhaps we could call these "exit slips" still, and maintain clarity in what these questions are, and why we're asking them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants