Getting the most out of retros
Use big group retros to uncover issues.
Use small focused discussion to resolve issues.
What are you hiring for?
When you hire someone you get:
- Existing knowledge and expertise
- Experience in applying knowledge in certain contexts
- Capability to generate new knowledge
Depending on what the organisation needs at the time should guide the balance of these three things.
If the area of expertise is new to an organisation, then experience of applying it more important and matters more than how much knowledge they have. Applying a few things well is more effective than applying lots of things poorly.
If the organisation is trying to mature an area, then hiring someone who is strong in existing knowledge helps most with that.
And if an organisation wants to innovate in an area, then they should hire someone who is good at generating new knowledge.
How much change can an organisation take?
Can an organisation take on continuous change? Or is the unfreeze/move/freeze approach better/more realistic?
Can all functions change at the same time? Or to put it another way, what might the consequences be of some functions changing and maturing at different paces. If tech, and finance and HR and design and delivery and product and everything else are all changing at the same time, is that too much?
Pacing layers matter. Different things change at different rates. People’s knowledge and skill changes more quickly than the people in the organisation (or at least should, if it doesn’t it might be a sign of not enough learning or too high turnover). Acceptance of change is somewhere in between. Changes in an organisation are accepted and adopted through a mix of people learning to do things differently and people who don’t want to change being replaced by new people.
MECE has a lot to answer for
MECE has a lot to answer for when it comes to synthesising and communicating complex information.
The idea that everything we need to know about can be placed in a box gives us a false sense of security and loses the messiness of knowledge.
What’s in my bag
As part of my goal of being even more minimalist this year, I’m going to try to live out of two 35 litre bags.
Clothing
- Hat – Warm hat
- Shell jacket
- Down jacket
- Waterproof jacket
- Fleece jacket
- Shirt x3
- T-shirt x3
- Jean x3
- Shorts x3
- Socks x3
- Trainers
- Belt
Ditch pack
- Passport
- Bank card
- Driving licence
- Cash
- Hard drive
- Spare car key
Wash kit
- Tooth brush
- Tooth paste
- Towel
- Flannel
- Shower gel
- Nail clippers
- Deordorant
- Moisturiser
- Hair trimmer
- Scissors
Tech
- Work laptop
- Work laptop charger
- Surface laptop
- Surface charger
- Phone
- USB to USB-C cable
- USB-C to USB-C cable
- Kindle
- Backup phone
- Wall plug
- Battery pack
- Wired earphones
Personal
- Glasses x2
- Sunglasses
- Swiss army knife
- Car keys
- Window tool
- Pen
- Notebook
- Headtorch
240115
Had an interesting interview. I love talking about product management, I have to contain myself and remember that most people I talk to don’t have all the history and context I do.
Struggled to plan my week today so need to spend some time on it tomorrow.
Had a few meetings all about lining up upcoming work. Yes, meetings about meetings…