In the world of STEM research, postdocs and faculty spend years mastering the architecture of experiments and honing their skills in their area of expertise. I have watched people obsess over variables, refine methodologies, and ensure that every data point is accounted for. There is an art to really great science. The piece that can be left out, and that is talked about far less, is how to design and care for the relationships as one navigates their postdoc career into new faculty roles and the many roles one might hold in multiple scientific collaborations.
I recently worked with a brilliant new faculty member who found herself in a position many of us know well: she was moving from the periphery of a large, complex collaboration serving as someone who was more temporary into a central leadership role where she would be more permanently a part of this project. On one hand she already knew the group and on the other, the group had a specific vision of her that she’s looking to update to the new scenario at hand.
She was navigating the delicate tension of what I call “delayed status update” that occurs when you have gone from being a long time graduate student and postdoc to faculty who is now a more senior contributor, yet are still perceived by the group as the junior researcher. I’ve met with many people who feel like they don’t have a way to change the hearts and minds of the group they have been working within.
While scientists have been trained to solve technical problems, when they encounter relational friction, we can accidentally treat it as a personal failing or a lack of "confidence."
It’s not about confidence; it's about coming up with a communication plan for the group. It’s about identifying the norms that have been happening, and suggesting that the group be more transparent. It's about getting yourself on the agenda to share updated news and create space for people to realign with titles, responsibilities, etc. (Have those been documented anywhere? If not, I’d recommend doing that!)
In this case the faculty member was carrying a large portion of the collaboration and not getting the title that work deserved. Yes, it might be easy to recommend that she just “speak up” but what we did in our session was different. We talked about everyone lacking clarity in what each person's role and responsibilities were and how to bring that next step to an agenda so everyone could start to get back on the shared page. With her responsibilities listed out (and everyone else's, too) it’s easier to see and share with the group the typical title that would accompany this level of responsibility. It’s no longer an ego argument about who gets the title but a more clear picture of what’s happening and why the titles would need to be updated.
In our work together, we shifted the focus from how to act to how to structure. We looked at the relational architecture of her role. We discussed the power of moving the "unspoken" into the "spoken” and the act of getting roles down on paper, redefining the status quo of communication, and creating a shared space where some of the norms people had been working within could be explicitly stated so the group can decide: do we like this or do we want to change this?
When we define the architecture of a relationship, we stop guessing where we fit. We can move from a state of protecting ourselves from judgment, to a state of embodiment, where we can actually inhabit our leadership and help everyone in the group gain confidence and clarity.
The most successful labs and collaborations aren't necessarily the ones with the most funding or the newest equipment. They are the ones where the people feel whole, seen, and clear in their roles. When I work with individuals and teams to prioritize the relational health of the team as much as the integrity of the data, we create a more sustainable way to keep going in STEM.
This blog post draws from real coaching that Erin-Kate Escobar Consulting conducted, working within STEM fields for over 10 years and utilized Duck AI’s Claude Haiku to help organize ideas.