Google Forms vs. Lightning Tools Lightning Forms

Appropriate Scenarios

• Data collection
• Formative assessment
• Survey/questionnaire
• File uploads (Can be limited to particular sizes or file types).

Inappropriate Scenarios

• Lessons where you need instant feedback to answers rather than waiting for the whole form to be completed.
• File Uploads where not all of the users have Google accounts.

Incentivized

We've used lightning forms on literally dozens of our SharePoint sites now and it's just excellent, especially because it doesn't interfere with our ability to governance and administer the sites

• Capture of information from clients and/or consultants for real-time analysis.
• Knowledge evaluation for our work team, the predefined templates allow the creation of tests and knowledge tests that are very didactic and easy to grade.
• The acquired data is cleanly integrated with google spreadsheets allowing for fast and accurate analysis.
• The form completion notifications are customizable and do their job well.

Incentivized

• Simple user interface - users of the forms intuitively aware of how/where to input information. This is in part due to being able to show or hide different questions or areas of the form, and making them required or not, based on previous answers.
• Low/simple code - building complex forms with automation and multiple dependencies or lookups is relatively easy once you get started. You have the power of JavaScript to use and do some quite clever things if you can get to grips with it - a lot of solutions are only a Google away.
• As it is based on SharePoint, it integrates perfectly with the rest of the M365 suite. Things like PowerAutomate enhance its functionality even further.

• Edit view limits the questions as seen by viewers. The view function is nice to toggle between to see what the question will look like, but the edit view of some questions (like checkboxes) is confusing for the editor.
• It would be wonderful to be able to assign responses to go to specific users. The user needs to go into the responses section and select the option to receive notifications, versus the owner of the form being able to do that.
• Having a dependency feature for questions (in addition to sections) would be very helpful, so that if a question is answered a certain way, another question appears.

Incentivized

• The styling of the form can sometimes be slightly awkward to use depending on what you're looking to do. For instance, if I was looking to highlight fields that users have missed (left empty), I would need to set up a validation for that question and then set a style for that particular field for when it is invalid. When you have a large and complex form with lots of dependencies, this is awkward.
• Support for complex and niche issues is slightly lacking in my experience. I submitted a helpdesk ticket for help with a strange issue I couldn't figure out, which took several weeks to get a response to. Because it is niche, it's more difficult to find an answer by searching the internet. Luckily, knowing there is likely to always be a fix if you find the right place/use the right formula, I manage to resolve the issue with some trial and error.
• It is disappointing that Lightning Forms does not integrate with the MS Lists app. Having the ability to access the form through the list app would add in a lot of useful functionality, including a better experience for users when taking photos to add as attachments.

I will definitely renew my use of Google Forms because I really like the ease of use and the number of tools that Google forms provide. I also love that I can administer a test in real-time and get results in a timely manner

Incentivized

The interface is simple and intuitive. The first time you use Google Forms, it has a built in tutorial that goes through all the basics. Most people can pick up how to use it with minimal support. There are some advanced features that require a bit more work but there are plenty of videos and directions online. Google has a great support section that is easy to follow

Incentivized

It is very user friendly both to me who is building the content (with little background knowledge of coding etc., other than what I have picked up from using products like PowerAutomate, PowerBI, a bit of html etc.) and to end users of varying levels of IT proficiency. This has been extremely important as we have used the forms to make relatively large process changes, and need to have our users on board and seeing that it is actually easier than it was before.

In the years I've used GoogleForms I've never ran into any issues with the reliability or availability. Google is a gigantic company with essentially limitless resources which makes it very easy to trust that I will continue to be able to enjoy the same reliability I've come to know and expect from GoogleForms

Incentivized

One of the things that comes as a benefit of the lack to create complex logic branching and truly custom design is that there isn't lot of room to bog down the software. GoogleForms has always loaded just as fast as my internet service and device would allow it. I'm not sure about front end integrations or integrations into the form itself, as I've never explored it, but on the backend, I've never had any issues with integrations channeling from GoogleForms from the GoogleForms's end of things.

Incentivized

I have not had to use Google Forms support - it's always worked as expected. However, with other Google products, I've always been able to find a plethora of resources for answering questions or dealing with issues. The benefit of Google is how widely adopted its products are and how robust its support is.

Incentivized

Some support has been okay, but in one instance of a fairly complex problem, the support team were not able to provide me with a fix within a few weeks, before I was able to find a workaround myself.

Google Forms is easy to use and affordable. The biggest benefit, however, is that our organization already uses other Google products heavily. Because of this Google Forms was our top choice. Some smaller departments in our organization still use other solutions, such as SurveyMonkey, but as a whole it has been helpful to standardize on a single product.

Incentivized

We were using Microsoft Forms, SharePoint Lists and PowerAutomate to attempt to do much of what we are currently doing. Functionality is very limited in comparison. The ability to make questions required based on previous answers was a massive improvement from normal SharePoint List forms and has greatly improved the quality of data. Also just the very visual display and customisation is much better.

GoogleForms lacks the ability for complex logic branching and the ability to truly design it in a custom manner. It's pretty obvious when you land on a GoogleForm that it is in fact a GoogleForm. This rating solely reflects the lack of flexibility which in turn makes it something that wouldn't usually be scaled. That being said, if needing to scale a simple solution, GoogleForms would be up for the job.

Incentivized

• Google Forms provides us a vehicle to gauge faculty and student response to our online courses and their features in real time so that we can keep our courses updated for students and faculty who facilitate them.
• Since Google is free, provides storage space, and provides Shared Drives (at least in our institutional account), using Google Forms helps us manage our data. We support over 400 courses with thousands of sections so Google Forms helps us manage the data coming out of these courses, mostly student and faculty feedback about what is working and what is not.
• We encourage our faculty to use Google Forms to survey their students for prior knowledge, for interest inventories, and the like. It's incredibly nimble and useful for collecting data quickly and presenting results in easy-to-understand charts and graphs.

Incentivized

• We changed the process by which site colleagues report repairs on behalf of customers. Instead of emailing them into a shared inbox, they now report them using a lightning form. We have seen a great improvement in the time taken for our team to log the repair issue from the time is arrives with them.
• We anticipate that streamlining our void property reletting process by using a SharePoint kanban board view with lightning forms (providing a single platform for all things void) will reduce avoidable days vacant and therefore reduce our void loss.