There are a couple chapters in there on the subject, but it's probably not the best book specifically for that subject. I haven't read it yet, but "Working Minds: A Practitioner's Guide to Cognitive Task Analysis " looks pretty good. One of the people behind the method wrote several books for a general audience and one of them, "The Power of Intuition" (not what it sounds like) has a few tips on how to learn from experts:
*Probe for specific incidents and stories. This is not the same thing as listening to war stories. It means selecting incidents where intuition was needed, and expertise was challenged, and then digging into the details.
*Ask about cues and patterns. Try to find out what the expert was noticing while making sense of the situation. You want to uncover types of discriminations that the expert has learned to make, types of patterns the expert has learned to recognize. The decision-making critique can suggest lines of questioning.
There's more, but I don't want to quote too much... One of the other tips is to ask how a novice would approach things vs how they would. He also recommends avoiding asking for general theories, the experts may not really be able to describe how/what they do without having a story to guide them.
The key difference between experts and beginners is the quality of their abstractions. Masters of a field mentally organize information in a way that's relevant to the tasks at hand. Amateurs may know as many facts and details as experts but group them in haphazard or irrelevant ways.
For example, experienced Bridge players group cards by suit, then number. They place the most importance on the face cards and work down. Bridge amateurs group solely by number and place equal importance on all numbers. Professional firemen group fires by how the fire was started and how fast it’s spreading-features they use to contain the fire. Novices group fires by brightness and color. Both have the same information, but the firemen hone in on the useful details faster.1
Learn abstractions from masters. If you ask a Software Architect which database technology you should use, circumstances will eventually change and you'll need to ask them again and pay them again. But if you ask the Architect to teach you how to choose a database then you can adapt to changing circumstances. Ideally you should emerge with a clear set of rules-something like a flow-chart for that decision. A good example is this article on whether you should use hadoop. Clear criteria let you make a high-quality decision by focusing on the relevant details.
After talking to the expert you can write up the flow-chart or criteria and send it to them to get their opinion. This ensures you understood what the expert was trying to say, and lets you get additional details they might add. Most importantly it gives them something valuable to share with people seeking similar advice, so you're able to add value to their lives as a thank you for their advice.
Caveats to this method: