We made it. July 17th is the last day of the school year so as of this week, Code Club is out for Summer.
Since our first practice session on 26th March, 25 Redgaters from right across the business have delivered over 1500 hours of learning.
We’ve had students from 20 countries (all the way from Brazil to Japan), and recordings of the classes for students that coudn’t attend live have racked up another few thousand views.
Feedback from parents has been universally lovely, and we get more and more comments each week. Here are a few of my favourites:
- Thank you for doing these! My older daughter loved the Python ones and my younger one loved the scratch ones! We love that they have learned some coding from folks in the UK, half way around the world! …
We’re currently running a high rate of research calls in my teams. A 45 minute conversation and follow up session every day is about normal for the last quarter. The frequency has allowed me to focus on something I’ve wanted to improve about my own practice for some time.
Research calls are for learning, not for pitching my product.
The theme of our current calls is around on-boarding and value awareness. It’s a perfect topic to force myself to avoid the pitch because every single day a customer will:
I’ve been on teams that demo every sprint, teams that demo if they have something they think stakeholders will care about, and some that don’t demo at all.
I’ve come to realise that the value in the demo is not the opportunity to update stakeholders. It’s the contribution it makes to the health of the team.
Here are a series of ways that the demo helps assess and improve team health.
There are other more formal ways to keep track, but if a team is demoing we’re delivering value every time. …
One of the first things you do as a PM joining an existing product team is to assess the lay of the land. Get to know the team, understand the current roadmap and priorities. The first few weeks go fast and before long you’re up to speed with the day to day.
At that point the fun stuff begins. You start asking the ‘why’ questions.
I was at this point very recently so wanted to share how I approach discovery on a large existing product, plotting out a course to sprint-level discovery in the near future.
This post, and my end goal of continuous discovery was inspired by this Teresa Torres keynote. Do go have a watch if you haven’t already seen it. …
This post is a response to Embrace the Interruptions over on the Aha! PM blog. It really resonated with me, and on further reflection over the last week I realised that it’s only half the story.
As much as I embrace the interruptions, taking the time to be unavailable is as important.
As a product manager your primary responsibility is connecting with stakeholders, understanding their needs, and working with your teams to solve their problems. The more you hear from everybody around you, the more you learn. …
It seems that the hardest part of writing any research is coming up with a good title.
Earlier this month King & Baatartogtokh published a paper examining the theory of disruptive innovation that was made famous in the book The Innovators Dilemma. They found (8 years after publication..) that less than 10% of the case studies cited in what has become something of a management bible actually demonstrated the theory in action. Their paper shifted ‘disruptive innovation’ from being a goal all companies should aim at to an observation that occurs in rare cases.
It should have been huge news, but they gave their work the less than exciting title of ‘How Useful is the Theory of Disruptive Innovation‘ and nobody seems to have paid much attention. …
I’ve been playing with the new IFTTT camera app and it got me thinking about how the original camera app on my iPhone isn’t as useful as it used to be. After all, it’s just a camera app. If I want it to actually do anything with the photo I’ve taken I have to tell it what to do. By pressing more buttons. How very 2014.
If you haven’t already seen it, IFTTT Do is a set of apps that extend the original IFTTT idea where you provide some simple rules and the software automates them. For example, if I take a photo of a receipt it automatically puts it into my expenses folder in GDrive, a photo of the little monster doing something will end up in a shared album for my family. …
Your work is out in the world, but you keep thinking of ways to improve it. Maybe your clients have got ideas to make it better. Or perhaps priorities have shifted and what you thought was important at the start is less so now.
The challenge for you as the designer then becomes about how to make those changes. Do you opt for subtle tweaks with each new update, or an entire redesign behind the scenes and release it all in one go?
It’s a conversation we’ve had a number of times in the team recently, but sitting down on the train and opening up Spotify this morning made me think about it…
We've recently been learning how mentors can help and/or hinder our progress through the startup maze. Here’s what we've discovered about picking and choosing their advice.
Like many other early stage tech companies we have mentors helping steer our work in the right direction. If you’re in a similar position I’m sure you do too, or if you’re thinking about getting in to the startup world I’d recommend you get some. You can’t be an expert at every aspect of your business, but you can find people who’ll help you learn pretty fast.
That said, I've become increasingly conscious of the need to pick and choose the advice we take; it’s easy to be awestruck by ‘older & wiser’ influences and to forget the reason you started the company in the first place. …