Working With Me

Some thoughts on research, mentoring, and working together

This page is intended to help students and postdocs understand how I approach research, what I value, and what it is like to work with me.

I am still relatively new to being a PI and mentor, and I am very much learning as I go. I do not claim to have figured out the best way to mentor or manage a research group. These are simply my current thoughts, preferences, and expectations, shaped by my experiences as a student, researcher, and now a PI. They will likely evolve as I gain more experience, and I welcome feedback along the way.

On this page

Values and Principles

  • Be curious about the science, not just the methods. I enjoy working with people who genuinely want to understand how the Earth works. Learning a new technique, developing an algorithm, or publishing a paper can all be rewarding, but I do not think any of these should be the ultimate goal. The scientific questions should come first.

  • Being busy is not the same as making progress. I value thoughtful, systematic problem-solving over simply trying lots of things. When something does not work, take time to identify the possible root causes. Develop hypotheses and design tests that can help distinguish among them. Trying different approaches without understanding why is often an inefficient use of time.

  • Be careful with implementation. Details matter. Small mistakes in code, data processing, or underlying assumptions can lead to incorrect scientific conclusions. Check intermediate results, validate your implementation, and be skeptical of results that seem too good to be true.

  • Have a plan, but be flexible. Research rarely goes exactly as planned. I do not expect you to predict every difficulty or meet every original timeline. However, I do expect you to have a clear idea of what you are trying to accomplish, what the next steps are, and when we should revisit the plan.

  • An unsuccessful experiment is not necessarily wasted effort. If a carefully designed test disproves our hypothesis or reveals something unexpected, we have learned something valuable. What concerns me is spending time on analyses that neither answer a question nor help us understand the problem.

  • Respect each other’s time. We all have competing responsibilities. Being prepared, following through on commitments, and communicating changes are basic ways of showing respect.

Communication

Give me good context

When we discuss a project, I find it especially helpful if you can clearly explain:

  1. What we discussed and agreed on last time.
  2. What you planned to do, and what you have actually done since then.
  3. What you learned, including unexpected results.
  4. What problems you encountered and what you have tried to resolve them.
  5. What you propose doing next, and where you would like my input.

You do not need to prepare an elaborate presentation every time. A few well-organized figures, notes, or a concise summary can be sufficient.

Asking for help

Please do not feel that you need to have everything figured out before reaching out. I would much rather know that you are stuck than have you spend weeks going in circles. However, when bringing me a technical or scientific problem, I appreciate knowing what you think the issue might be and what you have already tried.

Sometimes I will give you a direct suggestion. Other times, I may ask more questions or suggest that you investigate further. My goal is to help you develop your own problem-solving skills, not simply provide instructions.

What Does Not Work Well for Me

I think it is useful to be transparent about behaviors that I find counterproductive.

  • Lack of communication. I find it frustrating when a problem has been developing for a long time but has not been brought up, especially when an earlier conversation could have helped.

  • Activity without direction. Trying many things without a clear question or hypothesis can create the appearance of productivity without meaningful progress. I would rather see fewer, well-designed tests that teach us something.

  • Careless implementation. I expect people to take care with their analysis and check their work. We all make mistakes, myself included, but systematic validation and attention to detail are essential.

  • Lack of follow-through. If we agree on a plan or a timeline, I expect you to make a reasonable effort to follow it. If circumstances change, that is fine, but please communicate rather than letting commitments quietly disappear.

  • Focusing only on publication or technical accomplishments. Publications are important for building a scientific career, but I find research much more rewarding when it is driven by genuine curiosity and the desire to understand something new.

Things I Am Working On

I am also learning how to be a better mentor, collaborator, and PI.

  • Balancing guidance with independence. I often have ideas about where a project should go, and I can get quite involved in scientific discussions. I want to be helpful without taking away your intellectual ownership of the work.

  • Being patient with research progress. I like seeing projects move forward and can sometimes become impatient when progress is slow. I am working on distinguishing between delays that reflect genuine scientific challenges and those that could be addressed with better planning or communication.

  • Communicating expectations clearly. What seems obvious to me may not be obvious to someone else. I want to become better at making priorities, expectations, and feedback explicit.

  • Making time for the bigger picture. It is easy to get caught up in technical details and immediate deadlines. I want to make sure we also spend time discussing larger scientific questions, new ideas, and long-term goals.

I welcome constructive feedback about how I can improve, too.

This is a living document. My perspectives will continue to evolve, and I welcome conversations about any of the ideas here.