The product needed user verification, changes to payment methods, and a way to ban violators. Some of these changes had to happen quickly. Regulatory requirements said customers must be told in advance, so we had a fixed 30-day window.
Problem
Approval took most of the time. Design got the least. Every message to customers had to be correct, complete and sent on time, and a missed change would turn into angry support tickets.
Visual placeholder: verification flow, recreated with sample data
Add: one recreated flow or notice screen without real names.
How I worked
Design in parallel with approval. I did not wait for sign-off to start flows and interface text. I prepared options, and approval changed details instead of restarting the work.
Flows. Verification, changes to payment methods and bans for violators, with clear states for each user.
Words on the screen. Interface text and customer notices, written to say what changes, when, and what the user should do.
Email. Templates and unsubscribe rules for the mailing service. Segmentation was handled by an analyst.
Terms and privacy. The compliance engineer wrote the legal texts, and I updated them in the product and kept track of the nuances.
Support. Before a big release I listed the questions customers would ask and answered them in the interface and in the documentation.
Result
The changes shipped inside the notice window. Support received fewer repeated questions, because the answers were already in the interface, and could react faster to real problems.
Add if true: one more qualitative result from the team, for example no missed notices or a calm switch for customers.
What I learned
Mailings are serious, and few people want to dig into them. Very few people even had access to the sending step. I learned the basics of terms of use, privacy texts and correct bulk email, and I now plan the approval path before I draw the first screen.