All Collections
About Pathwright
🗺 What's on the roadmap?
🗺 What's on the roadmap?

Learn how we decide what features to build and suggestions to implement next.

Paul Johnson avatar
Written by Paul Johnson
Updated over a week ago

Pathwright has many features already and we launch new features frequently and smaller enhancements every week. Even so, there are – and always will be – hundreds more features that we could build but haven't yet. If you're wondering about one of those, then this article will give you some helpful insight on how we decide what to build and when.

How we handle feature requests

We love to hear suggestions for new features, so if you have one, please let us know. And just so you know what to expect, we'll respond in 1 of 3 ways:

  1. That's on the roadmap. If your feature request is already on our roadmap, we'll confirm with two important qualifications:
    - We usually can't confirm when a feature will be available (see "how we work")
    - Our roadmap is always subject to change (see "how we prioritize")

  2. That's not on the roadmap. If we don't have plans to build it, we'll be up front about that.

  3. That's an interesting suggestion! If we're not sure about it, we'll likely ask a few more questions and catalog the feature requests to consider later.

How we work on new features

  • We release smaller batches of updates every week. Towards the beginning of each week, we release smaller bug fixes, necessary platform maintenance, enhancements to existing features, and occasionally some entirely new features.

  • We work in seasonal cycles called Seasons to launch larger features. Most of these features arrive as Drops over the course of the Season.

  • We plan what to build next in between cycles. In between the larger Seasons, we work on smaller projects and decide what roadmap features we’ll commit to for the next Season.

How we prioritize features to work on

We pick which of the hundreds of features we could/should do at some point by…

  1. Selecting the highest impact features for all our educators that fit within our strategy and are within reach of our design/development resources during the time we have available.

  2. Prioritizing features that a partner funds and provides feedback and testing on when we can do so without impacting #1 significantly.

Have a feature suggestion?

Let us know! We'd love to hear from you.

Did this answer your question?