Submitting Ideas

Document created by Ike Bennion Administrator on Feb 2, 2017Last modified by Ike Bennion Administrator on Feb 22, 2017
Version 6Show Document
  • View in full screen mode


Our old way of collecting ideas took feedback from clients and put them into a sheet that we reviewed on a regular basis. But we missed out on a lot of key data points, like: Who else is interested in this? What is the exact problems or use cases involved? How many other people haven't asked the question but have the same problem? Providing immediate and additional transparency to other admins as well as to our product team allows us to get more detail and do better discovery on user problems.


Why can't I just use my CSM/Support to submit these? Because the key to us understanding more about your idea and eventually fixing it is being able to connect with you. The Bridge Community automatically updates our team as well as you when comments are made to your submissions. We can give all the right people visibility to your idea in a scalable way. Plus, we want to give you credit when we build something that you suggest.


How to Submit

  1. Navigate to Submit and Explore
    • You can get here by clicking into the Customer Lounge then click Submit and Explore. Or, just bookmark the page above!
  2. Click on Submit an Idea
    • On the bottom right there is a button that says "Submit an Idea".Screen Shot 2017-02-22 at 10.32.56 AM.png
  3. Provide a Title (or Select a Similar Idea)
    • Start typing your idea title. The community will automatically start searching ideas. If you find one that's similar, click it and upvote and comment on any specific nuances to your use case or problem.Screen Shot 2017-02-22 at 12.01.24 PM.png
  4. Provide a Description
    • Once you've titled your idea, provide a description of the problem or idea that you're experiencing. Note that this is required to submit the idea.
  5. Click Submit


Tips for Great Ideas

  • Have one idea per submission
    • "I really need tags in programs and the ability to delete them quickly and the ability to see how many courses have been tagged with one tag." This is really three ideas, it's hard to maintain directed collaboration and understand which ideas are most important to a broad base of clients.
  • Clearly describe the need or current deficiency
    • Oftentimes people have the best ideas for improvement when they are the most frustrated.  Try to state your idea clearly and concisely and avoid ranting or unnecessary information.  Remember that you are in a sense asking many community volunteers to read and consider what you write
  • Do not be overly prescriptive
    • State the desired outcome or goal and then let the product managers and engineers think about how they can best add a given functionality to the product. Sometimes too much time spent on an idea clouds the core problem.
  • Give use cases and scenarios
    • Make sure other readers can understand why you want the option to do something in Bridge.  Paint the picture of where you want to go or what you're currently facing. Why is the new world with your idea valuable? Sometimes the value that is clear to you needs a little more detail to be understood by others.
  • Give it time
    • Bridge is developed using agile methods that allow our team to update our code every week.  Community input is very important to that process.  But while it is true that the product changes frequently, many of these improvements take months and and thousands of hours of work to develop. This means that even if everyone agrees that developing a given feature would be a good use of finite development resources it may be a long time before the feature can be developed and it may have to wait in line as part of a larger development schedule.


To recap:

  • One idea per submission
  • Be clear and concentrate on your problem
  • Give a scenario
  • Be patient