Where it comes from

In early 2020, the question was simple: professional competencies relate to each other in complex ways — could those relations be drawn as a graph that's actually easy to understand?

Games had already solved this. Path of Exile, the Diablo series, Skyrim — all of them present sprawling systems of skills and experience to players through some version of a skill tree, and players navigate them without a manual. You see where you are, what's unlocked, what's next, and what it costs. Nobody writes a self-assessment essay to level up.

The move Skillforests makes is taking that presentation layer and pointing it at real professional competencies. Two convictions shaped how:

• Trees should be team-specific. A generic "front-end developer framework" fits nobody exactly. A tree built around the work one team actually does fits like a glove — so the method builds trees per team, not per industry.
• Trees should be built collaboratively. With a background in Design Thinking, the natural way to build them was together — workshops where the team maps its own work into skills and trees. People trust a map they helped draw.

The method ran for years on paper before it was ever software — growing real teams from a handful of people to a department. The forest metaphor stuck because it earned its keep: skills grow, trees have roots, and a healthy forest needs tending.