Collaboration (and support) in a work environment
This past summer, I started a new position at the Canadian branch of Audience Partners(AP), formerly Bering Media as a Fullstack Developer focusing on their new flagship product, FlightDeck.
Having spend nearly a decade in very small startups, usually as the lone developer or a member of 1-2 person teams, I was curious how I would adapt to a more traditional team structure made up of a Product Manager, UX expert, and other developers all with different expertise and professional backgrounds.
I was pleasantly surprised and made me want to note some key observations I’ve made which help make for a positive work environment. Some of this will be all too familiar to some of my colleagues but to others it may serve as a gentle reminder that there might be something better out there for you if your current position doesn’t make you feel as fulfilled or happy as you would like to be.
So what have I learned to appreciate at my new place of employment?
1) Positivity: good collaboration is all about positivity from the type of language used during a brainstorming session to the demeanour of someone reporting bad news, whether a bug, or a change in direction of the project. Positive language means there’s no finger pointing, feelings or resentment to the one bearing the bad news or no one feeling like the weight of a problem rests solely on one team members shoulders.
2) Equals: We are an agile shop. We have a backlog. We plan out sprints, and try to facilitate the process and keep the project moving at all times. This approach encourages self organization, to decide what you want to work on and become develop expertise. It gives a sense of value to an employee. Knowing you’re helping and being useful is one of the best feelings you can have.
3) Lunch & Learns: Sharing what you’ve learned makes everybody better. It builds cross knowledge and creates interest to members of other teams to what you might be working on. At AP, we’ll have at least 2 L&L’s each month.
Spend an hour eating catered food, having a beer and listen or talk about some new programming language or the newest IDE, or something that’s being refactored on another team and the who, what, when, where, why’s of them doing it? Sign me up. If you’re newer to a company it’ll help see the bigger part.
We also have weekly, or bi-weekly demos to round off the week and for teams to demonstrate what they’ve been up to the last little while.
Supportive teams just can’t be beat. If you’re faced with being one that’s dysfunctional, be open and address the situation. Your team is with you 40 hours a week. Be productive, collaborate and support your way through the course of your project. A collaborative and supportive team member helps everyone succeed.











