Simple Mode Leadership
The Meta Wins That Followed
Why Simple Mode Leadership
Redefining the Air Canada home experience was a dream project for me. I could have treated it as a chance to own the whole thing end to end, deliver a polished experience, and call it a personal win. That would have improved the home experience but left the system unchanged. I chose a different path. I used it to test a philosophy I believe in: simplify the problem, create clarity, and put belief in the team.
The real win was not the home experience itself. The real win was the meta win: proving the system could deliver bold moves again and again, growing leaders in the process, and making clarity repeatable at scale. The proof was simple and visible. Beta became possible on the front door of an airline, something most people thought could never happen.
Where I failed first
My first frame was not strong enough.
I looked at it through the customer pain lens and the delivery effort lens. I missed the deeper forces that were dragging the home experience down and set the team off in the wrong direction.
The customer pain was real, but it was tolerable. People were still muddling through. The business pain, on the other hand, was sharp and visible. Marketing ops were slowed down, development costs were heavy, brand clarity was fractured, and new products were buried.
The simple truth: pain moves people faster than unrealized gains. Once we framed it that way, the case for change became undeniable.
That clarity made it possible to do something people thought you could not do with the front door of a large org: launch a Beta. And not just launch it, but make it acceptable, repeatable, and proof that scale without heroics was possible.
Core principles of Simple Mode Leadership
Clarity over control → I set the frame. The team set the plan.
Builders over passengers → Ownership lives closest to the work.
Small loops to big loops → Start tight. Widen as belief grows.
Minimum Viable Knowledge → Ship to learn. Do not wait for perfect certainty.
Access over translation → Bring teams into rooms. Let them hear the why.
Trust without ego → Advise, warn, then step back.
Step in only at red alert → Intervene only when risk to trust is too high.
Guard the simplicity → Everything new must earn its place.
Simple metrics → New must destroy old. Faster, clearer, better on every dimension. The old experience should feel irrelevant and forgotten.
Beta as a safety valve → Lower fear. Create permission. Learn in production.
These were not theories. They were the anchors that made Beta possible on the front door of an airline.
Simple Frames
I keep frames simple enough to say in one line:
Find what you need fast.
Get the right answer fast.
Every click should feel obvious, not hunted for.
To keep decisions defensible, I use two anchors:
The top customer actions for the home experience.
The top revenue drivers for the business.
These anchors kept every conversation focused. On the home experience, they gave the team confidence to defend flight search against every other demand.
Turning a support team into a product team
The engineering group we partnered with had been focused on bug fixes and overflow support. We needed a product team. That meant anchoring them in shared purpose, giving direct access to decision rooms, creating a cadence that rewarded shipping over artifacts, and setting clear quality bars tied to the frame.
It took trust and standards, especially with vendor partners. But it worked. A team built for support became a team building a front door Beta. That shift, from support to true product team, was the engine that made Simple Mode possible.
Ambition and emerging leaders
Nicole set an aggressive goal and timeline. My gut said it was too fast. I did not slow it down. I gave council, flagged risks, pointed to landmines, then let the ambition stand.
If the frame is simple and clear, I want early career and emerging leaders to push further than I would. Fresh perspective resets what the system believes is possible. That is how molds break. That is how culture shifts.
Mastering the set up
Nicole mastered the set up. She set the vision and strategy, then paired closely with Christine, an emerging product leader, to carry it forward.
She shifted into council, moving from player to player coach as Marty Cagan describes. She supported rather than drove, showing and pairing until Christine had the confidence to take the lead.
This was Simple Mode Leadership in practice: clarity over control, trust without ego, and builders over passengers. Nicole’s shift enabled Christine to grow, and that growth made scale possible.
A rallying cry
Nicole gave the team a rallying cry: let’s win a Webby. Winning a Webby was not on my list, but it was on Nicole’s. I supported it because ambition like that pulls teams forward.
I saw the Webby as a by product. The deeper win was proving that clarity, Beta, and trust could move the front door of an airline. And the meta win was bigger still: once you prove the system works, you can repeat it. That is what scales.
What Simple Mode Leadership looked like day to day
Bringing product and design into executive rooms so context was first hand.
Asking for working demos instead of decks.
Framing Beta as a safe toggle with an escape hatch.
Backing the team’s no to keep the home experience simple.
Only stepping in when trust was at risk.
Listening and collaborating, being there for council not approval.
What I said often
“Solve the core problems we defined. No gold plating.”
“If this does not make the home experience faster or clearer, it waits.”
“New must destroy old. Make the old irrelevant.”
When I was wrong
I had a strong opinion that we did not need search for launch. I believed our new navigation would get people to answers fast enough. The team felt we needed search but could not prove it. So we shipped and the number one piece of feedback that came back was simple: “Where is the search?”
I was wrong.
We heard the feedback, and the team shipped search quickly. It proved something more important than the feature itself. Leadership is not about always being right. It is about building a system that responds fast when you are wrong. That is the real proof of trust.
Guarding simplicity after launch
Simplicity erodes one quick add at a time. We created a simplicity gate: if it did not map to customer actions or revenue drivers, it waited. My role was air cover when the team’s no needed weight.
New Must Destroy Old
I kept it simple. The team decided how best to define it.
It just had to be unquestionably better.
The signals told the story. Core actions surged. Performance improved. Some actions did not move at first, but the signals showed us where to focus. When the core held, the Beta became the default. The rollout was uneventful because the work was already proven.
The leverage
Most people inside large organizations think “we cannot.” We cannot Beta the front door. We cannot simplify something this complex. We cannot let early career leaders drive the most visible experience.
But we did.
Not because we had more talent. But because we used Simple Mode Leadership to make it possible, acceptable, and repeatable.
The real win was not the home experience. The real win was proving that when you simplify the system, teams can scale clarity instead of complexity. That is how you get meta wins: customer value, business value, and leaders growing all at once.
The mirror for you
If an airline can run Beta on its front door, the first experience millions of travelers see every day, what is stopping your team?
What part of your product have you convinced yourself cannot change?
Beta is more than a toggle. It is a symbol that risk can be safe, that bold moves can be reversible, and that even established brands can learn in public.
The blocker is not your customers. It is not your brand. It is whether you can create the clarity and trust for your team to run.
That is Simple Mode Leadership.
Nicole has shared the tactical side of how we made Simple Mode real on the home experience. You can read her post on postmvp. This is the leadership side of the same story. Together they show how clarity at both levels makes bold moves possible.


Great collaborating with you on this Jose!
My favourite line in your article: "Access over translation → Bring teams into rooms. Let them hear the why." I can attest that this was so powerful when you brought us into the rooms to hear executive feedback firsthand and helped the whole team operate with a clear understanding of the "why".