AI gives the lift, people set the course. Together, you fly higher.
The Kite Method is a way of working for software teams that combines the speed of AI with human direction. Humans decide what’s worth building and whether it’s right. AI builds it, fast.
Writing code is no longer the bottleneck.
The bottleneck has moved to two places: knowing exactly what you want, and being able to establish that what you got is right. Scrum and SAFe still assume human build capacity is the scarce resource. Teams that add AI without changing how they work run into three problems.
Review pressure explodes
Pull requests pile up and people start approving without really looking.
Rework rises
Agents build at lightning speed, but given a vague brief they build the wrong thing at lightning speed too.
Craft erodes
Juniors stop learning the trade and seniors lose touch with their own codebase.
Line and wind
A kite climbs because two forces work together: the wind that lifts it and the line that keeps it on course. The line is not a brake. It is the tension on the line that makes a kite climb.
Throttling AI back to autocomplete does not work either: those teams get overtaken. The Kite Method sits in between. Where it can, AI gets full speed. Where it must, a human holds the line.
Intent, acceptance criteria, judgment and final accountability.
Code, tests, documentation and variants, at speed.
Three tools to ship faster without losing control
The four flight zones
Route every work item to the right level of human involvement: Free, Guided, Paired or Held.
Flight zones → RhythmThe Kite Loop
A work rhythm that replaces the sprint. Every item runs its own loop: Frame, Fly, Check, Learn.
The Kite Loop → ResponsibilityHuman Anchors
A fixed set of responsibilities that deliberately stay human, written down so they do not quietly disappear.
Human Anchors →Every part of the kite has an owner
A team that neglects one part notices immediately. Without a Frame you build the wrong thing fast. Without a Tail, quality wobbles.
Frame
HumanThe spars that give it shape. Intent, boundaries, acceptance criteria and architecture rules.
Sail
AI, steeredCatches the wind. AI execution: code, tests, documentation and variants.
Tail
SharedKeeps it stable. Automated verification: tests, evals, checks and monitoring.
Line
HumanConnects it to the ground. Human judgment, customer contact and final accountability.
Start with one team and one product
You move from grounded to full altitude in four phases. Each transition has a gate with clear criteria, so nobody scales up before the previous phase works.
- About 2 weeks
Kite Scan
Baseline and interviews. Zones mapped.
- About 6 weeks
First flight
One pilot team. Brief, zones and loop running.
Gate 1
Pilot team chosen, baseline in place - About one quarter
Steady flight
Strengthen the Tail. Roles and metrics in place.
Gate 2
Rework not higher, team wants to go on - Ongoing
Full altitude
More teams on board. Internal Kite coaches.
Gate 3
Zone mix shifting, review load manageable
Durations are indicative and agreed per client. Each gate must be passed before the next phase starts.
Find out how high your team already flies.
In about two weeks, a few conversations and a short questionnaire give you a maturity level per part of the kite, a baseline of the six metrics and advice for your first flight.