Feature Ideas

Help us understand what you'd like to see in future Reciprocal.dev releases. Use the voting tools on each idea to tell us how important they are to you

  1. Build a Plugin ecosystem

    By enabling tech savvy users to build plugins for the Reciprocal.dev UI (integrations outside the UI are covered elsewhere) we allow them to build tools to bring in the data they want visualised against their product. This means that users can get infinitely more value from the tool if we're slow to implement an integration that they want. We should also look to set up a community around plugin development so that developers and users alike can get the most out of the plugin ecosystem

    Colin

    0

  2. Outbound Integrations

    While we want to teams to use Reciprocal.dev to enable the team to hold impactful conversations about their products we don't want to lock them into a silo as this would make our tool a pain to work with. By building an API for users to build tools to work with their Reciprocal.dev data and creating a set of integrations with populate tools our user's use we can further provide value to user's outside of Reciprocal.dev.

    Colin

    0

  3. Inbound integrations

    Most of the information that users will be looking to map in Reciprocal.dev will already live inside the tools they currently use such as design tools, issue trackers and knowledge bases. By building integrations with these systems we can streamline the user's experience of creating maps and make it easier for teams to adopt using Reciprocal.dev

    Colin

    0

  4. Multi-abstraction level mapping

    The User Journey map is the highest abstraction level that the product's team will work on. In order to get better insights into the way that the product is built and to better inform decisions it would be great to offer teams a means to view the user journey at different abstraction levels like: User Journey Data Flow System Component These levels could have a hierarchy allowing for data collected from lower levels to be bubbled up into the higher levels so a team could see bugs, technical debt and other development metrics from the System Component level in the User Journey level and dive into the details when appropriate.

    Colin

    0

  5. Add a means to make small changes based on configurable values

    In the MVP read-only map we had a means of making small changes based on a product's environmental configuration such as: Update screen images based on market region to show the correct currency symbols and address format Update the Step type and screen images based on the device type being used to show how the product worked on Mobile or Desktop Update the map based on an A/B test or feature toggle being active Following user feedback of the read-only map this was seen as valuable as it allowed for the team to map how the product changed based on where it was deployed and the end user's device & region. However user feedback when creating the editor found that building the map with this feature led to a lot of effort so it was removed. It might be worth revisiting this functionality and seeing if we can find a good trade off between the complexity to build the changes into the map and the value it brings to the teams.

    Colin

    0

  6. Group map entities into Features

    Create an abstraction level between individual entities and the map that would allow Steps & Connections to be grouped into Features. This would allow for data visualisation at a slightly higher level and would be more aligned with how product teams generally work. By being able to see the contextual boundary of the area they work on they can focus on the changes they want to make while also being able to see how that Feature interacts with others on the larger map.

    Colin

    0

  7. Visualise differences between two Map Versions

    As Map Versions are snapshots of the product's functionality as it evolves it might be useful to see a diff of the changes to the Steps, Connections as well as the coverage and inclusion of User Journeys and Test Cases. This would allow a team to quickly focus on what was added, removed and changed between versions and would be useful for diagnostic activities.

    Colin

    0

  8. Build convergent Map UI

    Make it easier to use Reciprocal.dev on tablets and mobile by building a map UI that adapts to the device's screen dimensions

    Colin
    #Improvement 👍

    0

  9. Generate thumbnails for Maps, User Journeys and Test Coverage

    It'd be great to have thumbnails for the Maps so that a user can quickly see a birds-eye view of the map within the account dashboard. We could expand this to show a linear flow of the Steps and Connections a User Journey and Test Case covers too in order to see the extent of the scope quickly too.

    Colin
    #Improvement 👍

    0