Advanced Search
Search Results
39 total results found
Validation at scale
Assessing a handful of people honestly is a discipline. Assessing fifty — while levels feed reviews, promotions, and eventually pay — is a system design problem. The pressure is predictable: once levels touch money, levels inflate. Not because people are disho...
The review cadence
A forest is a living map, and living things need tending. The method runs on two nested rhythms — one for people, one for the forest itself — plus one hard deadline. Individual progress: roughly monthly. A short catch-up per person keeps their levels accurate....
What a forest review changes
A forest review is gardening, and it makes exactly three kinds of change. Walking in knowing this keeps the session focused — two to three hours with the team and the lead, not an offsite. Skills move between ranks. Expectations shift. The skill that marked a ...
Consistency without flattening
The moment more than one team runs forests, a tension appears. The organisation wants consistency — comparable levels, comparable ranks, reports that add up. Teams want fit — trees that match their work, not a committee's idea of it. Resolve this the wrong way...
Reading your forest
Your role is a forest; this chapter is about walking it. First, learn to read the map from where you stand. Follow the arrows. Within a tree, arrows run from a prerequisite up to the more advanced skill. The path is the prerequisite chain — you can't take a sk...
Choosing a path
The forest shows every possible path. Yours needs choosing — and five principles do most of the choosing for you. Clear the roots first. Hold a tree's roots before entering it. Skipping entry requirements is the surest way to get stuck later — the missing foun...
Tracking your progress
A map only helps if it stays current. So the real question of this page isn't whether to track — it's where your forest should live so that keeping it honest costs you nothing. Paper works — and charges rent. The method predates any software: a page per role i...
Pitfalls
Five ways people trip on their own forest — all avoidable once named. 1. Trying to learn everything. The forest shows all of it, and ambition says take all of it. Resist. Focus is the discipline: three to five skills, moved deeply, beat a dozen touched shallow...
The team map
Point a forest at a team and it becomes something new: one picture of what the team can actually do. Three reads matter, in this order. Coverage. For each critical skill: how many people hold it, and at what level? Read this first, because it's the first thing...
Planning growth
A team's development plan shouldn't need inventing — the map, read against the future, mostly writes it. Three inputs: Match the forest to upcoming work. Take the next projects on the horizon and read off the skills they'll demand. Compare against current cove...
Hiring against the forest
Most job openings are written from memory and vibes — a list of technologies, some adjectives, "5+ years." A forest lets you write one from the map instead. Define the opening by roots and target rank. The forest's roots are the derived, honest answer to "what...
Reviews and 1:1s on levels
Reviews are where the forest pays for itself most visibly — because it replaces the worst part of them: the adjectives. Talk in levels and ranks. "Moved three skills to confident this half, holds the full mid-rank set, two skills from senior" is reviewable — c...
Developing the team
The map shows what to grow; these are the mechanisms that do the growing — and the guardrail that keeps it healthy. Skill champions. For each critical skill, name the person who can answer questions, mentor, and validate level assessments. Champions turn every...
Onboarding a person
Coaching with a forest starts the same way every time: four steps that turn "help me grow" into a route. 1. Assess the current state. Walk the relevant forest together and place the person honestly on each skill — yes/no, or beginner / confident / expert, usin...
Guiding progress
Onboarding drew the route; guiding is keeping the person moving along it. Four practices carry the months between the start and the goal. Work the prerequisite chain. Don't let someone reach for an advanced skill before its foundations — even when they're eage...
Coaching many people
Coach one person and the forest is a map. Coach many, and it becomes something better: a dataset. Patterns emerge that no single engagement could show. Spot common starting points and obstacles. The same roots block many beginners; the same skills stall many t...
Roles and ranks as one system
Every role has a forest; every forest has ranks; every person holds skills at levels. Run across the whole organisation, this becomes a single system with answers HR and leadership usually have to improvise. "Is this person ready for the next rank?" — a defens...
Ranks, evaluation, and pay
Connecting the forest to evaluation — and eventually money — is where the method carries the most weight and deserves the most care. Three principles. Anchor reviews on levels and ranks, not adjectives. "Moved three skills to confident, holds the mid-rank set"...