Authorities, Bad UX, Digitization

The other day at the business registration or: Digital vs. paper

A few days ago, I founded a new company and had to register a business. A quick search revealed that this should be possible online at hamburg.de. But then everything turned out completely different...

I got relatively far in the application section (without any major usability problems) but failed when entering the account holder (see picture below, Nr. 1) - please believe me that I entered the account holder according to the specifications. No idea what was going on there...
   
Eventually it worked, but the summary showed the very specific error message (see picture below, Nr. 2); of course, I knew immediately what to do... NOT!

1) The account holder must be specified. Valid values: max. length 120 characters; allowed are letters,numbers, and the characters “+ – . , &”;
2) Entry problems, Other document per file attachment missing


The application could not be sent, so I sent an email with a screenshot to the trade office to ask what the error could be. And here it comes: The first mail I received was the one below, telling me that I could expect an answer in about 8 weeks – which made me laugh out loud for the first time.

Dear Sir or Madam, We hereby confirm receiving your email. It is now being processed, which will take approximately 8 weeks due to the current situation. We therefore kindly ask you to refrain from any further inquiries. <br>Yours sincerely, Fachamt Verbraucherschutz, Gewerbe und Umwelt – Gewerberegister –

 
After all, 10 minutes later a second mail actually came from a section head (!) saying: “Dear Mr. Bosenick, better download the registration form from the office’s website, fill it out, scan your ID and send it to the above postal address. Regards…” That made me laugh the second time and also cry a little. So much for the authorities’ digitalization strategy.

Author

Tim Bosenik

Tim gründete SirValUse im Jahr 2000 und war Mitbegründer von nurago im Jahr 2005 und USEEDS im Jahr 2008. Als "Dinosaurier" in der UX-Branche konzentriert er sich auf die organisatorische Umsetzung von UX in Unternehmen und auf die Verbesserung der Mitarbeitererfahrung im digitalen Zeitalter.

Go back

Privacy settings

We use cookies on our website. Some of them are essential, while others help us to improve this website and your experience.
In this overview you can select and deselect individual cookies from a category or entire categories. You will also find more information about the cookies available.
Group Analyse
Name Google Analytics
Technical name _gat,_gtag_UA_120284862_1
Provider Google LLC
Expire in days 730
Privacy policy https://policies.google.com/privacy
Use Google cookie for website analysis. Generates anonymous statistical data on how the visitor uses the website.
Allowed
Group Essenziell
Name Contao CSRF Token
Technical name csrf_contao_csrf_token
Provider
Expire in days 0
Privacy policy
Use Serves to protect the website from falsification of cross-location inquiries. After closing the browser, the cookie is deleted again
Allowed
Group Essenziell
Name Contao HTTPS CSRF Token
Technical name csrf_https-contao_csrf_token
Provider
Expire in days 0
Privacy policy
Use Serves to protect the encrypted website (HTTPS) from falsification of cross-location inquiries. After closing the browser, the cookie is deleted again
Allowed
Group Essenziell
Name PHP SESSION ID
Technical name PHPSESSID
Provider
Expire in days 0
Privacy policy
Use PHP cookie (programming language), PHP data identifier. Contains only a reference to the current session. No information is stored in the user's browser and this cookie can only be used by the current website. This cookie is mainly used in forms to increase usability. Data entered in forms are e.g. B. stored briefly if there is an input error by the user and the user receives an error message. Otherwise all data would have to be re-entered.
Allowed
Group Essenziell
Name FE USER AUTH
Technical name FE_USER_AUTH
Provider
Expire in days 0
Privacy policy
Use Saves information of a visitor as soon as he logs into the frontend.
Allowed