Summary
There are—and always will be—hundreds of features that we could build but haven't. If you’ve ever wondered about how we prioritize what to build, here’s how we decide.
Pathwright has many features already, and we launch new features or enhancements every 6 weeks. Even so, there are—and always will be—hundreds more features that we could build but haven't yet.
If you’ve ever wondered about how we prioritize what to build, read on:
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 work in 6-week cycles to complete 1-2 big features and a batch of smaller enhancements that are completable within 6 weeks.
We plan what to build next in between cycles. After each cycle, we have 2 planning weeks where we decide what roadmap features we’ll commit to for the next 6 weeks.
How we prioritize features to work on
We pick which of the hundreds of features we could or should do at some point by . . .
Selecting the highest impact features for all our educators that fit within our strategy and are within reach of our design and development resources during the next 6 weeks.
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.
This article is part of our series Proudly Indie
