Skip to content
Lisa LoveraITEN
Case study · Master’s thesis in UX Design

Simplify Review

A web app that makes the most repetitive stages of a systematic review lighter (import, deduplication, filters and decision tracking) and always leaves the final word to the researcher.

Role: UX research & UX/UI design Method: User-centered design · ISO 9241-210 Year: 2024/25 Output: Clickable prototype in Framer
Mockup of the Simplify Review dashboard on a laptop: review flow counters, screening progress chart, recent activity and active projects, with the flow summary in the foreground.
Role
Individual project: user research, architecture, UI, prototyping and testing
Context
University of Siena, Communication Strategies and Techniques · UX Design
Tools
Google Forms, Miro, Figma, Framer, Python (Matplotlib)
Methods
Survey, semi-structured interviews, attitude map, AttrakDiff
25responses to the online survey: 22 in Italian and 3 in English
5semi-structured interviews with researchers and PhD students
20participants in the AttrakDiff evaluation
5.38/7perceived pragmatic quality: clear, intuitive, functional
01Context

The most rigorous method is also the slowest

Systematic reviews are the most reliable way to synthesise scientific evidence: explicit protocols, criteria stated in advance, every step replicable. This rigour is exactly what makes them costly. A single review can take months of work.

The early stages are the hardest: retrieving thousands of records from different databases, removing duplicates, aligning inconsistent metadata, applying the inclusion criteria and documenting every choice. Today this work moves from one tool to another, and every switch adds cognitive load and risk of error.

How do you find your way through the jungle of scientific research?

Today
DatabasesScopus, Web of Science, PubMed: exports in different formats
Spreadsheetduplicates and criteria handled by hand
Reference managerbibliography in a separate environment
Text editorreport and PRISMA diagram rebuilt afterwards
With Simplify Review
One single environmentImport→Deduplicate→Filter→Decide→Export

Core idea

A digital tool that does not replace the researcher but makes them more efficient.

Problem addressed

The cognitive load in the repetitive stages: deduplication, filtering and metadata management.

Goal

More transparency and traceability in decisions, for better-quality systematic reviews.

02Research

Listening to the people who do reviews every day

I followed a user-centred approach with mixed methods: a survey to measure habits, time spent and difficulties, and semi-structured interviews to understand motivations and frustrations. I cross-checked the two data sets with a thematic coding of the transcripts and I verified my interpretations with the participants (member-checking).

The sample: researchers, lecturers, PhD students and students of communication sciences and related fields, with different levels of experience. 72% had carried out at least one systematic review in the last two years.

25

Online survey

22 responses to the Italian version and 3 to the English one. Role, critical stages, screening hours, tools, expectations and fears about AI.

5

Semi-structured interviews

Seven guiding questions: from the last review carried out to the “ideal system”.

5

User profiles

Summarised in a map that combines experience and openness to AI.

Which tools do you use to manage the literature?

Multiple answers · Italian version, 22 responses
Spreadsheets (e.g. Excel)
86.4%
Manual and traditional methods
63.6%
Online databases and search engines
31.8%
Reference manager (EndNote, Mendeley…)
13.6%
Dedicated review software
0%

No one uses software designed for reviews. The spreadsheet is still the main tool, also for tracking inclusion and exclusion decisions. This is the clearest sign that an integrated solution is missing.

54.5%

spend between 10 and 20 hours screening articles; another 27.3% spend between 20 and 40 hours.

68.2%

rate the difficulty of defining and applying inclusion and exclusion criteria as 4 out of 5.

60%

would use AI-based tools, but only with a final human check on the decisions.

The chart and the 54.5% and 68.2% figures refer to the 22 responses to the Italian version of the survey.

I am afraid of introducing variables I cannot control. If an article is excluded, I must be able to explain the reason clearly.
From the interviews
I used ChatGPT to help me rephrase the research question and to summarise some texts. Useful, but I always have to correct it.
From the interviews
I worry that AI oversimplifies. I need to preserve the cultural nuances in the texts.
From the interviews

User attitude map

5 profiles · experience and openness to AI, scale 1–5
User attitude map Five profiles placed by experience with systematic reviews (horizontal axis, from 1 to 5) and openness to using AI (vertical axis, from 1 to 5). Enthusiastic technologist: experience 3, openness 5. Young researcher: 2 and 4. Reflective researcher: 4 and 2. Traditional methodologist: 5 and 2. Qualitative expert: 4 and 1. Ready to experiment Cautious experts 12345 12345 Experience with systematic reviews → Openness to AI → Enthusiastic technologist Young researcher Reflective researcher Traditional methodologist Qualitative expert

More experience, more caution

The profiles with the most methodological experience are also the least willing to rely on automation; younger researchers are the most open to experimenting. The tool had to convince both: fast for those who want to automate, transparent for those who must justify every choice.

Pain points

  • Inconsistent metadata
  • Duplicates across databases
  • Unclear criteria
  • Tools that lack transparency

Needs

  • Simplicity
  • Clarity
  • Reliability
  • Replicability
03Requirements

From needs to four design principles

I turned the findings into functional and non-functional requirements. Four principles guided every interface choice.

Human in the loop

The system suggests, the researcher decides

Every merge of duplicates and every exclusion needs a confirmation. Automation speeds things up, but it does not decide for the person who signs the review.

Transparency

No black boxes

Deduplication rules and filters are always visible and editable. Future AI features will show confidence indicators and the reason for each suggestion.

Traceability

Every choice leaves a trace

An audit trail records the date, reviewer and reason for each decision, and provides the counts for the PRISMA diagram.

Interoperability

Open formats, no lock-in

Import from CSV, XLS and RIS with templates for PubMed, Scopus, Web of Science and Cochrane; export to RIS, BibTeX and EndNote XML.

Non-functional requirements: short explanatory texts and actions that can be undone, stable performance even with thousands of records, privacy by design under the GDPR, and a modular architecture to add AI and collaboration in later versions.

04Prototyping

From paper to Framer, one level of fidelity at a time

I developed the prototype step by step (fidelity escalation): paper to explore the structure quickly, Miro to connect the flows, Figma for the high-fidelity interface and Framer to publish it as a clickable prototype for users to try.

Pencil sketch on squared paper with the structure of the screens: CSV upload, filters and article table.
PaperSketches to set the information hierarchy and the main steps.
Miro wireframe of the dashboard, with sidebar, quick actions and project overview in blue.
MiroDigital wireframes to define navigation, content and flows.
Figma dashboard with green header, sidebar and summary cards.
Figma → FramerHigh-fidelity interface in the project green, published in Framer.

Prototype scope: version 1.2 of the roadmap, with upload, deduplication, metadata filters and audit trail. It is front-end only: the flows are simulated, with no back end that really processes the files.

05Solution

One single environment for the early stages of a review

The navigation follows the real order of the work. Each step shows its status and leads to the next one, so the researcher always knows where they are and how much evidence is still left to assess.

Step 1 · Import

All sources in a single import

You drag in the files exported from the databases and combine several sources together. The fields are normalised before deduplication.

  • Templates for PubMed, Scopus, Web of Science and Cochrane
  • Progress status and number of records for each file
  • Accepted formats: CSV, XLS, XLSX, RIS
Upload data screen on a laptop: file drop area, upload history and database templates, with a detail of the history in the foreground.
Step 2 · Deduplication

Duplicates are flagged, not deleted

The system compares DOI, title and authors and suggests possible duplicate pairs with a similarity percentage. The researcher always decides.

  • Matching rules that are visible and editable
  • “Merge” and “Keep both” actions on each pair
  • Summary: total records, duplicates, unique records
Deduplication results screen on a laptop: three counters, matching rules and a table of record pairs, with the matching rules in the foreground.
Step 3 · Metadata filters

See the effect of each criterion straight away

Language, year, study type and open access can be combined as filters. The number of studies updates while you choose.

  • Active filters highlighted, removable with one click
  • Filter sets that can be saved and reused across reviewers
  • Every change goes into the audit trail
Metadata filtering screen on a laptop: active filters, a count of 612 studies out of 1,031 and the list of results, with the language filter in the foreground.
Step 4 · Audit trail

Every decision has an author and a reason

The log records who included or excluded each record, when and why. Charts summarise the choices, and the counts can be exported for the PRISMA diagram.

  • Stage, decision and reason for each record
  • Distribution of decisions and reasons for exclusion
  • Export of the log and the PRISMA counts
Audit trail screen on a laptop: counters, decision log with reviewer and reason, and charts, with two log entries in the foreground.
The system

Five screens, one continuous flow

Dashboard, upload, deduplication, filters and audit trail share the same sidebar, the same components and the same status logic.

DashboardUpload dataDeduplicationMetadata filtersAudit trail
Isometric view of the Simplify Review screens side by side on a dark green background.
06Evaluation

Clear and intuitive, but not yet distinctive

I evaluated the Framer prototype with AttrakDiff, a questionnaire that uses pairs of opposite adjectives, on a scale from 1 to 7, to measure both usability and the quality of the experience. 20 researchers and students with different levels of experience with digital review tools took part.

Mean scores by dimension

AttrakDiff · n = 20 · scale 1–7

Pragmatic qualityPQ · clear, intuitive, functional

5.38

Overall attractivenessATT · overall judgement

5.19

Hedonic quality · stimulationHQ-S · innovative, engaging

5.10

Hedonic quality · identityHQ-I · sense of belonging

4.87
14 · neutral7

Complicated ↔ Simple

n = 20
0
0
0
1
3
12
4
1234567
ComplicatedSimple

16 out of 20rated the interface as simple, with a score of 6 or 7.

All dimensions are above the neutral value. The highest score is for usability; the lowest is for identity: the prototype showed little character of its own. In the thesis I linked this to the still very basic look of the front end and to the lack of personalisation.

07Iteration

After the test: more identity, same clarity

For this portfolio I went back to the prototype, starting from the lowest score. I kept the green palette and the screen architecture, and I worked on hierarchy, states and visual identity. Drag the slider to compare the dashboard before and after.

Refined Simplify Review dashboard with a dark green sidebar and review flow counters. Thesis prototype dashboard with green header and summary cards. Thesis prototypeRefined

The refined screens have not yet been tested with users. The data shown are fictional examples.

  • 01

    Visible flow. The sidebar follows the real order of the work and shows the status of each stage: completed, in progress, to do.

  • 02

    PRISMA-style counters. On the dashboard: records identified, duplicates removed, records screened and included.

  • 03

    Explicit rules. The deduplication criteria are visible chips, with “Merge” and “Keep both” on each pair.

  • 04

    Immediate feedback. Removable active filters and a study count that updates while you choose.

  • 05

    Identity and accessibility. A logo, white text only on greens that are dark enough, and consistent status colours for included, excluded and stage.

  • 06

    Less noise. I removed the heavy dividers and the repeated boxes in the sidebar; there is only one contextual prompt.

08Limits and roadmap

A first step, with a clear direction

Front-end onlyWithout a back end, real operations such as CSV import could not be tested.
Limited sample20 participants in the evaluation: useful indications, not general conclusions.
AI not yet integratedAutomated screening and semantic analysis remain in phase 2.
One user at a timeMulti-user collaboration and external integrations are still to be designed.
Phase 1 · Core features
Phase 2 · AI and collaboration
v1.0CSV upload and deduplication
v1.1Advanced metadata filters
v1.2Audit trail and reasonsTested prototype
v1.3PRISMA export and API integrations
v2.0Semi-automated data extraction
v2.1Semantic analysis with explainable AI
v2.2Multi-user collaboration with roles
09Conclusions

Towards systematic reviews that are more

efficienttransparentcollaborative

Simplify Review is not an end point. The strongest contribution of the project is the method: user research, requirements, prototyping with increasing fidelity and evaluation, always with the researcher at the centre and with automation at their service.