Playbook
A playbook is not a set of rules.
It is a set of convictions.
The things we believe are worth protecting. The standards we hold ourselves to. The principles we return to when the answer isn't obvious.
At Typable, we work across strategy, design, technology, and brand. The work changes from project to project, but the way we approach it should feel unmistakably ours.
These are the principles that guide us.
01 — We care about the work.
The work matters.
Not because every project needs to change the world, but because anything we put our name on becomes part of the world.
We care about the details because details are rarely just details. They reveal how seriously we have thought about something. We care about the big idea for the same reason.
We don't aim to make work that is merely finished. We aim to make work we can stand behind.
That means choosing quality when quality takes longer. Looking at something one more time when everyone else is ready to move on. Making the difficult decision when the easy one would be good enough.
Good enough is sometimes enough.
But it should never be our ambition.
02 — We choose clarity over complexity.
Complexity is easy to create.
Clarity is not.
As projects grow, so do requirements, opinions, technologies, edge cases, and possibilities. It is tempting to respond by adding more: more features, more layers, more words, more visual language, more technology.
We try to do the opposite.
We look for the essential idea and make it clear.
A good solution doesn't need to show how much went into making it. The best work often feels obvious in retrospect — not because it was easy, but because someone took the time to remove everything that wasn't necessary.
We don't simplify for the sake of simplicity.
We simplify until the important thing becomes impossible to miss.
03 — We question the brief.
A brief is a starting point, not a verdict.
Clients come to us with problems, ambitions, constraints, and sometimes a solution they already have in mind. Our job is not simply to execute what has been asked of us.
Our job is to understand why.
Sometimes the right answer is exactly what was requested.
Sometimes it isn't.
We believe our responsibility is to challenge assumptions when doing so can lead to better work. That means asking uncomfortable questions, identifying the problem behind the problem, and being willing to say when we think there is a better way.
We don't challenge for the sake of challenging.
We challenge because we care about the outcome.
And when the brief survives the questions, we move forward with greater conviction.
04 — We design with intent.
Every decision should have a reason.
Design is not decoration added at the end of a process. It is a way of thinking.
The typeface, the interaction, the colour, the structure, the animation, the technology, the words — all of them shape how something is understood and experienced.
We don't make choices because they are fashionable. We don't add things because a page feels empty. We don't remove things because minimalism looks good in a presentation.
We ask what each decision is doing.
Good design can be expressive, beautiful, surprising, restrained, or even strange.
But it should never be accidental.
Intent gives creativity direction.
05 — We build what we design.
The distance between an idea and its execution should be as small as possible.
Designers need to understand technology. Engineers need to understand design. Both need to understand the problem we are trying to solve.
We don't believe in throwing work over a wall.
A design that cannot be built well is not finished. A technically elegant product that ignores the experience is not finished either.
The best results happen when disciplines work together from the beginning — when constraints become part of the creative process rather than something discovered at the end.
We design with implementation in mind.
We build with intention.
And we treat the space between the two as where much of the best work happens.
06 — We tell the truth about the work.
Good work needs honesty.
We give feedback when something isn't working. We question ideas when they are weak. We say when we don't know. We admit mistakes. And when someone has a better idea, we change our minds.
There is no value in protecting an idea simply because it is ours.
The work is more important than our ego.
That applies to everyone — regardless of role, experience, or seniority.
We want a culture where people can disagree without becoming defensive, where criticism is specific rather than personal, and where changing your mind is considered a sign of strength rather than weakness.
Honesty can make the work uncomfortable.
It also makes it better.
07 — We leave things better than we found them.
Every project leaves something behind.
A product. A brand. A codebase. A system. A process. A relationship. A new way of thinking.
Our responsibility doesn't stop at delivery.
We want to leave our clients with something that is more useful, more coherent, and more capable than what they had before we arrived.
The same applies internally.
We improve the systems we inherit. We document what matters. We clean up what we touch. We share what we learn. We make the next project easier for the person who will work on it.
Progress is not always dramatic.
Sometimes it is simply leaving fewer problems behind.
08 — We take responsibility.
Ownership means caring about the outcome, not just your part in it.
There will always be boundaries between roles. They are useful. But they should never become excuses.
If you see a problem, you can raise it.
If you can help solve it, help.
If you make a mistake, own it.
We don't believe responsibility should require permission.
This doesn't mean everyone does everything. It means everyone understands that the quality of the final result belongs to all of us.
We trust people to make decisions.
And with that trust comes responsibility for what those decisions create.
09 — We stay curious.
Experience is valuable.
But experience can also become habit.
The moment we assume we already know the answer is the moment we stop looking for a better one.
We stay curious about new technologies, new disciplines, new references, new ideas, and new ways of working. We look outside our industry. We learn from things that have nothing to do with the project in front of us.
Curiosity doesn't mean chasing every trend.
It means remaining open enough to recognise when something has changed.
We want to keep learning not because we need to know everything, but because there is always more to discover.
10 — We make it together.
Great work rarely belongs to one discipline.
A strategy can change a design. A technical constraint can improve an idea. A developer can find a better interaction. A client can reveal something the team had missed.
We want those conversations to happen early and often.
Design, engineering, strategy, brand, and the client should not operate as separate stages of a production line. They should be part of the same conversation.
Collaboration is not about agreeing with each other.
It is about making each other's thinking better.
The final work is stronger when no single person can point to it and say, "that's mine."
It belongs to the team.
The standard
A playbook only matters if it changes what we do.
These principles are not a checklist, and they are not meant to make every decision obvious. They are a standard to measure ourselves against when things become ambiguous.
They remind us to care about the work.
To question before executing.
To make things clear.
To think across disciplines.
To be honest.
To take responsibility.
To keep learning.
And, ultimately, to leave things better than we found them.
There will always be different ways to get there.
The way we choose to work is what makes the work ours.