Glad to hear that!
Basically, I didn’t like that the native form tool is so finicky and so directly linked with every column. The form facilitates four different types of requests, with follow-up questions for each (some the same, some different) and because of Workforms’ limited conditional logic, I had to have a separate variant of the questions that are the same for each request type—which resulted in several columns in the table that were all storing the same type of information. I also didn’t like that the only options for item name were ‘let the form submitter name it’ or have it be auto-named ‘incoming form response’; I wanted more useful information in the title (that helps a lot when working out of the My Work page!)
So I created a second board, which is a streamlined version. For example, there is only one “Description” field, and ALL variants of that question map their values into that one column. There’s only one “Add’l Information” column, and several request-type-specific answers go in there. Etc.
I have a bunch of automations on board 1 (12, in fact) that create items in board 2 and connect the items (via a two-way Connect Boards column). When configuring the automations, I can map the values received from the form however I want into the columns of that second board. Then I also have some automations to keep the two separate versions of “Request Status” column in sync (the language used for each status option differs between the internal board and the form-board, but I was able to translate by mirroring board 1’s status column into board 2, then configuring automations in board 2 to translate (e.g. "When [internal] request status changes to ‘In triage’, change [mirrored] request status to ‘Working on it!’)
There are some more nifty nuances involved, but I’m not sure how ‘in the weeds’ it makes sense to get here.
Here are some screenshots in case helpful. If you have specific questions, let me know. 
P.S. I’m self-employed (despite happily revealing some of my solutions here for free 
), and my business specializes in building workflow automations for other orgs. If you’d like to talk more and/or hire me to help with something similar, check out my website. 