grouperlab

Get, share, and use information well

Comings and Goings

It’s been highly eventful in GROUPER over the past month, since the beginning of Purdue’s Spring Break.  We’re really proud to announce that Natalie Benda, who had just submitted a blog entry to the site (“Bringing Sexy Back“), has won an NSF Graduate Research Fellowship. This is one of the most prestigious awards for graduate students, and highlights both her unique development and her engagement with society to influence the impact of research.  Congratulations, Natalie!  We certainly hope you’re back here soon!

 

Members of the lab defined Prof. Caldwell’s travel schedule as “March Madness,” which almost exactly matched the length (and complexity) of the NCAA Tournament.  On March 1, when the women’s Big Ten and other tournaments were starting up, BSC was in Washington, DC.  Since then, he visited Irvine, CA; London, UK (for the Global Grand Challenges Summit); San Diego, CA; and Shanghai, Nanjing, and Suzhou, China, before arriving in Seattle on April 8 — the day that Louisville won the men’s championship.  You may hear from BSC more soon.

 

In addition, Prof. Caldwell was escorted through much of his China visit by LIU Linyan, who was a visiting scholar to Purdue and GROUPER from the Nanjing University of Science and Technology.  Returning to Shanghai only hours after Prof. Caldwell’s arrival, Linyan (and her husband) were invaluable and  gracious in hosting and translating in settings as varied as Nanjing restaurants and Tongli historical museums.  We’ll miss Linyan, who also provided us with this message summarizing her experience:

 

It was a wonderful time since I became a member of GROUPER. Before I came to Purdue, I imaged the guys in the GROUPER, now I still can remember the day I came to this lab for the first time. Liang was the first person I met; she helped me with the registration. Then I met two guys just out of lab (I spent six month in the lab, studying, meeting , etc.), Jeremi and Omar. They were so kind and helped me a lot. In that week we had a GROUPER gather, I met all of the GROUPERs. We had Chinese food in a Chinese restaurant. I felt so warm.

During the six months I was in lab, we had GROUPER meeting nearly every two weeks in the lab, and we had personal meeting in Prof’s office. Every personal meeting, when discussed with Prof. Caldwell, you could find something new and should think more. Thank you, prof. Caldwell, the meeting, the books and paper you recommended helped me learning and getting new knowledge and enlarge my research field.

Time goes so quickly, when I recall the memory in GROUPER. I am in China now. I can remember everything so clearly like it happened yesterday. Omar took me to ITAP to modify my password and showed me how to use the scanner. In the noon, I was having lunch and listening to  Jake’s music; the pin (GROUPER pin), Marissa’s birthday, G4 in Natalie’s apartment, G4 in Prof. Caldwell’s house, and the pink poster we were drawing…. I will never forget the nice experience and I will treasure the pin (GROUPER pin) forever, because I am a member of GROUPER.

Thanks, GROUPERs. Prof. Caldwell, Marissa, Liang, Jeremi, Jake, Omar, Natalie, Kelly, Mina, Siobhan.

 

We’re all pulling for Siobhan as she recovers from her accident last month.  Things were a bit scary for a while, and remain tough.  As I mentioned to her and her family, Siobhan’s caught a crab affecting her race plan.  We’ll be getting back up to speed, one stroke at a time.  The most important thing is that such events help us to recognize that there are more important elements to our individual and shared existence than p-values and the number of citations in a given research paper.  We still emphasize the quality of our work, but even now, we can see direct impacts of what we do on individual quality of life issues–including those of our own members.

 

Congratulations also to Jake and Marie Viraldo, who have added to their team; Marie gave birth to Jacob Osborn last Thursday.  Once again, life sometimes trumps lab.  I may not want to always admit it, but having been a grad student with various intrusions of critical life events (birth of a child, life-threatening illness of a significant other, drastic shifts in research, unexpected opportunities and setbacks), I am sensitive and aware of how this is not just school, but one’s developing professional life.  For those of you just embarking on it, I am sympathetic.  (Not always soft or fuzzy, but sympathetic.)

Next time, perhaps a bit more about lab turnover… Jeremi finished her thesis, and Marissa will be finishing soon.   There’s always more to mention, because we’re never done.

 

 

Bringing Sexy Back (A Post from Natalie)

Instead of just hearing from me, we’re starting to add more posts from more members of the lab, and from more perspectives.  The first is from Natalie Benda, who is now a happy and proud GROUPER alumna.  Here’s an insight from her:

 

My journey to Purdue begins in Dubuque, IA, “the home of America’s river”. (Yes, that is what the sign says when you cross into my county). When I was younger, I always thought I would end up going into medicine. I come from a family where you were the odd one out if you did not work in the healthcare field. Knowledge of medicine was a pre-requisite for the majority of the conversations that when on at the “grown-ups” table when I was growing up. My parents even met in a hospital where they have worked for a combined total of about sixty years. So, naturally I chose to study engineering in college. That makes sense, right? No? Well, it will eventually.

 

In high school, when discussing my prospects for secondary education, many times I heard something along the lines of, “You’re good at math and science, you should be an engineer.” It must have stuck at some point, because I started to do my about it. I found the descriptions and coursework for computer, electrical, civil, mechanical and even biomedical engineering, were less than intriguing. I did not want to be in a lab or at a computer all day tinkering away with components.  In the words of my favorite mermaid, I wanted to be where the people were! So, when I came across material on industrial engineering, which emphasized the human aspect of engineering, it was a no-brainer.

 

With a newly found excitement for my presumed, I began the search for a school. My criteria – get out of Iowa but remain within driving distance, and find a large university with a strong reputation for industrial engineering. The three main schools I looked at were Northwestern, the University of Illinois at Urbana and Purdue. My junior year of high school, my mother and I trekked through a blizzard to visit Purdue on what was probably one of the coldest days of the year. I wish I could give a non-cliché account of all of the wonderful qualities that drew me to Purdue during this first visit, but I can’t. It just felt like the right fit, and I never looked back.

 

Fast-forward to my sophomore industrial engineering seminar. Although I was excited about getting out of freshman engineering classes and into my chosen discipline, I didn’t feel I had found that extra-curricular activity niche that many of my classmates had. Until one day, our seminar speaker gave a presentation regarding opportunities for industrial engineers in healthcare. Do you remember my rant about being destined to work in healthcare earlier? Is it starting to make a little more sense?

 

So, after their speech, I approached the speaker to learn more about how I could get involved in healthcare engineering at Purdue. It turned out she was a member of GROUPER. As many of you know, GROUPER works in many areas besides healthcare, however as Dr. C. says it is the new, sexy field for IE’s. This healthcare component was what initially drew me to the lab. What kept me there was breaking down the barriers of traditional engineering and finding ways to connect people and systems through communication. If you can’t tell by my quoting Disney movies and titling my entry after a Justin Timberlake song, I do not like to be subject to societal norms. And GROUPER is far from the norm.

 

In my two plus years as a GROUPER, I performed many tasks from managing the lab’s schedule to statistical analysis supporting Ph. D. research, and managed to stumble across some research of my own in the process. After organizing the lab’s document library, I found I had a special interest in chronic disease adherence. So, with the help of Dr. C. and the Medication Safety Network of Indiana, I designed a study that analyzed information flow between patients and pharmacists in pharmacy consultations for congestive heart failure medications. I could give you a dry, statistical run-down of the results, but for the sake of the blog I’ll get to the point: the results of the study evidenced the critical part that the pharmacist plays in patient medication safety by capturing potential adverse events the pharmacist was able to detect and prevent. The project is on hold for the moment, but now that we know these potential adverse events are there, couldn’t we find where they stem from? Could we in turn find the root cause of more adverse events that the pharmacist may not be able to prevent and discover ways to build a safer medication system?

 

Since my graduation from Purdue in December, I have begun a new job in Washington, D.C. as a research assistant for the National Center for Human Factors in Healthcare. In my first few weeks at NCHFH, I have worked on a number of projects that include validating the use of a serious game as an assessment tool (yes, I play video games at work), methods of reducing blood stream infections in dialysis patients and representing communication patterns through #socialnetwork mapping (okay, not that kind of social network, but you get my point).

 

The project that will be taking up the majority of my time is a classic information alignment problem. We will be working to help software vendors design electronic health record systems that facilitate providers’ ability to achieve “meaningful use” systems. The Office of the National Coordinator is strongly pushing the principles of user centered- and safety enhanced-design. To facilitate this, members of academia have developed a number of tools for the vendors to promote usability. As one could imagine, healthcare professionals, academic researchers and commercial software designers do not exactly speak the same language. Our goal is to help get to a place where these vastly different groups can understand one another and work towards the common goal of designing systems to deliver safer, more effective patient care. Thus far it is turning out to be a fascinating challenge, and my work with GROUPER has left me well prepared.

 

 

Updating Documentation

Now that there are a few new members of the lab, it’s time to pay attention once more to making explicit some of our expectations and shared experiences.  It’s interesting to watch, and to test, how stories or catch phrases easily become part of a local culture… only to be met by blank stares when a new person experiences it.

“What’s the best dissertation?”  “The one *you* can do in a reasonable amount of time.”

“Is that a title of a song on the album?”

” Delta Pain” (which is a title of a song on the album)

All of these represent elements of tacit knowledge, in that they are shared and understood by people who were in the lab when the event occurred, or maybe in an individual meeting with me, and have learned to experience and internalize the informal lessons of the lab in a particular way.  That’s great for an individual mentoring interaction, but not really good for organizing the productivity of getting a population of students to finish high quality thesis and dissertation documents.  Thus, we have to do some of these things with more explicit intent, and a more focused and determined documentation of elements of the lab’s culture.

Since the beginning of the Spring 2013 semester, we’ve been working on this in the creation and updating of four distinct documents:  A Master’s Thesis outline; a Dissertation prelim outline (oh, even that’s tacit, or at least implicit: the proposal document written in order to describe one’s dissertation so that one can be advanced to candidacy); a Doctoral Dissertation outline… and most recently, a semester-by-semester timeline for progress towards degree completion.  These seem to be very helpful for students, and help to summarize and integrate and transmit my experience in a fairly efficient way.  And why not?  I’ve supervised over 30 MS theses and 12 PhD dissertations, and sat on committees for another 25 or more graduate documents.  Most students, on the other hand, only do this once.  (I did have one of my students complete a second MS with me after finishing a first one elsewhere; no GROUPERs have ever tried to do multiple PhD dissertations.)  Rather than make everything trial and error, or suggest that there is no pattern that leads to increased probability of success, some people (among those are many engineers) would like to have a sense of the path, the rule, the “game plan” of how this graduate experience is supposed to play out.

Does this mean that there is a fixed and rigid procedure that everyone must follow?  Of course not, for several reasons.  One is that GROUPERs are different people, with different skills.  They don’t want to work in the same stream, or using the same data collection or analysis tools, or ask the same sorts of questions.  Fortunately, I’ve worked in a bunch of areas, so my tolerance for procedure variability is fairly high–I can advise a variety of dissertations, because I have done a variety of projects in different areas and methodologies.  (Some people may think of this concept as akin to Ashby’s discussion of “Requisite Variety”; no strict quantification here is implied.)  So, the level of consistency is not at the detailed level of “you must design a three-level, two-dimensional Analysis of Variance studying the influence of…” Everyone is expected to be able to answer, “Why would anyone want to read this thesis / dissertation?”  or “Why do we care about the question, or the work you did to answer it?”

It may also be relevant that one of the recent dissertations now making its way to conclusion is specifically addressing the question of procedure reliability and complexity.  A very often-repeated task, with few new or challenging elements, can have a standard procedure that is rarely, if ever, inappropriate for completing the task as designed.  If you’re developing a brand new task that has never been tried before, it’s highly unlikely that you can write a perfect procedure on exactly how to do it.  Most procedures are somewhere in between, even if we assume the procedure is always right.  At what level should we expect a new procedure to capture all of the experience that we gain in the development of a new system?

As time goes on, all of these documents will need to be updated–not necessarily because we were wrong, but because our knowledge evolves.  (OK, I was explicitly wrong on this item. I forgot to include a version of the well-known advice: “Tell them what you’re going to tell them.  Then tell them.  Then tell them what you told them.”  In other words, the last section of the introduction chapter should include an outline of the organization of the remainder of the thesis / dissertation.)  Even the working of the updating process is a helpful way of sharing the experiences and telling the stories of the lab.  And when we’re done, current and future generations of GROUPERs can know that I won’t get upset if they haven’t taken 15 credits or completed their plan of study or research proposal by the end of their first semester in the program.  Really.

 

I know, you’re wanting the links to these documents.  They’re still under construction.  Check back when they’re done and posted.

Broad, Deep and Wide

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.

rethinkIE_black

groupereng

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.

Inputs and Outputs

It’s not a great time to be a student–end of semester exams, project papers, and completing all of that work that seemed infinitely manageable back in October.  It’s not a great time to be a faculty member–thesis drafts to read, letters of recommendation and proofreading students’ research statements fall on top of grant proposal deadlines and all that grading.  So, it seems reasonable to be both a bit gentle, and a tad more explicit in clarifying the difference between “nice to have” and “required”.  Some extra data, or a couple more days to work on that draft of the term paper is nice to have.  What’s a challenge at the end of November is recognizing what is required, and how to get to all that is necessary in the too-little time available.

 

Most academics want to get grants to do their research.  That’s not an easy process, and the competition grows in complexity and sources of frustration.  Whether it be a development contract from a company, or a research grant from a governmental funding agency, the folks reading the proposal want to know “Who Cares” and “Why Should I Spend the Time to Read This?”  They don’t know about what you meant to say, and they probably aren’t in your field.  It’s your responsibility to communicate what’s so cool and new and shiny to you, to other people who may not even care until you show them why it’s valuable and critical and efficient to help them in what they do every day.  A challenge at the best of times; a burden worthy of Atlas if you’re trying to write five proposals in two weeks to different types of organizations.  Faculty usually talk about funding as an input measure (“Congratulations! You got the grant!  Now what are you going to publish, which students will graduate, and what new things will come out of that lab that other people also want to use?”) .  It’s also an output measure, of course: “I wrote nine proposals, and two of them got funded!  I’m a star!”  (Actually, that is kind of true.  Funding rates for proposals from the most competitive agencies are often described as being in the 6-12% range.  Hitting on 22% of your proposals would be good.  Like Ted Williams in baseball, hitting on 40% of your tries would make you a Hall-of-Famer.)  Either way, there is a big lag between the pain of creation and the success of the award.  (Maybe just long enough to forget how much it hurts.)

 

But faculty have another set of inputs and outputs: their students.   There was a recent article in the Chronicle of Higher Education on the evolution from being your professor’s advisee to being his or her peer.  I was able to send this to the current GROUPERs, and even to my five most recent PhDs.   I’ve even gotten a reply already–the start of a thread.  This helps me feel good about the students as outputs–but I can still gloss over the importance of inputs.  Not just the students as inputs (you need good material), but what we can do to get the student where they want to go.

 

Unfortunately, Natalie is leaving us in a few weeks: she’s graduating with her BS.  Although an undergrad, she’s been one of the more experienced members of the lab for the past two years, helping to keep us aligned and sequenced (she’s been the project management software goddess).  Student as input, student as person needing inputs, student as providing inputs… (that’s also modeling project we’re working on as well, within the SMELT stream).  The greatest reward though, was the news we’ve gotten over the past week or so.  At the HFES Annual Meeting back in October, I met a researcher from an organization doing research on human factors in healthcare.  Have I got a student for you, I said.  She’s already developed her own research study.  She is fantastic as part of my lab.  She wants to work in this area.  And now, Natalie gets to announce that she got a job!  And then she said that being part of GROUPER was a large part of how that happened… as well as my work that went into it.

GROUPER is an input into the students’ lives and professional evolution?  What I’m doing is a transformation that gives someone a better outcome, a stronger trajectory, a more favorable future?  OK, maybe that is worth it, and a great reward that turns into inputs for the next cycle.  That, and a few extra hours’ sleep.  And maybe some visits by the proposal writing muse.

 

Lab (Cleaning) Party

I find the weeks around the September Equinox fascinating and especially important for me.  At this time of year, change is evident, and rapid, and significant.  The weather shifts from sultry, to sunny, to stormy, and maybe back again a few more times.  The academic semester is now in full intensity: the students are busy with multiple assignments submitted, which of course affects my workload as I try to grade them.  And of course, my birthday is a personal milestone event, with greetings and connections to family and friends.

This year was an especially important and life-defining birthday… no, wait.  The calendar marks a date.  But, my sense of where I am—in my career, in the life of the lab, about my own experience—is defined more by how I feel in the morning during tai chi and while eating breakfast than by a focus on how many revolutions around the Sun the Earth has managed since I first appeared.  So, last week’s big lab event to mark my birthday?  A party.  A lab party.  Well, actually, it was a lab cleaning party.  Boxes of unnecessary and outdated materials were sorted and removed.  Non-functional computers were disconnected.  Tables were rearranged into a new and more functional configuration.  This was a very helpful meeting.

Hold on.  Are you telling me that GROUPER is just about room arrangements?  Of course not.  There are five research projects going on right now.  There’s two PERCH projects (pharmacist-based information flow for congestive heart failure patient prescription filling; patient information flow and expertise using electronic medical records); a SMELT project (alignment of learning outcomes for first- and second-year engineering courses); and a new DOPHIN / CORAL project looking at information presentation to control room operators.   The fifth project used to be looking at information concentrations and dynamics of information- and task-based elements of emergency responder situation awareness and event response.  This could be a great idea for simulation-based human factors engineering.  Except for a few tiny details.  It’s a non-equilibrium decision making and performance task.  With multiple scales of information dynamics.  And the requirements for several years of data that aren’t available.  Although there are examples of dissertations that had unexpected complexity or challenge, I believe it is one of the advisor’s responsibilities not to allow (or worse yet, intentionally create) a situation where the student finds themselves caught in a bad project.  As the Zheng Lab students say, “I want to graduate in less than 5 years… I want a job and I want to be free.”  So, let’s make an environment that helps that happen.  (And let’s shift an impossible dissertation to just a challenging and interesting and valuable one.)

Somewhere along the way, I came to believe that a university should be about people working together to explore what has not yet been seen, and translate it across disciplines and times for others to understand.  An advanced degree is not just about working on a more obscure detail for some research area that no one else cared to study.  It’s not about following exactly the same program areas as everyone else, because that’s the “hot funding area” or because “everyone in the field is working that problem”.  What do we really mean when we say that we want a PhD?  The humor, but too often the true experience, suggests that it’s just about “Piled Higher and Deeper”.  (You’ll have to wait for us to talk more about how GROUPERs learn from robots on Mars.)  But Ph.D.  means Doctor of Philosophy.  One who teaches how to think, and think different.

But, back to the birthday, and the lab party.  This group is coming together.  The lab looks and feels better, more ready for the year’s work.  There is lots to do, and I am thrilled to recognize that I feel more engaged and enthused to do it.  The trajectory of one’s life and career is often described in a particular way, and the most recent birthday is often associated with dirges and black crepe and funereal humor about negative second derivatives regarding hills.  (Okay, they don’t really say it that way.)  However, the fun of the lab party is that it was one of new preparation.  New opportunity.  We’re just getting started.  Chronological age aside, the past two weeks have been about a joyous recognition.  Since I’ve now spent a dozen years in Indiana (another recent milestone), it’s easy for me to hear John Mellencamp songs on the radio and in my days.  But one is certainly appropriate here: Your Life is Now

It is your time here to do what you will do…

In this undiscovered moment,

Lift your head up above the crowd.

We could shake these worlds,

If you would only show us how…

Your life is now.

Thanks for the cake, folks.  The frosting was delicious.

Summer Drives

Welcome back.

I don’t know if I have gotten used to it yet, even as I begin my 12th year on the Purdue campus.  Tomorrow is August 31, and we’re now finishing our second week of classes.  (My daughter, who is at the University of Wisconsin (where I was faculty before here), starts a week from today.  Just that difference in mentality regarding when the “Fall” semester starts seems to have a significant effect on cognitive, emotional, and social patterns of awareness and activity.  (In fact, this idea was one of the contributing elements at the foundation of our research on information alignment and information clutch factors affecting task coordination in organizations.)  The ramp up of demand may or may not match your increase in readiness for that demand, and if you’re not careful, that could cause falling into a task deficit “hole” that is extremely hard to climb out of later in the busy semester.  (Ah, yes, that would be my undergraduate controls course, talking about feedback systems and response dynamics to input functions.)

Every once in a while, my mind takes one of these enjoyable side trips, and it can lead to interesting research insights.  Members of the lab sometimes go along with me on these trips, which often involve discussions of mathematical definitions and relationships, as well as empirical or analytical planning and research designs.  For instance… let’s talk about what dispersion means, and how it applies to production systems.  Hey, does digital signal processing help us manipulate the timing and synchronization of entire files, rather than simple waveforms?  Can we link student advising questions to convolution functions that describe knowledge transfer?

A real advantage of the beginning of this academic year is that most of GROUPER is back intact.  Almost everyone was gone at some point: Natalie was in Germany (at Alcoa); Omar was in Egypt (finishing a Master’s at Alexandria and getting married); Jeremi was in Washington (at NSF); Kelly was in Cincinnati (at P&G) Jake was in San Diego (at SPAWAR); Liang even got to return to Xi’an China to see her family.  We’ve graduated two students since the Spring Equinox. Jeff Onken defended his dissertation (although he was already working at Northrup Grumman) and completed a final presentation to his committee.  Melvis Chafac completed her Hong Kong-based Master’s research writeups, and was off to MIT a few weeks ago after campus and conference presentations.   Now, we’re back in lab meetings, telling stories and sharing / renewing the culture of the lab.  (“Good idea / Bad idea” seems to be the best description of these culture shaping stories.)  Even though there’s no one new, the reasons for the stories still exist.

Things get much busier after this week.  I’ve taken on new responsibilities, both on campus and in the larger community.  (Yes, we’ll tell you; however, I’d like to wait for the official updates.)  I think I won’t be going much of anywhere this weekend—football season starts, but we’re also awaiting the arrival of a guest named Isaac.  Not great weather for a drive… unless of course you’re talking about a series of running plays from the Purdue offense.

Summertime, May 2012

At Purdue, summer starts in May.  Classes end in April; grades were due on May 8.  Jeff (our stalwart STINGRAY student) deposited his PhD dissertation, and I got to “hood” him at Commencement on May 13.   This past week, I presented some of our work at the Industrial and Systems Engineering Research Conference.  Oh, and I also got to see the SpaceX Falcon9 / Dragon launch.  Pretty cool.  

 

I’ve been accused of working too hard, and not having the ability to have vacations.  Well, that’s probably true.  (I did spend a few hours by the pool in Orlando after the launch and my conference presentations.)  So, what to do?

 

I’m going out of the country tomorrow.  When I get back, it’s visiting my daughter for her birthday, and taking some time off the grid.  Most of the lab is gone for the summer.  It’s quiet now in GROUPER.  We’ll get back to you in August.

Asking the Right Questions

At this point in the semester, it’s easy to look at the task load (student project presentations held at the customers’ locations; document deposits and graduation; assignment and course grading) and ask, “Why did I do this to myself?”  Of course, that’s not really the right question to ask.  Every semester has some elements like this, and no matter how one schedules one’s own work, there are always potential surprises and overloads—because it’s a busy time for everyone else.  So, let me not ask that question.

 

One of the things I did to myself was in the teaching realm.  For the senior design projects, teams are expected to make final presentations of their work.  In contrast to other faculty who schedule the presentations on campus as an academic activity, I encouraged the teams to schedule the presentations with the customer, at the customer’s site.  With 19 teams, this means a lot of presentations outside of greater Lafayette, and several cases of multiple teams presenting at the same time in different cities.  (If you know how to be in Hammond, Kokomo, and Lebanon at the same time, or get from one to the other in 15 minutes or less, please let me know.)  Today was the first day of presentations, and a pleasant experience occurred.  After two different team presentations (in different towns, for customers in different industries), spirited discussions ensued—not just between the team and the customer, but between different members of the customer group who represented different divisions, units, or work groups.   You mean we haven’t fixed that problem yet?  Can we get more communication between those groups?  When can we implement that new device technology?  Does changing or rerouting that form work to meet your information needs?  Of course, it’s one thing for me to say that I have a research interest and published papers on information alignment in production systems and an information clutch to improve knowledge sharing.  It’s quite different to have the project customers (doctors, nurses, purchasing managers, financial officers) to tie these concepts directly to their ongoing operations and what they should have done, or can do, about their organization.  Reading my paper isn’t necessarily what they should be doing.  Interacting with the students was what they should be doing.  The organizations learn.  The students learn.  If I pay attention and listen well, I learn what will be the next research questions to ask and projects to study—not from literature reviews, but from captured practice and expressed pain and demonstrated knowledge gaps. 

 

Members of the GROUPER Lab also talked about asking the right questions yesterday, but in a much less structured setting—our end-of-semester social event and potluck.  (These events are now known as G4, or “GROUPER group get-together gathering”.  No, I did not make that up.)  We were treated to a number of surprises and unexpected treats, about the lives of GROUPERs outside of, or prior to, their life in the lab.  Jake casually described the renovations to his house—not renovations they “had done,” but he and his wife had done them themselves.  Yeah, we built the bunk beds.  We just got this new counter top.  Having the heated floor on in the morning is really pleasant in the winter.  Yeah, she painted those portraits.  Oh, yeah, I was in the marching band.  (This is at a Big Ten university, where, of course, marching band is pretty serious stuff.)   

 

That was only part of the evening’s lesson.  Jeremi had been a cheerleader, and demonstrated a few of her favorites.  Omar talked about daily life, social media, and 10 year old checkpoint monitors in Alexandria, Egypt during Arab Spring, and the various people he knows who are helping to shape the transitions there.  In comparison to the various large families experienced by all of the other members of the lab, Liang told stories about “one-child” childhood, in Xi’an – oh yeah, where the terra cotta soldiers are.  Of course, I didn’t know about most of this.  Why not?  “You didn’t ask.”  Well, no, I guess I didn’t.  Lab meetings are for project schedules for upcoming research projects, and task timelines for conference and journal papers, and professional development advising regarding jobs and networking and identifying research topics.  As the students said last night, the G4s are good for a different type of learning, and a different kind of exploration.  It seems clear that the lab does something different during G4, and something that, although it doesn’t directly advance the professional activity or research impact factor of GROUPER, helps improve the coherence and mutual respect and awareness of what the members of the lab can do.  Laughter and food helps, too. 

 

In how many countries could we have G4 parties, now and the next 10 years?  (I guess that makes them G5: Global GROUPER Group Get-together Gatherings.)  Where will GROUPERs be, and what will they be able to influence and affect, over that time?  Those sound like great questions to consider… experientially, and not just academically.

Expert Blind Spot, Distributed Expertise, and Knowledge Sharing

Oftentimes the term “expert blind spot” is used to describe instances in which an expert’s understanding of a content area overshadows their knowledge of how to teach it. This isn’t exactly how it is being used in this context, but its usage is not much of a stretch here. Jeremi asked Dr. Caldwell, “How do you advise such a dynamic lab of students who all have varied interests and are at different stages in their programs? How do you do it?” Although a few ideas were faintly mentioned, what became apparent was that Dr. Caldwell was unaware of elements of his style that made him an expert-advisor. Jeremi didn’t stop at that answer; she probed other GROUPERs and found that the expertise on his advising style was distributed among his advisees. Now that we have begun to characterize it, we thought we would do some knowledge sharing. Our hope is that this information is not only beneficial to Dr. Caldwell, but also to others interested in advising (or mentoring, in general), and to those wondering what it’s like to have Dr. Caldwell as an advisor.

 

 

Kelly:

As an undergraduate coming into a graduate’s domain, the GROUPER lab, I felt very intimidated and insecure. Would I meet their expectations? Would they tell me I was the worst undergrad on the planet? All these worries and more swarmed my head, but that’s where Dr. Caldwell calmed my nerves. He assured me that I would fit right in and they wouldn’t expect me to perform at a graduate level. I could move at a pace that I wanted and was not going to be pressured to meet this deadline or that. That is what I love about being an undergrad advised by Dr. Caldwell: he is realistic about my abilities. Other advisers could have looked at me my first week being in the lab and said “You have to write this paper by this date and you better know how to write a fantastic research paper”. But, Dr. Caldwell had realistic expectations and in our 1-on-1 meetings, he has always been concerned about me, rather than a paper deadline. He has let me know that I am not required to find a topic right away, and he knows that I am busy with my coursework. He has guided me to finding a topic and was genuinely interested in what I wanted to get out of this experience and what I was going to enjoy writing about. There shouldn’t be pressure being an undergrad in a graduate lab, and Dr. Caldwell has definitely kept it that way. In the group setting, being in this research lab is my first group experience of the sort. I had been on teams before for projects, but this is by far the most positive one. Although we do get off task sometimes, the lab is very goal-oriented, and when we do get off task, it usually has a life lesson or reason attached to it. Everyone in the lab looks out for one another; there is no competition for papers, topics, or Dr. Caldwell’s attention. He treats everyone with the same level of respect and attentiveness and has never made the lab feel competitive in any nature. It is a very supportive environment and Dr. Caldwell, inside and outside the lab, is an extremely supportive adviser, especially to undergraduates.

 

 

MAV:

As explained in previous GROUPER blog entries and from browsing the GROUPER website, there are many ways in which Dr. Caldwell distinguishes the GROUPER lab from others. These include lab meetings that are filled with humor and light-hearted sarcasm and outside activities such as the G4s. Although Dr. Caldwell does a great job of advising his lab a whole, he does a superb job of advising his students as individuals. Let’s look at an example: me. Entering into a doctoral program, I knew that I had a specific style of advising that would work for me; any deviation from this style would be disastrous. Dr. Caldwell always e-mails me in a timely manner, follows through on tasks, allows for task-oriented discussions (as I do better with a list of tasks and deadlines instead of being let loose in the “forest”), and meets with me regularly. However, even though I believed that there were a certain set of standards I needed for myself, Dr. Caldwell added another guideline I wasn’t aware I needed in order to be a successful student: it’s ok for me to take a break, to step away from research, especially when I’m causing myself to become overly-stressed (and usually it’s for no apparent reason other than just me being a perfectionist). It almost seems to be counter-intuitive: why would my advisor ever want me to stop working on my research, even for a day, let alone several days? Causing me to spiral downwards on my research (again, for no good reason) would not do me any good and, thus, cause me to become less productive and maybe even have a grudge against my research. Ultimately, Dr. Caldwell wants all of his students to be successful (hence, the large list of GROUPER alumni). Dr. Caldwell has been advising students for years and he probably knows what’s best for me, even if I don’t know it myself. Having Dr. Caldwell as an advisor lets me know that both my research interests and personal sanity are being monitored for their well-being.

 

 

Omar:

As a new student, I was not sure on what topic to start working on for my doctoral thesis.  This was making me so nervous, especially since every time I pick a topic, I have a tendency to keep changing my mind.  I am amazed at how Dr Caldwell reacts to my changes.  A typical adviser would not like his student to discuss with him a certain idea over and over then simply drop it for another idea that looks more appealing to the student.  However, my professor always stresses how important it is to pick a topic that fits my interests and what I want to do in the future.  He discusses with me my future plans to be able to help decide what to do with my Ph.D. studies. 

The way he reacted to my hesitation over the 1st few months relieved all pressure that I might have had.  It added a lot to my self confidence and kept me focused to do more reading and exploring more ideas in order to be able to pick the research that suits me the best.  It is great if a student knows exactly what he wants to work on from day one.  But, trying to quickly settle is not the right thing to do. And that’s what I appreciate about my experience with Dr Caldwell on how he managed to help through the journey of picking the best fit for me.

Another very successful approach Dr Caldwell sticks to, that in my opinion helps all students in the lab, is weekly lab meeting.  In that meeting, I get a chance as well as my lab mates, to talk about my ideas whether I am still in beginning, middle or finalizing the research.  Feedback from academic students of the same interest with presence of a leading faculty member in the domain is found to be very helpful. 

 

 

Jeremi:

Mentoring and success drive Dr. Caldwell’s advising style. Dr. Caldwell places a very high premium on mentoring: he gives his time to meet with us individually and collectively on a weekly basis (with the exception of when he’s traveling, of course). Any outsider peeking into his life as a professor would say that hosting one-on-one meetings with five (or more) students every week –in addition to holding office hours for your class– is pretty remarkable! It is through our 1-1 meetings that it becomes apparent how deeply interested Dr. Caldwell is in exploring our ideas and discovering what topics interest us. In fact, he is beyond interested: he gets excited about exploring new ideas with us! Unbeknownst to us, somehow in the midst what seems like a pure exploration of ideas, he gathers information about what we are passionate about and our career goals. With these two pieces of information, he helps us settle on topics with which we will be satisfied. With this approach, his students excel. As we succeed, he succeeds.

His conception of mentoring extends to peer mentoring. Weekly lab meetings are designed in a way that we share updates on our respective projects; and through this exchange, we learn from one another about the milestones ahead. At times, Dr. Caldwell asks probing questions (that he already knows the answer to) such that others may benefit. Additionally, this informal exchange inevitably facilitates the development of our “elevator pitch” such that when we are away from the lab, we can respond succinctly and intelligently to questions people ask about what research we are working on. This is a specific example of how he transforms, what seems like, casual interactions into teachable moments.

I will quickly add a few others things that characterize his style. One, he is extremely well-read and as a result, is able to make fascinating connections because ideas that may seem unrelated on the surface. In Dr. C’s words, he’s able to “scan and connect.” Continuing with this idea, he also does what we call “management by wandering” which means emailing articles he comes across that may be interesting or relevant for us. Secondly, in meetings that involve committee members, he plays an interesting role, balancing between being coach and gatekeeper (through the milestone). At times, he uses an adaptation of the Socratic approach to get the student to share information/ explanations that he thinks would be helpful for the rest of the committee or to re-phrase committee members’ questions in a way that clarifies the question other members are asking. Third, he includes us in the strategic elements of his research enterprise. For example, our input is solicited when brainstorming ideas about the immediate goals and long-term visions for GROUPER, as well as some of the characteristics prospective GROUPERs should posses. Lastly, he’s real! He has a family, a home he invites us to once per semester, enjoys playing video games from time to time, thinks about next steps in his career… you know… facets of life that make people “real”- Dr. Caldwell has them. And this is not to say that other advisors don’t, but he’s personable enough to share elements of personality with us. As a student aspiring to make my mark on the world someday, I sometimes wonder about the possibility of work consuming life. It’s nice to see a model that demonstrates that you can have life outside of work, and those two ideas do not have to be in opposition to one another. Of course, Dr. Caldwell’s model is not perfect, but at least it shows that it is possible.