Maintaining your product when it enters the market
What is success defined as?
It would be absurd to try and come up with a definition of success that can be applied across every project. Success for project A is completely different to success for project B. So, we must set the success criteria on a per project basis. This is generally done at the start of a project but updated as we progress and as business demands change.
How can it be measured?
This is a tough question to answer. It generally depends on the type of goal you're trying to measure. Some goals may be quantitative, which can be measured by analytics tools. We'll discuss these tools in more depth shortly. Qualitative goals are harder to measure but can usually be done through user testing and more open-ended survey methods.
With background knowledge of our clients applications, business goals and success criteria, as well as experience using analytics tools, we've found ourselves in a great position to capture and synthesise product data. Product owners can be incredibly busy managing the application and helping deliver internal business goals. To ensure we're making data-driven decisions, we experimented with a few different formats. As mentioned before, what came out of this experimentation was product success consults.
Product Success Consulting
These consultations are delivered in the format of a 1 hour meeting scheduled every 4 weeks. Prior to the consultation, WM will observe collected analytics related to the previous 4 weeks. Afterwards, WM will deliver a Product Success Report detailing all items observed, discussed and the actions set. So effectively, it involves a short meeting to run through the most recent data and set actions based on that. In order to have effective consults, we must setup analytics tools. These tools are usually identified at the scope stage and are chosen based on what data needs to be captured.