Reflection Essay 1
This week, I grasped the importance of teamwork. I didn’t recognize how vital it was, and how pooling together our resources would be so crucial to the advancement of our project. For the first session, the ideas we had were dull, to say the least. It was not a fruitful discussion. I attempted to bring some ideas to the fore but my thoughts were instantly shot down. I tried to appeal to those gathered around the table; what if we tweaked it? What if we made a change here, and a change there? Could this be a feasible idea?
The group was still dismissive. I was not even remotely attached to any of these concepts. These were just part of a brainstorm. But it bothered me that there was no room for any ideas. If it was not a fully fledged, operational model, they were not interested. There seemed to me a dissonance: these people around me were engineers. Engineers usually enjoy tackling problems. They enjoy grappling with challenges, …show more content…
It didn’t particularly matter if it was feasible, or if it was fully operational. We brainstormed. I discovered the power of collaboration like I never had seen it before. None of us came in with a fully formed idea. But we used each other’s ideas, to combine them into something that resembled a project. I began asking about our members’ strongest skills. One answered that he was adept at electrical engineering, others were stronger at coding. Another was good with hands-on building, and another was skilled at sketching. And so we began to mold our project to fit our strengths. We sought to take advantage of our colleague’s electrical expertise, and so using a circuit became a feasible idea. We had been discussing the idea of an app to unlock the bike lock; now that our group had coding experience, an app seemed apt for our project. We played to our strengths, and we sketched, over and over again, until we agreed on a preliminary
This week, I grasped the importance of teamwork. I didn’t recognize how vital it was, and how pooling together our resources would be so crucial to the advancement of our project. For the first session, the ideas we had were dull, to say the least. It was not a fruitful discussion. I attempted to bring some ideas to the fore but my thoughts were instantly shot down. I tried to appeal to those gathered around the table; what if we tweaked it? What if we made a change here, and a change there? Could this be a feasible idea?
The group was still dismissive. I was not even remotely attached to any of these concepts. These were just part of a brainstorm. But it bothered me that there was no room for any ideas. If it was not a fully fledged, operational model, they were not interested. There seemed to me a dissonance: these people around me were engineers. Engineers usually enjoy tackling problems. They enjoy grappling with challenges, …show more content…
It didn’t particularly matter if it was feasible, or if it was fully operational. We brainstormed. I discovered the power of collaboration like I never had seen it before. None of us came in with a fully formed idea. But we used each other’s ideas, to combine them into something that resembled a project. I began asking about our members’ strongest skills. One answered that he was adept at electrical engineering, others were stronger at coding. Another was good with hands-on building, and another was skilled at sketching. And so we began to mold our project to fit our strengths. We sought to take advantage of our colleague’s electrical expertise, and so using a circuit became a feasible idea. We had been discussing the idea of an app to unlock the bike lock; now that our group had coding experience, an app seemed apt for our project. We played to our strengths, and we sketched, over and over again, until we agreed on a preliminary