Hi Emma (and Peter),
I get the idea of leading our technology explorations with pedagogy and in the big picture that's what we (hopefully) do. At a more practical level it's a messy process and quite iterative. We come to these explorations with a general sense of expections, hit some walls and also make some interesting discoveries that trigger new ideas. Over time these ideas and potentialities may fold back into revised pedagogies. One approach is to come up with some pedagogical challenges, what-if scenarios and play them out collectively on the tool(s) in front of us. (From what I've seen browsing around for ideas on how people are using Wave, it seems to be pretty good for managing complex, multi-level projects across an organization or work unit.) And then to debrief: e.g. What learning experiences or processes are enhanced by a tool like Wave? What is the "cost-benefit ratio" in time, effort and frustration versus some kind of productivity? Where would we recommend it and why? What type of support would it need?