In our previous post we described what should be done before starting implementation of a Product Management tool. This post provides tips for the implementation process.
Tip #5 – Customize the tool for your organization
Product Management Tools come with a generic data model and workflows. To provide the highest value for your organization, these generic processes must be customized to the product processes that work for your organization. While you may decide to adopt built-in processes that can help you, the tool should support product processes that work well for your organization.
Product Management tools are usually highly customizable. Analyze the product processes you use today, decide which processes you want to keep and configure the tool accordingly. If there are product processes that should be improved, use the tool capabilities to build better processes.
Tip #6 – Hold a practical workshop
Once you defined how to work with the tool in your organization, we recommend holding a workshop with the Product Managers to kickoff working with the tool.
In this workshop, the Product Managers start building their products in the tool so that it will be easier for them to work with it by themselves later. Walk them through the tool’s screens and ensure that they start inserting their product’ data. Allocate minimal time for explanations and most of the time for working with the tool.
Tip #7 – Provide guidance and support
After the workshop, when Product Managers start using the tool, they are likely to encounter questions regarding the workflow and methodology. Make sure they get the support they need as long as they need it.
This means that a person familiar with the Aha! implementation in the organization should be available for questions. In addition, we recommend holding periodic 1-on-1 sessions with each Product Manager to help them progress faster.
Tip #8 – Involve related teams
The introduction of the Product Management tool will impact R&D and other teams that work with the Product team. Involve relevant people from other teams in the process, so that they understand the implication on their work and the benefits for them. Show them the outputs from the that are relevant to them tool (e.g. requirements to R&D), get their feedback and address their concerns.
Tip #9 (for large companies with several products) – Start with 1-2 products and expand
When you start working with a new tool, you are likely to make mistakes in your initial definitions, especially when multiple people start working with a new tool at the same time. This can result in wasting time logging information in wrong places and having to repeat work, creating a feeling that you work for the tool instead of having a tool that works for you.
Therefore, we recommend starting with 1-2 products, validate that the tool is defined well for your organization and only afterwards expand to additional products. This will also enable you to show the rest of the Product team how the tool helps the first Product Manager, thus motivating the rest of the team to start using the tool as well.
StarVision helps companies implementing Product Management tools, ensuring smooth transition, short implementation time and effective implementation.
