Category: Career Advice

  • The Day My Boss Divided an Email into Four Equal Parts

    The Day My Boss Divided an Email into Four Equal Parts

    Image by macrovector on Magnific

    He was so excited about his idea.

    The email would go to, well, everybody. It would be divided into four equal sections, each featuring one of our product categories. We would list the manufacturers in each category and link them to our website.

    Before I throw him completely under the bus, you need to know something about my former boss.

    He was an incredible salesman. Energetic, charismatic, and no one knew our products better than he did. He could talk to a customer for five minutes and know exactly which product mattered, which objection needed answering, and which detail would close the sale.

    You also need to understand that the production industry was in the middle of a messy transition from tape to digital. Some customers were investing in solid-state workflows. Others were searching for professional-grade tape as shortages disrupted supply chains. Everyone was trying to figure out what came next.

    So from his perspective, the idea made sense. Show everyone everything. Let them choose what mattered.

    But I knew the email would fail.

    I had recently run a layout test. One version gave every product equal weight. Another was built around a single featured item with three smaller related products.

    The single featured item won. By a lot.

    I didn’t know how to calculate statistical significance yet. But I knew I was onto something, and the email he wanted to send was going in the wrong direction.

    When everything is important, nothing is important.

    Most people approach their inbox the way I approach a Whitman’s chocolate sampler box. They open it, poke around for a few seconds, and hope to find a caramel.

    That’s how email works. A quick glance of three or four seconds before they move on to the next message.

    If someone gives you three seconds of attention, a hero image can grab them. A clear recommendation can grab them.

    Four equally sized images usually won’t.

    My boss thought customers wanted choices. I knew they wanted direction.

    The campaign was a disaster.

    If memory serves, it didn’t generate a single sale. I wish I could tell you there was some hidden victory, like it generated a bunch of traffic. Nope. Or that it sparked useful conversations with customers. Not that either.

    It was exactly what I expected: four equally important pieces of information that nobody knew what to do with.

    At the time, I was frustrated because I had already run the test and seen the results. Larger featured products outperformed evenly weighted layouts.

    What I didn’t appreciate yet was that I was making my own version of the same mistake.

    I understood that customers needed direction. But I didn’t realize that my boss did too.

    I treated the conversation like the data should speak for itself. I wanted him to look at the results, connect the dots, and arrive at the same conclusion I had.

    But bosses are audiences too.

    And smart audiences still need help knowing which information matters. My boss was one of the best salespeople I’ve ever worked with. But sales conversations and emails are not the same thing.

    A salesperson can answer questions. A salesperson can adjust in real time and steer the conversation toward what matters most.

    An email gets a few seconds. And hopefully, someone finds the caramel.

    I’ll make other campaigns that fail. I’ll adjust, correct course, and move on. But I remember this one because it taught me that persuasion isn’t about adding information. It’s about helping people see what matters first.

    Sometimes that means helping a customer find the caramel. 

    And sometimes, it means helping your boss do the same.

  • Why I Still Hire Lifecycle Marketers Who Know HTML

    Why I Still Hire Lifecycle Marketers Who Know HTML

    Image designed by Freepik.

    When I hire someone for a lifecycle or CRM role, I have two non-negotiables.

    First: experience with any major ESP or CRM platform. Iterable. SFMC. HubSpot. Braze. I genuinely do not care which one. Despite what vendors claim, if you deeply understand one platform, those skills transfer. Data models and UI change, concepts do not.

    Second: basic HTML literacy.

    I don’t demand mastery or perfection, but I want my new hires to be able to hand-code a simple HTML email from a blank file using a notebook.


    What I Actually Expect (and What I Don’t)

    I do not expect:

    • Perfect syntax on the doctype tag
    • Deep CSS wizardry
    • Dark-mode sorcery
    • Pixel-perfect rendering across every email client

    I do expect:

    • Tables instead of divs
    • Clean, readable nesting
    • An understanding of how email HTML is different from web HTML
    • The ability to look at code and reason through what’s broken
    • Bonus points if you have usable comments throughout.

    “But We Use Drag-and-Drop Now”

    So do I. Drag-and-drop editors are so much better than they were even five years ago and I’ve grown to really enjoy using them.

    My team uses AI to help with conditional logic, personalization rules, and even layout experiments. That’s not the issue.

    The issue is that drag-and-drop has limits.

    Eventually:

    • The template won’t support the layout you need
    • The editor will introduce unnecessary wrappers
    • You’ll need to insert a custom HTML block to get the effect you want

    And when that moment comes, someone on the team needs to know what they’re looking at.


    AI Is Helpful. AI Is Also Wrong. A Lot.

    AI can:

    • Write conditional logic fast
    • Scaffold a layout in seconds
    • Save time on repetitive patterns

    AI can also:

    • Close an if statement too early
    • Nest tables incorrectly
    • Break mobile layouts in subtle ways
    • Introduce rendering issues that only show up in Outlook

    When that happens, the worst possible position to be in is trying to use AI to bug AI’s own broken code when you don’t understand HTML yourself.

    That is how a five-minute fix turns into a long, painful afternoon.

    If you can read the code and say:

    • “Oh, this table is closing too early”
    • “This conditional is wrapping the wrong element”
    • “This nesting is why the layout collapses on mobile”

    You’re back in control.


    HTML Is Not About Coding. It’s About Thinking.

    Basic HTML knowledge isn’t really about code. It’s about:

    • Understanding structure
    • Spotting patterns
    • Debugging logically
    • Not being blocked by tooling

    Lifecycle marketing lives at the intersection of:

    • Data
    • Logic
    • Messaging
    • Execution details

    HTML sits right in the middle of that intersection.


    The Bottom Line

    Tools change, platforms change, and AI will keep getting better. But the ability to look at a block of HTML (or any code) and understand what’s happening is still one of the most reliable forms of low-hanging fruit in lifecycle marketing.