Building a community-powered product roadmap

With the new Webflow Wishlist, you can request and vote on new features, and get a better sense of what we’ll build next.

Building a community-powered product roadmap

Jason Zucchetto
View author profile
Jason Zucchetto
View author profile
Table of contents

Introducing the Webflow Wishlist, where you can easily request new features, vote on others’ ideas, and both influence and get a better sense of what we’ll build next.

Managing feedback from 500,000+ Webflow users

Building a product roadmap that’s driven by the community and aligned with Webflow’s internal goals isn’t easy. Our community has grown tremendously over the past few years (now over 500,000 Webflow users!), and with that growth comes an increasing number of uses for Webflow: building full production sites, prototyping sites, various CMS use cases, building animations and interactions, and various use cases for creating forms, to name just a few.

The first step in building a community-powered product roadmap required organizing all of our community’s input. Community input includes a wide range of communication channels, such as forums, support tickets, social media, and emails.  

Sources of feedback for product direction.
All of the inputs!

Tracking requests internally

With open source software, this problem becomes a little easier: “Here’s the Github/Jira/etc. issue, please vote for it.” But without a public issue-tracking system like this, every employee must remember to duplicate customer issues as internal tracking issues, which quickly falls apart as both the number of employees grows and the number of customers increases.

Internally, this has created a huge backlog of Github issues, Helpscout tickets, Asana tasks, etc., that have been increasingly hard to keep track of.

Monitoring the forum

At the same time, the Wish List category on our forum has grown dramatically in the past few years, to the point that we’ve decided we need a better, more centralized, and more organized system to track and collect feature requests, find and merge duplicates, and provide timely feedback.

To put this problem in more perspective, let’s look at the Webflow Wish List forums, our primary mechanism for receiving Webflow feature requests:

Forum "Wish List" posts are growing beyond a manageable scale.
‍Forum "Wish List" posts are growing beyond a manageable scale.

With the growth in forums posts for Webflow feature requests, it has become increasingly difficult to provide timely responses, find and merge duplicates, and generally keep up with the volume of messages.

Alex Halliday
CEO
AirOps
Learn more
Aleyda Solis
International SEO Consultant and Founder
Orainti
Learn more
Barry Schwartz
President and Owner
RustyBrick, Inc
Learn more
Chris Andrew
CEO and Cofounder
Scrunch
Learn more
Connor Gillivan
CEO and Founder
TrioSEO
Learn more
Eli Schwartz
Author
Product-led SEO
Learn more
Ethan Smith
CEO
Graphite
Learn more
Evan Bailyn
CEO
First Page Sage
Learn more
Gaetano Nino DiNardi
Growth Advisor
Learn more
Jason Barnard
CEO and Founder
Kalicube
Learn more
Kevin Indig
Growth Advisor
Learn more
Lily Ray
VP SEO Strategy & Research
Amsive
Learn more
Marcel Santilli
CEO and Founder
GrowthX
Learn more
Michael King
CEO and Founder
iPullRank
Learn more
Rand Fishkin
CEO and Cofounder
SparkToro, Alertmouse, & Snackbar Studio
Learn more
Stefan Katanic
CEO
Veza Digital
Learn more
Steve Toth
CEO
Notebook Agency
Learn more
Sydney Sloan
CMO
G2
Learn more

The modern web design process

Discover the processes and tools behind high-performing websites in this free ebook.

Read now

Launching the Wishlist

To give you a more direct way to vote on and make feature requests, keep these requests better organized, and to make it clearer to our community what we’re working on, we’re phasing out our forum wish list category in favor of a new, community-driven wishlist website.

We’ve started migrating some of the top requests from the forum to the new wishlist site, and will be pointing existing forum threads to their corresponding wishlist threads over the coming days.

In the meantime, we invite you all to check it out and vote for the features you want most, or propose new ideas. It’s integrated with your Webflow account login, so you won’t need to create a new account — just use your existing Webflow account.

The Webflow Wishlist will be the new source of truth for feature requests and prioritization.
Voting and threading will keep the new Wishlist site much more organized.

The Webflow Wishlist is now our source of truth for all communication channels: support tickets, Twitter/other social media, emails, and so on.

The beginnings of a public roadmap

Many customers have asked us to create a public Webflow roadmap. While it’s often hard for us to describe exactly what the development team is working on (such as refactoring projects), our public wishlist site gives us a few ways to describe feature requests we’re actively working on or considering.

As requests are added to the wishlist, we’ll be tagging them with one of the following labels, which will help you understand where they fall within our development and planning timeline.

  • Planned: Features we plan to get to in the short to medium term. (Ideally, in 3-6 months, but timelines may vary.)
  • Considering: Features we’re actively looking for customer feedback on before prioritizing in our development schedule
  • Unlikely to build: Features that don’t line up with our long-term plans or vision for Webflow
  • Shipped: Features that have recently shipped, and any additional details
  • Already exists: Features requested by the community, but that already exist in Webflow

Looking to the future

Webflow has an incredible community of supporters, and we hope our wishlist site will be the first of many improvements we’ll make to bring more transparency to our development process. As with any project, the Wishlist will continue to be a work-in-progress, but we’re certain it’ll improve our ability to communicate our roadmap to you, as well as your ability to influence that roadmap.

Read now

Last Updated
January 17, 2017

Related articles

Threads is a lesson in internet nostalgia
Threads is a lesson in internet nostalgia

Threads is a lesson in internet nostalgia

Threads is a lesson in internet nostalgia

Strategy
By
Wren Noble
,
,
Read article
Getting through — when your audience is tuning out
Getting through — when your audience is tuning out

Getting through — when your audience is tuning out

Getting through — when your audience is tuning out

Strategy
By
Wren Noble
,
,
Read article
The marketer’s CMS buyer guide
The marketer’s CMS buyer guide

The marketer’s CMS buyer guide

The marketer’s CMS buyer guide

Strategy
By
Joanna Rutter
,
,
Read article
Communicating with web designers: a digital marketer’s field guide
Communicating with web designers: a digital marketer’s field guide

Communicating with web designers: a digital marketer’s field guide

Communicating with web designers: a digital marketer’s field guide

Strategy
By
Elijah-Blue Vieau
,
,
Read article
How Nike became the brand to imitate
How Nike became the brand to imitate

How Nike became the brand to imitate

How Nike became the brand to imitate

Strategy
By
Liz Huang
,
,
Read article
How not to design web forms
How not to design web forms

How not to design web forms

How not to design web forms

Design
By
John Moore Williams
,
,
Read article

Get started for free

Try Webflow for as long as you like with our free Starter plan. Purchase a paid Site plan to publish, host, and unlock additional features.

Get started — it’s free
Watch demo

Try Webflow for as long as you like with our free Starter plan. Purchase a paid Site plan to publish, host, and unlock additional features.