I wrote what I believe is my best piece of name handling last year. It had three fields legal_name, interpersonal_name, alias. When the user was signing up, t

I wrote what I believe is my best piece of name handling last year. It had three fields legal_name, interpersonal_name, alias. When the user was signing up, they were prompted with three questions: --- Your legal name that must appear on documents such as invoices and contracts: <signed xxx> The alias you would like us to use in our interface and emails, that only you see: <hi xxx> The name we should show other people when referring to you in our interface: <request from xxx> --- The page had live examples alongside, and checkboxes for 'as above'. I was worried I had overcomplicated it, but a lot of my early feedback called out that they liked it without prompting. It is worth saying the system is never expected to scale past a few thousand users, these users are professionally motivated and pay or get paid for the service - as such I could say "anything goes" in the content of the fields without abuse being likely. Conflicting names are discovered through distance measurements and flagged up to an admin to determine whether they should be resolved.