This is a live sample.Run your own free →

A real Themera analysis — 14 remote-work survey responses

This is a read-only preview of the Themera dashboard.

💡How to read this analysis

What the tool does

Themera automatically reads qualitative data (like interview transcripts or survey responses) and uses AI to identify common themes, build a structured codebook, and tag every excerpt.

What the result shows

Below is the output of unstructured survey responses about remote work. The AI generated a summary, built a Codebook, and organized Verbatim Evidence. The Coverage panel shows exactly what was (and wasn't) coded.

Why it's powerful

Manual tagging in legacy tools (NVivo, MAXQDA) takes days of work and costs €300–€1,200/year. Themera does the heavy lifting in minutes, saving immense time and money while keeping you in full control.

🎯Coverage
13 of 14 responses coded
x

Uncoded Responses

Keeping a routine. Without a commute the days all blur together.

Executive Summary

Across 14 responses, the experience of remote work is decidedly mixed. The strongest pain points are emotional and relational — loneliness and the erosion of work-life boundaries — alongside practical friction in communication, distractions, time-zone coordination, and video-meeting fatigue. A notable minority, however, report higher productivity at home thanks to fewer interruptions, and several worry that being remote harms their visibility and career growth. The picture is one of clear trade-offs rather than a simple win or loss.

📚Identified Themes (Codebook)

Loneliness & Isolation
2 mentions

Feeling disconnected from others and lacking human interaction while working remotely.

Lack of Work-Life Boundaries
2 mentions

Difficulty separating work from personal life and switching off at home.

Communication Friction
2 mentions

Slower, more effortful communication compared to in-person interaction.

Distractions at Home
1 mention

Household and family interruptions that make focus difficult.

Time-Zone Coordination
1 mention

Inconvenient hours and scheduling across distributed teams.

Video-Meeting Fatigue
1 mention

Exhaustion from excessive time in video calls.

Visibility & Career Concerns
2 mentions

Worry about being unseen by management and slower career growth.

Increased Productivity
2 mentions

Getting more done at home thanks to fewer interruptions.

💬Evidence by Theme

Loneliness & Isolation
Loneliness was the most emotionally charged theme. Several participants described going long stretches without human contact and missing the everyday social fabric of an office.

"it's the loneliness. I can go a whole day without speaking to another human"

negative

"I miss the social side, the coffee chats, just feeling part of a team."

negative
Lack of Work-Life Boundaries
Participants struggled to separate work from home, often unable to switch off when the workspace and living space overlap.

"I never feel like I can switch off. My laptop is right there, so I end up working at 9pm."

negative

"The lack of boundaries between work and home life. My desk is literally in my bedroom."

negative
Communication Friction
Everyday communication became slower and more effortful, with quick questions turning into long threads and delayed replies.

"Things that would take a two-minute chat at someone's desk now become a whole email thread."

negative

"People take hours to reply on Slack."

negative
Distractions at Home
Household responsibilities and family interrupted focus during the workday.

"Staying focused at home is hard. There's always laundry, the kids, or the fridge calling my name."

negative
Time-Zone Coordination
Distributed teams created inconvenient hours and scheduling strain.

"Time zones. Half my team is in the US, so I'm in meetings at 7am and again at 8pm some days."

negative
Video-Meeting Fatigue
Back-to-back video calls left participants drained by the afternoon.

"Too many video meetings. By 3pm I'm completely drained from staring at faces on a screen."

negative
Visibility & Career Concerns
Some worried that working remotely made them less visible to managers and slowed their career growth.

"Feeling invisible. I worry my manager doesn't really see how much I actually do."

negative

"Career growth feels slower. Out of sight, out of mind."

negative
Increased Productivity
Not all feedback was negative: several participants felt markedly more productive at home, with fewer interruptions.

"I'm more productive than I ever was in the office."

positive

"I get far more done without office interruptions."

positive

Before the analysis: pseudonymisation

Names, institutions and places are replaced before anything is analysed. Rules handle emails, phone numbers and IBANs; a language model handles names and places, because a rule cannot tell whether "Bergmann" is a surname or an occupation. German inflection is handled too — Müllers and Müllern are replaced along with Müller, which manual find-and-replace almost always misses.

Before
I: Frau Tölle, wie erleben Sie die Arbeit
am LKH Feldkirch?
B: Seit ich 2019 dort angefangen habe, hat
sich viel verändert. Dr. Bergmann hat die
Station übernommen. Schreiben Sie mir an
u.toelle@lkh-feldkirch.at.
I: Und Tölles Einschätzung dazu?
After
I: Frau [Person 1], wie erleben Sie die Arbeit
am [Organisation 1]?
B: Seit ich [Datum 1] dort angefangen habe, hat
sich viel verändert. Dr. [Person 2] hat die
Station übernommen. Schreiben Sie mir an
[Kontakt 1].
I: Und [Person 1] Einschätzung dazu?

You review every proposed replacement before it is applied — a technical term replaced by mistake damages your data as badly as a missed name exposes someone. Your real names are never stored: only a salted hash, which is enough to keep the same person as [Person 1] across every transcript in the study without us ever holding the key. Try it — free on every plan.

After the analysis: intercoder agreement

The answer to the question every supervisor asks. You re-code a random 20% sample yourself, blind to what Themera assigned, and get Cohen's kappa per category — plus a paragraph for your methods section. Note that running a model twice and comparing it with itself measures determinism, not codebook clarity; an independent human pass is what the criterion actually asks for.

Cohen's κ (pooled)
0.79
substantial
Agreement
91.4%
62 of 312 units
CategoryκUsed
Isolation and loneliness0.8824
Blurred boundaries0.8119
Autonomy over the day0.7617
Communication overhead0.4112
Home workspace quality0

The per-category table is the useful part. Communication overhead at 0.41 is a definition problem you can fix — sharpen it and re-run. Home workspace quality shows "—" because neither coder used it: with no variance there is nothing to correct against chance, and reporting 0 there would claim disagreement about a category both coders agreed on perfectly.

For your methods section

The codebook was generated computationally from the full dataset (n = 312 units of analysis) and then reviewed and revised by the researcher. The revised codebook of 9 categories was applied to the full dataset, with every assignment accompanied by a verbatim extract. To assess intercoder agreement, a random sample of 20% (n = 62) was independently re-coded blind to the computational assignments. Percentage agreement was 91.4% and Cohen's kappa, pooled across categories, was κ = 0.79 (substantial). Disagreements were reviewed and led to clarification of the affected category definitions.