DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Culture and Methodologies
  3. Career Development
  4. A Simple Rule of Thumb for Priorities

A Simple Rule of Thumb for Priorities

If you're heading up a company, then being able to effectively set priorities is key. We take a look at one example of such a strategy.

Baron Schwartz user avatar by
Baron Schwartz
·
Jun. 18, 18 · Presentation
Like (5)
Save
Tweet
Share
4.49K Views

Join the DZone community and get the full member experience.

Join For Free

As a CEO, there's always an endless list of things that all seem to need urgent attention. Circumstances, customers, employees, board members, and many other sources of pressure clamor to elevate their personal favorites on your priority list. It took me a while to learn how to isolate the few things that deserve focus. Along the way, I created a simple three-part prioritization framework that helps me a lot. Here it is.

1. Don't Break What's Working

Hopefully, some things are working well. They can always be improved, but they're working well enough that there doesn't appear to be a lot of uncaptured potential.

The sales team at VividCortex is an example right now. They're managed well, performing well, and hitting their numbers. More importantly, I don't think there's anything they're not doing that could dramatically change their performance for the better.

I have no intention of messing with the sales team or processes right now. I tell them to ask if they need me.

2. Manage Or Contain What's Not

Some things suck. They're a source of irritation or frustration. They're frequent, but often short, reminders of something that isn't as good as it should be, and when you encounter it you always want to fix it. And yet they don't have a lot of upside potential — just downside. This means that they're a nuisance, but the potential benefit from fixing them is no more than the relief from the nuisance, or the elimination of friction, or whatever. No matter how hard you work on them, you won't generate great outcomes, you'll merely reduce their detrimental effects.

When the deck chairs on the Titanic are in disarray, the right answer is often to simply manage or contain the problem. These problems deserve only enough focus and resources to neutralize their harm. Deck chairs might trip passengers on their way to the lifeboats, so pick up the ones on the escape path and throw them aside. Leave the rest as they are and loudly explain why.

This is a delicate topic because it often raises the specter of undervaluing things like investments in quality, technical debt, or people. But the reality is that a big part of your job as CEO is to help people connect their work to the impact it has, and if you do that well, most people will understand that although we want to get to that problem and fix it, there may be more valuable things for them to do right now.

When something isn't as good as it should be, but there's no benefit to perfecting it, try to figure out how to duct-tape it as cheaply as you can.

3. Invest Heavily In The Top Three Game-Changers

Of the rest of the things that could merit your attention, there's likely a very long list of stuff that has the potential to create outsized returns. These are the things that, if done well or if you get lucky, could add a big multiple to your results. But there's going to be way too many for you to actually focus on.

Three is a magic number for focus in my opinion. You can focus on one, or two, or three things — but it's virtually impossible to dedicate meaningful focus to more. When people say they have 8 priorities, I groan a little.

Pick the most impactful three items and focus on them. Objectives and Key Results can help.

My current three priorities at VividCortex are marketing, product management, and engineering. Each of these has the potential to swing the company's results this year, either directly or through amplifying something else. For example, marketing can make sales easier and enable sales to outperform in a way they can't do by simply working harder.

What about the rest of the list? Those have to go somewhere, and they do. They fall into the category of stuff you need to manage or contain, for the time being. Explain to the team why it can't be a focus yet, and thus needs duct tape now.

It's A Strategy

My three-part framework is actually a prioritization strategy.

A strategy is a plan to prioritize resources to achieve the desired objectives optimally, while considering the most important constraints and circumstances.

It helps me invest in what can produce upside, neutralize friction, and stay the hell out of what's working. I hope it helps you too.

Sales Magic number (programming) teams IT Framework career Data Types Engineering

Published at DZone with permission of Baron Schwartz, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Top Five Tools for AI-based Test Automation
  • How to Quickly Build an Audio Editor With UI
  • PostgreSQL: Bulk Loading Data With Node.js and Sequelize
  • Asynchronous HTTP Requests With RxJava

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: