'Our customer panel is involved in everything
Posted: Mon Dec 23, 2024 7:10 am
Try to keep the focus on testing your ideas and find out what is most important. Determine what is minimally necessary to launch your product on the market ( minimum viable product ) and which components can wait a while. If you have tested your product proposition well, it will also be much easier to determine how your application should work. For example, you can test the global interaction design with wireframes. A trained scrum team can then work out the graphic design per sprint for the components that are relevant at that time, based on house style standards and already available components.
Practical examples of how it should be done:
'In the start-up phase we will canvass here to arrive at a clear vision.'
'We mainly create graphic designs here for interaction design.'
'Within a few weeks we will have a vision, product backlog and the scope of the minimum viable product (MVP).'
'Wireframes and a global interaction design are developed for the MVP.'
'Construction starts without a functional design.'
'Each sprint, the customer panel provides feedback to improve the product.'
Examples of what not to do:
'This idea is simply good. Testing with customers is hospital email list not necessary.'
'In our situation, testing with customers is not possible.'
'This design is so beautiful, we definitely want it.'
'The management has already said yes.'
'Everything has actually already been worked out. The technicians just have to build it.'
“Everything is part of the MVP.”
Finally, get started?
You can read more about using canvases in this previous article . An explanation of how to use the vision board is best read on the website of Roman Pichler himself. His book ' Agile product management with Scrum ' (aff.) is also highly recommended
Quantitative and qualitative online customer feedback: you've probably heard about it. But what exactly is it? When we talk about quantitative and qualitative customer feedback, we're actually talking about objective and subjective data. Quantitative (objective) data shows numerical data, such as the number of clicks and the number of visitors, but also the scores (such as a Customer Effort Score or numerical rating of the page). In short: it's about numerical results.
Practical examples of how it should be done:
'In the start-up phase we will canvass here to arrive at a clear vision.'
'We mainly create graphic designs here for interaction design.'
'Within a few weeks we will have a vision, product backlog and the scope of the minimum viable product (MVP).'
'Wireframes and a global interaction design are developed for the MVP.'
'Construction starts without a functional design.'
'Each sprint, the customer panel provides feedback to improve the product.'
Examples of what not to do:
'This idea is simply good. Testing with customers is hospital email list not necessary.'
'In our situation, testing with customers is not possible.'
'This design is so beautiful, we definitely want it.'
'The management has already said yes.'
'Everything has actually already been worked out. The technicians just have to build it.'
“Everything is part of the MVP.”
Finally, get started?
You can read more about using canvases in this previous article . An explanation of how to use the vision board is best read on the website of Roman Pichler himself. His book ' Agile product management with Scrum ' (aff.) is also highly recommended
Quantitative and qualitative online customer feedback: you've probably heard about it. But what exactly is it? When we talk about quantitative and qualitative customer feedback, we're actually talking about objective and subjective data. Quantitative (objective) data shows numerical data, such as the number of clicks and the number of visitors, but also the scores (such as a Customer Effort Score or numerical rating of the page). In short: it's about numerical results.