Smartsheet2025–2026

Smartsheet Reports

The Report asset in Smartsheet combines data across multiple Sheets.

I led the effort to modernize the experience and help leadership decide how Reports should fit alongside adjacent platform capabilities.

HOW IT WORKS

Select Sheets

Choose the Sheets that power the Report.

Manage fields

Choose columns or summary fields to include.

Define rows

Choose which rows are included.

Smartsheet spent much of the 2020s rebuilding the core views within its primary asset, the Sheet.

Bringing those new views to the Report was the natural next step.

Table

Board

Timeline

More than a reskin

Early explorations made it clear there were fundamental issues preventing people from getting the most out of the tool.

The legacy Report bundled data aggregation and display controls into one admin-only configuration layer. Collaborators, anyone shared to the Report below admin level, got a read-only view with no ability to explore the data themselves. At the same time, the creation experience felt cumbersome and unintuitive, creating unnecessary friction for report builders.

TWO BIG PROBLEMS

Collaborator

Rigid consumption

Collabs are stuck with the admin’s setup, unable to filter, group, or sort the data for their own needs.

Creator

Guidance & usability

Defining which Sheets, fields, and rows belonged in the Report was complex, with clunky controls and little guidance.

Pulling the configuration model apart

The core insight was that some admin controls were essential to defining what data was included and how it was aggregated, while other controls were purely for changing the display of data.

We consolidated source data to three steps and isolated them from the display controls in the toolbar.

Aligning with nascent capabilities

The Sheet team was introducing a new way to save filters, groups, and sorts to views. This lent itself to the ability for admins to maintain curation of display controls while enabling collaborators to deviate.

I worked with that team to keep Sheets and Reports consistent, since both used the same view primitives.

Contributing new features

Reports needed grouping and summary calculations to reach parity with the legacy experience. Those features did not exist in the Sheet, so we designed with the intention to extend back to the Sheet.

SPEC SAMPLES

Figma Make

Prototype of grouping interaction and menu logic.

Figma Spec

Complete details for grouping and summary calculations.

Defending the Report's right to exist

Halfway through the project, our CPO asked whether Reports needed to exist at all. The question was fair: Smartsheet had several tools built on the table primitive, and customers were confused which tool was right for their job.

Reports, Custom Views, and Dynamic View all touched the same problem space, but no one owned the overlap strategy. I stepped in to lead the alignment across teams, map tradeoffs, and drive the group toward a clear path forward.

Leadership impact

I turned cross-team ambiguity into a clear direction people could build toward.

Reports stayed separate

Avoid a risky and expensive migration path for millions of existing Reports.

Sheet gained parity

Extend grouping and summaries into Sheets to reduce Report dependency.

Reports got clearer framing

Explore naming around Reports’ real value: combining Sheet data into one view.

Carrying the work forward

A company reorg moved me to another team before all planned releases were complete. I partnered with the incoming designer and PM to transfer the work and shape future releases, including Report rebranding and Smart Assist (AI) integration.

This project clarified the kind of impact I want to have: stepping into ambiguity, connecting teams, and turning competing directions into a product strategy people can build toward.