We launch new features every few months alongside small enhancements and fixes every week. To see the latest feature updates, click on the Changelog in the top right of your account (look for the "β‘οΈ" icon).
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, this article will give you some helpful insight into how we decide what to build and when.
We don't have a public Roadmap, but we are constantly experimenting and building what's coming next in our Pathwright "Labs" (here's a little more about our Labs if you're curious).
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:
That's in the Labs. If your feature request is already something we're researching or considering, we'll confirm that 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")That's not something we plan to build. If we don't have plans to build it, we'll be upfront about that and suggest an alternative whenever possible.
That's an interesting suggestion! If unsure, 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 that typically span 3 or more months of the year (for example, we often have a spring and fall season). Each seasonal cycle includes more significant features focused on a similar theme (for example, here's what we launched in a Mentor-focused season and a Cohort-focused season). These features are announced in the Changelog when they launch and by email or even a live preview event when they're significant.
We plan what to build next in between seasons. In between seasons, we work on smaller projects and decide what features we'll pull out of the Lab and build for the next Season.
What is Pathwright currently focused on?
In our current season, we're focused on two things: 1) making Pathwright better for what it's best at β simplifying, modernizing, and completing each core feature β and 2) building new teaching and learning tools for the next version of the Internet (we'll share more about this when it's ready).
How we prioritize features to work on
We pick which of the hundreds of features we could/should do at some point byβ¦
Selecting the highest impact features for all our educators that fit our strategy and are within reach of our design/development resources during the time we have available.
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.