Mark Zuckerberg Quotes

Building product is not about having a large team to manage. It is about having a small team with the right people on it.

I've never seen a job being done by a five-hundred-person engineering team that couldn't be done better by fifty people.

You’ve got to give great tools to small teams. Pick good people, use small teams and give them great tools so that they are very productive in terms of what they are doing.

... you want to be proud of how much you can get done with a small numbers of employees.

Companies generally work better when they are smaller. It's always worth spending time to think about the least amount of projects/work you can feasibly do, and then having as small a team as possible to do it.

We worked out a lot of bugs and figured out who was working and who wasn't and how this beast functions. It was a lot bigger than we actually thought, and now we have a well-run ship where it feels I can actually have time to imagine and not just stress out about everything.

The team architecture means setting up an organization that helps people produce that great work in teams.

The green-light decision process today consists of maybe of 30 or 40 people.

Keep the team as small as possible. Having been on several of these mega-projects, they seem to grow magically. People are attracted to the project like moths to a flame.

Haas is a small, but a very efficient team - I am having a lot of fun!

There are no more holes in my management lineup.

I've always found that in a team of 15 people, it's a little different than in a team of 40 or 50 people. If I name two or three people captains, inevitably you're disempowering more than you're empowering.

I feel like I'm guiding the teams and we're all making this together. It feels more free-spirited and less structured, but we have our deadlines and that's important. We have an editorial team, but we're having fun. I get to guide them.

I have an amazing team, and we find people who resonate with us, but sometimes our scope is still small because we are a pretty small group and we have so much work to do. We get approached a lot.

Organize as much as possible around teams, to achieve enhanced focus, task orientation, innovativeness, and individual commitment.

Get your team in order, assembly is key

With respect to Committees as you would perceive I am very jealous of their formation. I mean working committees. I think business is always better done by few than by many.

I guess if you include contractors that are six or seven people working on reddit, but when we got acquired there were basically three and then in the years since, we've added three more developer hires full time, and a community manger. But the site is still remarkably small.

I've come to feel very strongly, not as a joke, that if you appoint a committee of more than four people, their efficiency starts to deteriorate.

Visualize a wagon wheel as a complete team. A leader might be the hub of the wheel at the center. Now suppose the spokes are the connecting relationships the leader is building with people on the outer rim of the wheel. If the hub is removed, then the entire wheel collapses. In a situation like that, if a team loses the leader, the entire team collapses.

If you work for a team, you have a different view, if you own a team you have a radically different view.

Even when you have skilled, motivated, hard-working people, the wrong team structure can undercut their efforts instead of catapulting them to success. A poor team structure can increase development time, reduce quality, damage morale, increase turnover, and ultimately lead to project cancellation.

Running a football team is no different than running any other kind of organization.

I do appreciate that the most important thing as manager is to get good results.