Five adages and how to apply them as a product manager

2024 - Calum Shepherd

I recently came across these adages while browsing the web, and they resonated instantly - not least because one of them comes from my favourite film of all time.

• Murphy’s law
• Gilbert’s law
• Kidlin’s law
• Wilson’s law
• Falkland’s law

Let’s go through each one and how you can apply it as a Product Manager.

Murphy’s law

“Anything that can go wrong will go wrong.” “In some formulations, it’s extended to: ‘Anything that can go wrong will go wrong, and at the worst possible time.’”

Sounds gloomy, but I’ve found it a genuinely useful mindset - especially since first hearing it in Interstellar.

How to apply it

• Expect challenges. Working in software means accepting that not everything is within your control. You can manage certain things, but success often depends on others - usable designs, reliable code, and so on.
• Plan for edge cases. Invest time up front. Talk through designs and implementations with engineers, always keeping the customer’s perspective front of mind.
• Stay positive. When things go wrong - and they will - bring energy rather than panic. Get the right people involved and treat setbacks as learning, not failure.

Gilbert’s law

“The biggest problem with any task or job is that no one tells you what and how to do it.”

Fun fact: Gilbert also happens to be my father-in-law’s name.

How to apply it

• Be organised. Bringing structure to ambiguity is a core part of the PM job. Before diving into new work, take a moment to map out what’s needed to go from problem to solution.
• Communicate clearly. Whether you’re using a formal framework or a simple checklist, write the plan down and share it with the right people. It might take five minutes to draft, but the payoff is significant.

Kidlin’s law

“If you write the problem down clearly, then the matter is half solved.”

I’m not sure where this one originates, but it’s one of my favourites.

How to apply it

• Define the problem. Writing a clear, succinct problem statement is one of the hardest - and most important - parts of product development. Get it right and you stop teams jumping to solutions too early.
• Validate understanding. Play the problem statement back to colleagues and customers. Is it specific? Is it actually the problem you’re trying to solve?
• Iterate with confidence. Once the problem is nailed down, start exploring solutions. Expect new insights to surface along the way - that’s the process working, not a sign you got it wrong.

Wilson’s law

“Wealth is not an immediate goal but a byproduct of prioritising knowledge and intelligence.”

Sounds counterintuitive at first, but there’s more to it than meets the eye.

How to apply it

• Focus on growth. Your value as a PM compounds with experience. Take on stretch challenges and you’ll open doors to new opportunities.
• Redefine wealth. It isn’t only about money. Roles that centre the product and the people can be deeply rewarding in their own right - and don’t forget to prioritise what really matters, like family and personal time.

Falkland’s law

“Think about the things that are absolutely necessary.”

A game-changer for prioritisation.

How to apply it

• Stay focused. Once you’ve identified the specific problem, resist the pull toward unrelated issues. Stay disciplined and solve the thing you set out to solve.