Public View of the GoCanvas Roadmap

Comments

6 comments

  • Avatar
    Sara Kaplow, Community Manager

    Hey Dylan, 

    I appreciate this feedback. I'd say it's incredibly unlikely that we'll publish the roadmap publicly, for a couple of reasons. First, public roadmaps are the exception, not the rule. Yes, people do it, but it's not the standard. Second, when folks do release their roadmaps, they tend to be very general (think big themes like "we're going to do something to dispatch" as opposed to "we're going to fix this exact thing") and really conservative on dates. Finally, specifically here at GoCanvas, we know the roadmap is going to change, both the timing of things happening and what we're focused on. What is important for us to build today might change tomorrow because of any number of things (mergers and acquisitions, changes in the marketplace, security and policy changes like GDPR, platform/technology updates like when Apple release the iPhone X with the notch... the list goes on). 

    I know this isn't the answer you want, but I hope it sheds a little light into why we're more protective about our roadmap - we don't want to jerk people around, is really what it comes down to. 

    2
    Comment actions Permalink
  • Avatar
    Dylan Aafedt

    Sara,

    I understand where you are coming from, but the lack of transparency makes it very difficult for us on the customer end, especially for those of us to are the GoCanvas leads in our companies, to give our users answers when they ask about the availability of certain items. I'm not looking for exact dates and I understand that projects change, but it would be nice if quarterly you could tell us the projects you're working on and a quarter or half of the year you plan to release that item. I'm assuming that you aren't dropping half-baked projects completely just because of changes in technology.

    1
    Comment actions Permalink
  • Avatar
    Sara Kaplow, Community Manager

    I've been thinking about this all weekend, so forgive me for the novel :) 

    Philosophically, I completely agree with you and understand why it would be useful and also, in the long run, help us on this end keep folks like you engaged and advocating for the product. And you're right - we're not (usually) just throwing stuff out mid-stream, but we do have the habit/ability of working on things and then getting bottle necked or delayed somewhere else. 

    We generally tell people some of what we're working on (very big picture) at Transform. Last year, we talked about Analytics, which officially launched at this years Transform. This year we talked about multi-photo upload and the new look of the mobile app.

    Multi-photo is the interesting one, and gets into a bit of what I was saying previously. The mobile team had done their piece earlier this year, but it hadn't made it to the other development teams yet. So we were able to show a demo of it working on mobile in September, when our other development teams hadn't even touched it yet (you could add photos on mobile, but those photos didn't go into a Submission, and you couldn't actually create the field in the App Builder).

    Based on that, we could have said in May that it was being worked on, but at that point we didn't even know if it was going to get worked on by the other teams this year (it's being worked on now! but still might not be out until early next year). Hence the hesitation.

    All of that said, I'm going to surface this with the Product Management team again and see if we can find some balance. We spent a lot of this year working on not-at-all-fun, behind-the-scenes stuff, and once we get past that I think we'll be a bit more able to commit to feature-type things. 

    I appreciate the feedback. I'll do my best to get something we can share both regularly and more in advance. Thanks!

     

    1
    Comment actions Permalink
  • Avatar
    Dylan Aafedt

    Thanks Sara - I look forward to hearing where this goes. -Dylan

    1
    Comment actions Permalink
  • Avatar
    Dylan Aafedt

    Sara Kaplow, Community Manager any update on this?

    1
    Comment actions Permalink
  • Avatar
    Sara Kaplow, Community Manager

    Hey Dylan,

    The major movement on this has been in increase in our ability to start marking specific feature requests as "planned." Previously, we were very hesitant to do that, but we're increasingly comfortable with making that info public in advance. Just as an example: https://help.gocanvas.com/hc/en-us/community/posts/360010942973-Number-Field-plus-minus-option. We actually have a handful of new field types coming out shortly. So I'd recommend following feature requests you're specifically interested in for those updates. 

    I still don't have sign-off to share much more than that, but I'm making a push to be able to share the thematic things we're working on (say, hypothetically, an updated interface for the App Builder and additional collaboration-focused functions, some of which address specific feature requests). Now that we're less bogged down by things like migrating to a new billing platform, I think that's an easier sell. 

    1
    Comment actions Permalink

Please sign in to leave a comment.