July 13th, 2024

Trust as a bottleneck to growing teams quickly

Trust is crucial for team growth. Lack of trust increases workload and hinders collaboration. Symptoms of trust deficits include frequent escalations and deep involvement in decisions. Building trust requires proactive efforts like sharing mental models and overcommunicating.

Read original articleLink Icon
Trust as a bottleneck to growing teams quickly

The article discusses how trust can act as a bottleneck to the growth of teams, particularly in fast-growing environments. Lack of trust can lead to increased workload as individuals need to micromanage and inspect each other's work more closely. Trust is crucial for collaboration to scale efficiently, especially during intense work periods. The text highlights symptoms of trust deficits within teams, such as frequent escalations and deep involvement in decisions. Building trust requires proactive efforts, including sharing mental models, investing time in communication, trying out team members, giving feedback, and setting up inspection forums. The article emphasizes the importance of overcommunicating status and proactively admitting when things are not going well to earn trust. Trust deficits can be managed through continuous effort and investment in building relationships within the team, especially in high-growth scenarios.

Related

The 10x developer makes their whole team better

The 10x developer makes their whole team better

The article challenges the idea of the "10x developer" and promotes community learning and collaboration in teams. It emphasizes creating a culture of continuous learning and sharing knowledge for project success.

No Matter What They Tell You, It's a People Problem (2008)

No Matter What They Tell You, It's a People Problem (2008)

The article emphasizes the crucial role of people in software development, citing teamwork, communication, and problem-solving skills as key factors for project success. It highlights the importance of job satisfaction and team cohesion, underlining the significance of positive personal relationships within development teams.

Bad habits that stop engineering teams from high-performance

Bad habits that stop engineering teams from high-performance

Engineering teams face hindering bad habits affecting performance. Importance of observability in software development stressed, including Elastic's OpenTelemetry role. CI/CD practices, cloud-native tech updates, data management solutions, mobile testing advancements, API tools, DevSecOps, and team culture discussed.

The magic of small engineering teams

The magic of small engineering teams

Small engineering teams at PostHog operate autonomously, focusing on specific products or functions. Each team has a leader, encourages collaboration, and aims for a flat hierarchy to enhance individual impact and innovation. Challenges include communication management and hiring alignment.

How to Fix Broken Teams

How to Fix Broken Teams

Teams can be fixed by diagnosing issues, replacing managers, improving processes, changing culture, expanding teams, and aligning missions. Consistent effort over 6-18 months can transform dysfunctional teams effectively.

Link Icon 5 comments
By @NAHWheatCracker - 7 months
The article doesn't seem to address the main reason I learn not to trust some people: They aren't trustworthy.

At my last job I was on a project with two other developers, two data scientists, and a project manager. At the outset of the project I mostly trusted people to do their jobs. I'd only worked closely with one of the developers, but I'd had enough incidental contact to have a good opinion of everyone else. We divided the work up and made a decent plan early on. Then things fell apart.

One of the developers had a single 3-point spike story open for the whole quarter. He made one boilerplate PR and left no comments in any other PR. He regularly missed meetings and didn't add to any discussions. He talked a big game and never delivered.

One of the data scientists took six months to make an extremely simple model. He made the only PR for it on the last day of the quarter before he got switched to another project. He wouldn't answer any questions whatsoever about how the model worked. It was inefficient and not ready for use. I had to rewrite the model.

The project manager never wrote anything except titles in Jira tickets. He repeatedly didn't follow up on questions, even when we had a clear issue needing feedback from the customer, whom only he could talk to. He was completely oblivious to the lack of progress above, despite never seeing a demo from those people.

Luckily, the other developer and the other data scientist were capable and accomplished part of what was needed. The project was still a disaster because we had the software equipment of a car without wheels. I spent half a year begging my manager to move me to another project when I realized it was going this way.

I love to trust people. It's how I work. I tell you what I'm going to accomplish and I do it, every time. I expect the same from others. I don't care about performance as much as I care about doing what you say you will. There isn't a model to build trust with untrustworthy people.

By @glennericksen - 7 months
"Business moves at the speed of trust."

This is a good post exemplifying this axiom. It is one thing for a leader to be trustworthy. It's a different challenge to cultivate trust within an organization in the midst of rapid change. Enjoyed reading this account of Anthropic's adventures scaling trust.

By @wslh - 7 months
Indeed trust is a human scale problem at the root of civilizations. Seems like a rediscovery of the wheel.

This is why it is important to cite previous work on a topic. If we don't we run in circles thinking we are discovering something new.

By @choppaface - 7 months
Trust as a term is a bit overloaded. For software teams, I find “trust” can often be a shared lingo, shared mental model, and shared expectations. The first two can be easier if the two sides both use the same programming language and internal libraries. The latter can be hard, especially if the two sides have different Product Managers.

The OP alludes to ‘what trust is’ mentioning the ‘Dario simulator’ issue. Trouble arises when ‘the Dario’ holds a vision that might conflict with the team or the outside world.

By @ProAm - 7 months
Most employees and definitely new employees are not good. Ask any military unit about the FNG. Same applies to our business, especially and when RSO's matter.