Post by jonrojas on Apr 7, 2021 14:53:57 GMT
B.- How do you engage a team in innovating when they have anxiety around change?
What is the relationship between innovation and steady state? Should innovation be embedded in steady state?
A: I engage the team with data and results. I wouldn't suggest a change without laying the ground for why the change is necessary and how it can be beneficial to the task at hand. In my day-to-day work experience, I am constantly have to change my solutions to adapt to the constant changes in the world of technology. This eventually comes to a point where we have to start implementing new solutions and/or start looking at previous solutions from a different point of view. People working in field for a long time can become complacent in the solution tool set that they have. In order to encourage a tech to start to using a newer solution, I provide them with data and examples of how the new solution is utilized and how it can be make our process more efficient. Why take five steps to get to a resolution when you can take two? This idea is what drives me to keep pushing for new solutions and new ways to apply to previous ones. This is a great example of the balance between steady state and innovation. Steady state can produce a lot of results in the help desk environment and getting more efficient at applying a constant solution set helps to keep the support machine running. I think innovation should always be embedded in the steady state because no matter what you are doing, it can always get better. It can become more efficient. Preventing innovation from happening can stifle the progression of your steady state. While too much innovation can be bad, just right amount can help to keep the steady state improving over time.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
D. - Where did you see innovation?
What innovations intrigued you the most?
What was the team’s response to the need to innovate?
How did the leader drive innovation?
A: I saw two major innovations in those clips. The idea to turn off the devices to save power so they can successfully perform the re-entry and having to make a square peg fit in a circle hole in regards to a plan for the astronauts to build a new filter. The most intriguing one of the two for me is the plan to turn off devices to save power. This just seemed so far outside of their normal realm of thought and his suggesting of it didn't come easily. He didn't falter when they began to resist the idea either. He came in with a clear and thought out idea for the hail mary that they were looking for. The leader of the group became inspired by the idea and immediately began to divvy up ideas to each of them so they can find a workable solution. The leader continued to inspire them by leaning on their pride for their work and their country.
What is the relationship between innovation and steady state? Should innovation be embedded in steady state?
A: I engage the team with data and results. I wouldn't suggest a change without laying the ground for why the change is necessary and how it can be beneficial to the task at hand. In my day-to-day work experience, I am constantly have to change my solutions to adapt to the constant changes in the world of technology. This eventually comes to a point where we have to start implementing new solutions and/or start looking at previous solutions from a different point of view. People working in field for a long time can become complacent in the solution tool set that they have. In order to encourage a tech to start to using a newer solution, I provide them with data and examples of how the new solution is utilized and how it can be make our process more efficient. Why take five steps to get to a resolution when you can take two? This idea is what drives me to keep pushing for new solutions and new ways to apply to previous ones. This is a great example of the balance between steady state and innovation. Steady state can produce a lot of results in the help desk environment and getting more efficient at applying a constant solution set helps to keep the support machine running. I think innovation should always be embedded in the steady state because no matter what you are doing, it can always get better. It can become more efficient. Preventing innovation from happening can stifle the progression of your steady state. While too much innovation can be bad, just right amount can help to keep the steady state improving over time.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
D. - Where did you see innovation?
What innovations intrigued you the most?
What was the team’s response to the need to innovate?
How did the leader drive innovation?
A: I saw two major innovations in those clips. The idea to turn off the devices to save power so they can successfully perform the re-entry and having to make a square peg fit in a circle hole in regards to a plan for the astronauts to build a new filter. The most intriguing one of the two for me is the plan to turn off devices to save power. This just seemed so far outside of their normal realm of thought and his suggesting of it didn't come easily. He didn't falter when they began to resist the idea either. He came in with a clear and thought out idea for the hail mary that they were looking for. The leader of the group became inspired by the idea and immediately began to divvy up ideas to each of them so they can find a workable solution. The leader continued to inspire them by leaning on their pride for their work and their country.