thoughts on cisco

as much as possible, the activities should be exactly what they're required to do on the job. e.g. use the same tools, get calls from ersatz customers, emails as they're about to leave work.

games are cool but in real life, a large part of the challenge is figuring out what the problem is. hence, these exercises/experiences will be more like a business-school case, one that concludes, "What should Charlie do?"

is "mastery" the goal? or balance? how about optimal performance?

life isn't synchopated, nor should our program be. verisimilitude requires heavy periods and slow periods.