← Back to Work

Professional Tax Product Form Help

Designing in-product, form-level guidance within a regulated tax environment

Client: Intuit ProTax Group Year: 2023-Present

Overview

Design process wireframes

This project focuses on how in-product, form-level guidance was designed, operationalized, and scaled within a regulated tax environment.

The goal of this system was not simply to add more help content, but to design a preventative content layer that reduces errors, minimizes support dependency, and preserves user trust during high-risk workflows.

Problem Framing

A professional tax product, Lacerte supports hundreds of federal and state tax forms across multiple tax entities. Many individual inputs:

  • Represent complex tax concepts
  • Depend on nuanced eligibility rules
  • Carry downstream compliance risk if completed incorrectly

Despite comprehensive external documentation, users frequently encountered confusion at the exact moment of data entry, leading to:

  • Form errors discovered late in the workflow
  • Increased calls to support
  • Repeat questions tied to the same high-friction inputs

The core challenge was not content coverage, but contextual delivery.

My Role & Ownership

As a UX Content Designer on the ProTax Group Digital Delivery team, I owned the Lacerte Forms Help experience end-to-end, including:

  • Identifying which form inputs required additional guidance
  • Defining content patterns and terminology standards
  • Writing and maintaining the underlying help content
  • Translating content strategy into technical artifacts consumable by the product
  • Partnering with engineering, tax development, and compliance teams to ship updates safely

Identifying High-Risk Inputs

Not all form inputs warrant in-product help. To prioritize effectively, I evaluated inputs based on:

  • Frequency of related support contacts
  • Historical confusion or misinterpretation
  • Regulatory sensitivity
  • Downstream impact of incorrect entry

This ensured the system focused on high-leverage moments, rather than overwhelming users with excessive guidance.

Content Design Strategy

Structured content design approach

Writing for In-Product Context

Form-level help content was written to:

  • Assume users are mid-task and time-constrained
  • Focus on what to enter and why it matters
  • Avoid unnecessary tax theory unless required for correctness

Tone and structure prioritized clarity, neutrality, and confidence.

Terminology & Pattern Consistency

To scale across thousands of inputs, I:

  • Established repeatable content patterns
  • Standardized terminology across similar concepts
  • Reduced variation that could introduce doubt or confusion

Technical Implementation

Mapping Forms to Content

Each help access point required precise mapping between:

  • Tax module (e.g., Individual, Partnership, Corporation)
  • Jurisdiction (Federal or State)
  • Form container
  • Specific input field

I documented these mappings in structured CSV files, with each row representing a single in-product access point.

Deep-Linking Strategy

Rather than linking to generic articles, help access points used anchor links that:

  • Dropped users into the exact relevant section
  • Reduced scanning and cognitive load
  • Kept users oriented within the task

Build & Release Pipeline

The CSV files were converted into XML and delivered to engineering partners for inclusion in product updates. This pipeline ensured:

  • Version control
  • Predictable release cycles
  • Clear ownership of changes

Cross-Functional Collaboration

Shipping form-level help required alignment across:

  • Tax subject-matter experts (accuracy)
  • Engineering (delivery and performance)
  • Compliance and legal teams (risk mitigation)

Tradeoffs were often necessary between:

  • Completeness and brevity
  • Speed of delivery and review rigor
  • Flexibility and standardization

Outcomes & Learnings

What Worked

  • Designing content as part of the product, not an external reference
  • Prioritizing high-risk moments over exhaustive coverage
  • Building repeatable systems rather than one-off solutions

What I'd Improve

  • Earlier instrumentation for measuring in-product usage
  • Faster feedback loops from support teams
  • Expanded automation for identifying new high-risk inputs

Why This Matters for Trust & Safety

Trust & Safety work often focuses on:

  • Preventing user harm
  • Reducing error states
  • Supporting users in moments of uncertainty

This project demonstrated how in-product content design can function as a Trust & Safety mechanism, quietly preventing issues before they escalate and reinforcing trust through clarity and restraint.