A small team can hold a great deal of working memory.
There are ways of approaching a problem that have been tested in different organisations. There is an instinct for the decision that looks minor now and becomes expensive later. There are also assumptions that once served us well and need to be examined again.
Across Partech’s leadership there is more than a hundred years of combined experience. I find that useful as context for the work. It tells you that the team brings several long working lives to the table. It does not settle the question of whether a particular decision is right.
Make experience available
Experience helps a team when it can be passed around. A concern needs to be explained well enough that someone else can examine it. A decision needs a reason that survives the person who made it leaving the room.
“I have seen this before” can be the start of a useful conversation. The next part is to describe what seems familiar and what might be different this time.
That distinction matters in a company with a long history. Work for clients, work involving physical equipment, and work on independent apps can teach related lessons. They also take place under different constraints. The resemblance deserves attention; so do the differences.
Leave room for a fresh pair of eyes
A product team can become fluent in its own interface. The labels stop looking ambiguous. A sequence of screens feels natural because everybody knows what is coming next.
Someone new to the product does not have that shared memory. Their question may expose a problem the team has learnt to step around. It is worth preserving the question before explaining the design.
The same is true inside a team. A quiet contribution, a written note after a meeting or a question from somebody outside the speciality can change how a problem is understood. Speed and confidence are only two ways that an idea arrives.
Keep the organisation small enough to understand
One attraction of a small independent studio is that the distance between a decision and its consequences can stay short. The people writing the description can speak to the people building the feature. A support question can reach somebody able to change the product.
That closeness takes work to preserve. Unclear responsibilities and decisions left in private conversations can make even a small team difficult to navigate. A brief written decision, an explicit owner and a useful explanation can save considerable effort later.
For me, this is where the long memory matters most. It can help us recognise the habits worth keeping while leaving enough room to learn something new.