Finish your things
Starting things is exciting but it is finishing which brings real, lasting value. Always prioritize finishing over starting.
Musings on product development, product management, design and other topics.
Starting things is exciting but it is finishing which brings real, lasting value. Always prioritize finishing over starting.
It's tempting to think that ideas like referrals and influencer marketing were conceived recently. This book shows us that marketers were employing these ideas (and more) almost 100 years ago.
A summary of the book, Measure What Matters, by John Doerr.
Everyone knows that product managers have to be excellent communicators. But what does that mean exactly?
It's not always easy to explain what product management is. Here's my attempt.
My new year's resolution this year is to track my personal goals using the Objectives and Key Results methodology. Here's the results from January.
Prioritization and the various frameworks you can use to prioritize.
My summary of this excellent book on OKRs and getting things done by Christina Wodtke.
A summary of a thought provoking article by Julie Zhuo.
A summary of an excellent Indie Hackers episode where Andy Cook discusses hiring people, finding mentors, managing your own psychology and raising money.
It seems easy to save money by skimping on quality in internal tools. There may be a hidden cost that you're missing...
How to deal with secondary roadmap components such as target customers and confidence levels.
Themes and how to use them.
How to define your mission, vision and values.
How to gather inputs for the roadmap.
Investigating the primary and secondary components of a successful roadmap
The problems with most roadmaps and the high-level solutions to these problems.
Over the years I've distilled a core set of principles which lead to improved product delivery and happier teams
A continually updated set of notes on episodes of the a16z podcast. I don't listen to all the episodes, and when I do I don't always make notes, but when I do I publish them here.
How I tried and failed to win buyin from my own team, how I changed the way I spoke about the vision for our product and how I re-framed the conversation in a way that made sense for everyone
The following are attributes that I believe good deployment tools (e.g. Kubernetes) should have.
My personal thoughts on an article about how to treat yourself and your career as if it was a product. Useful to think about for anyone who is trying to improve their own product management skills
Notes and comments on an excellent comparison of the pros and cons of web UIs vs CLIs and when each should be used
My personal notes and addendums on Brandon Chu's excellent article about the investor model for managing PMs
It's tempting to think that internal tool UX sucks because people just couldn't be bothered but perhaps there are times when "just good enough" is the answer.
We all know silos in agile engineering teams are something to avoid but can you walk into a brand new team and recognize them immediately? Here's what I've seen...
Writing down the problem is such an obvious step that nobody could miss it right? Well... sometimes people do and it causes no end of problems.
Why we try to focus on one thing at a time.
After 6 months in my new role as Product Manager, I feel like I've had an epiphany and discovered a new level of value I can add. This post explores what it is and what it means for me and my company.
How the web confuses users by hiding affordances and multiplying their total number.
If a Story in the backlog is something you’d like to work on one day, but that day is definitely not in the next 12 months — does it make sense to leave that story open and sitting in the backlog, or just close it?
Figuring out the type of issue you're dealing with can be a common source of discombobulation. This easy analogy helps me figure out how to classify work.
Or what's the difference anyway?