Now showing / Alaska Airlines / People leadership

The Goodwill Bank

  • 2025-2026
  • Nov 4 -> May 1
  • People leadership
  • Progressive autonomy
  • Cargo Design

A designer transferred onto my Cargo team with a reputation already attached: careful, quiet, and slow to move without direction.

I treated that reputation as a clue, not a verdict. Over five months, I made a series of trust deposits: advocacy before asks, access before accountability, one clear behavior to practice, and real ownership with a safety net.

RoleSenior Manager, Product Design
TeamCargo Design, Alaska Airlines
TimelineNov 4 -> May 1
FocusTrust, coaching, progressive autonomy, field research

The Handoff

The transfer came with a warning label.

The read came in broad: not proactive, uncomfortable with ambiguity, risk-averse.

I understood why people saw it that way. He waited before speaking. Waited before volunteering. Waited before pushing on an open question. The behavior was real, but the label was too blunt to coach against.

So I treated the handoff like a hypothesis. The first leadership decision was to see the work, the room, and the conditions around him before deciding what kind of support would actually help.

Cream airport operations notebook with inherited observations circled as a hypothesis

Handoff evidence

Case file, not verdict

The inherited read existed before the coaching began. I used it as a starting hypothesis, not the plan.

The Diagnosis

The inherited reputation was a clue, not the answer.

01

Waiting for safety

From a distance, the pattern looked like low initiative. Up close, it looked like someone reading the room before deciding how much of himself to risk.

Two rooms, same read

Evidence

Two rooms, same read

Director and PM feedback pointed at the same hesitation pattern from different angles.

02

Learned caution

I did not see a designer who lacked ability. I saw someone who had learned that moving first could be expensive in the wrong environment.

Observation before prescription

Evidence

Observation before prescription

The coaching approach came from watching the rooms around him, not reacting to the label.

03

Missing context

Product had asked him to drive work before he had enough cargo domain context to own it confidently.

The ambiguity was real

Evidence

The ambiguity was real

The lower-deck workflow had enough operational complexity that context had to change with the expectation.

The Goodwill Bank

Trust deposits before ownership withdrawals.

I started thinking about the work like a bank account. Before asking for more initiative, I needed to make a few deposits he could actually feel.

Not praise. Not reassurance. Evidence. Evidence that I would advocate for him in rooms he was not in. Evidence that he had access to me before things went sideways. Evidence that the ask would be specific enough to practice.

Editorial framework graphic showing goodwill deposits building autonomy over time
01Advocacy before ask

Defend the context gap in a room he is not in.

02Predictable 1:1 access

Give him a reliable place to bring uncertainty early.

03One behavior target

Turn a broad reputation into one concrete rep.

04Paired field exposure

Make the room, domain, and questions legible.

05Private feedback

Move the critique out of the room and into a safer loop.

06Independent ownership

Step back once the room can become his.

The Coaching

Make the trust deposit first. Then make the ownership real.

The Montage

The work gave the coaching somewhere to land.

The growth happened through real cargo product work: field visits, workflow walkthroughs, operational questions, partner conversations, and presentation moments where the room needed clarity.

He watched me lead a field session. Then he led one. Then he presented the findings. Then he walked senior leaders through the workflow. Then he answered their questions without looking to me.

Illustrated Goodwill Bank field visit still at an airport cargo ramp
The coaching only worked once it had a real operating environment: field visits, workflow reads, partner rooms, and senior conversations.
Field observation photoField research

Field observation photo

The ramp context made the work concrete.

Lower-deck contextWorkflow understanding

Lower-deck context

The operating environment behind the ask.

Handheld scan flowProduct workflow

Handheld scan flow

The mobile workflow used in the field.

Desktop scan auditOperational proof

Desktop scan audit

The follow-through view for scanned bags.

Private coaching noteCoaching system

Private coaching note

Feedback moved out of the room and into a safer coaching loop.

Box Office Results

The proof was how little I had to perform leadership for him.

Dec

Advocated with his previous manager before asking him to change behavior.

Jan 13

Modeled fieldwork at SeaTac so the room, domain, and questions became legible.

Jan 21

He led the next field visit and presented the findings to cross-functional partners.

Feb

Senior leaders began defending the quality and thoroughness of his work without me prompting it.

Mar 31

He presented the cargo upload workflow to senior product and design leadership and fielded process-level questions on his own.

May 1

His PM publicly named the shift: he had gone from having little cargo context to jumping into projects and contributing right away.

By late January, he was leading fieldwork. By March, he was carrying senior conversations. By May, the people closest to the work were naming the change without me asking them to.

The outcome was not a louder designer. It was a more independent one.

Cinematic still of a product manager recognizing a designer's growth while the manager stands aside
The final signal was external: the people closest to the work named the change without me asking them to.
He went from having little cargo context to jumping into projects and contributing right away.
Product signal
The quality and thoroughness of the workflow readout started getting defended by leaders in the room.
Leadership signal
The best sign it worked was simple: he stopped looking for me before answering.
Tre signal

Director's Commentary

What I would do differently.

I waited too long to name the gap. I spent almost two months reading the situation before giving him one concrete behavior to practice. Three or four weeks would have been enough.

I also should have brought his PM into the coaching loop earlier. She was seeing the same behavior from a different angle. A short conversation in November would have created more consistent signals around him sooner.

End Credits

How I lead.

People rarely grow because someone tells them to be more confident. They grow when the environment gives them enough evidence to try.

That evidence can look small from the outside: a manager defending context, a standing 1:1, one clear behavior to practice, a field visit with a safety net, feedback delivered after the room instead of inside it.

Over time, those deposits change what someone believes is possible.

Animated Goodwill Bank team jumping in celebration on an Alaska Airlines cargo ramp
The point of the coaching was not a louder designer. It was a team with more room to move together.

Production Notes

The artifacts behind the story.

Goodwill Bank is a leadership story, not a product teardown. The evidence should stay compact, curated, and close enough to prove the growth happened through real design work.

01

Field Research

Real photos from cargo research trips or field visits, with faces blurred if needed.

02

Workflow Understanding

A before-process photo, operational map, or workflow diagram.

03

Presentation Readout

A deck screenshot or slide excerpt from the workflow presentation.

04

Coaching System

The Goodwill Bank deposits diagram or progressive autonomy model.

05

Product Output

A final screen or representative product workflow screen.

06

Feedback Evidence

PM, director, or executive quote cards.