Leadership

Senior, small teams: why we staff every project this way.

The thinking behind keeping our project teams small and experienced, and the trade-offs that come with it.

When clients ask how many people will work on their project, they're sometimes surprised the answer is so small. It's deliberate. We'd rather put two or three experienced people on a problem than a large team with layers of handover.

Why small works

  • Less telephone. Every handover loses detail. When the person who ran the workshop also writes the requirements and configures the system, nothing gets lost.
  • Faster decisions. Small teams don't need a meeting to schedule a meeting.
  • Clear accountability. You always know who owns what.
  • Lower cost. You pay for experience applied to your problem, not for coordination.

Why senior matters

Experienced people have usually seen your problem before in some form. They know which corners can be cut safely and which can't. On platforms like Salesforce, that judgement is the difference between a clean setup and one that needs rework a year later.

The trade-offs we live with

Small teams have limits. We can't throw ten people at a deadline, so we plan carefully and say no to unrealistic timelines up front. Holidays and sickness hit harder, so we document as we go and keep a trusted partner network for overflow. And we'll tell you if a project is too big for this model.

What this means for you

You'll deal with the people doing the work, from the first workshop to the final handover. If that sounds like how you'd like to work, get in touch.

Keep reading

More from TemTed.