Early Friday afternoon, I was riding back to the airport on the Metro Yellow Line in Washington, DC. Somewhere between L’Enfant Plaza and Crystal City stops, an older man looks at me and asks, “Are you a Boilermaker?”
“Yes, I’m on the faculty there.”
Much to my surprise, he reaches out to shake my hand. “I graduated from there… a long time ago.” He smiled as he got up, and then got off at his stop. I proceeded to look around at my bags, and noticed how he figured it out: my business card luggage tag was visible, with the Purdue University logo clearly showing. I was glad to know that seeing such a reference to his alma mater was a source of pleasure for this gentleman, and I do take those moments to reflect on the nature of the experience. As it turns out, it was the third interaction in less than 24 hours where someone sought me out for interaction due to the Purdue reference.
In the hotel lobby Thursday evening, I was introduced to the MS advisor of the IE Undergraduate Coordinator, Patrick Brunese. There was no mention of football, though Pat went to the University of Alabama. (You may recall that their football team won a particular football game earlier this week.) Instead, we talked about Pat’s interest in undergraduate IE education, and my attendance at the Industrial and Systems Engineering Research Conference. (I do intend to attend at least part of the conference, but I do have the challenge of also wanting to attend my daughter’s university graduation.) This morning, I had a discussion with a young faculty member who had heard of the interdisciplinary opportunities and sustained reputation of Purdue Engineering. When I mentioned the current effort of the College to increase the faculty size by 30% in the next five years, and the fact that she could find interested colleagues in Biomedical, Electrical, and Industrial Engineering (along with opportunities in the College of Science), she was hooked, and even grateful to me for taking the time to speak with her about it. I replied that I remember what it felt like to be “young, hungry, and grateful,” and wanted to provide whatever advice and mentorship I could.
I admit that when I was at Sandia National Laboratories in New Mexico earlier this week, there was some sports talk. But I was there for a formal talk and project work, including discussions regarding monitoring and procedure checking / validation tasks, and processes of distributed knowledge coordination and knowledge sharing.
These are examples of a more focused connection, and part of the level of Purdue recognition that focuses on our engineering reputation. There are over 400,000 Purdue alumni, 80,000 Engineering alumni, and over 8,000 IE alumni… pretty large numbers overall. But it’s not just number, or breadth of reach: we seem to be overrepresented in various circles (such as NASA or NSF, Sandia National Labs, or the “C-suites” of various companies) where I might interact. So, I continue a practice I learned long ago, and maintain the habits and rituals associated with Purdue representation (business cards, Block P pins, “Hail Purdue” mentions during formal presentations). We’re widely visible, and widely influential, as a university and engineering program. Why is this important for the GROUPER blog?
When we are doing our work, people notice, and take some notice of (and if they’re Purdue folks, maybe some pride in) it. They expect a Purdue person to be very good. As I say to the undergrads, the reputation that people know about and want to benefit from is borne on the shoulders of the history of past work and recognition. In my formal Sandia presentation, I talked about some of the prior GROUPER work in information alignment, root cause analysis, and event response. There were some very busy periods of note-taking, and challenging questions that not just addressed straightforward aspects of human error and performance shaping factors, but also more fundamental queries about the nature of complex system development, analysis, and evaluation. And of course, on every slide, there was the Purdue College of Engineering logo, the “Rethink IE” logo, and the GROUPER “data fish” logo.
Over the coming semester, we plan to increase our rate of posting—not just my various commentaries (once per month still seems the right rate for me), but to have other opportunities to highlight what is happening in the lab from a variety of sources. The goal is not actually just to broaden our discussion, but to address issues in a more focused way, from a variety of perspectives. Let’s see how that works.