The KVN Methodology — Project Management with Kavanah

Every act of delegation is, in some sense, an attempt to put intention into another head — human or machine. When the intention transfers cleanly, the work comes back recognizable. When it does not, you get drift: well-executed output that solves the wrong problem. KVN names the three axes along which the transfer most often fails, and forces the delegator to be explicit on each.

K — Know-How

Know-How is what the doer needs to be capable of, plus the context they need access to. It answers the question 'do they have what it takes?' before the work begins.

This includes obvious things — relevant skills, prior code, the right credentials, a deployable environment — and less obvious things — the customer's history, the institutional taste, the embarrassing decisions made last quarter that nobody wants to repeat. Know-How is the bag of context and capability the doer carries into the work.

The failure mode Know-How prevents is the silent skill mismatch. You hand a task to someone (or some agent) who plausibly could do it but does not have the specific context the work depends on. They produce something that looks right at a distance and is wrong in a way only the institutional memory would catch. Explicitly naming Know-How — even as a one-line 'needs access to the staging Postgres and familiarity with our auth middleware' — surfaces the gap before it costs you a week.

V — Vision

Vision is the end-state the work is in service of. Not the task description — the outcome. A task says 'implement endpoint X.' A vision says 'so a logged-in customer can finish checkout without leaving the SPA, even on a flaky connection.' The difference is enormous.

Vision is where most management instruction stops too early. The doer hears the task and runs. The doer does not hear the end-state, and so cannot use judgment when the task description is incomplete — which it always is. Without Vision, every small ambiguity becomes a request for clarification or, worse, a guess that resolves in the wrong direction.

Vision is also what lets the AI-amplified worker correct themselves. When an agent encounters a fork — 'should this be a 401 or a 403 here?' — it can answer from the Vision if you have stated one, and from its own priors if you have not. The priors will be plausible. They will sometimes be wrong. The Vision is the only mechanism that keeps the work pointed at your outcome instead of the model's defaults.

N — Negation

Negation is the boundary the work must not cross. The things explicitly out of scope. The trade-offs the doer is not authorized to make. The patterns this team has rejected and does not want to relitigate. Negation is the hardest of the three to write because it requires you to have already learned the lesson at least once.

Every management framework tells you to say what to do. Almost none teach you to say what not to do. The result is doers who, in the absence of explicit nos, fill the gap with their own preferences — often by reaching for the most recently learned pattern, even when the team has already debated and rejected it.

Negation is what makes a delegation safe to leave alone. With Know-How and Vision but no Negation, you have to check in on the work, because you do not know which trade-offs the doer might quietly make on your behalf. With Negation written, the doer (human or AI) can charge ahead at full speed inside the fence and stop cleanly at the edge. Negation is the axis that turns supervision into trust.

Why all three, and why now

Any single axis on its own underdetermines the work. Know-How without Vision produces capable people doing the wrong thing. Vision without Know-How produces ambitious people who cannot execute. Vision without Negation produces ambitious people who execute beyond their authority and ship a regrettable decision. Know-How and Negation without Vision produces well-bounded, capable people doing something that has no point.

The three together compose. Know-How fixes the floor — the work is at least possible. Vision sets the ceiling — the work is in service of something. Negation draws the walls — the work cannot wander outside the room.

Kavanah forces KVN at three scopes because each scope leaks into the next. The workspace charter — your standing K, V, and N for the company — is the default every project inherits. The project charter — K, V, and N for this project — refines the workspace defaults to the project's specifics, including the project's 'false friends' (other projects that look similar and are not). The task K, V, and N — set when needed, generated by AI for routine work — is the per-delegation override. When a question comes up mid-work, you ladder up: check task KVN, then project KVN, then workspace KVN. Almost always the answer is already written down once. The hard part was writing it.

KVN is the spine of everything else in this course. Auto-task generation uses Vision and Negation to decide what becomes a task and what does not. Capability-aware assignment uses Know-How to route. Metrics measure whether each axis is actually doing its job. From here on, every lesson assumes you have a draft charter to refine, not a blank page.

K — Know-How

Know-How is what the doer needs to be capable of, plus the context they need access to. It answers the question 'do they have what it takes?' before the work begins.