Assets on StoriesOnBoard

Get familiar with all assets you can create and manage related to your products.

Tamás Párványik avatar
Written by Tamás Párványik
Updated over a week ago


What assets are available on StoriesOnBoard

A product team often need to handle multiple assets as the project is progressing. StoriesOnBoard offers end-to-end product management solutions that includes the following assets:

  • Products

  • Insights

  • Ideas

  • Portals

  • Personas

  • Story maps

  • Roadmaps


Products are shared team spaces where a dedicated team can isolate and manage a single product or an entire product line with their all assets (story maps, user personas, roadmaps, insights, ideas, portals).

Creating separate products on the workspace allows organizations to isolate teams who works on the particular product. This approach is crucial when your organization handles multiple projects at the same time for various clients. Establishing products on the workspace will eliminate the possibility for users to access unauthorized projects or documents.

This isolated product entity helps teams to stay focused and find everything at a single interface including a dedicated product dashboard. This interface allow teams to save time accessing relevant product assets and even link external product attachments sharing only this specific group of users who has access to your product.

💡 Tip - Learn more about Products.


Insights are often referred as user insight or customer insights. They help to gain knowledge about their expectations, behaviours, needs or experiences interacting with a product or solution. StoriesOnBoard helps product teams to collect all product insights into a single repository.

Once you’ve got a flat backlog of product insights from different channels, at this stage, you have only one goal: sort the insights by their goal and empty the insights inbox.

Link insights to an idea to create actionable feature ideas and add related insights to see where ideas originally came from. Incubate insights if you need some more information before deciding on an insight, set it aside. Archive insights: unrealistic ideas or low-priority requests? Push them to the archive where you can find them at any time without them taking up space on your backlog.

💡 Tip - Learn more about Insights.


Ideas are larger building blocks in the product development process. Incorporating several insights, ideas serve as the middle level in the product feedback hierarchy. Ideas should be created for features that could be pushed to development. So while insights are only crumbs of information, ideas might be putting the icing on your donut where several crumbs (or drops) make up that icing.

Ideas are presented on a customizable Idea Board where you can define your own structure. Furthermore, you can prioritize, organize and label ideas, and set custom views on the board as well to display relevant ideas only.

💡 Tip - Learn more about Ideas.


On Portals you can make some of your feature ideas and their statuses public and invite your power users to vote and comment on them. You can select your preferences which Ideas you want to share from your Idea Board and set portal details for them. Visitors on Portals can help prioritizing ideas by upvoting or they can send new feedback for the team for consideration.

💡 Tip - Learn more about Portals.


User personas help the product manager and other members of the product team to understand the key characteristics of a particular user group. Creating user personas is a key part of the agile product development process, and it is essential to do it at the beginning of the product planning process i.e. during the product discovery phase. Create Local Personas relevant for individual story maps or Global Personas that can be called into any story maps if required.

User activities are milestones where the user’s mindset change. Describe users’ mindsets and behaviors at every stage you’ll find differences. Use this additional information to prioritize features or to improve the user experience. Take a deep dive into a selected part of the user’s journey. You can easily hide other non-relevant activities. Narrowing your scope lets you discover missing steps or additional ideas.

💡 Tip - Learn more about User Personas.

Story maps

User story mapping is a lean method that is often used by Agile teams. It involves using story cards – the advanced method to replace sticky notes – and sketches to map out the interactions that the team expects users to have with a digital product to reach their goals.

There are three levels of depth in a user story map:

  • activities or goals (the broadest category)

  • steps

  • details (the most specific actions).

Story maps on StoriesOnBoard provides a great experience, even for beginners. Instead of messing everything on the board, we created multiple Views to show the right amount of information on the cards.

Discovery View provides a lightweight overview of the board — so you can focus on what matters, mapping the narrative flow and collecting user stories.

Planning View helps you to prioritize and organize the backlog into releases. In order to mark priorities on the story cards, we added a lightweight block to rate priority, business value, and effort.

Backlog View is for adding specifications and story points and does manage your backlog and follow status changes. The quick estimation widget helps you to adjust story points with your mouse or your keyboard.

Tracking View is a great place to assign cards to team members and see ongoing releases with great details.

💡 Tip - Learn more about User Story Maps.


Story maps are a great tool for digging deep into user journeys by mapping out all the steps the user does in the product. This information and user stories could be too granular to stakeholders who want to have a quick (and high-level overview) of what will happen around the product in the next few months or quarters.

Besides, as a product owner, you often start with a large chunk of backlog items (eg.: add a blog to an e-commerce website) which can be detailed later (as part of an existing story map, or on a brand new story map). So creating a roadmap of these large items could be helpful to:

  • gain oversight on

  • prioritize

  • schedule large backlog items.

Moreover, it provides an informative view for tracking the development's progression later on. StoriesOnBoard offers various roadmaps to choose between.

💡 Tip - Learn more about Roadmaps.

Talk to an expert

If you need any assistance to find the best way to start, talk to an expert and get personal guidance to get started in minutes. - Book a product walkthrough.

Did this answer your question?