The Seven Conditions of Enterprise Performance: What Leaders Should Intentionally Design For

This series argues that organizations should design deliberately for the conditions people experience, not just for efficiency — the environment created by how leadership, governance, and technology are built, which shapes how people think, decide, and act. In the previous brief, I introduced the Enterprise Performance Model and suggested that enterprise design should be judged not simply by its efficiency, but by the quality of the conditions it creates. That should leave you wondering: if conditions are the hidden output of enterprise design, which conditions matter most?

Not every characteristic of an organization qualifies as a condition. And not every organization should optimize for exactly the same ones. Strategy matters. Industry matters. Organizational maturity matters. The conditions a start-up intentionally creates may not be the same as those of a global manufacturer, healthcare system, or utility.

What follows, then, is not intended to be a universal checklist. It is a working point of view — the seven conditions at the center of the Conditions Architecture framework I introduced in the last brief. These consistently enable enterprise performance regardless of industry, because they influence how people think, decide, collaborate, learn, and ultimately execute strategy. For the purposes of this series, I define enterprise conditions as:

The characteristics of the organizational environment intentionally created through enterprise design that influence how people think, decide, collaborate, learn, and execute strategy.

That definition immediately rules out many things we often discuss. Engagement is not a condition. Innovation is not a condition. Performance is not a condition. Even culture is not a condition. Those are outcomes. Conditions are what make those outcomes possible.

The Seven Conditions

1.  Strategic Clarity:  People understand what matters most.

As I thought back to my childhood afternoons outside, I realized something simple: our objective was never complicated. We were trying to have fun. That singular purpose guided hundreds of small decisions without anyone needing to supervise us.

Organizations are no different. When people clearly understand what matters most, they make better trade-offs, prioritize more effectively, and align their daily work with enterprise strategy. Strategic clarity doesn't eliminate uncertainty. It provides direction within it.

2.  Information Transparency:  People have the information and context required to act.

Growing up, we didn't carry weather apps or receive push notifications warning us about every storm. Information was simpler, but what we had was trusted. We knew where to look, who to listen to, and what to do when conditions changed.

The same is true inside organizations. People don't need every piece of information. They need reliable information, accessible information, and enough context to exercise good judgment. Transparency isn't about overwhelming people with data. It's about removing unnecessary uncertainty.

3.  Trust:  People have confidence in leaders, colleagues, and organizational systems.

Storms rarely worried me because I trusted the people around me. I knew every neighbor. I knew which porch offered shelter. I knew that if I ended up at Mrs. Smith's house, she would call my mother before handing me a towel and probably a cinnamon candy. Trust creates confidence long before it is needed.

Inside organizations, trust is built through integrity, consistency, and follow-through. It allows people to spend less energy protecting themselves and more energy solving problems together.

4.  Psychological Safety:  People can question, experiment, and learn without disproportionate personal risk.

One of the wonderful things about children is their relentless curiosity. They ask why. They challenge assumptions. They test boundaries. Most adults encourage that curiosity because they recognize it as learning.

Organizations should do the same. Psychological safety is not the absence of accountability. It is the confidence that thoughtful questions, new ideas, honest mistakes, and respectful disagreement will be treated as opportunities to learn rather than reasons to retreat.

5.  Learning Velocity:  People have access to, and time for, building new skills as fast as the required skills change.

The best way to become comfortable navigating storms is to experience them. Not once. Repeatedly. Then learn from each one.

Organizations are facing a version of that same test, just faster. Technology is changing which skills matter faster than most job architectures were built to handle. The organizations that keep pace won’t be the ones with the best training catalog. They’ll be the ones that give people real access to build new skills as fast as their current ones stop being enough. It’s part of why some companies are shifting toward skills-based pay, and why job descriptions are starting to read less like fixed roles and more like outcomes — the specific skills required to hit them won’t hold still long enough to document.

6.  Shared Accountability:  Success is experienced as an enterprise responsibility rather than a functional responsibility.

Many of my favorite childhood adventures happened with friends. If a storm rolled in, none of us considered leaving the others behind. We were in it together.

Enterprise performance works much the same way. When success is shared, collaboration becomes natural. When accountability is fragmented, optimization happens locally while performance suffers globally.

7.  Agency:  People have the confidence, authority, and support to exercise judgment and act despite uncertainty.

This may be the condition I have thought about most. It never occurred to ten-year-old Shannon to stop having fun simply because it started to rain. We adjusted. We kept going. Standing in the rain wasn't an act of resilience. It was the natural outcome of the conditions around us. We knew what mattered. We trusted the people around us. We learned as we went. We acted.

That, to me, is agency — the ultimate expression of good enterprise design. It is what happens when people stop waiting for certainty and start exercising judgment.

Designing for Performance

The purpose of identifying these conditions is not to create another checklist. It is to shift the design objective. Spend less time asking whether the organization is efficient. Spend more time asking whether it’s creating the conditions for people to perform.

In the next Executive Perspective, I'll explore who is actually responsible for designing these conditions and why I believe that responsibility sits squarely with leadership.

Intellectual Property Notice

The concepts, terminology, frameworks, models, diagrams, and written content contained in this publication are the intellectual property of Shannon Thomas and Titanium Vectors unless otherwise noted. No portion of this publication may be reproduced, adapted, or incorporated into other works without prior written permission.