Notion vs. StoriesOnBoard

Notion is good for a plethora of use cases. The templates that it offers give just a few established pages for common uses but these are some of my favorites:

• Kanban board: we use it a lot in my company to manage tasks and meetings
• Note taking: whether in a professional or academic environment, Notion is well suited to take notes of everything regardless.
• Software documentation: the "code" component to insert code snippets is perfect for creating tutorials and documentation for software development.
• Finance control: I use the "my finances" template to have a proper following of my monthly transactions, which allowed me to be more responsible with my money.
• Inventory management: Since I own multiple peripherals and general equipment, being able to have a portable inventory of all of it that includes their original value, warranty length and current state has been perfect to know when clean, maintain or straight up replace everything.

As mentioned earlier, we also use StoriesOnBoard to create other processes (customer and employee journey). We use the swim lanes to differentiate between measures, tools and processes and working with them is very easy and understandable for this purpose.

Less easy is the use of context, i.e. when one part of a story map depends on another story map. This cannot be avoided (at least for us) to avoid creating redundancy (and the risk of creating different stages). At appropriate places, we refer to the other map in the title.

• Team Collaboration. In Notion's software is the ability to see precisely who is working on a project and where. This eliminates any confusion when on calls or when working on the same project simultaneously. It is easy to tag co-workers to precise moments and build conversation streams.
• Text Coding. When transitioning text from our Notion ideation and drafting boards to our website backends, the coding holds on all of the text.
• Organization. Whether it's utilizing a "pin board" set up or nestling pages within pages, it is possible to keep everything organized and easy to find for every member of your team.

Incentivized

• User role management
• Jira integration
• Keyboard shortcuts
• Filtering by personas

• The increase in integrations with third parties will always promote the adoption of the platform in companies.
• Personalization with logos and corporate colors sometimes makes the difference when selecting a tool in a corporation.
• Having multiple functionalities for working in manufacturing companies and with devices developed by third parties encourages other companies to select Notion as their flagship tool to offer implementation packages under alliances that favor its use.

• Switching the view to a vertical mode (easier to scroll).
• Better availability of information on user story mapping.
• Possibility to link to activities and steps from other maps (Context).

StoriesOnBoard works really well; all features are well thought through. It could look a bit fresher, although the new updated dashboard is already much better than it was.

Trello only has the Kanban board feature and is great for task management, while Notion has a vast array of features, is easier to use, and has a more visually-appealing interface. I choose to use Notion over Trello due to its increased versatility and greater customization capabilities.

Incentivized

The only other competitor we looked at was cardboardit.com. Both had solid functionality, but StoriesOnBoard was more user-friendly and quick to learn and use in our opinion.

• In just a short amount of time, the majority of my course draft has been transferred into an interactive online course, always live
• Sufficient control over page structure gives a clean look, with sufficient means to add some personal touches
• After a learning period, I could concentrate on the content rather than the tech
• A huge motivational drive to learn more about no-code platforms (enthusiastic learner!)

Incentivized

• StoriesOnBoard (and story mapping in general) creates a low-cost visual method of aligning on high-level business and technical requirements early in a project and provides an ongoing reference as the project progresses. Having this alignment is critical for the later stages of the project.