How to Reframe Risk Management as Useful & Innovative Management Practices

New Way Old WayThis is Johanna Rothman’s November 2026 Pragmatic Manager newsletter. The Unsubscribe link is at the bottom.

In this issue:

  • Featured content: How to Reframe Risk Management as Useful & Innovative Management Practices
  • Read More…
  • Links of Interest

How to Reframe Risk Management as Useful & Innovative Management Practices

Do you feel as if “all” the technology you use is no longer reliable? I certainly feel that way. And while we might not know the various causes of all the problems and outages, I can be sure of this: As an industry, we do not do enough management risk management.

While project-focused risk management is useful, managers cannot easily use a risk register or a top ten risk list. That’s because risks often arise as signals, creeping toward us. Some organizations call those signals “technical debt.” If we ignore those signals long enough, the problem becomes a crisis. However, we don’t need crises to prompt us to do better management risk management. We can choose innovative management practices instead.

Here are the three ways to reframe risk management as useful and innovative management practices:

  • Assess how your product reaches your customers. What does that how rely on?
  • Make sure the people who work on those products or streams have the expertise and care about their work. Or, that they are willing to learn.
  • Rank all the work by value, including the risks when “everything” breaks.

Let’s start with where you need management risk management, the infrastructure problem.

Assess How Your Product Reaches Your Customers

How does your organization release value to your customers? Not just which products offer value, but how the value gets to your customers. That how is often infrastructure. Infrastructure gets old one day at a time. Until finally, it’s so old the infrastructure is only marginally useful or does not work.

I’ve never been a fan of “replace the architecture” projects because I’ve seen too many of them fail. Instead, I practice and encourage using the Big Ball of Mud approach to isolate pieces of the architecture, replace those, and iterate as we proceed. (See A Project Minute: Bad News Never Ages Well and Possible Organization Changes for a Product Approach, Part 5 for more information.)

When teams separate small chunks from the large effort and test as they proceed, everyone can see their progress. The project/program teams can see where they have trouble. The product leaders can see the product challenges. And the senior leaders can see where they might need to fund more (or less!) work to achieve the desired outcomes. Even better, that offers the idea of how little thinking for this effort.

I’m not suggesting you do the minimum to manage your necessary infrastructure changes. Instead, I’m advocating a risk management approach of continual small, iterative upgrades. That requires a management approach of experiments and bets.

What if you don’t see the signals until have you a crisis? That’s when the quality of the people you hire matters even more.

Hire People with Expertise Who Care

Managers practice risk management every time they hire new people.

If you specify narrow job descriptions and focus on just technical skills, you might have people with that specific technical expertise. However, that’s only part of the necessary expertise. The more agility you want in your product development, the more people need to be able to learn new things with others. Part of that learning is empathy with customers.

The more your people care about your customers, the more likely they will work to create a better experience for those customers. Very few, if anyone, needs management pressure to do a good job. Instead, they need the space to do the work and others to work with. What tools do your people need? Make sure they have the tools and knowledge they need from the start.

And if these caring, collaborative people realize they need more training? Find a trainer and get them training ASAP. Because infrastructure always tends to entropy, that chaotic state. Infrastructure work never benefits from delays.

Then, there’s the risk management of being able to see all the work.

Rank All the Work by Value

Long ago, I wrote Might Three Backlogs Be Better Than One? as a way to help several clients see the work they had not yet done. If they did not see the work, they could not decide whether to actually do that work. Transparency is a risk management practice.

And while I now suspect those clients could have tossed most of that old work, they had infrastructure problems.

The less we value infrastructure work, the more we postpone that work to “later.” Later often means that infrastructure work will cost more and take longer. Worse, the aging infrastructure will create problems when we have the least bandwidth to solve those problems. (A function of Murphy’s Law. See all the laws in Little’s Law for Any Kind of Product Development: How to Learn How Long Your Work Will Take.)

Risk Management is Innovative Management

When we manage risk, we use our current circumstances to plan a little or experiment to avoid problems in the future. We need to do project- and product-focused risk management. But that’s not enough. Managers also need to manage risk. That’s the innovative management practices part.

When managers do risk management, they have the option of two kinds of thinking:

  • Recognizing that there will always be “gotchas” that could prevent business as usual.
  • Considering options to provide better flow of value from the organization to the customers.

That better flow of value allows managers to use innovation as a differentiator. Even—or maybe especially—in the infrastructure decisions.

Read More…

This newsletter touches on ideas in these books:

(If you have read but not yet reviewed my books, please leave a short review somewhere, such as Goodreads. Thank you in advance.)

Links of Interest

New to the newsletter? See previous issues. (I post these newsletters to my YouTube Channel a few days after I send them.)

Here are other links you might find useful:

Johanna

© 2026 Johanna Rothman
Pragmatic Manager: Vol 23, #11. ISSN: 2164-1196

Leave a Comment

Scroll to Top