QuickStatements 3.0/User stories
User stories are informal and short descriptions of a user's activities or needs during their work. In software development, they help bridge the gap between technical teams and the community needs, making them an essential tool in user-centered software development. In the context of QuickStatements, user stories help register the diverse workflows of its user base, which ranges from beginners to bot operators and data curators. These stories serve multiple purposes:
- Identifying main use cases;
- Prioritizing features;
- Informing interface and interaction design;
- Translating needs in accessible interoperable formats;
- Supporting iterative development.
Methodology
[edit]For this project, user stories are especially valuable because they reflect both current limitations and desired improvements, and offers insight into how the tool is used across different contexts and communities. They were developed through a qualitative and iterative process grounded in user-centered design principles and community participation through interviews and surveys. The process consisted of the following main stages:
- Mapping: Key types of users were identified, such as: beginners and casual contributors, batch editors and data curators, GLAM-Wiki contributors and librarians, bot operators and developers, linguists, researchers and wikimedians in residence.
- Interviews: We conducted semi structured interviews, and launched a survey and gathered the insights from members of the community and recollect previous feedback on Wikidata-related events.
- Draft: Stories were written following the standard format "As a
<type of user>, I want to<do something>, so that<a goal can be achieved>." Each story was accompanied by contextual scenarios and workflows and, when possible, examples that demonstrated QuickStatements usage. - Publication: Finalized user stories were then published here, creating a structured overview of user needs and development opportunities for the future.
