Choose One Useful Problem
Choose One Useful Problem Before You Decide What To Sell
Your experience becomes valuable when it helps make somebody else’s problem easier.
Start With Their Friction, Not Your Filing Cabinet Of Knowledge
The problem tells you which piece of your experience is worth bringing to the bench.
Choose One Useful Problem Small Enough To Solve Properly
You do not need to package your whole life. You need one useful result another person can recognise.Experienced people are almost invited to make a particular mistake when somebody tells them they could earn online from what they know. They sit down with a cup of tea, look back across forty or fifty years of work, family life, hobbies, mistakes, victories and assorted bits of practical wisdom, and immediately ask themselves the biggest question possible: “What could I sell from all that?” It sounds sensible. It is also enough to make a perfectly capable person shut the laptop again before the tea has gone cold. A lifetime is not a product brief. It is a warehouse. Somewhere inside may be dozens of useful little solutions, but standing at the entrance shouting “What shall I turn all this into?” is rather like walking into B&Q and asking which item in the entire building you ought to buy. We need a smaller question.That is why the mantra sitting above today’s work matters: Money Comes From Solving Problems For Other People. Notice what it does not say. It does not say money comes from having the longest CV, the biggest collection of certificates, the cleverest AI tool, or the most impressive pile of knowledge. Knowledge matters, of course, but knowledge sitting inside your head is inventory. It becomes useful when another person has a difficulty, and some part of what you know helps reduce it. Confusion becomes clearer. A mistake becomes easier to avoid. A job takes less time. A decision becomes safer. A beginner stops staring at six choices and finally knows which one to try first. That is where experience stops being history and starts becoming value.
The Problem Chooses Which Experience Comes Off The Shelf
Take an old heating engineer. Ask him what he knows, and you may get forty years of material before breakfast. Boilers. Pumps. Radiators. Controls. Water treatment. Pipe sizes. Fault finding. Quoting. Customers. Apprentices. Suppliers. Bad installations. Good installations. Jobs that should have taken two hours and somehow became a three-day siege involving a floorboard, a dog, and a compression fitting last seen rolling towards the skirting board. All of that experience is real. None of it, by itself, tells him what digital product to make. Then somebody asks, “Why is one radiator cold when all the others are hot?” Suddenly the warehouse becomes useful. The problem has walked in carrying a shopping list.
The engineer no longer needs to explain everything he knows about heating. He only needs the small part of that knowledge that helps somebody understand this particular problem. The useful answer is a simple sequence of checks. It may become a homeowner checklist explaining what they can safely notice before calling a professional. It may be a short guide to describing the symptoms clearly so an engineer arrives with better information.
The format can come later. The important shift is that the problem has chosen the relevant experience. Instead of squeezing forty years into a product, we pull one useful drawer open because somebody actually needs what is inside.
That is the first reason to Choose One Useful Problem. It gives your experience a job. Without the problem, you are selecting knowledge because it feels important to you. With the problem, you select knowledge because it helps produce a useful result for somebody else.
Take an old heating engineer. Ask him what he knows, and you may get forty years of material before breakfast. Boilers. Pumps. Radiators. Controls. Water treatment. Pipe sizes. Fault finding. Quoting. Customers. Apprentices. Suppliers. Bad installations. Good installations. Jobs that should have taken two hours and somehow became a three-day siege involving a floorboard, a dog, and a compression fitting last seen rolling towards the skirting board. All of that experience is real. None of it, by itself, tells him what digital product to make. Then somebody asks, “Why is one radiator cold when all the others are hot?” Suddenly the warehouse becomes useful. The problem has walked in carrying a shopping list.
The engineer no longer needs to explain everything he knows about heating. He only needs the small part of that knowledge that helps somebody understand this particular problem. The useful answer is a simple sequence of checks. It may become a homeowner checklist explaining what they can safely notice before calling a professional. It may be a short guide to describing the symptoms clearly so an engineer arrives with better information.
The format can come later. The important shift is that the problem has chosen the relevant experience. Instead of squeezing forty years into a product, we pull one useful drawer open because somebody actually needs what is inside.
That is the first reason to Choose One Useful Problem. It gives your experience a job. Without the problem, you are selecting knowledge because it feels important to you. With the problem, you select knowledge because it helps produce a useful result for somebody else.
