Mike Russell

A subtle form of organizational suboptimization can lead to not-so-subtle problems.

Process optimization has been popular for decades … and often needed.

When technology became a key driver, “tech stack” optimization came to the forefront as well. “Moving to the cloud,” AI, and other tech developments have only added to a necessary focus on optimizing the various technology layers.

But what about optimizing the overall organization?

That’s another “stack” that is often overlooked: the org stack.

It’s helpful to optimize processes and technology.

However, neglecting people, culture, organizational structures, etc. can undo all our other process optimization efforts. More likely, the resulting chaos and even dysfunction in the rest of the organization “system” will outweigh the targeted optimizations. Hence, suboptimization rather than overall improvement.

Pay attention to the entire organizational system when making improvements.

This applies to both startups and established businesses, especially most transformation initiatives, digital or otherwise.

We have assessments that can identify your highest ROI improvements. Don’t guess or take on popular projects … apply your scarce investment and time where it counts most. Contact us to discuss your objectives and needs.

Most people don’t understand “coaching” via words or descriptions … it helps a lot to experience it.

That’s why we offer you a free session to see what it’s like … before you have to make any commitments to anyone.

We have a small number of openings each month across our team for trial sessions.

Don’t wait until the openings are gone or too late to do the prework …
Contact us to arrange your free session.

Outsourcing product development brings opportunities AND new challenges to success …

This challenge can create life-threatening risks from medical devices:

Fraudulent Data

An old (as in half a century or more!) simple prioritization approach is “Dump, Delay, Delegate, Do” … “4D” priorization.

How will AI help?

First, a brief explanation of the 4D prioritization steps in order … the order is important:

1. Dump – decide what NOT to do. As important, dumping means NO ONE in your organization should be doing it. An often overlooked step in some leadership guidance, yet key to implementing 80/20 thinking and reducing waste. If others need to know it’s dumped, communicate.
2. Delay (variously placed before or after Delegate) – Is it safe (enough) to wait a bit and find out more before anyone works on it? Do you need to find someone to delegate this to but they’re unavailable or need to be added to the team? Or maybe the situation might resolve itself? Note: you should set a trigger to review so not forgotten.
3. Delegate – if it needs to be done but you are not the best person to do it (skills, responsibilities, effectiveness, low return for your time, etc.). Who can do it better or more appropriately? Then follow good delegation processes …
4. Do – if it needs to be done and you’re the best person to do it. Prioritize against your existing “do” stuff.

How does AI enter into this?

Two steps depending on your AI use: Delegate and/or Do.

Which step depends on how much:

• You can “hand off” to AI
• You will be doing it in concert with AI. This is where a lot of personal productivity examples have been published.

Delegating to AI can also save your team’s time in addition to yours.

Either way, AI can multiply your effectiveness and that of your team.

As AI progresses, prioritization after the “dump” stage will center around “what should we be doing as humans” … what’s the most value a human can bring and focus on that. Let the AI take care of the rest – an evolution of what automation can handle for us.

AI output usually cannot be left “as is” …

There needs to be some form of checking before letting it loose, unless incorrect information has virtually no impact. “Trust but verify” applies.

The degree of checking will vary with the risk/impact of errors.

For example, LinkedIn is apparently using AI to generate article ideas and then send invitations for people to contribute to the articles. Sometimes I get multiple invitations a day.

The results range from the rational to the irrational.

Here’s one of the latter that is more subtle:

Software Project Management • 326,911 followers
How can you improve communication with team members using problem-solving skills?

If the team members are using problem-solving skills, couldn’t they solve the communication problem themselves? 😉

Of course, it’s also unclear if the team members are using problem-solving skills, or the invitation meant using problem-solving skills to address communication … and also why checking is needed!

Software continues to be a leading cause of medical device recalls.

It’s usually one of the top 3 recall reasons and all too often, the number 1 reason.

Businesses – startups and established – struggle with using more productive software development methods like agile or lean, while maintaining safety and regulatory compliance.

We can provide an overview, more detailed training, or consulting about how to do that … whatever level assistance you need for regulatory approval and market success.

Contact us to discuss your situation.