Designing through ambiguity

CoinTracker’s 1099-DA experience

I helped lead the design of a new tax workflow that helped crypto users understand, upload, reconcile, and act on a brand-new IRS form before the industry had a clear playbook

Team

PM, UXR, Eng, CPAs, UX content, & Me

Timeline

About 7ish weeks

Status

Shipped and live in January 2026

The problem

Crypto users were about to receive a new IRS form called the 1099-DA from exchanges and brokers.

Many users would not know what the form meant, whether the data was accurate, or what they needed to fix before filing.

What do users care about?

What do users care about?

What happens if I ignore this?

What happens if I ignore this?

What happens if cost basis is missing?

What happens if cost basis is missing?

What do I need to do next?

What do I need to do next?

What is a 1099-DA?

What is a 1099-DA?

Is my exchange data correct?

Is my exchange data correct?

Why this was hard

This was not a normal feature where the rules were stable and behavior was known. The form, requirements, and industry expectations were still forming while the product was being designed.

Why this was hard

This was not a normal feature where the rules were stable and behavior was known. The form, requirements, and industry expectations were still forming while the product was being designed.

The form was new

Users had no existing mental model for what a 1099-DA meant.

The form was new

Users had no existing mental model for what a 1099-DA meant.

Rules were evolving

The team had to design flexible flows while tax guidance was still being interpreted.

Rules were evolving

The team had to design flexible flows while tax guidance was still being interpreted.

Trust mattered

Users needed to understand why CoinTracker could help validate cost basis and mismatches.

Trust mattered

Users needed to understand why CoinTracker could help validate cost basis and mismatches.

My role

I translated tax complexity into a guided product experience, working closely with CPAs, PM, UXR, and engineering.

My role

I translated tax complexity into a guided product experience, working closely with CPAs, PM, UXR, and engineering.

Mapped user journeys

Created early concepts

Partnered with two CPAs

Designed edge cases

Defined final states

Progress

Users needed exchange-level progress.

Explanations

Mismatches needed plain-language explanations.

Discovery

Before final screens, I worked with the team to understand core tax scenarios, user risks, and product requirements.

Learnings

Users needed education before action.

Early concepts

Exploring different ways to guide users.

Early concepts

Exploring different ways to guide users.

Education-first entry

A lightweight explanation of the new IRS regulation before asking users to upload or review anything.

Exchange checklist

A task-based list showing which exchanges needed action, which were completed, and which were waiting on forms.

Upload and match flow

A guided way for users to upload a form and compare it against CoinTracker data.

Reconciliation dashboard

A summary view showing proceeds, cost basis, mismatches, and next steps.

Focused tax flow

A more focused workflow that reduced distractions and helped users complete the task.

Missing form state

A path for users who had not received a 1099-DA yet, so they could return later.

We tested whether users could find the workflow, understand why it mattered, and confidently identify what action to take next.

We tested

Start points, upload flow, reconciliation, exchange statuses, and next actions.

We learned

Users needed reassurance, simpler tax language, and clearer progress by exchange.

What changed

We improved education, hierarchy, mismatch copy, and completion states.

UXR testing

Before final screens, I worked with the team to understand core tax scenarios, user risks, and product requirements.

UXR testing

Before final screens, I worked with the team to understand core tax scenarios, user risks, and product requirements.

User sentiment

Before final screens, I worked with the team to understand core tax scenarios, user risks, and product requirements.

User sentiment

Before final screens, I worked with the team to understand core tax scenarios, user risks, and product requirements.

Challenge 1

Users who visit only during tax time skip instructions/copy

Solution: Design for users who only show up during tax season and may skip instructions or detailed copy. Make the experience clear enough for tax-time users who skip detailed guidance.

Challenge 2

Calling out “audit risk” early creates heightened fear, users question every step

Use language that feels encouraging and confident, without sounding too alarming or overly promotional.

Challenge 3

Users are confused by adjustments—what’s the purpose? What’s their task?

When showing two different numbers, always explain what each one represents, what is driving the difference, and why it matters to the user.

Final journey

A guided path from confusion to completion

Final journey

A guided path from confusion to completion

Waiting for form

Mismatch found

Error state

Completed

Duplicate exchange

Built for real tax-season usage

Impact

The final experience launched as part of CoinTracker’s tax-season product and helped users navigate a new IRS reporting requirement with more clarity and confidence.

8M+ eligible
users

8M+ eligible users

User sees a 1099-DA entry point in the tax experience.

38% completion
rate

38% completion rate

User sees a 1099-DA entry point in the tax experience.

2026 tax
season ready

2026 tax season ready

Designed for launch and extension-period usage.

Designed for launch and extension-period usage.

What this project taught me.

This project pushed me to design with more ambiguity than usual. We were working with new IRS requirements, incomplete industry standards, and users who had no mental model for the form yet.

The strongest part of this project was not just designing screens for a tax form. It was helping create clarity around a new, high-stakes tax experience before the industry had a clear playbook.

What this project taught me.

This project pushed me to design with more ambiguity than usual. We were working with new IRS requirements, incomplete industry standards, and users who had no mental model for the form yet.

The strongest part of this project was not just designing screens for a tax form. It was helping create clarity around a new, high-stakes tax experience before the industry had a clear playbook.

© 2026 GaryDid. All rights reserved.

© 2026 GaryDid. All rights reserved.

© 2026 GaryDid.

All rights reserved.

© 2026 GaryDid. All rights reserved.