Self-assessment

Start team self-assessment

For the best results, gather a few team members with various roles to do the self-assessment. We recommend including people of various expertise and team seniority.

We recommend that product leaders do the self-assessment together with their product teams for each product they work on.

~1 hour

3 - 4 team members

The assessment needs to be completed in one session.

Your self-assessment score

After the assessment, you will receive a score and detailed assessment scores and playbook recommendations through email (specified in next step).

Each team can only do one assessment every 6 months.

Score

125

~1 hour

playbook

Let's go!

We recommend that product leaders do the self-assessment together with their product teams for each product they work on.

Which company are you working in?

Which product are you working with?

Provide the product name of the product for which you are doing this assessment.

What is your role?

Provide the role you have in your team.

Please provide your email address

Please provide a valid Visma email where the results of the assessment will be send.

Who are you doing the assessment with?

For the most accurate and least biassed score, we recommend doing the assessment together with your team.

Click here

You need to answer all the questions above in order to proceed to the next step.

Product vision and strategy

Who owns the Product Vision and Mission in your team?

CEO CTO CPO Head of Product Product Director Product Manager Product Owner We don’t have a Product Vision We don't know Other

Does your Product Vision and Mission feel inspiring and make you want to work towards it?

Strongly disagree Disagree Somewhat disagree Somewhat agree Agree Strongly agree We don’t have a Product Vision and Mission

Does your Product Vision and Strategy align with your company’s business objectives (e.g. OKRs or financial targets)?

Yes No We don’t have business objectives We don’t know

Who owns the Product Strategy in your team?

CEO CTO CPO Head of Product Product Director Product Manager Product Owner We don’t have a Product Strategy We don't know Other

What is your current Strategy Score in Peakon?

Less than 0 0-29 30-49 50-69 70+ We don't know We don’t use Peakon

Does your Product Strategy contain:

Select all applicable options.

Market analysis and trends Competitive analysis and USPs Target markets and customer segments Strategic themes, objectives or bets as high-level focus areas Targeted product investment split in high-level focus areas Diagnosis of current product development capabilities None of the above We don’t have a Product Strategy We don’t know

Which roles were involved in creating the Product Strategy, Vision and Mission?

Select all applicable options.

Company Leadership CPO, Head of Product or Product Director Product Manager / Owner Other product team members Customer-facing teams like sales & support Marketing Customers None of the above We don’t have a Product Strategy We don’t know

How often do you review if you are progressing with your Product Strategy or if you need to revise it?

Monthly Quarterly Semiannually Annually On a more irregular basis We don’t follow up on the Product Strategy We don’t know

You need to answer all the questions above in order to proceed to the next step.

Operations and organisation

Which roles do the product development teams contain in your company?

Select all applicable options.

Product Manager and/or Product Owner or similar Back-end Developer, Front-end Developer or similar Business Analyst Data Analyst / Data Scientist UX Designer, Product Designer or similar UX Researcher Quality Assurer / Tester Other

What activities does your product team perform in order to inform and make roadmap decisions?

Select all applicable options.

We are guided by management recommendation and ideas We reach out to existing users to gather feedback on new products or features they are thinking about We reach out to prospective customers to gather feedback on new products or features they are thinking about We send out surveys to prospective customers in order to make product decisions We send out surveys to existing users in order to make product decisions We build new features and products based on pNPS, CES and/or product usage data (behavioural data tracking) We spend time optimising existing features and products based on pNPS, CES and/or product usage data We review what's important for our strategic purposes We analyse product usage data regularly in order to define whether or not a product is successful None of the above We don't know Other

How do you validate that your roadmap and product decisions are providing value to your customers?

Select all applicable options.

We rely on the opinions of management Research done by the sales team on e.g. loss review and new sales Customer Success, e.g. onboarding feedback Support tickets In-app feedback, e.g. pNPS, CES, CSAT or free text One-off data analysis of product usage/user behaviour Routine data analysis of user behaviour data, e.g. CES, feature adoption or task success One-to-many communication avenues with customers e.g. focus groups, community forums One-to-one communication with users, e.g. user interviews, usability testing, design sprints Product experiments, e.g. A/B testing or pilot customers We don’t validate that we provide value None of the above We don't know Other

Does your organisation have a definition of the main user value or a metric that illustrates that a user has seen or experienced value in your product?

Yes No We don’t know

What kind of initiatives does your roadmap have?

Select the option that best describes the initiatives.

Features Functionality Outcomes or objectives representing value for users, customers or business Other We don’t know

Do you set business or product metrics as targets for your bigger, roadmap-level initiatives?

Select the option that best describes the process.

We sometimes use target metrics, but we have no established process Business metrics (MRR, churn % or similar) whenever a direct measure is applicable We always have target product or traction metrics (CES, engagement, efficiency or similar) No We don’t know

Do you run experiments for your product initiatives?

Select the option that best describes the process.

We set up experiments on an irregular basis We experiment for both new features and improvements, as well as to improve existing ones We have an established experiment process & tooling that can be used for a multitude of projects or initiatives We don't run product experiments We don’t know

What metrics do you use to measure the success of your product / product team?

Select all applicable options.

Revenue Traffic User satisfaction pNPS CSAT User Retention Active user population CES We don't know Other

What recurring feedback loops do you have in your organisation?

Select all applicable options.

Sales and/or integration conversations Support ticket reviews Improvement requests forums for internal stakeholders Product usage metrics reviews User interviews Regular in-app feedback reviews, from e.g. pNPS and/or CES We don’t collect user and customer feedback We don't know Other

You need to answer all the questions above in order to proceed to the next step.

Continuous Discovery & Analytics

What feedback loops do you use as part of discovering & delivering product initiatives?

Select all applicable options.

In-house stakeholder conversations Surveys Pre-release user interviews Prototypes-and-usability-testing Pilot customers to test before full-scale releases Recurring post-release interviews In-app comments from users and customers, from e.g. CES User panel We don't know Other

Are you working in product trios? I.e. Are Product Managers / Owners, Developers and Designers collaborating actively, iterating with short feedback loops?

Yes, actively on a weekly basis At times, e.g. when we work with bigger product initiatives No We don’t know

What type of experiments do you run?

Select all applicable options.

We build and usability test prototypes before implementation We A/B test ideas in production We validate ideas in customer conversations We build MVP features and test them in production We don't run product experiments We don't know

For what purposes do you experiment?

Select all applicable options.

To validate packaging and pricing choices To understand whether to commit to building a product initiative/feature or not To determine whether we should release functionality currently being developed or improved To validate and de-risk strategic choices We don't run product experiments Other

Do you collect, track, and analyse data on how users interact with your product such as product events / logs?

Yes No I don't know

What type of detail are you able to look at / analyse from your current event tracking setup?

We look at basic things like number of clicks, submits, pageviews We are able to track some custom events and workflows how our users interact with our product We have a very rich customised tracking process of how our users interact with our product We don't know

Which of the following most closely resembles your current product analytics stack?

Select all applicable options.

We manually access usage logs in our product We have a tool for real-time product usage data tracking and collection We have a tool for behavioural data visualisation and analysis We have a tool for setting up experimentation projects None of the above I don't know

How do you typically make use of user behaviour data?

Select all applicable options.

We occasionally use user behaviour data for tasks or projects but we have no structured approach to it. We have a data dashboard that we regularly look at and work with. We quantify product metrics with user behaviour data which are then used in a structured way for experimentation and product improvements. None of the above I don't know

What type of metrics do you track continuously based on user interaction with a product?

Select all applicable options.

Daily, Weekly or Monthly Active Users or similar Feature adoption broken down to customer and/or user level Average task/workflow completion times Date, time patterns and/or time spent in the product User Retention None of the above We don't know Other

When does your team consider a feature or feature improvement to be 'finished'?

Select all applicable options.

The feature "works" on a technical level The feature works and looks in according to documented requirements and design The feature has been developed tested with end users with satisfactory results The feature has been designed and tested with end users, and achieved satisfactory post-release measurement results We don't know

You need to answer all the questions above in order to proceed to the next step.

Cloud accounting software built for small businesses

Start team self-assessment

Product vision and strategy

Operations and organisation

Continuous Discovery & Analytics

Product Discovery

Design Studio

Product Analytics

Playbook

Success Stories

Resources

Start team self-assessment

Product vision and strategy

Operations and organisation

Continuous Discovery & Analytics

Product Vision

Product Strategy

Peakon Strategy Driver

Product Strategy

Roadmap

Ensuring Customer Value

Measure User Value

Rapid experiments

Product Trio

Tools

Gather vs. Utilise

What “done” means: