It Depends On Your Role In Your Organization

As you read these patterns, it will soon be apparent that there are many patterns that you can do nothing about. For example, few of us are in a position to do something about CompensateSuccess; we don't hold the purse strings of the organization. Frankly, many of these patterns have management overtones, and non-managers are relatively powerless to change them. Furthermore, many of the "non-management" patterns apply to specialized roles; ArchitectAlsoImplements applies to only a few roles. 

You can react to this fact in one of two ways. One way is to become angry and frustrated. You identify yourself with Dilbert, and begin to see your boss with pointy hair. "Why can't my company's upper management get a clue?" 

There is a much better way, though. Instead of focusing on what you can't change, focus on the patterns that may apply to you. That set varies depending on your role. For example, you might find it useful to EngageQualityAssurance, or EngageCustomers. Perhaps you see yourself as a GateKeeper or a MatronRole. It may be worthwhile to strive to become so good at what we do that we eventually become a LegendRole

In reality, we will react both these ways; we're human. The trick is to try to let go of the things we can't change. Or at least, they become filtering mechanisms when we consider taking a position in a new organization.