Table of Contents
Overview
Submitting an Idea
Example Product Idea
What Happens Next
Functional Blockers
Related Articles
Overview
If you discover something about one of our products that you think would make it better – something you think other members of our community would also find to be useful – we want to hear about it! You can share this with us by submitting a Feature Request or “idea”.
Submitting an Idea
Ideas are submitted via the same steps as support tickets.
Step 1: Click the "Submit a Ticket" option at the top of our Help Center.
Step 2: Fill out all of the requested information in the ticket.
Product
Select the product this idea applies to.
Tell us why you’re contacting us today
Select “Idea” from this drop down menu.
How is this impacting your business processes?
Help us understand how critical this request is for core business processes.
Options include:
Low impact to business process
Some impact to business process
High impact to business process
Business process halted
Subject
Summarize the idea in a way that briefly captures the need.
A good example might be, “Show changes between current and proposed requirements in proposal view”.
Description
This is where you make the case for your product idea on a high-level.
What problem is this idea trying to solve and why is it a problem?
Summarize the problem for us; tell us why/how it is an issue and outline the proposed solution. How does this solve the problem?
A good example might be, “Currently in order to know which courses were added or removed from a program – or which requirements were changed – an approver needs to open the requirements in the "Changes" tab of the approval screen and compare all text, requirement credits, and courses one at a time to determine if a course number, text, or requirement credit values have changed. This adds a lot of time to reviewing each proposal.”
Provide more context on the business impact.
Tell us what led you to select the option you chose from the “How is this impacting your business processes?” – and the impact your solution would have.
Describe any workarounds. How are they or aren't they sufficient?
Tell us how else the same objective could be accomplished and why your idea outshines the workaround.
A good example might be, “The workaround would be to carefully compare the before and after one line at a time to find out what has changed, but this is time-intensive and inefficient.”
How exactly would your proposed solution be used?
Tell us who would be using this functionality, how they’d use it, and what the experience will look like for them.
A good example might be, “This would be used by approvers when viewing proposals and would help them more quickly see if the proposal includes any changes to requirements (and what those changes are, if so).”
Will this idea require a change to our integration?
In other words, will we need to pull in additional data to ensure the enhancement works?
Attach File
If you have a screenshot that captures the need or have mocked up a visual of what you’re proposing, please attach those to your idea.
Add an explanation of what those file(s) show somewhere in the description.
Step 3: Click “Submit”.
Example Product Idea
The below product idea includes all of the best practices outlined above.
What Happens Next
Product Ideas submitted via the Help Center are regularly reviewed by our Product team, but they are typically prioritized and fully investigated during our quarterly roadmap planning sessions.
We only provide updates on product ideas if they are added to the roadmap.
Functional Blockers
If your product idea is more urgent or is an issue that is blocking your institution from product use or adoption, please contact your Coursedog representative directly so they can flag it internally.