Email: Enterprise Internal Email Standards

Project Overview

  • Client: Bank of America
  • Role: Lead Content Strategist, UX Writer
  • Scope: Enterprise-Wide Internal Communications | Process Owner Education
  • Services: Content Strategy, Information Architecture, UX Writing, Design System Integration

The Challenge 

Internal communication overload degraded employee focus and lowered operational compliance across the organization. System owners sent unstructured, uncoordinated emails lacking actionable call-to-action (CTA) buttons, support links, or consistent visual hierarchy. Unstandardized layouts increased security risks by making legitimate internal messages difficult to distinguish from phishing attempts.

The Approach 

To standardize email design and reduce cognitive friction, I authored an enterprise email governance guide for application owners and internal communicators. The framework converts raw text broadcasts into scannable, functional UI notifications through structured content models and standardized visual components.

  • Communication Categorization Model: Established three distinct functional tiers (Action Required, Awareness, Announcement) to help authors define use cases, standardize audience targeting, delivery timing, and CTA mechanics.
  • Structural Information Architecture (5Ws Framework): Adapted journalistic conventions into a operational model (Who, What, Why, When, Where, How) to enforce clarity in body copy and metadata.
  • Subject Line Syntax: Formulated standardized subject line formulas incorporating required actions, target platforms, tasks, and deadlines to enable fast inbox sorting.
  • Visual Standards & Accessibility Guidelines: Integrated brand-compliant assets, clear button hierarchy, direct help desk links, full system name expansions, and screen-reader accessibility rules into standard layouts.

Content Governance & Education

I developed several education assets to walk email authors through:

  • Use Case Definition: Selection of the right email type for their audience and purpose (Use Case Definition)
  • Heuristics: Writing subject lines and email previews for scanning and sorting (Heuristics); Designing emails that
  • Information Architecture: Defining and prioritizing data points through 5W’s
  • Branding & Security: Pre-designed email templates promote and ensure design consistency and anti-phishing techniques
  • User Experience & Engagement: Pre-defined templates with CTA logic

EDUCATION ASSETS

  • Find Your Email Classification Matrix: Organizes internal communications by audience, intention, goal, and execution requirements across Action Required, Awareness, and Announcement tiers.
Matrix graphic categorizing internal emails into Action Required, Awareness, and Announcement columns detailing audience, goals, execution rules, and CTA standards.
  • The 5Ws Content Architecture: Outlines the core mandatory data points (Who, What, Why, When, Where, How) required for internal operational broadcasts.
Explanatory screen defining the Five Ws framework for email clarity, listing Who, What, Why, When, Where, and How with brief functional definitions.
  • Subject Line Structural Syntax: Demonstrates precise subject line construction for Action Required and Awareness notifications using visual callout arrows to break down required components.
Diagram illustrating subject line formulas for Action Required and Awareness emails with red arrows pointing to action indicators, system names, tasks, and due dates.
  • Pre-Designed Email Templates

With pre-designed email templates, application owners could

Business Impact & Results

  • Reduced Cognitive Load: Streamlined inbox management through standardized subject line formatting and structured layouts.
  • Increased Task Completion: Improved response rates and deadline compliance for mandatory system workflows using clear CTA buttons and explicit consequence statements.
  • Enhanced Security Profile: Established consistent visual typography and brand-approved assets to help employees identify legitimate internal communications and avoid phishing scams.
Illustration showing a "Before" email that does not have a clear subject line and does not indicate "Action Required." The email is written in paragraphs with no information hierarchy and there is no visible user path or call to action.
Illustration showing an "After" email with a clear subject line indicating "Action Required." The email provides scannable, essential details and a visible Call-to-Action, branded button.

This project was initiated and supervised by Bank of America’s (BofA) internal UX design studio, Enterprise Experience Design.

All work generated was a collaboration between me, an EXD designer and our design lead.

Because the work involved proprietary BofA information, this case study does not reproduce internal policies, procedures, or confidential content. Examples and visuals have been recreated or generalized for portfolio purposes, while preserving the underlying design approach and problem-solving process.

All materials presented in this case study are representative of the work performed and do not reproduce Bank of America’s internal policies or confidential content.