Superposition
With a flourish and frenzy of activity, the cycle has completed itself and begun once more. This week, of course, was particularly hectic. On Tuesday, we in GROUPER were pleased to celebrate Liang’s successful defense of her dissertation (now to finish the writing!), and after a 2-hour lab meeting, I went home and got some pleasure reading in. Wednesday was a travel day, with challenges of unstable weather leading to one canceled flight, and ground stops due to ramp closures at both the start and finish of the second leg of the trip. Hours late, but with the air cooled from the rain, I finally finished the trip and got home for a good night’s sleep.
“Hold it. You were at home, then you got stuck during thunderstorms, and finished the trip, and went home? Did you not get to your destination? Was your trip canceled?”
Even as I write this entry, there is a type of surrealism about this week. I’m sitting in one of the chairs I have had for over five years, with Amber on my lap, looking at her cat tree and food and a bunch of other items I clearly recognize. The window still faces east, but the image is different: instead of an empty parking lot across the street, I see a tall tree and an office building. In other words, the shift has now occurred. Amber and I have moved to Washington, DC to start my position as a Jefferson Science Fellow. My first day is next Monday, and I have begun enjoying the exploration of the neighborhoods of McPherson Square and Thomas Circle, and picking up coffee and pastry and fruit at the White House Street Market.

Amber exploring the new window view
My world is changing significantly, and yet some things remain consistent. I am still an engineering faculty member, but I am thinking about a completely different set of issues this August compared to last August. Our lab meeting addressed a very interesting topic based on students’ recent experiences, and one that I will be considering very hard in the coming months. Academia, government, and industry are considered vastly different places, and representing wildly divergent career paths for those with PhDs. And yet, we’re taught (and have first hand experience) that a variety of people all craft their actions, decisions, and processing of information based on perceived risks, costs, and outcome benefits. There’s only one challenge. The benefits that drive most industry teams (profit—hey, I hear the new Aston Martins are really nice) don’t come into play at all for most academic or government folks, and the primary risk keeping academic folks up at night (someone already published my idea in that journal I love!) don’t seem to bother industry or government people much. A government employee may complain bitterly about the costs of having to work 5-10 hours of overtime one week; many academics and industry research folks take a 60-70 hour average work week as pretty much standard.
You may notice that the website (http://www.grouperlab.org) looks very different than a few months ago; that took us a while to work through. Elliott, our wonder-undergrad, did a pretty thorough redesign and architecture job, but what was more important was not just the scripting language or tab sequences. We went back to a very basic question: who comes to our lab’s website? Three different types of groups (yes, it’s that “use case” thing) want distinct types of information, at varying grain sizes. Even our own GROUPER alums represent different types of interaction profiles. We’ve got government employees seeing how our work can inform improvements for federal agencies. GROUPERs are also rising up the ranks in industry, and may be in a position to hire a new or recent grad (in this sense, GROUPER is definitely a distinct and valued brand). With the lab’s traditional gender mix (somewhere approaching 2/3 female), it’s not surprising that a number of alumnae list their primary function right now as “Mom”. I see no reason to hide that, or feel guilty or ashamed to highlight such life pathways. If everything is a system, and GROUPERs look at information everywhere, can’t those skills be applied to everything from medical information use for family members, to understanding the daily experiences of neurodiversity, to getting a front-row seat to the miracles of how humans develop broad processes of learning and skill development sets in ways that still challenge our most sophisticated machine learning algorithms.
Over the next few months, the GROUPER blog will be more active again, but it won’t be focusing as much just on our current lab research. We’re still researching, of course, but we have other stories to tell, and other forms of impact and effect to consider for how we get, share, and use the information we’ve been gathering and lessons we’ve been learning. Thanks for visiting us again after our quiet period. Hey, it gets busy learning how to be in multiple places at once.
September 5, 2016
Back to School
The Labor Day holiday weekend is drawing to a close, and I have finished up my second week of the Fellowship. Even though the start dates of the semester and my tenure here in DC were the same, I have gotten to notice how much the routines differ between the two environments. Unlike my academic routine that can adapt and adjust based on the day of the week and the differences between class and no-class, committee and research schedules, things feel distinct here. There is a bus I catch, most days, between 8:14 and 8:40. On Wednesdays, there will usually be lunch with the other Fellows. There are Monday and Thursday morning “huddle” meetings.
However, that is not what I notice the most from the past two weeks. I admit that I have developed a particular appreciation for my manager. Each day, there is a specific new thing I have to learn. How do I send a particular type of email? What is the formatting for this kind of documentation? Who do I contact for this activity? Of course, he’s seen this all before, but it’s my first time. And it’s not like I have had 3-4 weeks of easing into the situation. I’ve already worked on international memoranda, and meetings between embassy staff and local representatives, and sat in on planning discussions with the offices of some folks whose name might appear on someone’s bumper sticker. (But notably, the importance of the office is communicated by an acronym, or even a single letter; the people whose names are used are names I don’t recognize, and even those names go with acronyms.) The most appropriate phrase for this experience is one that I learned during my first few weeks as an undergrad at MIT: “Drinking from the firehose.”
In that environment, where I’m supposed to come up to speed quickly, it seems like a luxury to have someone check in with me as many as 3-5 times per day to help me with one task or another. In truth, some of the help sessions seem a bit remedial, teaching me things I do already know. But he doesn’t know that. And more importantly, I don’t always know when something I think I know how to do isn’t exactly how this organization does it. So, I find myself learning to be more patient when being taught, and listening all the way through the lesson. I even have a guiding document for goals to achieve over the next month or so—distinct from a to-do list of tasks, and an in-process list of assignments.
One of the things that surprises me most about this firehose experience is a new-found empathy and appreciation for the situations that confront new students in the lab. We’ve been working on SoS and PoSE conceptualizations of ICT use in the SHARK and DOLPHIN and PERCH* streams for years—why are you nodding blankly at me? Of course. I’ve been doing it for years. You just got here. I just used a bunch of acronyms—shorthand for me, incomprehensible jargon for you. Even when we get to time for a thesis outline, or a prelim draft, or a set of PhD defense slides, it does take some reminders to recognize that two dozen years of practice and 75 or more iterations don’t get transmitted easily to someone who is experiencing it all new and in an intense, nervous state.
I would like to hope that this lesson comes back to Purdue with me next Fall. For a new student, or new faculty member, each new item can be part of an overwhelming onslaught of novelty and complexity. Maybe it won’t stay that way for long, but it feels like that now. In the senior capstone design course I teach, I remind the students to take the time to capture those initial moments of novelty and first attempts at processing and decision making, because it will be really hard to recall those feelings (and assumptions, and senses of confusion) again later. I can tell them that, but it was a long time since I have felt that at the level I feel it now. It’s good to be reminded of what the first few, chaotic weeks of new experience feel like.
Photo of Little Kern Golden Trout by Middleton and Liitschwager (1988), hanging in the C Street entrance lobby of the National Academies.
*Acronym decluttering:
SoS: Systems-of-Systems. or a description of complex systems engineering settings where individual components of an overarching system represent complex systems in their own right (such as individual aircraft, with pilots and co-pilots, in the airspace over Washington, DC while Marine One is traveling across town).
PoSE: Perspectives on Systems Engineering. This is a course that I developed to teach about four distinct traditions of systems engineering, ranging across systems thinking, cybernetics, component-whole relations, and project management. Only in its second iteration as a hybrid distance / on-campus course, it is one of the most subscribed courses in Engineering Professional Education (and I’m not even teaching it this semester).
ICT: Information and Communications Technology. When I first started as a faculty member, most computers had line-by-line display screens in single colors of amber or green; email and word processors and bulletin board chat groups were the most sophisticated information exchange tools available. Even with all of the changes in capability, it’s still important to recognize that the point of these technologies were, and are, for humans to communicate.
SHARK, DOLPHIN, PERCH: These are designations of project areas within the research lab, referring to knowledge sharing architectures, information flow delays, and applications to healthcare delivery improvement, respectively. Check them out at https://engineering.purdue.edu/GrouperLab/streams/.