Built by operators, for operators

Waya OS MCP

The diagnostic frameworks that find your real constraint — then get to the root of why it's stuck. Running right inside the AI assistant you already use.

The Challenge

Most improvement work is busy work aimed at the wrong target. Teams pour effort into what they understand and control, the loudest complaint gets the budget, and a month later the main number still hasn't moved. When a problem does get attention, the fix usually chases a symptom — because no one stopped to ask why it's really happening.

Waya OS puts the diagnostic method inside the assistant you already use. Two moves do the heavy lifting: find the one constraint that's actually blocking the goal, then get to the root of why it's stuck — with the evidence to back it up. Aim before you fire.

An operator at a whiteboard mapping a system to find the bottleneck

See it in action

Watch a diagnosis run

A short walkthrough of Waya OS finding a constraint and drilling it to root cause — live, inside the assistant.

Wayaframes

Point the tool, then dig

Connect the MCP once and these become commands in your AI assistant. Each one facilitates a proven method with you, step by step, and hands you a real deliverable at the end.

/constraint-identification

Constraint Identification

Every system has exactly one constraint relative to a goal — one thing that, if you improved it, would move the number more than anything else. This Wayaframe locks in the goal, maps the system, pressure-tests your candidates against the comfort-and-control bias, and validates the real bottleneck before you spend a dollar attacking it. Then it points you at the right way to fix it.

/gap-analysis

Gap Analysis

A vague, contested problem becomes a validated set of root causes. It solidifies the problem against SMART-P criteria, picks the right method — 5 Whys for a contained issue, Fishbone when it crosses departments — and facilitates the analysis until the causes are actionable and evidence-based. The output you can defend later, not a hunch.

/a3-thinking

A3 Thinking

The master frame the others run inside. Adapts depth to the problem — a fifteen-minute quick pass or a full engagement — and opens the narrower methods at the right step. The default entry when you're not sure where to start.

/experiment-design

Experiment Design

Turns validated root causes into small, testable experiments with clear success criteria and a real test–learn–revise loop.

/impact-effort

Impact–Effort

Ranks competing options — gaps, experiments, fixes — by impact against effort, so you act on the two or three that matter and park the rest.

How it fits together

Aim. Diagnose. Fix.

The frameworks work stand alone or as a sequence. Each framework hands it off to the next if necessary, and Waya routes you to the right steps so you don't skip the one that you need.

Step 01Aim
/constraint-identification

Find the one constraint blocking the goal and validate it moves the number. Most companies never do this — they attack whatever's loudest.

OutputA named, validated constraint — and where to point next.
Step 02Diagnose
/gap-analysis

Now that you know where, get to why. Drill the constraint to root causes you can defend with evidence.

OutputValidated root causes, via 5 Whys or Fishbone.
Step 03Fix
/experiment-design/impact-effort/a3-thinking

Turn root causes into experiments, rank them by impact and effort, and run the test–learn–revise loop. Break this constraint and the next one surfaces — the loop begins again.

OutputPrioritized experiments with clear success criteria.

Not sure which step you're on? Start with /a3-thinking — it opens the right method for you.

What it looks like

From "everything's on fire" to one validated cause

The setup. Goal: grow monthly revenue from $500K to $800K this quarter. Three teams each swear they're the bottleneck. Ops has already cut its error rate from 50% to 5% — and sales still hasn't moved.
Step 01Constraint ID

Candidates get pressure-tested against the goal. Ops improved and the number didn't move — so ops wasn't the constraint for this goal. Upstream test: sales isn't slow, it's drowning in unqualified leads.

FoundConstraint: lead quality. 60% of pipeline is unqualified; sales closes 40% of qualified leads and 3% of the rest.
Step 02Gap Analysis

Drill why lead gen produces 60% unqualified leads. A 5 Whys chain traces it to a targeting spec no one owns.

FoundRoot cause, with evidence — not a hunch.
Step 03Fix

Design an experiment on the targeting spec, size it against the alternatives with impact–effort, run it, watch the goal metric. If revenue moves, the constraint was real. If it doesn't, back to Step 01 — and that's the method working, not failing.

NextA prioritized experiment tied to the number that matters.

Every figure here is illustrative — the point is the sequence, not the numbers.

Getting Started

Connect it once, use it forever

Waya OS works with any AI assistant that supports MCP, like Claude. Connect it once and the Wayaframes show up as commands you can invoke any time. Free to connect — no payment, no seat.

  • 01Connect Waya OS: follow the setup guide to add the Waya OS MCP (pro-mcp.wayaframes.com/mcp) to your assistant, then sign in.
  • 02Aim: run /constraint-identification to find the one thing actually blocking your goal — or /a3-thinking if you're not sure where to start.
  • 03Diagnose: run /gap-analysis on the constraint to reach root causes you can defend.
  • 04Fix: turn causes into tests with /experiment-design, rank them with /impact-effort, and run the loop.

The number doesn't move by working harder. It moves by working on the right thing.

Waya OS finds the one constraint that's actually in the way, gets to the root of why, and points you at the fix — inside the assistant you already use. Free to connect.

Add Waya OS

Frequently Asked Questions

Everything you need to know about Waya OS

What is Waya OS?

It's a Waya MCP — a small server you connect to your AI assistant — that adds a set of Wayaframes: guided, step-by-step diagnostic frameworks the assistant runs with you. It helps you find the one constraint blocking your goal and get to the root of why it's stuck, instead of guessing from a blank chat.

What is a Wayaframe?

A Wayaframe is a facilitated framework that runs inside your AI assistant. Instead of a blank chat, the assistant walks you through a proven method — asking the right questions in the right order — and produces a real deliverable at the end: a validated constraint, a set of root causes, a ranked list of experiments.

What's the difference between constraint identification and gap analysis?

Constraint identification is the compass: of everything you could work on, which one thing actually blocks the goal? Gap analysis is the drill: given that thing, why is it happening? You point with one and dig with the other.

Who is this for?

Founders, operators, and leaders past the earliest stage — anyone whose improvement work isn't moving the main number, who's deciding where to spend scarce resources, or who needs a diagnosis that holds up later. It's domain-independent: operations, sales, hiring, support, finance, product.

What does it cost?

Waya OS is free to connect today — no payment and no seat. When you want a specialist to run the diagnosis with you, you can schedule a call.

What do I need to run it?

An AI assistant that supports MCP, such as Claude. You connect the Waya OS connector once, and the Wayaframes become available as commands you can invoke any time.

Find the real constraint

Connect Waya OS and run your first diagnosis today. When you want a specialist in the room, we're right here.