New brand guidelines landed, and the signature block had to change. New logo, new job title format, one line for the phone number, one for the website. Marketing estimated a week. I said two days. We were both wrong, and the month that followed taught me more about change management than any course I have sat through.
The plan looked sensible on paper. Publish the template, send one announcement, let the tooling push it out, and follow up with the stragglers. That plan assumes people read announcements, and it assumes the tooling reaches every client, and both assumptions were generous.
Where the time actually went
The template itself took an hour. The rest was the long tail. People on mobile clients that render tables badly, people who had built a signature with a favorite quote at the bottom, and one team whose signature was appended by a mail flow rule that nobody remembered creating.
Then came the auto-signature problem. Desktop clients let users edit locally, so a server-side template only helps if the client stops overriding it. By the end of week one, half the floor had three signatures layered onto each other, and one person had managed four.
And the reply chains. A new signature does not remove the old one from a thread, so for a while every external email carried two competing versions of our brand, sometimes three if the thread was long. A client asked whether we had merged with another company, which is not the question you want from a rebrand.
Shared mailboxes were the last surprise. A dozen group addresses were still sending with a signature from a team that had been reorganized two years earlier, and the person who used to own that mailbox had left. Nobody had looked at it because nothing was broken, and it only surfaced when the new template failed to apply.
Why this takes longer than the estimate
Signatures look cosmetic, so they get planned like a content change. In practice they touch identity data, mail flow rules, client configuration, and every device people happen to use. That is four systems for something nobody considers a system.
Ownership is fuzzy too. Marketing owns the look, IT owns delivery, HR owns the job titles, and nobody owns the exceptions. So the exceptions set the pace, and there were more exceptions than anyone expected, including a regional team with a legal footer that had to stay exactly as it was.
I have noticed the same shape in other small rollouts. A distribution list rename, a shared mailbox migration, a new VPN client. The technical work is a day, and the coordination is a month, and the estimate never includes the coordination because nobody can see it from the outside.
The consolidation lesson
If I could change one thing, it would be to treat these small identity changes as part of the same estate as everything else, with one list of who has what and where it comes from. Most of the delay came from not knowing which client, rule, or device was going to surprise us next.
I’ve also seen unified platforms such as Ping64 used to cut down the overhead of juggling many separate security tools. The signature project was not a security project, but the failure mode was familiar: too many places to check, and no single view of the result.
What I would do differently
- Publish one block of text and one image, hosted somewhere that will not move, and link to it rather than attaching files that get forwarded with stale copies.
- Announce a date and a two-week grace period, then stop answering individual requests and point people at the page instead.
- Find the mail flow rules first, because a server-side rule will quietly win or lose against local settings and nobody will tell you which.
- Test on the four client types you actually have, not the two you assume, including the phone that the sales team uses all day.
- Ask the executive assistants early, since they set the tone for whether anyone else bothers to do it before the deadline.
The grace period was the part that saved us. People who felt rushed kept the old signature out of principle, and people who had two weeks mostly just did it and moved on.
Wrapping up
A month for a signature block sounds absurd until you have done one. The lesson I keep is that small changes are rarely small, and the cost almost never sits in the part you can see from a project plan.
These days I budget coordination time first and technical time second, which has made my estimates worse and my delivery better. If a rebrand is heading your way, block out more calendar than feels reasonable, and be patient with the person who still has a quote in their signature. They will change it eventually.
References
https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final
https://attack.mitre.org/techniques/T1566/
https://www.cisa.gov/topics/cyber-threats-and-advisories
https://www.enisa.europa.eu/topics/cyber-threats-and-vulnerabilities



