Closed gedankenstuecke closed 7 months ago
I would go for experiences with a storytelling aspect that helps identify any learnings behind the experience and inspire other people to share relevant experiences to the community.
I would go for "experiences" too. I always tend to be curious and read "stories" when I find them, because I enjoy the storytelling element π but somehow I think the term might suggest that the content of the "story" is not quite real, but at least partially made up or collated ad-hoc from different "experiences". The term "experience" suggests something more authentic and less manipulated to me -could be a very personal take on the words though!
Thanks @giuliatomba and @AlexandraAAJ, I think that mirrors my concerns about "stories" quite a bit.
I just wonder whether from a "data contributor" perspective, story might feel more inviting, but I guess we might just have to see how people feel about it!
I would also agree with the above perspectives on "stories" having connotations around fabrication or perhaps embellishment vs experiences. But as you mention @gedankenstuecke it would be most useful to speak to the data contributors about their views, since "experience" might also result in contributors feeling pressured to include all aspects, including painful details...
thanks @Arielle-Bennett !
It's really interesting to read the perspectives above. I would chime in that I perhaps disagree with the notion that "stories" would create more room for dismissal than "experiences". I've seen both used as a means of dismissing qualitative data, with "stories" being dismissed due to their narrative element (seemingly as opposed to more empirical description) and "experiences" being dismissed due to their individualised element (i.e. someone's 'experiences' is their own - and only their own and not more broadly generalisable).
Journalists, anthropologists, and user experience design researchers use the terms "story" and "storytelling" specifically because of this narrative element. This holds power because narrative shapes the way in which people think about an idea, person, concept or event. So I'm guessing that in the context of AutSPACES, the ability to share one's one story, on their own terms and narrative style could shift that power back into that of people, and not just the fields for which storytelling might be their "specialty". Each of these fields has had lots of questions & reflections about power, like this podcast about anthropology and journalism, or this user experience blog about narrative bias. I've found that folks who utilise and think through 'storytelling' may be more attuned to the notion of situated knowledge and power, i.e. that knowledge production of all kinds, storytelling and otherwise, always come from particular places and particular perspectives, and have implicit power relations tied up in them.
"User experiences" don't necessarily have those kinds of stakes or associations with power that I think user experience researchers in particular have capitalised on, which means that they might be easier to wield and use in this context. I agree with asking the audience and folks who would use this tool what they prefer - and what these two terms mean to them! Thanks for the invitation for feedback, Bastian.
Thanks for that great counterpoint @aleesteele! It's nice to see the beauty of interdisciplinary work in action as I suspect and see some anecdotal evidence in the comments here for there being some discplinary divides in how people feel about the wording π
I guess coming from a biomedical research background "experience" feels something that people are also not super at ease with (when are people ever when it comes to qual. dataβ¦) but that has gained some acceptance, maybe also because of the moves towards "personalized medicine" that puts the individual back into medical practice (or at least does so to some level).
But I definitely hear and have encountered your points about narrative elements and the power that comes with allowing people to "share/tell their story". Which ultimately might mean having to decide on a trade-off between what audience and benefits we want to centre in the project.
I think based on today's really great feedback in the community session the main take aways are:
I think that framing of "share your sensory processing experiences in a story" is quite good. We can use the "story"-framing in the UI (share story, my stories, read stories, β¦) β this makes sure that the elements people interact with have a consistent label. In the copy text where there's more space we could use both aspects?
Copy editing in #621 will include framing "share your sensory processing experiences in a story"
Summary
Currently the AutSPACEs frontend uses both
Stories
andExperiences
to describe the data that people enter, and I think it can be confusing for people that aren't familiar with AutSPACEs. I think it would be good to unify it around using either of those terms (but there might also be good reasons to keep both?).Experiences:
Stories
Personally I have to say I'm really not a fan of the term "stories" and try to avoid it when giving presentations or writing/talking about AutSPACEs. I think for me it's because on the one hand calling the contributions "stories" at least runs the risk of devaluing or invalidating people's experiences β and on the other hand it there's a strong tendency among quantitative people to dismiss qualitative data, and calling it "stories" feels to me like we implicitly agree with that.
But I appreciate that this might be more my own baggage speaking rather than a more general impression. Also there might be an aspect that for contributing users "stories" feels more approachable β so maybe it's a matter of which audience we're talking to?
What do other folks think?
Deadline
What needs to be done?
Who can help?
Updates