How We Decide What Goes on the Tidewell Roadmap

We get more feature requests than a small team can build, which is a good problem to have. Now that our customer community lives on this network, we want to be open about how we choose.

Where requests go

Post them in Tidewell Customer Community. One request per thread, please, with a sentence on the problem you're trying to solve, not just the feature you imagine. "Our volunteers can't see who's on shift with them" helps us far more than "add a team view".

What we weigh

• How many venues have the problem. This is where votes and replies help.
• How painful it is for the people who hit it. A few completely stuck customers can matter more than many mildly annoyed ones.
• Whether it keeps the product simple. Many volunteers use Tidewell for ten minutes a week. Every setting we add is one more thing for them to learn.
• What it costs to maintain, not just to build.

What happens next

Each quarter we pick a short list, post it in the group and mark the threads that inspired it as planned. Requests we've decided against get a reply explaining why. We'd rather give you an honest no than leave a thread hanging for two years.

Votes aren't the only thing we look at, but they help. If a thread describes your situation, add a reply with your own example. Those details are what our designers read first.