Part of the Pressure Intelligence™ framework
guide
Member
Member
Member

The Speed of Now

A field guide for a leader whose market is moving faster than the company: raise the speed at which your organization learns and responds.

The Speed of Now
99
the-speed-of-now

Why the world outside can change faster than a company can read it, and how to raise the speed at which your organization learns and responds.

Navigating outside forces

The challenge: AI and the pace of innovation are moving faster than we can

The pace of new tools, new competitors and customer expectations is set outside the company. What a leader can work on is how fast the organization notices a change, decides what it means and tries something in response, and the gap between those two speeds is what falling behind feels like. A large program announced before anyone has tried anything, or new tools added to old work, tends to widen it. Inside are ways to learn with real work, in small pieces, and raise how fast the company learns.

Who it’s for: Senior leaders watching the pace outside the company outrun the pace inside it: a chief executive, a general manager, a function head deciding whether to make a big bet, run a small test or wait. Read it on your own first, then take the conversation in part three to your leadership team.

How it shows up

Part 1 of 3 · Notice the effect. The scene, where it lands, and the questions that often sit with you before you fix anything.

The scene

The quarterly review looks fine. Revenue is on plan and the roadmap is on schedule. Near the end, a newer analyst mentions that she rebuilt last quarter’s customer analysis over a weekend with an AI tool. The original took three people most of a month. The room laughs, then turns to the next item. Afterward, a sales lead tells the CEO that two deals last month went to a smaller competitor that shipped, in six weeks, a feature this company has on next year’s roadmap. The company does have an AI plan. It is a working group that meets monthly and is drafting a usage policy. The CEO walks back to her office with two questions she can’t answer yet: how far behind are we, really, and how fast can we move without breaking what already works?

Where it lands

  • In you: you often sense the ground moving before the numbers show it, and you aren’t sure whether the right response is a big bet, a small test or waiting until things settle.
  • In your team: some people tend to be using new tools on their own while others wait for permission, and the processes they work inside haven’t changed.
  • In your organization: competitors, some of them much smaller, typically try things you discussed and set aside, the dashboards show the current plan working, and new ideas take months to get from a conversation to a decision.

Questions to ponder

Think of the last outside change that caught our company late, and ask:

  • How long did it take to reach the leadership team after someone inside first noticed it?
  • Once it arrived, how long did it take to try something in response?
  • How many people tend to approve a small test before it can start?
  • In the last year, how many times did the company change direction because of something a competitor or a new tool did?
  • Do people know which parts of the business should hold steady while others change?

Questions to discuss

With the five answers from Try this week on the table, what has changed that our plan doesn’t know about yet:

  • What changed in the last six months that our plan doesn’t know about? Ask the people closest to customers first.
  • Which part of how we work was built for conditions that no longer hold? Start with the longest-standing process.
  • How could we change the way we work together so that each of us helps the others try something small and share what it found, and a test needs one conversation rather than five? Name one test each of you could start in the next two weeks, and who would need to hear what it finds.

Try this week

Ask five people outside the leadership team the same question: “What has changed in the last three months that our plan doesn’t know about yet?” Choose people who talk to customers, people who lose deals, and people already using new tools in their work. Write the answers down without arguing with them. Bring them to your next leadership meeting as context, and ask one follow-up: which of these could we test in the next two weeks?

Keep reading with a free account

  • Which of three versions you have: outside news that reaches you late, a company that sees the change but can’t try anything quickly, or one that reacts to each development and finishes few
  • The standing question to open a leadership meeting with, and who to invite to answer it
  • How to run a two-week test of a new tool with a named owner and one approval conversation, and the question to ask before making any process faster
  • How to name what doesn’t change, so the team can tell which new developments matter to you
  • The research behind it, and books to read next
  • The toolkit: questions to ponder, questions to discuss, things to subtract, actions to take
  • The kit, as downloads: the full Field Guide, a Leader’s Guide, and slides for the team conversation
Create a free account

Free, no card.

Open the field guide >>

About the author

Mark D. Benson
Mark D. Benson
Founder of Resonant Vector™
Resonant Vector
Full profile →

Mark D. Benson is the founder and principal writer of Resonant Vector, the home of Pressure Intelligence, and the host of Pressure Rising™. He is a product and systems leader who has spent his career running global teams, complex platforms, and consequential decisions under real constraint.

His career sits where strategy, technology and large human systems meet, in places where high stakes are the norm.

Resonant Vector is his commitment to learning in public and sharing what helps leaders and teams perform under pressure.

More about Mark can be found at markdbenson.com.