Skip to main content

Popping Pills

Why is it that every time someone goes to the doctor they come back with drugs? I was talking to a friend the other day. She had just come back from a visit to the doctor. Her ailment was painful, but one that her body would naturally heal. Yet her doctor prescribed strong pain medication that made her unable to function effectively at work.

We seem to live in a society in which no one (even doctors) accepts that sometimes the most healthy response to an ailment is to let your body heal itself. Sure, when you invest the time and money, it's unsatisfying to discover that it was unnecessary to visit the doctor in the first place. But isn't letting your body heal itself, even after a visit to the doctor, sometimes the best course of action?

Comments

HealthReviews said…
Hi, my name is John Adams and I have suffered from severe acne. In fact, I also had problems with hair loss and weight loss and I lost all self confidence at some point and all my friends too. Now, a few months later, after discovering the Health Reviews website, I feel much much better. After reading their success stories and recommendations, their Top Health Reviews really helped me. Do you realize how good can this be? NO more problems. Finally I can got back my smile. That is the reason I am so happy now!
HealthReviews said…
Hi, my name is Kenny Williams and I have suffered from severe acne. In fact, I also had problems with hair loss and weight loss and I lost all self confidence at some point and all my friends too. Now, a few months later, after discovering the Health Reviews website, I feel much much better. After reading their success stories and recommendations, their Top Health Reviews really helped me. Do you realize how good can this be? NO more problems. Finally I can got back my smile. That is the reason I am so happy now!

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Use Case as a Black Box

Consider the following use case: Purchase Items Actor: Purchaser Precondition: Purchaser types at least thirty words per minute and has a web navigation efficiency rating of at least 40. Postcondition: For the average Purchaser acting at full efficiency, the number of seconds elapsed is no more than 30 + 20 * n, where n is the number of items purchased. The name of the use case represents a functional requirement. What does the product do, or enable the user to do? Purchase items. What are we to make of the preconditions and postconditions? What relationship do they have to the requirements for the product? Answer: the preconditions and postconditions are the nonfunctional requirements attached to the functional requirement . Another way of expressing the nonfunctional requirement would be as an attribute and associated constraint: Usability: For a Purchaser who types at least thirty words per minute and has a web navigation efficiency rating of at least 40, it shall take no

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the