Arshdeep joined the iHub in April as the Communications & Operations Lead after graduating from programs at OCAD and Humber College. In this blog she reflects on what she learned in her first 60 days working at the Innovation Hub and discusses what it means to work collaboratively in a team setting.
Written by Arshdeep Kang, Communications & Operations Lead, Honours Bachelor of Design
On my first day at the Innovation Hub, I walked into work not knowing what to expect of the team or how I might be perceived by them. I was worried about how my workstyle might fit in with my colleagues— how much would I need to learn? Getting comfortable being outside my comfort zone is the first thing I learned. The second was that I would need to adopt a growth mindset. Reflecting on my first 60 days here at the Innovation Hub, I am learning quite a bit about the workplace and growing as an individual. I’ve learned a great deal about how collaborative work with team members means being able to ask for help when needed, being open to new ideas and approaches, and not feeling stuck in my work.
From Silo to Cross-Functional Team
During my undergrad I was always given individual assignments, so I learned to be a strong independent worker, only relying on myself to complete the work. I felt like I was working in a silo. Coming to the iHub, I was launched into work that requires daily team collaboration— there’s no such thing as siloed work here. In my first week I was asked to create visual icons for the iHub’s internal digital system. Initially I thought I was meant to complete it by myself but quickly realized it was an assignment for my team. I had to shift my work style to learn how multiple people’s ideas can lead to one final product, even if they are small visuals.
The team approach was an experiment. I decided that everyone on the team show their work in progress so we could give our feedback— this feedback loop led to fruitful conversations where we were able to build on each other’s ideas. Quickly the iHub’s collaborative working environment had taught me that great work isn’t a solo sport – it’s collaborative. I’ve learned that I can move from working in a silo to co-working with a team, and that this style of work produces incredible work because everyone’s great ideas are incorporated.
Being Open to Change
The first time I presented a project brief to my team, I realized how differently team members approach the work. In the back of my mind, I had a set process of how we will get the work done— understand the brief, conduct research, brainstorm ideas, and iterate on those ideas to then step away with a draft of the final product. When the team and I were halfway through the process, I introduced to them the idea of rapid prototyping. This is where we would quickly generate iterations of one idea in 5 minutes and move onto the next. But before I could even start, I looked at my team’s reaction and a few of them were surprised. One team member asked, “5 minutes for 1 idea— are you sure?”, to which I answered, “Yes, only 5 minutes”.
As a leader, I quickly learned what it means to understand my team’s strengths and weaknesses— some team members were excited to work by rapid prototyping while others didn’t have this experience and were nervous. So, I suggested that we try out rapid prototyping first, then come together and discuss what changes we can make as a team, without a time constraint. By changing the process and giving the team the opportunity to play out their strengths, I learned how important it is to be open to change.
Asking for Help
In my first few weeks working at the iHub, I would try to figure everything out on my own before asking someone else. Until my supervisor approached me one day and asked why I was holding on to a task. It wasn’t until that moment that I realized not asking questions would hold the work back. I was so afraid to ask for help, thinking that I would be a distraction to others if I asked too many questions.
In my past experiences, both in professional and academic settings, I had been so accustomed to figuring things out on my own, that even if it meant the work would take longer to complete, it was better to struggle through it and learn on my own. This is when I learned that asking questions is just another form of collaboration. When I shifted my perspective, it became much easier to ask for help not just from my colleagues and supervisor, but from my team as well. Asking for help doesn’t mean that I am incapable of the work, it just means that I need the missing piece of the puzzle to complete my work.
The Continuous Journey of Learning
Reflecting on my first 60 days, I can confidently say that being open to change and adopting a growth mindset has helped me work through any challenges that have come up in the workplace. The collaborative approach to work has taught me how to not only be a good team player, but also a great team leader. But most importantly, asking for help is okay, it doesn’t mean that I am incapable. Seeing how much I have learned over these past 2 months, I am excited to see how much more I will learn about myself and my work style over the next year.
0 comments on “My First 60 Days Working at the iHub ”