Designer/developers, replace T-shaped with V-shaped for a sustainable career.
The T-shaped skill model, where one has deep domain knowledge and multiple shallow skills elsewhere, often creates unhealthy skills anxiety.
By definition, a T-shaped person has:
⢠Deep expertise in one area.
⢠Surface-level understanding in various other areas.
This approach can lead you to focus on quantity over quality, feeling compelled to tick off all the boxes from various job descriptions.
This never-ending and ever-growing to-do list can lead to burnout.
In contrast, the V-shaped skill model, as defined by Jeroen Kraaijenbrink, also involves deep expertise in one area but emphasizes gradually broadening knowledge in adjacent areas.
For example, as a front-end developer collaborating with my team:
⢠I learn UI/UX principles, not necessarily Figma expertise.
⢠I understand key networking concepts, rather than learning Python.
⢠I develop expectation management skills, rather than full-fledged product management.
Instead of trying to deepen my knowledge in multiple professional areas, I aim to communicate effectively across disciplines, forming a V-shape.
To summarize, V-shaped model is more beneficial because:
1ļøā£ It offers a focused and sustainable roadmap for growth.
2ļøā£ It relieves the pressure to learn everything.
3ļøā£ It emphasizes bridging gaps, fostering better collaboration.
Most importantly, it allows you to focus on shining in your area of expertise and passion āØ
If youāre interested in learning more about the V-shaped concept, here are two helpful resources that inspired this post:
1. Jeroen Kraaijenbrinkās intro to V-shaped concept: https://shorturl.at/aGrIp
2. T-Shaped vs. V-Shaped Designers: https://shorturl.at/hNV4l
What do you think about the V-shaped concept? Is it better than V-shaped? Iām very interested in hearing your perspective!