The method behind every session Hobbit writes

The problem this method answers

A player makes thousands of decisions in a match and touches the ball for a couple of minutes. Yet most youth training is built around the touches: cones in a line, a queue behind them, a coach calling out what to do next. Players get better at the drill and no better at the game, because the drill removed the only thing the game is made of, which is choosing under pressure with someone in your way.

The alternative is not a better drill. It is a different job for the coach. Design an environment where the right choice is the one that scores, then let the players find it. That is what Hobbit builds, every session, and the rest of this page is how.

DGC: decision-making, game-related, creativity

DGC is the test every activity has to pass before Hobbit will put it in a session. D, decision-making: the activity must force the player to read, decide and act. If there is only one right answer, there is no decision, and it fails. G, game-related: the activity must carry what a match carries, a direction to attack, an opponent in the way, something to transition into. C, creativity: the player must be free to solve it their own way. The coach designs the problem; the player owns the solution.

Three habits follow from it, and Hobbit refuses to write a session that breaks them. No lines, because a player waiting their turn is a player not learning. No laps, because fitness comes out of the game itself at these ages. No lectures, because a long explanation is the fastest way to lose a nine year old. The coach spends roughly four fifths of the work designing the environment and one fifth asking short questions inside it.

The lever for all of it is the rules. Change the touches allowed, the time on the clock, the size or shape of the area, the way a goal counts, the number of players on each side, or what they are allowed to say to each other, and the same pitch produces a completely different problem to solve. Rules teach without stopping play, which is why every Hobbit session names the one rule that carries the theme and says what it is meant to produce.

Where DGC comes from

DGC is not invented from nothing and it is not a survey of other people's systems. It is a distillation, taken from the public development methodology of five European federations and built on the places where they independently agree.

From the FA in England it takes the four corners, so a session is judged on technical, physical, psychological and social development rather than on drills completed. From the RFEF in Spain and Horst Wein's school it takes game intelligence as the first thing to develop, along with the rondo and small-goal formats that train scanning. From the KNVB in the Netherlands it takes insight valued above technique, and the four against four game as the building block. From the FFF in France it takes starting from the game, isolating the problem, and returning to the game. From the DFB in Germany it takes Spielintelligenz first, the protected right to make mistakes, and the reform that removed league tables from the youngest ages.

None of these federations endorses, certifies or partners with Hobbit. Their methodology is published, Hobbit studies it and distils from it, and that is the whole of the relationship. What makes the distillation worth trusting is the convergence itself: five countries with different traditions, arriving separately at the same conclusion that the game is the teacher and the decision is the skill.

Why every team gets its own AI

A method that only produces sessions is a method that forgets. The same theme suits a squad of eight and buries a squad of sixteen; the progression that worked in March is the wrong starting point in October; a plan written for a group who have never defended a transition is not the plan for a group who spent a month on it. So in Hobbit the unit is not a session. It is a team.

Create a team and it gets its own AI: the same engine and the same method, wrapped around one squad. It holds the roster and the ages, the philosophy you wrote for that team, what the last debriefs and results said, who has been turning up, and what is on the calendar next. Ask it for a session and it already knows the numbers you have. Ask it what to work on and it answers from that team rather than from youth football in general.

Be clear about what that is and is not. It is a configured assistant, not a coach who was at your training. It knows what has been recorded, so a session you never wrote down never happened as far as it is concerned, and it will tell you what it is working from rather than implying it watched. That boundary is deliberate. An assistant that quietly invents context is worse than one that admits it only has the roster.

What the method produces, and what it refuses to

Ask Hobbit for a session and it does not retrieve one from a library. It designs a progression: a warm-up, a technical phase, a skill phase and a conditioned game, each stepping up on decision layers, opposition, space and time pressure, or how close it sits to a real match, with the theme running through all four and a free small-sided game to finish. Every phase names its core rule, its competition, the decisions it should force and the questions worth asking, and carries a pitch diagram drawn to match the text.

The same method runs the rest of the work. Hobbit draws drill diagrams from a plain description, writes match reports and parent notes, turns a recorded voice debrief into structured reflections, keeps the roster, attendance and calendar, and gives each team a public page parents can open. It reads and answers in English, Chinese, Japanese, Korean, Spanish, Portuguese, French and Vietnamese, and it covers the ages from U5 to U18.

What it will not do is as much a part of the method as what it will. It will not rank children against each other, and it will not build a session around who scores the most, because at these ages a table teaches the wrong lesson. It will not hand a coach a session and call it finished thinking: every plan says what it is trying to produce, so the coach can disagree with it on the pitch, which is where the judgement belongs.