Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Summary
This is part 2 of a 3-part series on prioritization, led by Harry Max, author of Managing Priorities: How to Create Better Plans and Make Smarter Decisions. Part 1 | Part 3 For executives, prioritization comes down to the ordinal list of what matters most. The challenge, however, is that they must deal with an array of competing imperatives: how to make money, use resources efficiently, pursue goals and objectives, satisfy existing customers or constituents, grow market share, hire and retain talent, manage unit cost economics, and so on. And pitting one imperative against another is tricky business. It’s a tightrope act. But leaving it to chance isn’t an option. Effective prioritization unlocks the latent power of teams. It supercharges strategy activation and taps the potential to align people to accelerate and get traction. Clear priorities enable change. This conversation will explore why leaders must prioritize at the right logical level to achieve their desired results.
Key Insights
-
•
Leadership prioritization involves managing epic challenges due to conflicting imperatives and scale, unlike individual or small team prioritization.
-
•
Prioritization is best understood as a continuous process, supported by periodic and episodic events that formalize decision moments.
-
•
Effective prioritization balances speed versus accuracy; doing it too slowly or too quickly can lead to costly mistakes.
-
•
Delegation works best when leaders assign ownership to those whose strengths align with the priority and who can independently drive it forward.
-
•
Explicit and mature operating models, like Salesforce’s V2MOM or EOS, are critical for aligning priorities and managing work effectively across large teams.
-
•
Publishing clear priority lists reduces organizational noise by allowing teams to focus on what truly matters and avoid unnecessary distractions.
-
•
Lower-priority tasks, such as technical debt or infrastructure improvements, must be acknowledged as necessities or managed carefully with dedicated time budgets.
-
•
Priorities guide attention and options but do not replace judgment; decision-making still requires balancing competing needs based on context and risk.
-
•
Prioritizing at the right organizational level of abstraction is crucial to avoid breaking coordination across functions or missing stakeholders.
-
•
Starting prioritization improvement individually encourages a ripple effect, helping to align teams and eventually organizations more naturally.
Notable Quotes
"You never have enough time or enough people to actually get done everything you wish you could, so you learn to prioritize well or you won’t be successful."
"Prioritization is like hiking — you’re always looking where you’re putting your feet and adjusting continuously based on what you see around you."
"All lists are prioritized lists; even bullet lists have an order, and the most important should be at the top."
"Your priorities don’t tell you what to do; your judgment points you in the direction of how to allocate resources and make decisions."
"Getting the date right is really important — you can change it once, but don’t change it twice, or it breaks coordination."
"You want to delegate something only if the person has ownership, competency, and feels safe to come back and ask for help if needed."
"Companies where prioritization goes well typically have an explicit operating model and a level of maturity around it."
"The way to fix a bad decision is to make several good ones afterward, because there is no undo button."
"Publishing your explicit list of priorities is a great way to reduce noise and focus the organization’s efforts."
"Prioritize at the right level because it’s easy to miss important stakeholders or criteria by working too narrowly."
Or choose a question:
More Videos
"Each species lost is a thread untethered from the web of life that supports us all."
Alex Hurworth Bonnie John Fahd Arshad Antoine MarinDesigning a Contact Tracing App for Universal Access
October 23, 2020
"These brand new practitioners can bring fresh perspectives and new ways of thinking to hopefully see current problems in a new light."
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
"If you come with a big idea, they’ll try to dial you back to the smallest iota you can test first."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"If your budgets don’t connect to strategy goals, maybe those budget items shouldn’t exist."
Nathan ShedroffDouble Your Mileage: Use Your Research Strategically
March 31, 2020
"Mobile devices not only have built-in screen readers but also pitch-to-zoom and magnification settings out of the box."
Sam ProulxMobile Accessibility: Why Moving Accessibility Beyond the Desktop is Critical in a Mobile-first World
November 17, 2022
"Documentation and making findings visible even without a dedicated research librarian helps maintain program momentum."
Feleesha SterlingBuilding a Rapid Research Program (Videoconference)
May 18, 2023
"Bumble’s single feature of women making the first move addressed a huge cultural challenge and lifted the brand."
Neil BarrieWidening the Aperture: The Case for Taking a Broader Lens to the Dialogue between Products and Culture
March 25, 2024
"Leadership roles have to evolve depending on whether you’re building awareness, influence, capacity, or measuring impact."
John DevanneyThe Design Management Office
November 6, 2017
"Small experiments that fit into existing structures make it easier to involve collaborators and reduce resistance."
Katy MogalBut Do Your Insights Scale?
March 12, 2021
Dig deeper with the Rosenbot
What role do collaboration and partnership with other departments play in building research ops infrastructure?
How does Tristan suggest balancing developer productivity with environmental awareness in tooling?
How can solo researchers or small teams scale their impact without dedicated operational resources?