How is an Expert Answer like an Oracle?

by Andi@Zeo on December 7, 2010

in Expert Answers,Sleep Science

In Ancient Greece, if you had a question, chances are you’d head out to an oracle and ask her.  While the answer might not always be what you had in mind, you always got one, and–in that weird twist of fate– it usually ended up being pretty revealing and relevant.

If anything, those who didn’t head the oracle’s advice–or didn’t ask any follow up questions to clear any confusion– often paid for it later (See: Oedipus; parents).

More Answers, Less Divination

If you think about it, the Expert Answers process is pretty similar.  Like a Greek hero on a quest to “know your sleep,” you send along a question and get an answer back from an expert.  As a result, you take action and share your findings to help others make better decisions.

Today, we’d like to further your journey by sharing one Zeo user’s question, as well as the Expert Answer from John Winkelman, MD, PhD, of Sleep HealthCenters in Brighton, MA.  Hopefully, it will help you navigate through untold hazards along the way, like having one too many drinks with Bacchus close to bedtime, or being lured by the sleep-in sirens of Sunday morning.

The Question:

BobfromQueensNY asks:

Has anyone had success with a product or remedy which “prevents” them from rolling onto their back?  Will inhibiting my movements be more disruptive than the breathing issues positional therapy is supposed to fix?

The Answer:

Not the question you had in mind?  Ask yours here! You can also consult our YouTube channel for additional Q&A.  More will be posted in the coming weeks; subscribe to stay tuned!

Andi (ZQ: 86) is the editor of Zeology. By tweet or by post, email or Expert Answer, she makes sure people get the information they need about sleep.
Bookmark and Share

Leave a Comment

You can use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Previous post:

Next post: