journima

Decide what to fix next.

Pain points and opportunities from every map land in one portfolio with a key, a type, a status and a score. Then you can argue about the right things.

Keys people can say out loud.

OPP-12 and PAT-4 mean the same thing in the map, in a meeting and in a Jira ticket. Types and statuses are yours to define.

  • Custom types and statuses. Pain point, opportunity, solution, or whatever your practice calls them.
  • Item linking. Connect the solution to the pain it addresses.

Score it your way.

A 0 to 100 score per item, on whatever axes you agree on. Bubble size reflects how much evidence is attached, so loud opinions and quiet data are visible at the same time.

  • Two-by-two chart. Impact against ease, or any pair you choose.
  • Summary dashboard. Counts by type, status and map.
  • Kanban board. Move items across statuses as work happens.

Hand it to the roadmap team.

Export the portfolio to CSV when someone asks for it in a spreadsheet. On the Business plan, link an item to the Jira issue that delivers it, or create the issue from the item, and its key and status show on the item, in the portfolio table and on the map card.

Questions teams ask

Does every pain point have to be scored?
No. Unscored items sit in the portfolio and can be scored later, or never. Scoring is a tool for conversations, not a gate.
Is there a Jira integration?
Yes, on the Business plan. An admin connects one Jira Cloud site. Editors link a portfolio item to an existing issue, or create one from the item. The issue's key, summary, status and assignee show on the item, and the key and status show in the portfolio table and on the map card. They refresh every day. Linear is on the roadmap.

See your journeys take shape.

Start your free 14-day trial. No card needed.