> ## Content Index > Fetch the complete content index at: https://www.anthroviasolutions.com/llms.txt > Use this file to discover other available public pages before exploring further. # What is a Management System? Rob’s Seven Domain Framework. - URL: https://www.anthroviasolutions.com/what-is-a-management-system-robs-seven-domain-framework/ - Published: 2026-10-23T15:30:00.000Z - Updated: 2026-10-23T17:32:49.000Z - Author: Robert Thursby *A management system is a set of domains which represent and define the expectations of teams and individuals. Many systems are emergent; they are created over time. Ideally, systems are intentionally designed.* # An Organizational View To understand the management system, we first need to anchor the organization as a whole. As pictured in Figure 1, I see the organization in three parts; the foundation, the management system, and the results of the management system. ![](https://storage.ghost.io/c/e2/02/e2024a8a-a1ba-49d4-8934-99cf243fea05/content/images/2026/10/data-src-image-93491a65-8e1f-4bb6-9f4b-8416c968aa60.png) **Figure 1** Rob’s view of the organization **The Organizational Foundation** The organization's purpose is separate from its products and service; it is the reason why the organization exists. An airline's purpose may be "to connect the world safely and consistently". The organization’s strategy is how it intends to compete. Most organizations will have several strategies at any given time in practice, with some single or combination which is central to how they will outpace their competitors. An airlines core strategy may be low-cost driven from efficient operations while maintaining brand quality. They may also employ a strategy for developing unique hubs or to invest in digital systems to improve the passenger journey. **The Management System** The management system is the (often-hidden) architecture that in addition to people and technology, runs the organization. Leaders and team members may come and go, but the underlying system remains. The system is made up of seven domains. Each domain has specific functions itself, as well as multiple interactions with others. Learning loops are central as all six other domains should be feeding organizational learning, and learning should be affecting changes to each domain. **What the System Produces** Culture is at the heart of organizations and has been identified as the primary barrier to organizational change, including becoming a data-driven organization (1). While many leaders prefer to believe they somehow control culture, in reality the organization’s culture is often a reflection of what has been rewarded and reinforced, and those are driven from the system. I make no claim the only factor to culture is the management system, but I do posit that the most effective way for organizations to sustain a culture is to invest in domains that can outlast any given person. Execution depends on clarity of what must be done, who must do it, what good looks like, what and how it will be measured, what information is required, and how do teams work together. This is the management system. **The Relationships** Purpose and strategy provide direction. The management system establishes how strategy is represented by the various teams who need to accomplish it, as well as setting up the various policies and processes required to operate. Culture and execution are the important outcomes influenced by the domains, along with other factors. ## An Integrated Whole The management system view helps move beyond focusing on individual departments, initiatives, or processes. An organization's purpose and underlying strategy(s) are unlikely to change often. Execution and culture depend more on what is allowed and rewarded over what is said. The management system domains provide leaders with a way to view problems and opportunities regardless of team silos or strong/key individuals. When intentionally designed and maintained, the management system helps support continuity of an organization's culture and execution through disruptions such as market and leadership changes. Although the term has been used in other contexts, the process of actively building and maintaining a management system can be called Organizational Stewardship. When the domains are actively designed and maintained, the system is intentional. When the domains are left to happen based on various leaders, subject matter experts and whoever has the say at the time, the system is emergent. # So, What is a Management System? The domains represent specific areas of focus, each with their own context which will be explained later in this article. Practically speaking, a management system is tangible in the form of policies, procedures, organization charts, meetings, and measures, along with how leaders act (especially as it relates to what they say). Each domain will have varying levels of documentation, digitalization, and personalization. Documentation is core as it forces us to write our intentions in a way that should be understandable by others. Digitizing helps with data/information and can provide controls. Personalization means that elements of the organization that everyone needs to understand (priorities, who gets to decide, measures) are made meaningful to various teams, communicated consistently while being translated into language relevant to each team/level. Having these items is not indicative of an intentionally designed system. It is the combination of their active use and evolution that shows intention. The purpose is not bureaucracy, but clarity. Without a designed system, staff are left to interpret; teams are left to argue and compete with themselves instead of the external competitors, and culture is left to be whatever the leaders at the time unconsciously allow. I believe the common need for "transformations", business and digital, are a result of organizations who neglected to focus on their internal workings, on their management system. If you are always evolving, using the seven domains I propose or otherwise, there would not be a need to transform which by definition means changing the foundation of an organization. # The Seven Domains of the Management System Each domain functions independently and interacts with the others, and all of them provide the opportunity for ongoing organizational learning. I provide this framework to help people have a perspective on organizations, understanding there are others. ## Strategy Translation How do the team members who need to execute the strategy understand it? Strategy translation is the process of taking the strategy and turning it into actionable priorities, choices and measures, moving from abstract to specific. True strategy includes trade-offs, choices about what an organization will and will not do. It is important to translate what has been decided the organization will not do along with the objectives, as it can avoid interconnected team conflict and individual assumptions. The value contribution of strategy translation is strategic alignment, ensuring that all stakeholders regardless of their place in the hierarchy understand what the strategy is, and how their work aligns to it. The strategy translation lens is helpful when leaders face a problem of their intention not being seen in what people are actually producing. There may be team or individual issues, but first the leadership must establish if the strategy has been appropriately translated (multiple times if needed) to the various teams who need to execute. ## Decision Rights Decision rights is the design of authority and clarifies who must decide, typically by naming the specific role accountable. Local versus centralized decision making is included in decision rights, as well as what triggers needing senior leadership approval. In organizations with weaker decision rights, the majority of decisions are made by committees. While they have their place in certain situations, decision committees as a default diffuse accountability, delay decisions and allow individuals to avoid taking ownership. It is much easier to say “that was the committees decision” versus “I made the decision, I own it and in hindsight, it was not the right way to go”. Decision rights contribute value by providing clear authority. By naming roles that own decisions, teams do not need to spend time debating or figure out who will decide, and organizations avoid the decision committee trap. Decision cycles are faster, resulting in less time per decision and given there are clear owners, learning can occur by creating an environment which does not punish people who provide information that may be hard to hear or challenge assumptions/direction. A fundamental element of decision rights relates to governance, discussed next. When organizations review decisions, there is often too high a correlation between the decision and the result. A bad decision can yield positive results as a good decision yield negative result. High impact decisions need to be well documented, so when the result happens whether positive or negative, leadership can learn if the decision (given the conditions & information) were optimal or if adjustments need to be made. ## Governance “Aren't governance and decision rights the same thing?” This is the most common question I receive when people first view the management system framework pictured in Figure 1\. Where decision rights is the design of authority, governance is the oversight and control of authority. Governance ensures that authority is visible, exercised appropriately, monitored, challenged, and held accountable. The value from governance is effective oversight. To provide clarity, let’s say Alex owns the decision for software for their department; Alex can fully make the decision. Where decision rights confirm Alex as the decision owner, governance would be in place which indicates that all software purchases must be approved through the IT security manager. The security manager does not own the decision but is required to be consulted as part of the process. ## Performance Management What you say you will measure is often what you will get, meaning if you say you want a 5% lift, don't be surprised if your organization puts all their efforts into showing a 5% lift. Performance management is about defining what success looks like, including what gets measured. A good example of the domains interacting together can be found with performance management and strategy translation. If an organization's strategy is to redirect staff time from issues to customers, this makes sense but is not something that can be measured. Translation would show (for example) that to have a material impact, staff need to spend far less time dealing with system issues, so a measure is put in place to reduce internal helpdesk tickets by 25%. Lowering the reoccurring issues of helpdesk on its own may never have related to improved customer value, but the domains together help produce clarity about how to get there. Of note measures would also need to be put in place to avoid incentives to game the system to achieve the reduction; the measure is a proxy for the result, not complete proof that it has been achieved. Performance visibility is the value generated by this domain; how outcomes are measured, monitored, interpreted and acted upon. ## Information Flow Some organizations remain very manual and have little or no data; information depends on specific people. Others have large amounts of data from years of history, available to staff in dozens or hundreds of reports and dashboards, even with daily pushes and alerts. Still, people have Excel files on their desktop or rely on relationships to get the information they want. Information flow ensures that trusted data, context, and insight moves smoothly through the organization. Trusted data that is of decision-ready quality is the highest challenge, particularly if the current culture does not trust the data. More data and information is not necessarily a good thing, and effort is required to make sure that information is flowing and being used. Without trusted, timely decision quality data, people will revert to relying on gut instincts or what was done prior. Information flow provides value in the form of trusted, decision quality information. Information is democratized and regularly reviewed to ensure everyone is getting what they need, and any notion of distrust is investigated immediately. Ideally information flow pairs with decision rights and governance, pushing leaders to make data-driven decisions and expect the same of their teams. ## Operational Cadence Of the seven domains I expect this one to be the least intuitive based on the title. Operating cadence speaks to the rhythm of the organization, things like meetings, reviews, planning cycles, and cross-functional coordination. Strong operating cadence provides organizations value in the form of coordinated action. Leaders cannot simply spin their teams off in new initiatives that do not support the core strategy(s). Cross-functional teams do not need to fight about who should join and contribute to what. Meetings are set with expectations. Reoccurring meetings are reviewed for value, and leaders have clear understandings of then they are to learn, act and reset on organizational priorities. ## Learning Loops Brining the domains together is the continuous act of organizational learning through learning loops. Learning allows experience and results to change how the management system operates and, when appropriate, can inform changes to strategy. The value contribution of learning loops is adaptation; organizations can remain agile and resilient because they are not relying on past success repeating itself. A sign of a strong learning organization is one where disruption – market, technology, leadership – does not impede the organization's ability to sustain its culture or execution. Organizations who continuously learn know that change is constant and so should be the system and organizational evolution. Initiatives have their place, but no quick fix can bring sustainable learning to organizations; continuous learning, and critically, actions based on learning, need to embedded as part of the intentional management system. # Bring and Keep Everyone Together The framework is a way to structure analysis, rather than a claim that every organizational problem has the same cause. Owners, boards and senior leaders can use the framework to enact questions to their teams that may not have surfaced previously. Directors and managers can use the framework to help pose questions, suggestions and statements to superiors in language that is meaningful and consistent. Individuals can use the framework to help understand organizations at a deeper level, potentially helping to understand where certain frustrations may stem from and how to go about discussing them. # Reference: (1) Bean, R. (2022, February 24). Why becoming a data-driven organization is so hard. Harvard Business Review Digital Articles, 1–6\.