
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 happens if I ignore this?
What happens if cost basis is missing?
What do I need to do next?
What is a 1099-DA?
Is my exchange data correct?










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.

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.
What we tested
Start points, upload flow, reconciliation, exchange statuses, and next actions.
What we learned
Users needed reassurance, simpler tax language, and clearer progress by exchange.
What changed
We improved education, hierarchy, mismatch copy, and completion states.







