![A man using a laptop](/sites/g/files/omnuum13026/files/styles/hwp_21_9__1920x825/public/2026-04/pexels-viralyft-16546201.jpg?itok=79jSx_Sc) 

 



 

#  HarvardSites Drupal Site Builder Research Survey Findings 

 





Understanding user perceptions, satisfaction patterns, and opportunities for improvement in the HarvardSites Drupal platform.



 

April 08, 2026

 

 

 [ Laurier Cress ](/people/laurier-cress) [ Dan Cabral ](/people/dan-cabral) 

## Introduction

HWP conducted a study to understand the experiences, needs, and satisfaction of Harvard community members who build, edit, or manage websites using the HarvardSites Drupal platform.

Insights will inform future improvements in usability, design flexibility, content management, and collaboration features, while also establishing baseline metrics for ongoing tracking and evaluation of platform progress over time.



 

 

 

##  Executive Summary 

- HarvardSites Drupal is perceived as **competent and reliable** but cognitively heavy.
- Users are moderately satisfied and appreciate structure and consistency, but struggle with confidence, design flexibility, and the mental overhead of "doing things the right way."
- The platform succeeds as a governance-friendly system but demands users understand system logic rather than guiding them through intent-based actions.



 

##  The Core Story 

 



149

Survey Responses

 



3.4

Satisfaction Score

Out of 5 possible.

 



45%

At Risk

Neutral or dissatisfied.

 



 

 

 

 

 

##  Satisfaction Distribution 

Satisfaction clusters strongly in the "somewhat satisfied" range, indicating the platform is broadly acceptable but not delightful. This is classic "gets the job done" platform.

 

 



 

    ![A bar chart showing a distribution of how many people are satisfied with HarvardSites Drupal. Most people report being "somewhat satisfied," followed by people who feel "neutral" about the platform ](/sites/g/files/omnuum13026/files/styles/hwp_1_1__960x960_scale/public/2026-04/Screenshot%202026-04-08%20at%202.37.22%E2%80%AFPM.png?itok=kVaaQmf7) 

 



 

 Incremental improvements to clarity, confidence, and flexibility could move a large portion of users into "very satisfied" without needing radical platform changes.



   

##  The Two-Tier Experience 

 



##  Page-Level Work 

 



Basic content editing is generally rated easier and feels approachable to most users.



 

 

##  Site-Level Architecture 

 



Structural tasks like taxonomy, navigation, and global settings skew toward moderately to very difficult, feeling expert-only.



 

 

 

 

##  What Users Love 

 



 ### Structured Content Model

Users appreciate predefined components and consistency, especially valued by staff managing institutional or flagship sites.



 

   ![scaffolding](/sites/g/files/omnuum13026/files/styles/hwp_16_9__480x270/public/2026-04/pexels-alexey-k-458081116-30467764.jpg?itok=RQlkHoQT) 

 

 

 

 ### Predictable Patterns

"Intuitive" often appears after a learning curve. Power users express relief once patterns are understood.



 

   ![a stack of colored lines](/sites/g/files/omnuum13026/files/styles/hwp_16_9__480x270/public/2026-04/pexels-enginakyurt-15121181.jpg?itok=cWvbUBh1) 

 

 

 

 ### Centralized Management

Strong appreciation for having everything "in one place," compared favorably to less structured or legacy systems.



 

   ![a red sphere with spokes coming out of it](/sites/g/files/omnuum13026/files/styles/hwp_16_9__480x270/public/2026-04/pexels-brett-sayles-4985154.jpg?itok=NkKHr5Cj) 

 

 

 

  

 

 

 

##  Core Challenges 

 



 ### Cognitive Load

Users describe the experience as confusing, time-consuming, and overwhelming. Hard to remember "what goes where."



 

 ### Design Flexibility

Users want more layout control and visual customization. Perceived mismatch between Drupal's power and actual design freedom.



 

 ### Fear of Breaking Things

"I'm never sure if I'm doing this correctly." Hesitation to experiment, over-reliance on documentation, slower workflows.



 

 ### Taxonomy & Navigation

Structural elements are hard to conceptualize, poorly surfaced in the user interface (UI), and difficult to debug when something goes wrong.



 

  

 

 

 

##  You said: Core content editing works well, but advanced tasks feel risky 

Many of you told us that everyday content updates like editing pages, adding content, and managing basic layouts feel intuitive once you are familiar with the system.

At the same time, tasks such as navigation setup, taxonomy management, and global site settings often feel stressful or high risk.

 

 



##  We Heard: 

 



The challenge is less about capability and more about confidence, clarity, and guardrails.



 

 

##  What We Are Doing: 

 



- Improving guidance around high-impact actions so it is clearer when changes affect a single page versus an entire site.
- Refining documentation and training to better distinguish content editor tasks from site administrator responsibilities.
- Using this feedback to inform UX and documentation improvements that reduce fear of unintended changes.



 

 

 

 

##  The Confidence Crisis 

 



 

*"I'm never sure if I'm doing this correctly."*

Confidence is a mediating variable for satisfaction. Users lack confidence editing without breaking something, and this correlates directly with neutral or lower satisfaction scores.

**This is a trust issue, not a skill issue.**



 



      ![a person using a laptop computer](/sites/g/files/omnuum13026/files/styles/hwp_1_1__480x480/public/2026-04/pexels-karola-g-8003528.jpg?itok=cvEYLkxD) 

 

 

  

 



 

 

 

##  You said: It is not always clear why some options are limited 

Several responses noted a desire for more design or configuration flexibility, alongside confusion about why certain options are unavailable.

 

 



##  We Heard: 

 



You value consistency and standards, but want clearer explanations of the tradeoffs behind them.



 

 

##  What We Are Doing: 

 



- Strengthening communication about how design system standards support accessibility, sustainability, and long-term maintainability.
- Partnering with school and unit governance groups to better explain which decisions are local, which are institutional, and why.
- Incorporating clearer “why” language into training and support conversations.



 

 

 

 

##  Most Requested Improvements 

 



1

Better Guidance

Inline help, clearer labels, and examples embedded directly in the UI at the moment of action.

 



2

Safer Editing

Undo/version confidence, clearer previews, and reassurance that changes won't cascade unexpectedly.

 



3

Expressive Design

Layout variation, visual hierarchy tools, and less reliance on "knowing the right component."

 



4

Reduced Setup Friction

Starter content that feels relevant, clearer "what to do first" pathways, and launch-readiness checklists.

 



 

 

 

 

 

##  Three Critical Insights 

 



 ### Power vs Confidence Paradox

HarvardSites Drupal is objectively powerful but subjectively intimidating. As power increases, confidence decreases unless carefully mediated by user experience (UX) patterns.



 

   ![a wavelength](/sites/g/files/omnuum13026/files/styles/hwp_16_9__480x270/public/2026-04/AdobeStock_1937015490.jpeg?itok=WSSQWxeP) 

 

 

 

 ### Expertise Gradient Problem

The platform assumes users will become semi-experts, but many build one site, update occasionally, and never fully internalize Drupal concepts. This creates long-term friction for low-frequency users.



 

   ![Illustration of figures standing on blocks](/sites/g/files/omnuum13026/files/styles/hwp_16_9__480x270/public/2026-04/AdobeStock_1797562808.jpeg?itok=_27oq8JD) 

 

 

 

 ### Design-Led Satisfaction

User satisfaction correlates more strongly with feeling oriented, safe, and expressive than with the number of features available. This is a strong argument for UX investment over net-new functionality.



 

   ![multiple digital screens](/sites/g/files/omnuum13026/files/styles/hwp_16_9__480x270/public/2026-04/AdobeStock_567642900.jpeg?itok=Z78NNAxd) 

 

 

 

  

 

 

 

##  The Path Forward 

 



##  Key Takeaway 

 



Satisfaction is fragile but improvable. Nearly 45% of users are neutral or dissatisfied, suggesting they tolerate pain points because of institutional necessity, not preference.

**Small friction points may disproportionately affect overall sentiment.**



 

 

##  Recommendation 

 



Focus on incremental UX improvements that increase confidence, reduce cognitive load, and provide better guidance—without requiring radical platform changes.

The opportunity is clear: move users from "somewhat satisfied" to "very satisfied" through thoughtful design refinements.



 

 

 

 

##  What this means going forward 

Your feedback confirms that HarvardSites Drupal is meeting its core goal of enabling non-technical users to manage content on secure, accessible, and sustainable websites. It also highlights where the next phase of improvement lies: building confidence, clarifying roles, and making governance more transparent as our shared web ecosystem matures.

We will continue to share updates as improvements are made, and we appreciate your ongoing partnership in shaping a platform that works for both individual site builders and the University as a whole.

Thank you for taking the time to share your experience.



 

 



 

 

 Share on:- [     Facebook ](#)
- [     Twitter ](#)
- [     Linkedin ](#)