This website is best viewed on desktop!
speaking +
trend briefings
I help teams understand what’s actually changing in AI, automation, and the way work gets done... and what deserves a response.
speaking + trend briefings
I help teams understand what’s actually changing in AI, automation, and the way work gets done... and what deserves a response.
When teams don’t share context, strategy fractures quietly.
By the time someone names it, the cleanup is already expensive.
Most teams aren’t reacting to different trends. They’re reacting to different interpretations of the same change. One department adopts a new AI tool. Another builds a workaround. Someone automates part of a process without realizing what it changes downstream. Each move makes sense on its own. Collectively, the direction splinters.
When teams don’t share context, strategy fractures quietly.
By the time someone names it, the cleanup is already expensive.
Most teams aren’t reacting to different trends. They’re reacting to different interpretations of the same change. One department adopts a new AI tool. Another builds a workaround. Someone automates part of a process without realizing what it changes downstream. Each move makes sense on its own. Collectively, the direction splinters.
The Problem
Every team member is responding to the same shift differently. AI gets adopted unevenly. Workflows change in pockets. Decisions that look efficient locally create friction somewhere else.
The Opportunity
When a team shares context first, decisions start reinforcing each other instead of competing. Execution gets clearer. Trust holds. This briefing creates that shared footing before time or budget gets spent correcting drift.
The Problem
Every team member is responding to the same shift differently. AI gets adopted unevenly. Workflows change in pockets. Decisions that look efficient locally create friction somewhere else.
The Opportunity
When a team shares context first, decisions start reinforcing each other instead of competing. Execution gets clearer. Trust holds. This briefing creates that shared footing before time or budget gets spent correcting drift.
What happens in a briefing
I interpret what’s shifting, and why it matters, across three areas:
ai + tools
What’s actually useful, what’s mostly noise, and where adoption is changing expectations.
workflows
The way automation and new tools reshape how work moves, friction, and human judgment.
customer + culture
How behavior, expectations, and broader shifts are changing what people notice, trust, and respond to.
ai + tools
What’s actually useful, what’s mostly noise, and where adoption is changing expectations..
workflows
The way automation and new tools reshape how work moves, friction, and human judgment.
customer + culture
How behavior, expectations, and broader shifts are changing what people notice, trust, and respond to.
This isn't prediction. It's pattern recognition applied to your context before it costs you something. Teams leave knowing what's changing, what deserves a response, and what can safely be ignored.
WHAT COULD WE LOOK AT TOGETHER?
Depending on what’s changing inside your organization, a briefing might focus on:
- AI adoption, tools, and where they actually belong
- Automation, workflows, and the hidden cost of “efficiency”
- Customer behavior, culture, and changing expectations
- Growth, change, and keeping teams aligned as things move faster
Every briefing is shaped around what your team is actually navigating, not pulled from a canned trend deck.
Clarity shouldn’t live in one department.
When context is siloed, reasonable decisions conflict. When context is shared, decisions reinforce each other.
Fewer reactive initiatives. Stronger alignment across functions. Faster execution with less rework. Confidence that the strategic direction isn't going to shift next quarter because someone in a different department made a move nobody else saw coming.
Alignment doesn't happen because everyone agrees. It happens because everyone is working from the same brief. Agreement without shared context is just politeness.
If your organization is navigating AI, automation, changing workflows, or broader shifts in how work gets done, this is a good place to get oriented before resources get committed.
Clarity shouldn’t live in one department.
When context is siloed, reasonable decisions conflict. When context is shared, decisions reinforce each other.
Fewer reactive initiatives. Stronger alignment across functions. Faster execution with less rework. Confidence that the strategic direction isn't going to shift next quarter because someone in a different department made a move nobody else saw coming.
Alignment doesn't happen because everyone agrees. It happens because everyone is working from the same brief. Agreement without shared context is just politeness.
If your organization is navigating AI, automation, changing workflows, or broader shifts in how work gets done, this is a good place to get oriented before resources get committed.
BEFORE EVERYONE STARTS SOLVING A DIFFERENT VERSION OF THE PROBLEM, GET THE ROOM ON THE SAME PAGE.
I’ll help your team understand what’s changing, what matters, and what deserves a response.
BEFORE EVERYONE STARTS SOLVING A DIFFERENT VERSION OF THE PROBLEM, GET THE ROOM ON THE SAME PAGE.
I’ll help your team understand what’s changing, what matters, and what deserves a response.