Instructions – 52questions
About the card deck
The questions are deliberately left open. The idea here is: go with the flow. Don’t think too much about the question. Instead, go with the first thought that comes into your head when considering the answer.
If you’re working alone with the cards: make sure you make a note of the answers, even if it’s just in short hand for the time being. This will keep you from hiding the truth from yourself.
The 52 questions are above all an opportunity for reflection. What you do with them is up to you. But the idea is: even little steps are a step in the right direction. All improvements and every change is welcome! Take your answers and turn them into concrete action for yourself. Seize the initiative!
Simply place those cards you can’t answer straight away to one side and come back to them later.
There is some overlap between the questions. That is intentional though as I don’t expect you to get through all cards in the space of one day.
Some terms are certainly specific to certain industries and fields. For example, the terms customer and user are basically synonymous for our purposes.
Buckets of cards
Understand the Problem
Find a Solution
Do some Planning
Get it done (Implementation)
Listen & Learn (Optimization)
All forces united (Team)
Grow! (Personal)
Possible scenarios for use
Pick a card every morning and take 15 minutes to think about the question. You will see more clearly and your actions will be more considered as a result.
Team up with a colleague to form a learning group: each of you answers the question for yourself and then presents your answer to the other. Of course, the other person then gives their feedback on the answer.
Take one of the subject areas (e.g. Get it done) and then work specifically on enhancing your strengths in this area.
As Head of Product or Team Lead, you can make use of the cards in your 1o1s. Placing a card on the table to begin and get the conversation started.
As an Agile Coach/Scrum Master, you can use the cards as a way of supporting the product manager by asking them smart, relevant questions.