I’m Pepeluche Diazgarcia, Senior Automation Anywhere Developer at Northwest Mineral Processing Inc. We’re a mining and metals operation with 201–500 staff, and most of my day is building RPA bots for production logs, inventory tracking, approval workflows and operational reporting. A big part of my job is gathering feedback from plant operators, maintenance crews and supervisors to figure out which manual processes are still causing bottlenecks, so I know what to automate next. Before SurveyLegend, I was using plain basic forms, and they didn’t work well out on the mine floor. Our field staff fill these out on rugged phones between shifts, and the old forms looked messy on mobile, so completion rates were terrible. I’d end up with barely enough responses to tell if a bot design was actually going to help the teams on site.
What I love most about SurveyLegend is how clean and mobile-native every survey looks right out the gate. Our crew doesn’t sit at desks all day. They pull up these forms on cracked work phones, sometimes out in the processing plant where connectivity is spotty. SurveyLegend renders smoothly, the buttons are sized big enough for gloved hands, and I can drop photos of control panels, inventory stations or paper log sheets directly into questions. That’s a game-changer. Instead of asking vague questions like “Is this data entry step slow?”, I can show them a picture of the exact form they use and ask for their input. People understand the question instantly, and I get way more useful, specific feedback.
I also really appreciate how straightforward the branching logic is. I build separate paths for production operators, warehouse inventory staff and admin approvers. If someone marks they work in crushing operations, it skips the questions about loading dock inventory checks and jumps straight to their workflow pain points. It keeps each survey short, and people are far less likely to abandon it halfway through. I don’t have time to fuss with a complicated survey editor between bot builds, and the drag-and-drop setup lets me spin up a new feedback form in 15 minutes when I’m kicking off a new automation project.
Another thing that fits our workflow perfectly is the real-time dashboard. I don’t need to wait until the end of the survey window to see the responses rolling in. If I start getting consistent comments about a specific bottleneck in the shift reporting process, I can adjust my Automation Anywhere design priorities right away, instead of waiting weeks to collect all feedback. When I export the results, I feed those insights into my process documentation and design notes for the RPA bots.
For our kind of heavy industry environment, it hits the sweet spot. It’s not overloaded with fancy marketing fluff, but it’s built so people on the ground can actually fill it out easily. The better feedback I collect from the plant teams, the smarter my automations end up being. Instead of guessing which manual tasks are wasting the most time, I can build bots that directly solve the pain points our operators are actually dealing with every single day. Review collected by and hosted on G2.com.
While SurveyLegend works fine for grabbing feedback from our plant crews, it has a few consistent issues that slow me down when I’m planning out new RPA workflows. I ran into a really annoying issue a couple weeks ago when I put together a survey for our maintenance team about manual log entry tasks. I added multiple image reference questions showing our paper shift sheets, set up all my branching rules carefully, and shared the link out to the crew across different processing zones. A few operators messaged me right away saying the embedded images wouldn’t load for them out in the processing yard where internet service is spotty and bandwidth is limited. The platform doesn’t support offline saving at all. If connectivity cuts out mid-response, all their progress vanishes instantly, with no way to pick back up later. We lost a handful of valuable feedback entries that day, some from senior maintenance techs who took the time to type out detailed workflow pain points. I had to resend the survey, follow up with supervisors to remind everyone, and push back my timeline for designing that new Automation Anywhere bot. It threw off my whole development schedule for that log-entry automation.
One of my bigger frustrations is the CSV export limitations. A lot of my surveys include image selection questions where team members pick which workflow screenshot or paper form layout matches their daily task. When I export the raw data, those responses only come through as long, messy image file URLs, not simple descriptive labels I can read at a glance. I end up having to manually map each URL back to what the picture shows, cross-referencing against my original survey assets. For a survey with 40 or 50 responses, that manual matching takes up a solid chunk of my afternoon, time I could spend drafting bot logic or testing process steps. I need this clean, readable data to document bottlenecks, validate pain points, and build reliable automations in Automation Anywhere, and this extra manual step adds unnecessary overhead every single time I run a feedback round. It’s not a showstopper, but it adds up fast when I’m running multiple surveys across production, inventory and maintenance teams each month. Review collected by and hosted on G2.com.
