This week, I was introduced to Enterprise Architecture. Enterprise Architecture (EA) is a type of management system for organizations. It outlines the ways to strategically plan the way they make decisions about technology and other resources (Bernard, 2012). The main concept is that organizations need to have clearly defined goals, and then organizational structures and processes in place to meet these goals. With these things in place, organizations are much more productive and functional. Additionally, using EA, organizations can identify areas of concern and work to improve them (Bernard, 2012).
As part of my Module 1 assignment, I had to contact multiple people in my district to find out about the organizational structure we have in place. I needed to determine if we use an EA-like approach to managing our district. I talked to, and emailed, quite a few people including the: Chief Technology Officer, Educational Technology Coordinator, Accountants, Technology Director, Superintendent's Assistant, and Principals. They provided me with a wealth of information about the decision making process in our district. Each person provided the same description of our decision making process, which led me to believe that the decision making process is well organized. The Cabinet is made up of the main decision makers, which I didn’t even know about. I knew we had Assistant Superintendents but I had no idea there were three of them and they were part of something called the Cabinet. I also didn’t know they had a process of decision making specifically about technology. It was fascinating to learn that the organization I am a part of has such a well organized management system. It’s also kind of scary to admit how much I didn’t know about my own district. The only part of the decision making process I have been a part of has been piloting curriculum and/or being trained on the newly adopted technology systems. I now know the lengthy process that these systems went through before being shown to teachers at school sites.
All of the details comprised in an EA are still so new to me and I know I have a lot to learn. After my initial research on my district’s management system and decision-making process, I am impressed with the system that we have in place. After more scrutiny and evaluation, I’m wondering if my perceptions will remain the same. I think this information is extremely valuable and would love to share it with my colleagues. Through my research, I discovered that the Cabinet (made up of the Superintendent, 3 Assistant Superintendents and our Chief Technology Officer) determines the district’s needs and then gives the Curriculum Committee possible technology choices to adopt. I never knew how vital our Curriculum Committees were to adopting a new technology system for the classroom. It makes me wonder if the representatives on the committee are aware of the responsibility they hold. I ended up making a flowchart of how communication flows between the decision makers to the school sites and I feel like it would be valuable to share this with my colleagues. If they ever wondered how or why technology systems were chosen, my flowchart will help them understand the decision making process.
Bernard, S. A. (2012). An introduction to enterprise architecture. Bloomington, IN: AuthorHouse.
As part of my Module 1 assignment, I had to contact multiple people in my district to find out about the organizational structure we have in place. I needed to determine if we use an EA-like approach to managing our district. I talked to, and emailed, quite a few people including the: Chief Technology Officer, Educational Technology Coordinator, Accountants, Technology Director, Superintendent's Assistant, and Principals. They provided me with a wealth of information about the decision making process in our district. Each person provided the same description of our decision making process, which led me to believe that the decision making process is well organized. The Cabinet is made up of the main decision makers, which I didn’t even know about. I knew we had Assistant Superintendents but I had no idea there were three of them and they were part of something called the Cabinet. I also didn’t know they had a process of decision making specifically about technology. It was fascinating to learn that the organization I am a part of has such a well organized management system. It’s also kind of scary to admit how much I didn’t know about my own district. The only part of the decision making process I have been a part of has been piloting curriculum and/or being trained on the newly adopted technology systems. I now know the lengthy process that these systems went through before being shown to teachers at school sites.
All of the details comprised in an EA are still so new to me and I know I have a lot to learn. After my initial research on my district’s management system and decision-making process, I am impressed with the system that we have in place. After more scrutiny and evaluation, I’m wondering if my perceptions will remain the same. I think this information is extremely valuable and would love to share it with my colleagues. Through my research, I discovered that the Cabinet (made up of the Superintendent, 3 Assistant Superintendents and our Chief Technology Officer) determines the district’s needs and then gives the Curriculum Committee possible technology choices to adopt. I never knew how vital our Curriculum Committees were to adopting a new technology system for the classroom. It makes me wonder if the representatives on the committee are aware of the responsibility they hold. I ended up making a flowchart of how communication flows between the decision makers to the school sites and I feel like it would be valuable to share this with my colleagues. If they ever wondered how or why technology systems were chosen, my flowchart will help them understand the decision making process.
Bernard, S. A. (2012). An introduction to enterprise architecture. Bloomington, IN: AuthorHouse.