In many of my 30 years in academia, I loved helping graduate students, post-docs, and new faculty get started (or to get back on their feet after a fall) and moving in a confident direction. Even though I didn't know very much, I still had some perspective or experience that was useful. In the Land of the Blind, the one-eyed man is King.
One of purposes of this website is to pool together a lot of wisdom from a bunch of us one-eyed Kings and Queens so that that our graduate students and new faculty don't have to learn it by falling off of cliffs. This website tries to pull together helpful "tools and tips on how to graduate, get tenure, teach better, publish more, and have a super rewarding career."
The first step was to begin curating some of the more credible insights and experiences from all sorts of people in academia. This way, a person could get substantive advice instead of the top ten things that popped up on a Google search. Collecting these insights ongoing process and I love it when people share things (see the footer below for all of the types of examples of things you could share if you have them).
One comment I was given a while back was that it would be even better if I turn some of the insight pages into infographics. There are a few infographics that have been made that highlight some of the insights on a page and at least give a road map of where to click for more. One example is the infographic at the top of this post, which outlines the content on the >New Professors >Start Strong page.
Someone also suggested, "You should turn some of the infographics and blog posts into Youtube videos," so people don't have to read them. "I don't like to read," is probably something a person shouldn't put on their PhD application. Still, this is an important point to consider.
I'd love to know how this website and it's related content could be most useful to you. You can either email your insights at AcademicsOnly@yahoo.com or to my personal email. We can then schedule a call if that would work best for you.
There once was a legendary, larger-than-life professor. If Marvel’s 137th movie of this year is named UltraProf, it would be based on John Shank. He taught a dry subject (think Accounting), but his charisma and his orchestration of his class made each class session seem like 60-person David Mamet plays. Every class had passion, drama, and some surprising reveal at the end that people still talked about ten years later. Here’s a quote:
Although the opposite is true, some believed he was only about style. This is because he wore Brooks Brothers braces, walked with a MVP swagger, drove a Dartmouth green sports car, and he had a runway model wife who was like some VP of Finance somewhere. His office was professionally-decorated with French draperies, super-thick Dartmouth green carpeting, and a massive 18th century French desk which sat in the middle of the room so his desk chair could face the doorway. Even his two huge perfectly groomed dogs were effortlessly well-mannered. On Saturdays he’d come to work, and they’d sit on either side of his desk and face the door. They were like lions on either side of a throne, and he was like Odin . . . or John Wick. His dogs keep eternal vigilance. My dog wets on me and then licks my face.
This was 1992. Because he had about the highest MBA teacher ratings at Dartmouth's Tuck School and I had about the lowest ratings, he let me sit in on his classes so I could suck less . . . so I could learn better teaching strategies and classroom management skills. One Saturday during a Tuck alumni reunion, I stopped by his office and told him I had overheard some alumni who were still talking about what they had learned in a class they had taken with him 10 years earlier.
He looked up over the top of his half-glasses, and said, “That’s what they’re supposed to do. It means I’ve done my job.”
He said his goal isn’t to teach students to get a great first job (or to, analogously, get a high score on the GRE or MCAT), his goal is to teach them to succeed for wherever they will be in 10 or 20 years. Although he got outstanding teaching ratings, he brushed them off by saying that teacher ratings mainly measured the moment – they mainly measured the warm feelings a student had at the time. Ratings might capture style (which he was very good at), but they may not always measure long-term substance.
When the school year ends, lot of amazing teachers will take their course evaluation ratings and use them to improve their classes for next year. John’s view was that we need to also focus on the long-term impact of our courses.
I regret that I never had the presence of mind to ask him how he did it -- how he knew what long-term impact to aim at. Since he was on boards and did a lot of consulting with upper management, I suspect he taught his courses like he was teaching board members and upper management. That is, when he was teaching, he treated them like they were high level managers. That’s one way to do it.
A second way to try and teach for long-term impact might be to ask. After they graduate, it will be more apparent to them whether your course helped them live a better life (more useful, meaningful, successful, or whatever), and how your course might be improved. It’s easier to get this feedback than you might think. You’ve probably saved your class lists (somewhere) from 5 years ago. You might have their emails, or the alumni office will have both their emails and their snail mail addresses. You can simply ask them.
Ten or fifteen years after I left Dartmouth I was in Boston, and I rented a car to drive up to visit John. I wanted to thank him for being so generous, and I wanted to prove to myself that his office, desk, and dogs were as amazing as I remembered them. There was a different name on his door. I was too late. I later found out he had passed away in a car accident on March 30, 2006.
There are 100 things on your mental To-Do list. There are daily duties (like email and office time) and pre-scheduled stuff (like classes and committee meetings). But what still remains at the end of the day are the things that are easy to put off because they don’t have hard or immediate deadlines – things like writing an intro to a paper, submitting an IRB proposal, drafting a grant, completing some analysis tables, and so on. At the end of the year, having finished all of these might be what makes the difference between an exceptional year and another “OK” one.
But these projects are also the easiest things to put off or to only push ahead 1 inch each week. If you push 100 projects ahead 1 inch each week, you’ve made 100 inches of progress at the end of the week, but your desk is still full and you’re feeling frustratingly resigned to always be behind. This is an incremental approach.
A different approach would be to push a 50-inch project ahead until it is finished and falls off the desk; then you could push a 40-inch project ahead until it falls off; and then you can spend the last of your time and energy pushing a small 10-inch project off your desk. This is the “push-it-off-the-desk” approach.
Both approaches take 100-inches of work. However, the “push-it-off-the-desk” approach changes how you think and feel. You still have 97 things left to do, but you can see you made tangible progress. For about 12 years, I tried a number of different systems to do this – to finish up what was most important for the week. Each of them eventually ended up being too complicated or too constraining for me to stick with.
Eventually I stopped looking for a magic system. Instead, at the end of every week, I simply listed the projects or project pieces I was most grateful to have totally finished. Super simple. It kept me focused on finishing things, and it gave me a specific direction for next week (the next things to finish). It’s since evolved into something I call a “3-3-3 Weekly Recap.”
Here’s how a 3-3-3 Weekly Recap works. Every Friday I write down the 3 biggest things I finished that week (“Done”), the 3 things I want to finish next week (“Doing”), and 3 things I’m waiting for (“Waiting for”). This ends up being a record of what I did that week, a plan for what to focus on next week, and a reminder of what I need to follow up on. It helps keep me accountable to myself, and it keeps me focused on finishing 3 big things instead of 100 little things. Here’s an example of one that’s been scribbled in a notebook at the end of last week:
Even though you’d be writing this just for yourself, it might improve your game. It focuses you for the week, it gives you a plan for next week, and it prompts you to follow-up on things you kind of forgot you were waiting for.
Sometimes I do it in a notebook and sometimes I type it and send it to myself as an email. It doesn’t matter the form it’s in or if you ever look back at it (I don’t), it still works. I’ve shared this with people in academia, business, and government. Although it works for most people who try it, it works best for academics who manage their own time and for managers who are supervising others. They say it helps to keep the focus on moving forward instead of either simply drifting through the details of the day or being thrown off course by a new gust of wind.
If you work with PhD students or Postdocs, it could help them develop a “Finish it up” mentality, instead of a “Polish this for 3 years until it's perfect” mentality. It’s also useful as a starting point for 1-on-1 weekly meetings. If they get in the habit of emailing their 3-3-3 Recap to you each Friday, you can share any feedback and perhaps help speed up whatever it is they are waiting for. Especially if it’s something on your desk. Ouch.
Good luck in pushing 3 To-Dos off your desk and getting things done. I hope you find this helps.
A close friend of mine believes successful PhD students have three things in common: They're smart, they work hard, and they have good judgment. The secret sauce here is "good judgment." Although smarts and hard work are important, most PhD students would have never been admitted if they weren't already smart, hard workers.
But having good judgment is more elusive. It includes things like knowing what's "interesting" and what isn't, knowing what's worth worrying about (and what isn't), knowing what's important to prioritize, knowing how to solve a people problem, knowing whether to persist on a project or to move on, and so on.
But advising a PhD student to "Have great judgment" is like advising a football team to "Score the most points." It doesn't tell them how. You can't say "Have great judgment" and then say "Next question," "QED," or drop the mic and walk out.
Maybe there's two types of judgment -- technical judgments and nontechnical judgments.
For graduate students, building technical judgment is about learning the whys of research. One way to build better technical judgment is to boldly ask lots of "Why?" questions of your mentor, advisor, or of an older student: "Why did you send it that journal? Why didn't you use a different method? Why did you ask the research question that way?" Most of us shied away from asking technical judgment questions because we didn't want to be irritating or look like we didn't belong. Most professors I know actually like to answer these questions, and they love to see an engaged student step out of a silent huddle.
Developing good nontechnical judgment is trickier. Yet this is the critical judgment you need to troubleshoot how you can be a better teacher, or whether to choose the risky dissertation you want to do versus the safe dissertation your advisor wants. It involves figuring out how to deal with your off-the-chart stress level or whether you should take a job at a teaching college or go into industry. Our tendency as a graduate student is to get feedback from peers in our same year. A more effective one may be to get it from recent graduates or from professors who have seen cases like these and know how they worked out. You can even get nontechnical advice from professors you know in other departments. The best nontechnical dissertation advice I got was from a Medical School professor from my church. It was straightforward, unbiased, kind, and based on lots of students he had known.
As professors, we can help to build better technical judgment by encouraging questions about our research judgment calls, or we can give it as color commentary or as context when we discuss a research project. But again, helping students with nontechnical judgments is trickier. One way to do this is in the third person. This can be by discussing a problem that "their friend" is having or by discussing a relatable case study.
Here's one approach to building nontechnical judgment. I used to teach a PhD course where we'd meet in my home for a casual last class session. The first half of the session would be a discussion about graduate student success and the last half would be dinner. Each student had been asked to anonymously write down a dilemma that "one of their friends" was facing that was being a roadblock to their success. We'd mix these 9-10 dilemmas up, and we'd relax in the living room with a glass of wine and discuss them one at a time. For each one, we'd talk about similar experiences, options, solutions, and so forth. By dinner time, we had a more balanced perspective and some suggested next steps for many of the dilemmas.
Over the years, it seemed that about 70% of these dilemmas were about the same 7-8 issues. These were like the issues mentioned above -- "risky vs. safe dissertation," "stress level," "leave academia," and so on.
Here's a second approach to building nontechnical judgment. Given how similar these dilemmas were from year to year, I wrote up 1-page PhD student case studies that involved slightly fictionalized people who were facing these common problems. These case studies were in the syllabus for the course, and we'd take the first or last part of each class to talk about that week's case study. The common dilemmas faced in your field may be different, but the enthusiasm your students would have in discussing them would probably be the same.
Some people might be born with great judgment, but for the rest of us, it's a lot of trial and error and a lot of asking bold questions. If you're a graduate student, you've got a lot more license than you might think to learn from trial, error, and bold questions. If you're a professor, there's a lot we can do to help them.
Academics Only is a how-to community that helps us share our best practices as PhD students, new professors, and independent scholars.
Helpful tools and tips on how to graduate, get tenure, teach better, publish more, and have a super rewarding career.
Some Older Posts