Reflect on the work you did to collect information for the Brick work. What value do you see in this tool?
Using a tool such as a brick to display the current and projected use of an application or system is very valuable. Although it is neatly organized with minimal text, it serves to give a concise snapshot of the life expectancy of a given system or application to anyone who is inquiring about that information. For example, if a stakeholder or parent were to ask about a given application this would be a clear piece of information to share with them. It is free of lots of text that may cause ambiguity to someone who isn't well-informed about the technology the organization is using. A brick gives a brief explanation and timeline. It gives the reader a snapshot into the plan of the organization without overwhelming one with too much unnecessary information. However, for the creator of the brick it serves as a tool for a thorough analysis. One cannot complete a brick without having done research or asking lots of questions. The author of the brick must know the application or system well enough to give a succinct description. They must also know the plan of implementation, as well as the future status and goals of the system or application. I feel that any stakeholder would appreciate having this information. As a matter of fact, seeing this tool through the perspective of an educator, I could see value in this tool for organizing district curriculum as well. Seeing a well laid out tool such as this and envisioning it with curriculum that is fully adopted or piloted would be helpful. Overall, this is a tool that I would like to see in use in any organization.
Using a tool such as a brick to display the current and projected use of an application or system is very valuable. Although it is neatly organized with minimal text, it serves to give a concise snapshot of the life expectancy of a given system or application to anyone who is inquiring about that information. For example, if a stakeholder or parent were to ask about a given application this would be a clear piece of information to share with them. It is free of lots of text that may cause ambiguity to someone who isn't well-informed about the technology the organization is using. A brick gives a brief explanation and timeline. It gives the reader a snapshot into the plan of the organization without overwhelming one with too much unnecessary information. However, for the creator of the brick it serves as a tool for a thorough analysis. One cannot complete a brick without having done research or asking lots of questions. The author of the brick must know the application or system well enough to give a succinct description. They must also know the plan of implementation, as well as the future status and goals of the system or application. I feel that any stakeholder would appreciate having this information. As a matter of fact, seeing this tool through the perspective of an educator, I could see value in this tool for organizing district curriculum as well. Seeing a well laid out tool such as this and envisioning it with curriculum that is fully adopted or piloted would be helpful. Overall, this is a tool that I would like to see in use in any organization.