Skip to content

Effective Principles for Working as a Team in a Startup - Reading Time: 3 Mins

  • Career
  • Communication
  • Leadership
  • Startup

📅 February 07, 2021

⏱️6 min read


undraw team spirit hrr4

No man's on an island. One man can only do so much without a team to complement and achieve an objective. Being part of a team provides benefits unlike as an individual by covering each other's weakness. As an individual, there is a limitation of what you can do. Special forces often operate in teams despite individually they are as an army of one.

Here are my thoughts in working as team base upon my experience. Working in multiple startups and operating in a high-performance team environment through my military service.

Communication is Key

undraw Work chat re qes4

There is alot of reasons a project, startup or company may fail. I believe one of those reasons is communication between team members. I had been in projects where I was an outcast unable to communicate & perform effectively due to my communication skills.

Without trust & a line of communication in a team can result in a toxic environment. Full of finger-pointing and in fighting to say that this is not my fault whenever a problem arises.

I would suggest that you read the book The DevOps Handbook & [The Phoenix Project][4]. These books talk about ways to establish the line of communication & restoring trust across teams or departments for rapid feedback & response to formulate a plan to solve a problem.

What is Their Tour of Duty?

![undraw career progress ivdb][5]

[Tours of duty][6] is often used in the military to have a rotation of personnel to various positions to understand the role that serves the organisation while progressing in their career. When these individuals are in these roles, they gain awareness and insights from multiple perspectives to formulate solutions that make the organisation better.

For me, I will stick to [The Alliance][7] definition for [tour of duty][8]. Which means a person will work for 2 - 3 years or less within the company or startup to the gain the necessary skills, experience & knowledge to prepare them for their next tour of duty.

Therefore I will do my best to talk to my teammates in water cooler chats about on their motivation & purpose in the company. So you can help your team member or as the leader to steer them towards their specific objective while achieving the team's business objective.

Taking Ownership Regardless If Your a Leader or a Follower

![undraw stand out 1oag][9]

You take responsibility as an individual for every failure, problem or setback which happens in the team even despite your gut tells you that this may be another person's fault.

I understand this can be a hard pill to swallow. That is why some agile teams use [blameless post-mortem][10] to reduce the finger-pointing & victimhood between each other to discuss and think of a way forward.

When I first read about this, I am like you who thinks that this is absurd since whenever problems happen. There is always another person's fault for the screwup which that person is not me. The problem with that mentality is that you are pushing the blame onto another person.

This mentality does not serve you. Instead, this makes you focus on the "other" guy. Costing you in the opportunity to reflect about yourself to prepare or improve to deal with future problems or situations.


![undraw result 5583][11]

I had covered what I had learned over the years. From books and being in teams from high performing team to low performing in toxic environments. Seek to part of teams to gain first-hand knowledge or experience by involving yourself through volunteering.

Volunteering your time & resources for your interest groups, conferences or contributing to open-source projects. Providing you with a glimpse of either high performing or unproductive teams to be a better follower and eventually a leader.

In learning to be a good follower and eventually becoming a leader in a team. You read books like [How to Win Friends & Influence People][12], [On Writing Well][13] & [48 Laws of Power][14]. These teachs you communication, understanding power dynamics and building relationships.

If you like this article do sign up for my [Adventurer's Newsletter][15]. Which contains interesting content I stumble across over the week in the area of Python, Web Development, Startup and articles that I wrote.

Subscribe to get the latest update of my article.

Lastly, are you looking to specialise as a developer? If yes, I am giving away my free ebook called ["Picking Your Specialisation as a Developer"][16]. It is for anyone interested in commanding a higher salary or doing the work they like.


  • [The Alliance][17]
  • DevOps Handbook
  • [The Phoenix Project][18]
  • [Extreme Ownership][19]
  • [Blameless Post-Mortem][10]
  • [How to Win Friends & Influence People][12]
  • [On Writing Well][13]
  • [48 Laws of Power][14]
  • [Tours of Duty Wikipedia][6]
  • [Tours of Duty][8]
  • [Teams of Team][20]
  • [UnDraw][21]

[4]: ( [5]: // [6]:,length%20of%20their%20service%20commitment. [7]: [8]: [9]: // [10]: [11]: // [12]: [13]: [14]: [15]: [16]: [17]: [18]: [19]: [20]: [21]:

← PrevNext →
  • Powered by Contentful
  • Max Ong Zong Bao's DEV Profile