Design craft & growth / 4 MIN READ
T-shaped designer’s skills
Depth gives designers a point of view. Breadth helps that point of view become useful to a team.
A designer does not need to be equally good at everything. But being excellent at one thing is rarely enough to move a complex product forward.
The T-shaped model offers a useful way to think about this tension. The vertical stroke represents depth: a skill you can rely on when the work becomes difficult. The horizontal stroke represents breadth: enough understanding of other disciplines to collaborate, ask better questions and recognize consequences beyond your own screen.
The goal is not to become a whole product team in one person. It is to make your expertise more useful to the people around you.
Start with a real depth
Depth is more than familiarity with a tool. It is the ability to make sound decisions when the brief is incomplete, the options conflict and there is no obvious answer.
For one designer, that might be interaction design for complex workflows. For another, it could be research, visual systems, accessibility or service design. The discipline matters less than the quality of the thinking behind it.
A helpful question is: What kind of difficult problem would other people trust me to lead?
If the answer is vague, adding more skills to a profile may be less valuable than spending time on one challenging area. Repetition, critique and reflection make that area deeper.
Build breadth around the work
Breadth does not mean collecting an endless list of capabilities. It means understanding the disciplines that shape the decisions you make.
A product designer might need enough:
- Product strategy to connect a proposed experience to a customer problem and a business goal.
- Research to distinguish an assumption from evidence and recognize what remains unknown.
- Engineering to discuss feasibility, dependencies and the cost of maintaining a solution.
- Content design to see language as part of the interaction rather than decoration.
- Analytics to ask whether a change helped, and what a metric cannot explain.
- Marketing to understand the expectations people bring into the product.
You do not need to take over these disciplines. You need to know when to involve someone who understands them more deeply.
A stronger T is built through collaboration
Reading about another discipline is a start. Working through a real decision together is often more revealing.
Sit with an engineer while discussing an edge case. Ask a researcher why a question was framed in a particular way. Review a campaign with a marketer before it launches. Examine a metric with someone who understands how it is collected.
These conversations expose the constraints that disappear in a handoff document. They also make it easier to explain your own decisions in terms other people can use.
The practical shift is from “Here is my design” to “Here is the problem, the trade-off and the decision we need to make together.”
Use the model to support growth, not label people
The T-shaped model becomes less useful when it turns into a rigid hiring checklist or a scorecard of everything a designer lacks.
A team does not need identical Ts. It needs complementary strengths, shared foundations and enough overlap to work together. Someone with exceptional depth may contribute more than a generalist who meets every checkbox.
For a development conversation, three questions are enough to begin:
- Where can this designer already make a strong contribution?
- Which adjacent skill would make that contribution more effective?
- What real project would give them a chance to practice it?
That creates a more concrete direction than asking someone to “be more strategic” or “improve their business thinking.”
Choose the next useful skill
A useful growth plan is selective. Pick one area to deepen and one neighboring area to understand better. Connect both to work you can actually do, with feedback from someone who can help you improve.
Depth gives your work substance. Breadth helps it connect. The balance will change as your role, team and product change — and that is a reason to revisit the model, rather than treat it as a final description of who you are.