This is really a bad name for what this forum section is about.
Roadmap implies that Wyze will be implementing it at some point. Look at all the tech companies posting roadmaps, and you would see that every one of them shows what the company will be doing in X amount of time. That isn’t to say roadmaps don’t change, they do.
Here, we got everyone posting feature requests or ideas that may or may not be implemented.
So, this is really confusing to people that don’t understand that “Roadmap” in this context means it is a feature request.
Would be nice if we see an actual Roadmap section for what Wyze is working on now, (a product or feature that Wyze has solid plans for).
Thanks for your feedback! The reason this is being called a roadmap is because you can filter based on tags and actually see where we’re at on everything. We’re looking into ways to adjust grouping so it’s more obvious. We’re hesitant to give firm deadlines until we’re a good chunk of the way through the development process with features but we want to be transparent about where everyone’s feature requests are on the list. We also use this to help guide where we should allocate our dev resources.
My nerdy heart is leaping at the idea of Wyze-Trek. Big fan!
Do you two feel okay with the idea of waiting until we do a restructuring that we’re looking into and seeing if that helps with this issue? I’m totally up for revisiting this.
The terminology is just wrong, you are not supposed to be able to filter anything on a roadmap, a roadmap is supposed to be a clear presentation, something that people / investors and so on can look at, and see where the company is heading, and what is coming up. It doesn’t have to be specific either, just “New product coming in Q3 2019” or whatever. Things that will never be done shouldn’t even be in the roadmap at all.
Don’t think groupings would help, since, again, things that can’t be implemented shouldn’t be listed.
Feature requests on the other hand, can and are filtered to see what is feasible, those that are, and there is enough interest in them get moved to the roadmap, showing that, yes, they WILL be implemented. Those feature requests that are not feasible would NEVER be on the roadmap, so, why change the terminology here?
We had a specific plan to have a separate roadmap that was more like you were describing but there were concerns about adding too many steps and locations for community members so they were combined. If the groups were panels with main headings like “In Process” and “Researching” so that the other stuff wasn’t visible unless you went to the bigger area, would that help?
@BigBurly13, you’re welcome! I’m still up for revisiting this later, though.
Wyze Team could use tags to actually mark in which version each feature was/is-going to be included.
Tagging more than 1 year in future shouldn’t be allowed, as this kind of periods aren’t always honored.
I agree, it is a “wishlist”.
When some poster thinks of something they need done we are referred to a similar topic in #roadmap to vote for it.
I have not found anywhere that tells how a “vote” is valued or what it really affects. I’ve voted for some things that I thought “yes, that would be nice” and other things “YES! YES! YES! I need that”
“A technology roadmap is a flexible planning technique to support strategic and long-range planning, by matching short-term and long-term goals with specific technology solutions” from the wicki
With the ability of anyone to vote for anything and vote for as many things as they can it dilutes the value of a “vote”.
Perhaps at least limit our voting to 5 or 10 items and that would show what we really want.
We are in the process of splitting #roadmap into Roadmap and Wishlist, the former being features in development and the latter everything else. Please stand by.
UPDATE: As of today, #roadmap has been split into #roadmap and #wishlist. The former is now just for features that are in development, testing or launched. The #wishlist category is for user submission of future feature ideas.
