Now that you’re acquainted with the data model and how to reflect your work within, let’s dive into the main areas of the platform:


At, we believe your roadmap is a critical strategic planning and communication tool. The Strategy section provides you with a flexible space to develop your roadmap and communicate it in different ways to various stakeholders. Within the Strategy section, you will find:

  • Strategic Inputs: The place to draft and maintain your product strategy. Provides the strategic context and rationale for Feature planning and prioritization. Take a look at the Strategic Inputs walkthrough video for more information.

  • Roadmap: A selection of views that will help you craft your strategic plan. The roadmap has five different views: Strategic Roadmap, Release Summary, Swimlanes Roadmap, Kanban Roadmap, and Timeline Roadmap.


In the Define section, you can find useful, out-of-the-box views which allow PMs to outline feature specs, organize their data according to their preferred hierarchy and visualize how new features are to be prioritized.

  • Product Backlog: One of's main features is the ability to build your backlog in a hierarchical manner - you can nest features under epics, which can be grouped into products. The Product Backlog View is built specifically to make the process of creating the item hierarchy easier.

    This view gives you a dedicated space to manage your backlog and efficiently create, organize and view your product work items: get the full picture of your product hierarchy; quickly add new items to your hierarchical product tree; empower the view by adding custom fields as table columns to provide more context.

  • Requirements: You can find the Spec Editor and Story Mapping view under "Requirements". To switch between Spec editor and Story mapping views, click on the arrow next to the Requirements menu item or on the View Type button from the view controllers.

    • Spec Editor: Create the supporting documentation for your product here, including describing the user problem, business opportunity, and the corresponding solution design and spec requirements. The Spec Editor is where you can see your entire workspace hierarchy as well as add new Ework items and write detailed specs in a doc-like format.

      Tap into best-practice templates to write clearer, more refined specs from the get-go, or create your own templates to align the product organization to work using the same methodology.
      We’ve created a quick Editor overview to help you get started.

    • Story Mapping: A powerful visual tool to help define and prioritize your Product’s Features. Story Mapping is great for the initial ideation and specification of a new Product and gives you a sticky-note type environment to quickly add and view new areas of your product.

      See the Story mapping overview, or check out our Story mapping walkthrough.


As a product manager, our Planning section is where you will spend most of your time in We’ve created both overview videos and detailed walkthroughs to take you through our key Planning features:

  • Planning Views: This is where you can create, prioritize, and plan your work items. We created a variety of views to support different purposes when coming to slice and dice the data and present it in the most suitable way.

  • Capacity Planning: Use the powerful capacity planning view to effectively allocate resources and easily adapt to capacity changes as products evolve. With multi-dimensional capacity planning, allows you to drill down into specific parts of your business to get a deeper understanding of capacity availability. This means you can outline capacity parameters across various dimensions of your team, e.g., front-end development teams, back-end development teams, and various squads.

See this guide to explore further how capacity planning works in


Under the 'Track' section, there are two useful views that allow you to keep track with your work item's progress and current state.

  • Product status: This Kanban view is automatically grouped by 'status', where you can follow the status for each of your items. This view allows to easily update an item's status by dragging and dropping it under the appropriate status column.

  • Dev status: A Table view grouped by Sprint, along with a set of fields related to the appropriate Dev tool that make it easy to understand what's going on in Development.


The fifth section of provides you with the tools needed to collect feedback and make informed product management strategy decisions.

  • Feedback Portal: Capture the voices of your customers and internal teams in a self-branded Portal and then turn these ideas into clearly defined Epics/Features in your live Workspace. Read more about the Feedback Portal, how to set it up and how to promote feedback.

Personal Views:

Create, save and re-use custom, personalized views that only you can access.
Whether it's an idea you'd like to polish before sharing with the wider team or a view that focuses on work items under your responsibility, saving personal views is quick and valuable.

Did this answer your question?