TThe Jasmine Star Show
← All frameworks
LeadershipBlake Eastman

Context-First Team Alignment

Explain the why behind changes before asking a team to change direction

Difficulty
Easy
Time to result
~days to results
Steps
5
Confidence
97%

Context-first alignment treats missing explanation—not imperfect nonverbal behavior—as a major source of team friction. When a leader changes direction, shortens meetings, rejects work, or behaves unusually, team members otherwise have to invent their own explanation. The leader should explicitly describe the constraints, reasoning, and implications of the change, acknowledge work already done, and clarify what happens next. This preserves meaning and reduces the impression of erratic leadership. The same method can be used to explain personal working preferences, such as needing concise meetings or unusually precise visual execution. Once people understand the mechanism behind the behavior, they can coordinate around it rather than interpreting it as arbitrary.

Origin

Extracted from The Jasmine Star Show.

Core principles

  • 01Behavior becomes easier to accept when people understand its context
  • 02Direction changes require an explanation
  • 03Unexplained pivots can make completed work feel diminished
  • 04Alignment matters more than performing an ideal leadership persona

How to run it

  1. 1

    State what is changing

    Describe the new direction or working expectation plainly so the team does not have to infer it.

    Pro tip Contrast the previous and new direction in one sentence.

    Watch out Do not bury the change beneath motivational language.

  2. 2

    Reveal the decision context

    Explain the constraints, evidence, and trade-offs that caused the change.

    Pro tip Spend a few focused minutes on the reasoning when substantial work is being redirected.

    Watch out Context is an explanation, not an excuse for chaotic behavior.

  3. 3

    Protect the meaning of prior work

    Acknowledge what the team contributed and explain why the pivot does not make that effort worthless.

    Pro tip Identify anything learned or retained from the previous direction.

    Watch out Ignoring sunk effort can make people reluctant to commit to the next plan.

  4. 4

    Define the new alignment

    Clarify the priority, ownership, communication channel, and immediate next action.

    Pro tip Ask team members to repeat back what has changed.

    Watch out An explanation without a concrete next step still leaves the team misaligned.

  5. 5

    Invite correction and pushback

    Create a specific opportunity for people to challenge assumptions or identify consequences you missed.

    Pro tip Let others speak before offering your own response.

    Watch out Do not request pushback if disagreement will be punished.

In the wild

Redirecting a virtual team

A founder stops a project after new customer evidence changes the strategy. She spends five minutes explaining the evidence, acknowledges what the project taught the company, identifies reusable work, and assigns the new priority.

→ The team understands the pivot without concluding that its previous effort was casually discarded.

Explaining a visual-quality obsession

A leader explains that visual inconsistencies prevent him from confidently publishing work, then explicitly permits the team to spend additional time perfecting important landing pages.

→ Designers can interpret his detailed feedback as an operating requirement rather than arbitrary criticism.

Common mistakes

Announcing a pivot without the why

Changing direction without explaining the decision makes leadership appear erratic and diminishes prior work.

Assuming context is obvious

Leaders possess information and pressures their teams cannot see unless they deliberately communicate them.

Requesting performative pushback

Asking for disagreement while reacting defensively teaches the team to remain silent.

Is it for you?

Best for

Fast-moving teams whose leaders frequently update plans in response to new information.

Not ideal for

Emergencies requiring immediate action before sensitive context can safely be shared.

From the transcript

“To build a good team, your team needs more context than you're giving them.”

Blake Eastman · 26:33

“You could spend 3 to 5 minutes explaining the intricacies of why you made that decision so that they don't feel like their work has…”

Blake Eastman · 27:12

“It's just you need to overcommunicate, not overcommunicate. And then your team will appreciate love. And most importantly, you'll be aligned.”

Blake Eastman · 27:12

From the episode

Nonverbal Communication Secrets That Drive Sales and Build Trust with Blake Eastman

Blake Eastman

→