Discovery Workshop for PWr Students
Info for Non-PWr Students
On 2021-10-19, I gave pre-recorded lecture on Discovery Workshops to PWr students. Unfortunately, I was not able to do it live because I was sick and I lost my voice.
This article is a collection of resources to fulfil my presentation.
Fun-fact about pre-recording
- There were 15 cuts in the video, because I had to get my voice back between them.
- How many did you spot? :)
- Sorry, for not telling jokes during the presentation. I was trying to survive. :)
What can you do right now?
If you listened to my lecture then I encourage you to work on your own project in this way. You can perform Competitive Analysis, Segment Your Customers, then open Miro and proceed with Product Vision, Unfair Advantage, Proto-Persona, Journey Mapping, User Story Mapping and Prioritization.
Below you may find some resources for each step.
After that (or in the middle) you can msg me on LinkedIn to ask questions. I will be super happy to answer.
How to be an awesome developer?
Go to YouTube and find presentations made by Wojciech Seliga. You can simply click here. I encourage you to watch all Wojtek’s presentations from 2012 to 2018.
Watch this YouTube video on Cynefin.
Just ask if there are any competitors on the market with similar idea to yours. If so, try to use their experiences. Analyze their products.
However, you may be really innovating, which means you may work on Blue Ocean product. Then it will be super hard to proceed with Competitive Analysis. In this scenario, you can understand what it means to be in the Blue Ocean by watching this video - https://www.youtube.com/watch?v=sYdaa02CS5E.
Your product will be used by people. Try to think about them. Maybe you can group them into a few separate segments? It will help you understand the differences between them and create much better final solution, which is going to meet their expectations.
To work on that you can use template from Radical Product available in their toolkit - https://www.radicalproduct.com/toolkit/.
This is additional step, which may help you focus on the biggest advantage that you would like to provide in comparision to your another existing solutions. What’s the ONE thing that you want to do better than everyone else does?
Simplified Value Stream
In that case, do not focus too much on theory that you may find on Google. Just take a paper and try to draw people and systems, who exchange information in the domain that you would like to build a solution for.
Try to understand very big picture. Use icons, avatars, logos to paint the process.
Personas are great. This is one of the best tools you can imagine. However, performing high quality user research is very expensive. For your own projects maybe it will be enough to ideate on some imaginary person, who will be using your product.
Try to get into their shoes and uderstand the pain points, which they have. List the pain points down.
Map the process, that the persona lives in. Your solution will be the part of it.
If you get understanding of what’s happening in the beggining and at the end - it will enable you to build better product for your users. Do not narrow your perspective only to the part, which is going to be directly covered by your product.
This is not a list of features! This is a list of activities, which your persona does when they want to get the job done.
Finish this step by drawing a rectangle to highlight an area in the process, that you would like to create your solution for.
This is a method, which may help to understand more complex problems. I do not want to ellaborate on it today. You can skip it. However, if you would like to learn more then go to this page - https://github.com/mariuszgil/awesome-eventstorming. Btw, maintainer of this repository is from Wroclaw! :)
User Story Mapping
This step is entirely about your product. Map the process, that you will be building. List down the stories for each step.
More info: https://www.jpattonassociates.com/story-mapping/.
Use user story map to define 1st testable increment and MVP.
Leave everything else in the backlog at the bottom of user story map.
Remember, the most important elements go on top of the map.
If you want to learn more about prioritization methods, check: HiPPO, ICE, Cost of Delay, Impact/Effort.
Take a break and start your project
Go for a walk. Think about it. Get back to the computer and work with your colleagues on building this awesome product!
Want to ask Rafal a question?
I will be happy to answer your questions via LinkedIn. Add me to your LinkedIn connections and simply ask whatever you want. Maybe even we can have a call after I get my voice back?
Do not forget to say “Hi!” to Maciej and Mieszko during the hackathon! :)
Good luck! :)