About two weeks ago, I returned after having honored a request from a Mayo researcher to give my poster presentation (a rational and extremely profitable OR scheduling and analysis system that I’ve actually used) at the Mayo Clinic’s 3rd Annual Healthcare Systems Engineering conference in Rochester Minnesota. While there, I had the pleasure of meeting a couple of people with whom I’d been talking shop on Yahoo’s hme group site, and met a couple of more bright people with whom I’d really like to chat again. Some of the lectures were good. Some not. I was amazed that things I had implemented 14 years ago have just begun to be topics of conversations on the theoretical level. Not sure what to think…except that it could explain why I’ve had so few comments on my blog posts.
As for my poster presentation…
It was a combination of 20+ years of clinical OR practice, economics/finance, risk management, and systems engineering. Yep, not a whole lot of people with enough background to appreciate it. Guess it’ll be another 14 years (or forever).
The best lecture, was on the last day by a fellow in charge of research (I believe) at Mayo. He said that it was a rare researcher, often a pariah, who draws from many different fields to create game changing improvements. He implied that you don’t learn that ability, you are born with it. Question: Is the person who recognizes talent like the person who has the talent for asking the right question? Both find the right answers.
I’ve been posting on this blog for 8 months, hoping for discussions and input. They have been few and far between. Lots of downloads which can be seen from my blog statistics, but not much given back to me through way of comments. I’ve always said that when one stops learning from a conversation, one should walk away.
One final note:
A degree in education gives you teaching principles for good teaching, it doesn’t mean you know the subject enough to teach it well (it’s better for the expert in a field to learn to teach). A degree in systems engineering teaches you principles, it doesn’t mean you know a different field well enough to effectively implement those principles (it’s better for the expert in a field to learn systems engineering).
1) Simulations are based on premises. Lots of premises. They are logic equations. If any of the premises are wrong, then the simulations are junk. You need to know the constraints on the premises to interpret the simulations. If you don’t intimately know the subject, you risk creating absurd or useless conclusions. How do you know junk when you see it? Because you’ve seen what happens in real life.
2) Teach everyone systems engineering. It’s like teaching people to read, but easier. The economic return will be worth it.
3) Teach everyone economics and finance. The economic return will be worth it.
4) Teach everyone risk management. The life (quality of life) you save may matter to you. And, the economic return will be worth it.
Take care. I’ve a sunset to watch…