mogkit

Wedge · 5/5

Stakeholder & Conflict

Name the incentive before you argue the position.

knowledge engine: coming · standalone skills shipped

The problem

When a decision stalls, the room usually argues about the surface question — build vs buy, ship now vs ship later — while the real disagreement sits underneath: who owns the call, whose quarter takes the hit, what nobody wants to say out loud. Most senior PMs eventually learn to map this out by feel. mogkit ships the structured version so you don't have to wait for the seniority.

The level-up path

Two standalone skills:

  • stakeholder-map — for each stakeholder, their stated position and their likely role-level incentive; the real fault line under the surface argument; the minimum set of conversations that would actually unblock the situation. Names dynamics; never scripts manipulation or persuasion tactics.
  • tradeoff-frame — once you can see the real disagreement, this exposes the axes the options optimize against and the evidence that would actually move a reasonable person. Frames; does not pick.

A note on the knowledge engine

No stakeholder-side engine in v1. Stakeholder dynamics change too fast for a versioned graph to be the right model, and the failure mode of such a tool (writing scripts to “manage” specific named individuals) is exactly what mogkit shouldn’t ship. The standalone skills name the dynamic; you handle the room.

Visual setup walkthrough

  1. npx mogkit init my-conflict-workspace (or use any existing mogkit workspace; these skills don’t need a corpus).
  2. Paste the decision and the stakeholders into stakeholder-map. Get back the map.
  3. If the call is still contested after that, paste the options into tradeoff-frame. Get back the axes.
  4. Walk into the room as yourself. The map is diagnosis; the conversation is yours.

Skills to install

stakeholder-map

intermediate
standalone conflict

Maps the stakeholders around a decision — each one's stated position, the likely underlying incentive, where the real disagreement sits (often not the surface one), and the minimum set of conversations to unblock. Names dynamics; never scripts manipulation.

tradeoff-frame

intermediate
standalone conflict

Frames a contested decision honestly — names the real axes of disagreement, what each option optimizes versus sacrifices, whether the decision is a one-way or two-way door, and the evidence that would actually move a reasonable person. Frames; does not pick.

All of these install automatically when you run npx mogkit init.

Material

A curated path. Not a link dump.

    by Roger Fisher & William Ury

    Separate positions from interests. The foundational mental model behind `stakeholder-map` and most senior PM disagreement work.

    by Jeff Bezos

    Source material for one-way / two-way door decision making, customer obsession, and operating-tempo language. Read them in sequence.