Google Sheets for UX researchers on Mac in 2026: shortcuts, pivots, SUS scores, and Lazur

UX researchers use Google Sheets on a Mac for survey exports, usability session logs, SUS scores, and coding of open-ended answers. You open it in a browser on your Mac, and that works well for most of this job. This page covers setup, shortcuts, pivot tables, and the size limits that trip people up. It also shows where Lazur helps, and where it stops.

How Google Sheets runs on a Mac

Google's pages did not confirm a native Mac app, so plan on a browser tab. Chrome, Safari, and Firefox can all open Sheets. Google's product page lists co-editing, revision history, sharing controls, and offline access. Revision history lets you roll back a bad cleanup. Sharing controls let you limit who can edit or view.

Know one Safari detail. A May 2023 Apple Community thread described large sheets in Safari loading the first rows, then stalling. Chrome and Firefox worked in the same report. The thread was later marked as a Google problem that Google fixed. If a big sheet hangs in Safari, open the same file in Chrome before you blame your data.

Google Sheets keyboard shortcuts on a Mac

Google keeps the full shortcut list on one help page. Press ⌘ / inside a sheet to see it. The four shortcuts below cover most research work. Learn them in your first week, and you will reach for the menu bar less.

The Tool finder is the one to learn first. When a command hides in a menu, open the Tool finder and type the words you remember. Lazur can also help. Hold ⌥⌘ and ask where a command is, and Lazur circles it on screen and labels it.

Set up a research sheet that stays fast

A good research sheet has three layers. Keep the raw export on its own tab, and do not edit it. Put cleaned data on a second tab, with one row for each session or response. Put summaries, pivot tables, and charts on a third tab. When something breaks, you can trace it back to the export that came from your survey or session tool.

• Name tabs by what they hold, such as raw_survey, clean_sessions, and summary.
• Put one header in row 1 for every column. Pivot tables need headers.
• Use one column for each variable. Never put two answers in one cell.
• Use participant codes, not names, in the clean tab.

Delete empty rows and columns you do not use. A third-party guide by Ben Collins says blank cells slow Sheets down dramatically. Keep your data range tight, so formulas and pivots only read the rows that matter.

Pivot tables for task success and time on task

Pivot tables answer the questions most usability studies ask. Which task failed most often? Which tasks took longest? Start with the clean tab. Select the source cells, including the header row. Then go to Insert > Pivot table, and choose a new sheet for the output so the raw data stays clean.

1. Select the cells in the clean tab, header row included.
2. Go to Insert > Pivot table, then choose a new sheet.
3. In the side panel, add the task column under Rows.
4. Add the completion column under Values, and set the summary you need.
5. Add time on task under Values, and set it to average.

Google's help says a pivot table refreshes any time you change its source cells. You do not need a refresh button. If the numbers look stale, check the source range first. A range that stops early will miss rows, and Sheets will not warn you.

SUS score in Google Sheets: method and template

The System Usability Scale, or SUS, turns a short questionnaire into one score. Lyssna offers a Google Sheets template for it. You export results as CSV, import them, and the scores calculate. If you want to build the sheet yourself, the method is simple. Here are the steps in plain order.

1. For each odd-numbered item, subtract 1 from the response.
2. For each even-numbered item, subtract the response from 5.
3. Add all the adjusted values for one participant together.
4. Multiply that total by 2.5 to get the SUS score.

In the sheet, place each adjusted item in its own column. Use one SUM formula per participant row, then multiply the result by 2.5. Keep the raw responses beside the score, so you can check one row by hand. Check a few rows this way before you trust the whole column. Hold ⌥⌘ and ask Lazur to explain the formula on screen if you get stuck.

Watch for skipped items. A blank answer changes the total, and a formula may treat it as zero. Decide your rule before you export. For example, you can drop any participant with a missing item. Write that rule on the summary tab, so a second researcher reads the same logic.

Import survey and session exports without losing data

Survey and session tools usually export CSV files. Use File > Import in Sheets, then choose the file and the separator. Excel files work too. Google's Workspace page says you can open and edit Excel files in Sheets without making a copy.

Converting Excel files has one trap. Google's Drive help says a conversion drops any cell over 50,000 characters. Long interview quotes and open-ended answers are the usual victims. Before you convert, search the export for the longest text cells. Keep the original file, so you can compare the two after the import.

Google Sheets size limits for research files

Google's Drive help gives a file limit of up to 20 million cells or 100 MB. Connected Sheets lets you analyze BigQuery or Looker data without writing SQL. Its pivot tables cap at 200k rows. Extracts run to 500k rows or 5 million cells. Plan your structure before a study grows past those numbers.

Those limits rarely hit a single study. They hit a tracker that grows every month. When a file starts to lag, split the raw data by quarter into separate files, and keep one summary file that reads from them. Keep an index tab with the file names, so the next person can find the data fast.

Why Google Sheets is slow on Mac, and what to fix first

Slow sheets usually have a few causes, and you can check them in order. Ben Collins' guide says Google doubled the speed of calculations in a June 2024 update. Formula design still matters, though. These are the causes to check first.

• Blank cells. Delete empty rows and columns in the data range.
• Volatile functions. TODAY, NOW, RAND, and RANDBETWEEN recalculate on every change.
• Array VLOOKUPs. The guide says they run significantly slower than single VLOOKUPs.
• Conditional formatting on large ranges. Limit the rule to the rows you actually use.
• IMPORTRANGE. The guide says it can stall around 20,000 rows.

The TODAY case is easy to fix. In one blogger's test, 100,000 TODAY formulas took about 5.5 seconds. With a single cell reference, the same job took about 4.1 seconds. That test ran once, on an unknown date, so read it as a direction, not a benchmark. Put the date in one cell, and point your formulas at that cell.

Code open-ended answers in a sheet

Qualitative coding fits well in Sheets. Use one row for each quote. Add columns for participant code, task, and one or more theme labels. Filter by theme to read every quote that fits. Then build a pivot table that counts themes by task. Keep a codebook tab that defines each theme, so a second coder can match your labels.

Templates from the Template Gallery

Templates save setup time. Open the Template Gallery at the top right of the Sheets home page, and pick one. Google opens a copy, so the template stays unchanged. Some template features only work with a work or school account. Check that before you build a tracker on a personal account. If the menu has moved, look for the gallery on the home screen.

Gemini in Sheets for cleanup and formula help

Google's Workspace page lists Gemini features in Sheets. You can build a sheet from a prompt, fill a column with Gemini, and ask it to write or debug a formula. Google's October 16, 2025 update adds multi-step edits. One prompt can add conditional formatting, add a pivot table, run find and replace, and clean up data in plain language.

Use it for the boring cleanup. Ask it to merge 'Very satisfied' and 'very satisfied' into one label. Then check a sample of changed cells by eye. Review every automated edit before the sheet goes to a stakeholder, the same way you would check a colleague's work.

Where Lazur fits into your Sheets work

Lazur is a voice assistant for the Mac. It lives in the notch. Hold ⌥⌘ to ask about anything on screen, and Lazur answers out loud. Lazur sees your screen only while you hold the shortcut. It points at things, explains steps, and guides you one click at a time. It waits for each click. It does not click for you or edit your files.

• Ask where a control is. Lazur draws a circle and a label around it.
• Ask how to do a task. Lazur guides you one click at a time, waiting for each click.
• Hold fn to dictate session notes at the cursor in any app.
• Ask Lazur to draft a participant thank-you note or a finding summary.
• Send a research question to run in Lazur's own Chrome tabs. It returns a summary and a report.

Ask Lazur to walk you through your first pivot table. You keep your hands on the mouse, and each click waits for you. That can suit a first pivot better than a long video. Once you know the steps, ask Lazur for a shortcut or a quick formula check.

Lazur runs on macOS, on Apple silicon and Intel Macs. Windows is planned, not available. It starts with a free trial that does not need a credit card. Check the pricing page for current plans, and download Lazur to try it on your Mac.

Mistakes UX researchers make in Google Sheets

• Mixing raw data and summaries on one tab. One careless edit can break both.
• Leaving a column without a header. A pivot table needs a header for every column.
• Editing the raw export. Copy it first, then change the copy.
• Trusting a pivot table without a check. Compare a few totals with the raw rows.
• Putting long quotes in cells, then converting from Excel. Cells over 50,000 characters get dropped.
• Sharing with edit access when you meant view access.
• Leaving pivot suggestions on in a file you share with stakeholders.

Most of these mistakes come from speed. A deadline pushes you to skip the setup. Spend a few minutes on tabs and headers at the start. That time pays back when you add a second study and the first one still reads cleanly.

Protect participant data in a shared sheet

Research sheets often hold personal details. Use participant codes rather than names. Check your organization's rules before you put interview data in a shared sheet. Google's sharing controls let you choose who can edit or view. Review those settings each time you share a file, not once a year.

Lazur listens and looks at your screen only while you hold the shortcut. Audio and the screenshot go to AI providers to answer you. They are not stored. Content is never used to train AI models. A screenshot of a sheet can still show names or quotes. Hold the shortcut only when you need help, and close sensitive tabs first.

Next steps after your first study

Start with one study. Build the three-tab layout, add headers, and make one pivot table. Then add the SUS template if you run usability questionnaires. If your team also works in Figma, read Figma for UX researchers on Mac for FigJam templates and memory fixes. Sheets stays the place for the numbers. Your other tools can link back to it.