Design Manual¶
- Design and a11y review process
- Direct File Design System Wiki
- Taxonomy and Nicknames
- Information Architecture and tax preparation task flow
- Organizing terms (internal)
- Pages types: Navigational
- Page Types: Flow screens
- Communicating scope
- Message system
- Direct File Design Guidelines & Processes
- Product vision
- Operating Principles
- We are collaborative.
- We design with taxpayers, not for taxpayers.
- Content is the design.
- We exclusively design in mobile dimensions.
- Good design is design that works for everyone.
- Filing in other languages should be just as easy as in English.
- Progress, not perfection.
- We use lean and sustainable processes.
- Understanding taxpayers
- Beyond 508 Compliance
- Flow logic: How were the questions designed and sequenced?
- Data Import system
- Paper Filing Path
- Rejections design guidelines
- Direct File Email Messaging
- Looking Ahead: Future Design Problems to Prioritize
- Future Improvements to The Direct File Screener (eligibility checker)
- Future Improvements to Direct File Information Architecture (IA)
- Deeper look at hypotheses
- Hypothesis # 1: DF should group income types into categories.
- Hypothesis # 2: DF should separate the reporting of taxable payments from follow-up questions about complex tax situations.
- Hypothesis # 3: DF should only show tax forms/situations on the Checklist that are relevant to that TP.
- Hypothesis # 4: DF should allow TPs to report income tax forms in any order.
- A small tangent: why “other tax situations” is hard to categorize
- Conclusion
- Tasks
- For Future Exploration: Adding A “Getting Started” pre-tax-prep module
- Direct File Content Approval Process
- Content Batch workflow
- Insights to action
- Resources for Learning About Taxes
- Direct File Content Style Guide
- Direct File Taxpayer Foundational Research
- Research Templates and Protocols