Why do capable professionals avoid the tools meant to help them collaborate?

Turning an observation into a study-ready question

Turning observations about elders' struggles with workplace software into a structured research question supported by literature and an actionable study design. The topic came from curious questions tickling me through lectures and my own observations of people around me.

• Define a focused research problem grounded in CSCW literature.
• Develop research questions that address digital resistance at work.
• Create a feasible mixed-methods study (interviews + surveys).
• Practice designing ethical, study-ready UX research documentation.

Concept in one breath

A mixed-methods study designed to explore why middle-aged professionals resist workplace groupware, grounded in CSCW theory and real-world observations.

Process

From curiosity to a study design

• 1. Observations → topic curiosity. Noticed elders around me struggling with workplace tools and began questioning why digital adoption feels harder for some groups during class lectures.
• 2. Patterns from reading journal. Weekly CSCW readings revealed recurring themes around resistance, competence, overload, and organizational pressure.
• 3. Narrowed research scope. Focused the broad idea into one specific population (middle-aged professionals) and one behavior: resistance to online groupware.
• 4. Focused literature review. Synthesized relevant papers to understand known barriers and justify why this research gap matters.
• 5. Research questions + hypotheses. Framed targeted questions and early hypotheses around cognitive load, confidence, and workplace expectations.
• 6. Study design (mixed methods). Created a feasible plan using interviews + surveys to capture both lived experiences and measurable patterns.
• 7. Ethics + feasibility. Ensured the study respected participant confidentiality, minimized risk, and could realistically be executed within constraints.

Theories

My research proposal was grounded in key CSCW and HCI theories that explain why users adopt, avoid, or resist workplace technologies. These frameworks helped me understand resistance not as a "lack of tech skills," but as a combination of cognitive, emotional, and organizational forces.

• Technology Acceptance Models

  TAM and UTAUT, used to frame how perceived usefulness, effort expectancy, and social influence affect willingness to adopt groupware (Venkatesh et al., 2003; Marikyan & Papagiannidis, 2023).

• CSCW & groupware adoption

  Work showing that groupware use depends on social worlds, work practices, and organizational context, not just the UI (Mark & Poltrock, 2004; Ellis et al., 1991).

• Technostress & usability barriers

  Research linking technostress, information overload, poor UI, and lack of digital skills to low adoption and workarounds (Jalo & Pirkkalainen, 2024; Bagrationi & Thurner, 2023; Owoh, 2024).

• Multilevel Model of IT Resistance

  Treats resistance as a multi-level, organizational phenomenon shaped by perceived risks, norms, and power structures (Lapointe & Rivard, 2005).

• UX-driven interventions

  These theories together justified focusing on UX solutions, cognitive load reduction, adaptive interfaces, clearer navigation, and structured onboarding, as ways to reduce resistance.

Research questions

Methods

A two-phase mixed-methods plan: click a card to see what each phase involved.

• Phase 1, Quantitative: why surveys? +
• Phase 2, Qualitative: why interviews? +

Study context & participants

Research settings

Corporate environments where day-to-day collaboration depends on online groupware like Teams, Slack, Zoom, and Trello, across sectors such as consulting, healthcare, IT, and finance.

Who I focused on

Middle-aged professionals (40–60) who regularly use, or are expected to use, these tools in their roles, often in administrative or leadership positions where decisions and teamwork rely heavily on digital communication.

Sampling & recruitment

Planned recruitment through HR teams, LinkedIn/professional networks, company mailings, and usability platforms, aiming for 20–30 participants for interviews and usability testing, and 200–300 participants for surveys, to balance qualitative depth with quantitative reliability.

Data analysis

• Thematic coding to analyze interview and think-aloud data and uncover patterns behind resistance.
• ANOVA and regression to test relationships between adoption attitudes, usability perceptions, technostress indicators, and prior experience.
• Comparative UX testing to quantify how design interventions affect performance and engagement.

Expected outcomes

• Inferred

  Cognitive overload, technostress, and complex interfaces will emerge as the primary drivers of resistance, with middle-aged professionals struggling due to high information density, non-intuitive navigation, and overwhelming tool features.

• Inferred

  Adoption attitudes will strongly depend on workplace culture and prior digital experience, where progressive environments and past positive exposure lead to better engagement, while rigid or hierarchical cultures increase resistance.

• Inferred

  UX interventions such as adaptive interfaces, streamlined navigation, AI-supported onboarding, reduced notifications, and age-inclusive design will significantly improve groupware usability, helping middle-aged workers feel more confident, supported, and able to sustain long-term use.

Read the Research Proposal →

Reading journal

My reading journal became a space where I learned how to think like a researcher, not just read papers. Each week, I wasn't simply summarizing CSCW and HCI articles, I was tracing how ideas like technostress, digital friction, workplace norms, and tool breakdowns connect to real human behavior. And so, here it finds a place on my portfolio.

I started to notice

• How people's emotions, identities, and confidence shape their interactions with technology far more than interface elements alone.
• How collaboration tools succeed or fail because of social dynamics, hidden power structures, or mismatched workflows, patterns I saw echoed across the papers I reviewed.
• How middle-aged professionals in particular experience digital change as cognitive load, pressure, or even embarrassment, exactly the phenomenon I later explored in my proposal.

What I got

• I learned how to extract real insight from academic papers, connecting concepts like technostress, cognitive overload, and workflow breakdowns to the everyday struggles users face with collaboration tools.
• I learned to recognize patterns across CSCW and HCI research, noticing how workplace norms, confidence, and past experiences repeatedly shape how middle-aged professionals engage with technology.
• I learned to translate theory into research direction, using my weekly reflections to build a clear thematic foundation that ultimately guided the problem framing and research questions in my proposal.

Read the Reading Journal →

What I learned

• Bridging psychology and UX research. I learned how cognitive load, self-efficacy, technostress, and emotional reactions meaningfully shape technology resistance, showing me how psychological constructs directly inform UX decisions.
• Developing HCI-driven research thinking. As an HCI student, I gained confidence in translating theories (CSCW, TAM/UTAUT, resistance models) into clear research questions and choosing methods that genuinely fit the problem space.
• Understanding users as social and contextual beings. This project strengthened my perspective as a UX researcher that adoption isn't just about interface quality, workplace culture, identity, confidence, and past experience deeply influence user behavior and must be designed for intentionally.

Research Proposal → Research Journal →