ThreeSixty Published Roadmap

This roadmap gives you visibility into the current initiatives of our product development team, the "next-up" features we're already planning for, and our plans for what we think will come further out into the future. This is a live, transparent look at our product roadmap, which is updated often based on feedback, technical roadblocks, and other changes to the needs of you, our customers.

To access the product roadmap from within the web client, select the Help icon that displays in the bottom right corner of the application, then select Product Feedback & Roadmap to see the embedded roadmap. You can also view the roadmap directly here.

Product Vision: Provide our ThreeSixty customers with a dependable, modern constituent engagement platform that covers their advanced needs. ThreeSixty is a modular and extensible membership management platform that empowers enterprise-sized, mission-driven associations through managing finances/e-business, CRM needs, engagement, inventory, certifications and marketing.

In Progress: these are the initiatives that are currently in the hands of our engineers and work is being done to build them out—code is actually being written and the items you see here will be the next major enhancements or features you see rolling out in a near-future release.

Planning: the items you see in the next 2-6 months on the timeline are currently being researched, planned out, and evaluated by the Product Team. They are the things we are confident will be up next, after we complete the items in progress, and we’re working to get those initiatives ready for our engineers to pick up and run with. Often in this stage, the Product team is soliciting deeper feedback, working on designs and mockups, and setting goals.

Future: for items on the roadmap timeline 6+ months out from the current date, these are the current estimate of our next projects after we get through the items in the In Progress and Planning stages. The timeline on these items is the squishiest, and sometimes a feature or enhancement we think will be important turns out to be a lower priority than we thought as time goes by, and will fall off the roadmap. It is always kept up to date, however—so even though they are subject to change in the future, you can be sure that whatever you see here is what the Product team currently thinks our priority will be after the shorter-term projects are complete.

Customer FAQs:

Are these dates confirmed?

While items displayed in the current or next few months are fairly firm, we will always communicate exact launch dates through our Release Notes communications, as it becomes clear and reliable that we can estimate a delivery date for you. When the completion date isn’t imminent, however, these dates are estimates only, and subject to change. When an engineer picks up a problem and starts to tackle it, potential problems or underlying technical issues may not be apparent until we’re deep in the code. For many features, we may discover related ways to improve something or a new direction that will improve the product for more users, and it changes our scope. Sometimes with brand new features, we’ll let early users experiment and grow the feature so we don’t actually go in with a set expectation of what “done” means. These are all proven, positive product development methods that ultimately result in a stronger and more reliable product for you—but it does mean that sticking to a pre-determined date without compromising on quality is difficult. 

I saw something on the roadmap last week, but now it’s gone. What happened?

The 6-12+ month stage of our timeline represents our current guess of what we think will be most important to work on after the items in progress. We make that guess based primarily on our customers’ needs and goals—and those don’t always stay the same! If something that we thought was going to be important to you, our customers, starts to fade to the background and other valuable opportunities come up to serve your needs, we don’t want to be stuck doing something we anticipated would be a good idea 6 months ago just because that was our guess back then. To be agile and adapt to the Association world’s changing needs, the longer-term roadmap for this product must also be agile and adaptable. That said—we do put a lot of thought and research into what goes into this roadmap, and we still think it’s valuable for you to see what we’re thinking in the long-term, and give us your feedback on that vision.

Why don’t these initiatives have more detail? I’d like to see the specifics of what will be in each feature.

The roadmap is intended to show our higher-level vision, and the direction of the product. We don’t list out all the details of what each initiative will include because that’s not necessarily communicating that vision, and we don’t want to include too much noise in showing you where we’re going. But more importantly—we don’t always have all of that detail figured out yet, especially for items further down the roadmap. As outlined above, the process of building new things is iterative and built on research and exploration. We don’t always know what will work best until we’ve spent time working through designs, prototypes, and testing. However, once we are ready to launch a new feature, we will provide ALL the details you could want! Our Release Notes outline every new feature or enhancement in detail, and all of our online help articles/videos/etc. are updated to reflect the changes prior to launching them.

Is everything the engineers work on included in this roadmap?

Nope—for the most part, the initiatives you see here are major projects that move the product forward towards our vision. The roadmap doesn’t include bug fixes, small “quality of life” tweaks or enhancements, or compliance/tech debt items we must complete. Those are always communicated in our Release Notes, but don’t necessarily contribute to the roadmap message.

How do I provide feedback on these items or other things I want to see on the roadmap?

Great question! In addition to our Idea Incubator in the ThreeSixty Client Community, we now have a dedicated feedback portal for you to submit ideas through the web client. This feedback is not just for major roadmap ideas—any small improvements, general problems you encounter, things that take a lot of time, etc. should be submitted here. Submit feedback any time, as often as you like. All feedback submitted through the portal is reviewed daily by our product team, and organized in our own system to track trends, specific areas for improvement, and get a general sense of the problems you run into. It is purposely not displayed publicly, unlike the Idea Incubator, so that we can gauge truly organic feedback based on YOUR needs and daily usage of the system, rather than ideas you’re seeing from others. Rest assured that feedback is read, valued, and contributes to our product roadmap!