What’s in it for me? Build calmer, smarter teams that perform well when the pressure is highest.
Deep-space missions are easy to romanticize from a distance.
You picture the rocket, the spacecraft, the asteroid target, the triumphant launch.
But Psyche, NASA’s $1.
2 billion mission to the metal-rich asteroid Psyche, depended on 12 years of work, thousands of contributors, a long chain of partners and subcontractors, and the Jet Propulsion Laboratory in Pasadena helping manage an enormously complex effort where even a small technical problem could put everything at risk.
In the final days before launch, a serious thruster issue showed just how fragile a mission like this could be, and how much success depended not only on engineering skill, but also on the way people communicated, thought, and worked together under pressure.
That’s the larger frame here.
Psyche provides a vivid example of the kind of teamwork demanded in any high-stakes environment, where many specialists have to coordinate well over a long period of time.
It all comes down to team culture: how individuals conduct themselves, how trust and communication spread through a group, and how leadership keeps people focused on reality instead of drama.
In this Blink, you’ll see what a mission like Psyche reveals about how strong teams are actually built.
You’ll move from the individual habits that help people stay useful under pressure, to the relationships and shared norms that turn a collection of specialists into a real team, and then to the kind of leadership that protects culture, knowledge, and honest decision-making when the stakes are high.
It starts with the smallest unit of team performance: the way you speak and act when something goes wrong.
When the pressure is high, the first thing you owe your team is steadiness.
Calm speech turns pressure into progress
On the Psyche mission, a serious thruster problem emerged just days before launch, with huge costs and reputations on the line.
What helped the team function was calm, focused communication.
People listened, shared useful information, and worked the problem together instead of spreading panic.
That lesson isn’t limited to space missions.
You can see the same failure pattern in any workplace: a practical problem appears, someone sends an emotional message, blame spreads faster than useful information, and the group loses time and energy arguing instead of fixing what’s wrong.
The scale may be different, but the principle’s the same.
Teams make progress when people lower the temperature, return to the facts, and focus on what helps next.
That gives you a simple standard for your own behavior.
When you feel anger, frustration, or cynicism rising, pause before you speak.
Ask yourself what result you want from this exchange.
If your words mainly discharge emotion, they’ll usually make other people defensive or shut them down.
If your words help the group think clearly, they create room for good decisions.
You also need to stay on topic.
Edit yourself, make the point that matters most, and connect it clearly to the discussion already happening.
Speak up, but do it in a way that invites people to keep thinking with you.
Offer specifics.
Suggest a next step.
Help move the room forward.
A useful tool here is the risk statement that was used at the Jet Propulsion Laboratory.
State the issue in a clean sequence of problem, cause, and consequence.
That keeps attention on the work instead of on blame.
Another habit is to picture an important meeting before it happens.
Think through likely reactions, decide what outcome you want, and state that purpose early so everyone is aligned.
Once you can speak this way, the next challenge is action.
Complaining feels active, but it changes nothing.
The better move is to turn a problem into a question, gather evidence, and keep the solution space open long enough to find the best answer.
Frame the issue carefully, look at its scope and effects, and only then compare possible fixes.
That’s how you stop reacting and start leading.
Now let’s look at how to keep going when setbacks pile up, and how to build the kind of resilience that teams can rely on.
Resilience means staying responsible while you adapt
A serious project will eventually hit setbacks.
The people who keep it moving are the ones who stay honest about what’s happening, hold on to their standards, and adjust without losing momentum.
When facing setbacks, the real test is whether people stay honest, responsible, and adaptable.
On Psyche, the launch delay didn’t become clear until an experienced outside engineer sat down with the schedules and showed the project manager that the software wouldn’t be ready in time.
Lower down, the engineers closest to the work had already been saying they needed more resources and more specific expertise, but that warning hadn’t traveled upward clearly enough.
After the slip, the response wasn’t to hide the failure or collapse into blame.
The team confronted the communication breakdown, opened up broader discussions about the mission’s real condition, and later used a recurring internal survey to check whether communication and culture were actually improving.
That way of thinking depends on a growth mind-set.
If you believe ability can improve, failure becomes temporary and useful.
If you believe ability is fixed, every problem starts to feel final.
One of the most practical habits is experimentation.
Try small changes, pay attention to the result, and learn quickly.
You might fail, but the point is to use each attempt to make the next one smarter.
Even ending a project can be the right move when you have tested the reasonable paths and the cost no longer makes sense.
That can be a disciplined decision.
As pressure builds, quality matters even more.
Quality shows up in your notes, your reliability, your emails, your meetings, and the way you correct your own mistakes.
When you treat all of your work as evidence of who you are, you become more dependable and more valuable to the people around you.
To keep improving, you need one more skill: thinking about your own thinking.
Step back from habit, ask how you know what you think you know, and test whether your process is actually working.
That’s how you stop running on autopilot and start improving on purpose.
In the next section, we’ll look at how strong teams are built one relationship at a time.
A team starts to become real when people stop relating only through roles and start relating as human beings.
Strong teams grow from one relationship at a time
Although a team may look like one unified whole, trust is built through dyads, meaning the one-to-one relationships between individual team members.
Every encouraging comment, misunderstanding, hesitation, and act of loyalty is filtered through one of those relationships.
If you want a stronger team, start by strengthening the direct connections that make the larger group work.
On Psyche, that mattered because the mission relied on people from different specialties and organizations staying connected through pressure, handoffs, and shifting phases of work.
This gives you a practical place to start.
Make it normal for people to be known as more than their job title.
When someone new joins, have them share a little about who they are as a person, along with what they do on the team.
That helps others see their value more fully and makes respect easier.
Then keep asking yourself: Who here do I still not know well enough?
Go talk to them.
Ask what is going well and where they are stuck.
Listen before you explain.
And when tension rises, stay helpful.
Even a shared meal can make people feel more connected and less defensive.
You also need to watch for status, because status quietly distorts communication.
Differences in title, background, education, or perceived power can make some voices carry more weight than they should.
Hierarchy is always going to exist, the trick is to treat each person as worthy of respect before rank enters the picture.
Loyalty works the same way.
Organizations don’t feel loyalty, but people do.
Long-term support and trust live in relationships, not in the institution on paper.
That’s why your real strength at work depends so much on the quality of your dyads.
Once those connections exist, the next step is to decide together how the group will work.
After Psyche moved into its cruise phase, the team held a workshop to reset expectations, examine communication, and build shared norms for the new stage of the mission.
High-performing teams take time to agree on behavior, process, and culture, because the way people work together shapes what they can achieve together.
In the next section, you’ll see how information, authority, and decisions start to flow through a team once that foundation is in place.
Open communication and shared authority make teams effective
Once a team has trust and shared norms, the next challenge is flow.
Information has to move to the right people, authority has to sit close enough to the work, and decisions have to be made in a way that people can understand and support.
A good team doesn’t keep important context locked inside a small circle.
After Psyche missed its 2022 launch date, the team began holding all-hands Webex meetings.
At first, it wasn’t obvious that everyone would want that much detail.
Some people weren’t deeply involved in spacecraft integration at that point.
But broad attendance made something clear.
Many people felt cut off from the mission’s real condition, and once they were brought into the loop, they felt more connected and made better decisions in their own parts of the project.
That’s a useful standard for you as well.
Share wins, share problems, and make room for questions.
Team communication should sound honest, not polished for appearances.
That matters even more because silence can hide danger.
One of the biggest failures on Psyche came when senior leadership believed software teams were behind but still likely to recover.
Deeper down, a key subteam was saying something more serious: they lacked the resources and specific experience needed to finish in time.
That message didn’t travel upward accurately, and the launch slipped.
The lesson?
A quiet team isn’t always a healthy team.
Sometimes it’s a team carrying bad news that the culture has made hard to surface.
You have to build a habit of telling the truth early, especially when the truth is unwelcome.
Once information is moving, authority has to move with it.
Assigning work well means matching support to experience.
A new person may need the goal, the expected output, and the steps to be clearly defined.
A more experienced person may only need the goal.
Over time, people should gain more room to shape the work and improve the plan itself.
That kind of autonomy is a sign of respect, and it helps people become self-managing contributors instead of passive task takers.
The same idea applies to decisions.
When resources are tight, closed decisions breed resentment and poor judgment.
The better model is to make tradeoffs visible, hear the arguments openly, and let the leader decide after the team has been heard.
One useful tool is NASA’s science traceability matrix.
Start with the big goal, then make it specific enough to act on.
For example, instead of “gain market share,” narrow it to “increase market share in high schools with new science microcredentials,” then define how success will be measured, what actions come first, what output each action should produce, and what people, time, and money it will require.
That gives people a shared way to move from ambition to execution.
When communication is clear, authority is real, and decision-making is open, your team can act with more speed and less confusion.
In the final section, let’s look at leadership from above and the work of protecting culture, memory, and reality.
At the final level, leadership is about protection.
Leadership protects the team and keeps the mission real
You protect the team’s culture from fear and ego, protect hard-won knowledge from disappearing, and protect the work itself by staying honest about how it is really going.
If you have power, people will study your tone, your standards, and your habits more closely than you think.
So you need to live the behavior you want from others.
Communicate openly.
Share information instead of hoarding it.
Don’t ask people to accept rudeness, confusion, or silence from you while expecting discipline from them.
A leader’s job is to keep the team steady enough to do excellent work, especially when pressure is high.
You also have to stop your team from losing the recipe – the practical know-how that experienced people carry in their heads and hands.
Some of the most important knowledge in any project can’t be fully captured in a manual.
It lives in judgment, touch, timing, and repeated practice.
On Psyche, key subcontractors ran into trouble because specialized knowledge had quietly retired with the experts who held it.
That’s why training has to be more than documentation.
People need time together, side by side, learning through apprenticeship and shared work before that know-how disappears.
Then you need to face reality in a measurable way.
You need margins, meaning built-in room for error, and metrics, meaning clear signals that tell you whether progress is actually happening.
Assume that estimates are optimistic, plan extra room, and make the numbers visible to the team.
On Psyche, one formal way to handle risk to cost or schedule was to bring threats and possible impacts to a committee so they could be tracked and discussed before they grew into larger failures.
Finally, you have to measure the health of the team and extend your culture beyond the team itself.
During the delayed launch year, Psyche used a repeated internal survey to check whether communication and culture were improving.
And because major work depended on outside organizations, leadership also had to manage responsibility without direct authority by aligning expectations early and responding quickly when a subcontractor slipped.
Calm meetings, granular schedules, weekly milestones, and daily stand-ups were part of that playbook.
That brings the whole approach together.
You strengthen yourself, build real relationships, create a team that shares information and authority, and then lead in a way that protects people, knowledge, and truth.
That’s how you give a group its best chance to do hard things well.
Final summary
In this Blink to Mission Ready by Lindy Elkins-Tanton, you’ve learned that strong teams are built from the inside out.
They begin with individuals who stay calm, communicate clearly, take responsibility, and keep improving their own thinking.
They grow through trust between real people, shared norms, open communication, and the kind of autonomy that helps people do their best work.
And they succeed when leadership protects culture, preserves hard-won knowledge, measures reality honestly, and keeps partners aligned.
When you combine personal discipline, healthy relationships, and steady leadership, you give your team the best chance to perform well under pressure.
Okay, that’s it for this Blink.
If you can, please take a little time to leave us a rating.
We always appreciate your feedback.
See you in the next Blink.