We use Spigit in multiple instances or communities. Our biggest community spans engineering, product management/marketing, research, and parts of manufacturing for our consumer electronics division, all working on new product features and ideas for our headphones, music speakers, home theater systems, etc. Our most active community at the moment is the one for our retail salespeople, which is focused on operational improvements -- what selling techniques work best, what merchandising has been successful, and so on. We've also had temporary communities for cross-functional teams of a few dozen people working on special projects.

Idea Submission: This is the bread and butter, and it's fairly easy to customize a template for idea input to make it work for your organization.

Idea Progression: There is a lot of criteria on which you can trigger the progress for an idea, and it's very easy to configure.

User Reputations: Weighting the value of each user's input based on the past perceived value of his/her input works well and is pretty useful, both in the core functionality (submitting and evaluating ideas) but also in helping us identify power users.

Responsiveness to Customer Needs: We've definitely seen features added that we specifically requested. They use their own tool within their user community to help them identify and prioritize product improvements.

Events and Conventions: The Spigit user events (the Ignite summit in particular) have always been high quality and a great help to energize and inspire their community managers and customers.

Detailed Idea Evaluation: It's difficult to do things like expert reviews or specific topical reviews, or to rate ideas by multiple criteria. The built-in visualizations for comparing ideas against each other don't make use of the granularity available in the data, and are mostly useless.

Custom Reports: In six years, they're now on their third platform for custom reports. This is important, because their built-in reporting and leaderboards don't track the kind of metrics we want to track. The first reporting system was a complex scripting language that was powerful, but still limited in some respects, and required paid custom work by Spigit employees if you needed high-powered reports that required extensive knowledge of their internal database schema! And still, it had limitations. The second reporting system was a sort of cross-tab dashboard tool that never worked the way I thought it would, and couldn't show the things I wanted anyway. The new tool seems to be a much-improved dashboard-style tool, but it has a bit of a learning curve that we haven't taken the time to climb yet.

Site Design and Customization: If you don't pay them for custom work, and you don't like the default pages, you're in for a lot of frustration and helplessness, as their widget system features hundreds of obscurely-named widgets with unhelpful documentation pages.

Page-Level Analytics: We have a private site for confidentiality reasons, and we have no idea about how our customers use the site to be able to improve their experience or identify what's working. The platform has no built-in page analytics tools like Omniture, Google Analytics, etc. And we can't use them on a private site because there's no way to get past password protection.

If you have a community with more than 100 active users, and you're looking for ideas around operational improvements that can be acted on in a 6-12 month window, Spigit will work great, and it's one of the best options out there. If you're trying to customize the platform much, you should plan on paying Spigit's service group to do that for you, because it's not easy to do yourself. If you're looking for ideas that will take more than about a year to implement, Spigit is as good as anyone else because that's a really tough thing to do in an innovation community!

I have hands on experience experience deploying, launching, and operating Spigit software. This experience includes four deployments in organizations from ~1,000 users up to 165,000 users. I also have experience with the operation for two other companies. Across those deployments, it has been used both enterprise wide and with various departments whose leaders are looking for employee engagement in innovation activities.

I have used the solution to access very large crowds, especially for filtering and selection. Their Pairwise (A-B voting on ideas) generated ~100,000 votes in less than 1 week for one specific event.

I have used the solution to engage crowds over ~100K users and less than 10. In each case, the user experience can be tailored to meet specific objectives for the sponsor or it can be deployed in the exact same way repeatedly.

There are many ways to configure the solution. Some features make more sense to use at times and should be hidden from users at other times. It would be nice if Spigit had pre-defined configuration templates that reflect the experience and knowledge of their current customer's experience using the software and not just a 1 size fits all base configuration. The good news is with a little experience, these configurations can be created as saved templates.

Spigit is great for working with HUGE crowds and people who can't get together in person. It's also possible, with the right planning and experience, to "blend" digital and analog experiences to create a more robust user experience. There are times when meeting and collaborating without a crowd-sourcing technology in place is the right way to drive innovation. It's important to recognize those situations and not force the use of the technology.

In my company, Spigit is used across the whole organization, with sponsorship and support from HR/Leadership & Development. It is used as a collaborative improvement tool to engage everybody in the company to take part in challenges of disruptive innovation, continuous improvement and operational (micro) improvement. In our company it plays firstly an educational role (to collaboration) and then an operational role. It may be considered in its experimental phase.

As I said, Spigit is a great trigger to share a change of culture when it comes to take part in the improvement and innovation of a company. It may be less appropriate to implement a structured innovation process, from idea to actual project. It is of course more appropriate in a digital ready company, otherwise your "experts" and "key figures" are not as easy to engage.

Spigit is being used across the organization. We are using it as an idea collection platform trying to generate innovation within our culture. Our culture is not accustomed to this as they are very comfortable in silos. We are using this platform to change the way we think. We want our people to understand that not every idea ever thought of is a winner. Good ideas start somewhere and with collaboration they can evolve to a great idea that can affect more than just a few. We generate challenges and reward frequent users and ideators whose ideas are implemented.

On-site training: Spigit provided hands on training very well. I left my level 1 training feeling equipped to make changes and use my instance.

Kick off - spigit creates a great team that allows a company to initiate the use of their system. They assigned staff to our organization making it easy to communicate with the same person and create that trust needed to share the internal desires of the use of the system.

Follow up - main sales contact follows up with us yearly if not more often to make sure all is still going well. We can address areas of concern with them and they direct us to the appropriate person to handle that concern.

The platform - it is not intuitive. Would like to see it more user-friendly. i.e. creating the store and adjusting the points was very difficult. Platform terminology created a break in ability to delegate implementation. manipulating the look of the challenge should be made easier. Right now we are limited to the options, unless the user is very good with computer terminology.

Help desk questions - response to tickets takes too long. Generally when a question is posted the user is looking for an immediate response.

Kick off team - it would have been very useful to have a team that was familiar with our industry. There were differences in terminology that created a break in communication at times.

Mentors - I would have liked to have been linked up with an organization similar to mine who has been using the system. I tried creating this link at the 2015 conference, but the user did not respond. If this was preset by spigit, it might make this step easier for the newbie.

Spigit is being used throughout Ingeus UK operations and is across multiple contracts. The platform is used to generate ideas from staff members to support the business to improve in a numbers of ways such as: ways of working, technologies, and customer service. Ingeus has roughly 100 offices, and so the platform also provides staff from across the company to network and engage with each other; this can be a productive way to share best practise.

Spigit has also been used as a way for management to communicate with staff and involve them in business decisions (through using challenges). Challenges have also been used to gather staff opinion and ideas - for example on new contracts.

Idea Implementation - Once an idea has been accepted on the system, I believe more could be done to support users to manage the implementation process and also to ensure staff are kept up-to-date with progress.

Site Editor/ Widgets - The widgets area could be made easier to use and edit and also to navigate. it is quite a dated aspect of the Administration Settings!

Spigit is used across the whole organization. We've identified several open topics that will have an "Always-on" type of challenges to capture the normal ideas that people might have related to these general topics. Also, we've identified closed challenges that are sponsored by senior management and these are closed and time bound for people to compete in. It normally addresses problems related to energy saving, cost optimization and process enhancements as well as innovation.

We use Spigit in various departments but for a limited amount of users (200 registered users). These are individuals throughout various functional areas that act as spokespeople for their respective areas on new product concepts. Our main goal with the Spigit software is to generate new product concept ideas that we can bring into our New Product Innovation (NPI) process. We are using it as an idea generator, idea storage and prioritization tool.

Spigit is very good at walking you through the initial process, giving you their professional advice as the expert in this field while still letting the tool work the way you want - what's best for your organization's individual needs.

Spigit provides a lot of flexibility around how to use the tool, whether you're launching to every person in your company or whether you're focusing the tool in one particular area, such as new product ideas, process improvement ideas, etc.

The guided launch process is very structured and we had some intnerla issues preventing us from following it exactly. There was some trouble getting this worked out, however, in the end, the Spigit team helped brainstorm ways to accomplish both our goals and conserve their team's time and resources.

I think Spigit is geared towards opening up the site to your entire organization and have open collaboration. Our goals were slightly different and we wanted to start by only allowing 200 users in the company to view and contribute to the site. Because our goals were different than their standard client, there was some struggle around aligning the way they normally do things with our goals, however, they were able to adapt and still make a successful innovation site that worked for us.

We use it across the whole organization and it's difficult motivate employees to participate. We designed beautiful material to engage all people and configured a special store but no one participated until today. A majority of people were on vacations and returned this week. I hope that next week we have some participation. Whatever, I have to review what happened with my challenge next week, maybe the challenge it not clear to people.

Internally, Spigit is used across the whole organization. We've created challenges for the entire company and some challenges by department. Most of the time, we've helped to deploy Spigit in other companies, in those companies Spigit has allowed them to save money and increase productivity with new ideas. The innovation process is completed using Spigit because the tool helps them make a decision.

Spigit is well suited when the organization has a innovation model defined or if the organization already has worked in innovation process. If an innovation model does not exist then maybe Spigit will not be used completely.

Spigit is being used across our whole organization, this includes those on the ground floor of our plants and operations. We have used Spigit to address a wide array of business problems from training, to new ideas to foster innovation, collaboration, and ways to better engage our external and internal customers.

I'm only a short time user but from our first challenge; Spigit was easy to use and the overall experience for the user community was outstanding. The results from the challenge were better than expected and larger to do with the ease-of-use. For companies that are geared toward empowering their employees to think outside the box and are allowed to express themselves freely; this is the way to do it. Make something fun for people to share knowledge, ideas and gain recognition.

We use Spigit enterprise-wide to engage the workforce in solving challenging business problems. We have used the platform to address issues ranging from customer satisfaction to talent retention to specification development. Users included sales, marketing, customer service, operations, human resources, engineering, product development, and finance. We incentivized participation and rewarded those with the top ideas.

Spigit does a great job engaging users and providing a platform that looks and feels like social media. Navigation is intuitive and administrative functions are easy to understand. While reporting was cumbersome at first, we were able to create custom reports that worked very well for our business and provided sponsors with data needed to drive decisions.

We are using the Spigit platform across the company. We are using it to find innovative solutions to broad client-driven problems. We are trying to address the problems of silos and grassroots idea flow across the company.

Acknowledges and supports the culture around the problem and market it is trying to serve. Just using the platform won't solve our problem, we need a cultural shift and Spigit has helped support that process.

Customer service - just overall amazing service. Responses are very quickly turned around, they've gone the extra mile many, many times. They are also very open to platform improvements and take feedback very seriously.

As the system administrator, I feel their platform incorporates a great balance of templates, out-of-the-box formatting, etc., and customizable content. In a nutshell, we are able to do what we want but we don't have to spend forever to do it. We can use what they have or we can add in our own design.

There are some aspects of setting up a new challenge that are cumbersome and/or difficult to locate. For example, the menu to modify one option is hidden in a separate area of the platform.

The platform does take some getting used to. I think it takes people a few days to figure out how to successfully navigate. This was more of an issue at first but they have been steadily making improvements.

It is open to being used across the whole organization, though select groups have used it thus far. It has done well to surface ideas for incremental improvement initiatives as well as enhance employee engagement. Each of the challenges we have run has led to actionable ideas and has seen very strong participation rates.

So far it has been very strong for running time-bound challenges. It would not be appropriate for teams not looking to support the program with dedicated resources (at least part of their full time role). There is a desire to use it in other settings in the future; can report back then on whether it is well-suited or not.

Spigit is currently being used by one department for two purposes: the generation of ideas, and the management of ideas. We have launched two challenges to develop new product concepts, and we have also built out a separate component of Spigit to serve as a repository of ideas that are being considered for commercialization.

Spigit is an extremely valuable crowd sourcing tool. The interactive nature of the tool provides a very good platform for engaging users and encouraging dialogue among the user community. This leads to the development of a cohesive, well considered concept.

Spigit was used in one organization, it focused around allowing different groups to collaborate on a specific problem. Most people used it as a way to gather different ideas for a problem their own group had. We also used it as follow up for conferences.

Well suited to an engaged community with a focused challenge to be addressed and where there are good downstream processes to evaluate and progress ideas.Works less well where just looking for general improvement.

Planview Spigit Scorecard Summary

About Planview Spigit

Spigit is a software for crowdsourced innovation, and is used by companies in systems integration, financial services, insurance, pharmaceutical, healthcare, technology, and more. Spigit’s customers include IBM, Capgemini, Citibank, and Pfizer. The vendor says 4.5M users from 150+ countries have generated over $1B in increased revenue from their enterprise innovation programs. The vendor says Spigit was founded to help companies unleash the power of their employees, partners, and customers to drive innovation.

Spigit is headquartered in San Francisco with offices throughout the U.S., U.K., France, Germany, and Australia.

Planview Spigit Screenshots

Planview Spigit Integrations

Spigit has REST API and a semantic API that works hand-in-hand with existing enterprises. We support our customers to broker connections between Spigit and their business processes. Also supports social integration such as Yammer

Planview Spigit Competitors

Pricing

Does not have featureFree Trial Available?No

Does not have featureFree or Freemium Version Available?No

Has featurePremium Consulting/Integration Services Available?Yes

Entry-level set up fee?No

Our pricing is unique, and designed to fit your specific needs. For pricing inquiries, please contact us at: https://www.spigit.com/contact-us/
Spigit is here for our customers’ success. Our standard offering includes site configuration and implementation support, free of additional charge. We also offer a full senior strategy advisor team.