Tenon • Internship • Shipped

Empowering marketers with insights that drive confidence

Role

Product Designer
UX Researcher
Product Strategist

Timeline

May - August 2025

Team

2 Product Managers
5+ Developers
2 Marketers
Product Design Lead

Skills

Product Design
User Research
Design Systems
Cross-functional Collaboration

Tenon is a CRM with thousands of marketers creating, managing, and optimizing their campaigns.

With control over email/SMS campaigns, contacts, attribution, and performance across the customer lifecycle, marketers using Tenon’s CRM do important work for their teams. However, the platform’s original home page wasn’t supporting marketers with the streamlined processes they expected. My role during my internship at Tenon was to redesign the home page as a functional MVP.

Tenon case study splash image

The homepage was not helping marketers move through their day.

The platform’s original home page was just an empty placeholder screen created by developers. It showed basic email activity, but offered no real orientation, insight, or action. There was friction embedded within every action and certainly did not support the streamlined CRM processes marketers expected.

Original Tenon home page screenshot

Researching what marketers value in their CRM software.

To close that gap, I combined user interviews, a brief focus group, competitive analysis, heuristic evaluation, and contextual inquiry. Research was limited by time and budget, so I used a small but fast-moving mix of methods to understand how marketers actually worked through the platform.


That process mapped a consistent workflow:

Friction journey workflow diagram

The workflow itself was not broken. Marketers generally knew what they needed to do. The problem was the friction layered into every step.


Users were constantly jumping between pages, scrolling through long tables, manually searching for campaigns, and piecing together performance across different objects. Each issue looked small on its own, but together they increased cognitive load and made the product feel heavier than it needed to be.


I grouped these problems into three core friction types:

Orientation friction

Users landed on a static homepage with no immediate signal, summary, or next step.

Navigation friction

Resuming work or creating something new required too many clicks, too much page switching, and too much manual searching.

Insight friction

Performance data existed, but it was not aggregated in a way that supported quick decisions.

Framing the problem this way helped me move from isolated usability issues to a more systemic opportunity. The homepage did not just need better widgets. It needed to reduce friction across the marketer's daily workflow.

My mission was to bring clarity to this mess.

I used affinity mapping to cluster ideas directly around the workflow breakdowns, then narrowed scope through card sorting across three tiers: realistic, optional, and stretch. After that, I used an impact versus effort evaluation to prioritize concepts based on how much they reduced workflow friction, how feasible they were for engineering, and whether the required data was actually available and reliable

Affinity mapping, card sorting, and prioritization exploration

This process cut ideas that depended on immature data models or heavy backend work and surfaced a clearer MVP direction. I then moved into sketches and low-fidelity wireframes to test hierarchy, layout, and entry points into key workflows.

How do we provide valuable performance insights?

Everything else on the homepage was relatively straightforward and tested well with users. The main open question was how to surface performance insights in a way that felt useful, lightweight, and realistic to ship.


Competitive analysis showed that other marketing CRM homepages often relied on data visualization to communicate performance at a glance. Early on, that direction had internal support and I explored chart-driven summaries for campaign health.

Competitive analysis of marketing CRM homepage interfaces

Later in the process, PMs shifted direction and reserved data visualization for a future reports page. I pivoted to an AI-driven performance section highlighting high and low performers.


High and low performers AI-driven performance concept

As feasibility reviews progressed, developers flagged backend aggregation and predictive logic constraints that Tenon's current system could not support reliably. I pulled the concept back to the core user need: fast, digestible performance feedback.


That led to the grounded Recent Performance module built from existing metrics, giving users a strong pulse check without speculative infrastructure.

I prioritized a simple, familiar, and clean interface.

With orientation, navigation, and insight friction clearly defined, I designed the homepage to function as a control center for the marketer's daily workflow.

Direct CTAs

Clear entry points reduced unnecessary page switching and made it easier to start new work from the homepage itself.

Recently Viewed and Drafts

These modules made it easier to resume in-progress work without digging through tactic pages or long tables.

Recent Performance

This module gave users an immediate pulse check on campaign health the moment they logged in. Instead of manually piecing together data from multiple pages, the homepage surfaced meaningful signals in one place, with room for a future advanced AI layer.

The goal was not just to improve a screen. It was to improve how marketers moved through login, action, and monitoring as one continuous loop, shifting the homepage from a passive landing page to an operational starting point.

The project moved faster than expected and created momentum beyond the original scope.

I completed the homepage in 6 weeks instead of the expected 10, and used the remaining time to support additional projects.

In final testing, every participant reported a clearer sense of their marketing journey compared with the previous homepage.

The feature also became part of ongoing client conversations, with 3 deals pending that included this direction.

What I learned

Designing at the systems level matters

The biggest shift in this project was realizing that the homepage problem was not really about one page. It was about workflow friction across the product. Once I framed it that way, the right solution became much, much clearer.

Rapid adaptability is part of the job

Between limited research bandwidth, ServiceNow constraints, and team changes midway through the internship, the process was rarely clean. I learned how to keep the work grounded in user needs while adjusting quickly to what was technically and organizationally real.