🚧Small teams

Telepath is structured for speed, autonomy and innovation.

Many traditional organizations have big, separate functions. You have a product team, an engineering team, customer support, and so on. This slows things down when you scale because there are more layers of communication and complex approval chains. This stifles innovation - you have to get your boss to talk to someone else's boss to get work done. It also means that people can't really see the impact of their work.

Telepath started off as a completely flat company with one big goal: to increase the number of successful remote teams in the world.

As we are getting bigger, we anticipate that it will get harder for people to see the direct impact of their work, which reduces the sense of ownership.

We have therefore introduced Small Teams. These are designed to each operate like a startup.

How it works

  • The overall goal for a Small Team is to own an area of the product/company and be as close to its own startup as possible, with only a handful of centralized processes

  • A Small Team should strictly be between 2-6 people

  • A Small Team has a Team Lead responsible for its performance - whoever is most appropriate depending on what the team is working on. This does not mean the most experienced person on the team.

  • A Small Team must have a customer(internal or external)

  • There may be certain functions where at our current stage we don't need a Small Team yet.

Last updated

Was this helpful?