Quick answer: Before recommending or building anything, we evaluate go to market initiatives in a fixed order. Workflows first: understand the actual motion, buyers, handoffs, and signals. Friction second: find where time, data, or coordination genuinely breaks down. Outcomes third: define what measurable change looks like before a single workflow gets built. Reversing that order, starting with a tool or a target instead, is the most common reason GTM initiatives underdeliver.

Most GTM initiatives start backwards. A team decides it wants a new capability, an AI agent, a platform, a dashboard, and works backward from there to justify it. By the time anyone asks what problem it's actually solving, money and momentum are already committed. We use a different sequence, and it's deliberate: workflows first, friction second, outcomes third.

What does "workflows first" actually mean?

It means understanding the real GTM motion before touching a platform. Not the motion as described in a deck, the motion as it actually happens: how a buyer moves from first touch to closed deal, where handoffs occur between marketing and sales, what signals actually predict a good outcome versus a busy one.

This step gets skipped constantly because it's slower than jumping to a solution. But a tool applied to a motion nobody's actually mapped tends to optimize the wrong step, faster.

Why does friction come second, not first?

Because friction only means something once you understand the workflow it's disrupting. Teams that start with "where's our friction" in isolation tend to list symptoms: slow campaigns, missed handoffs, inconsistent data. Those are real, but without the workflow context, it's hard to tell which friction point is actually costing the business something versus which one is just annoying.

Once the workflow is mapped, friction becomes specific and diagnosable. Is the friction in coordination, two systems that technically connect but don't actually share the right data. Is it in time, a manual step that a team repeats every cycle. Is it in data, information that exists somewhere but isn't reaching the person who needs it. Each type of friction points toward a different fix, and none of them point toward "buy a smarter tool" as the default answer.

Why does defining outcomes come last?

Because an outcome defined before the workflow and friction are understood is usually a guess dressed up as a target. "Increase efficiency" or "improve pipeline" sound like outcomes, but they're not measurable until they're tied to the specific friction point an initiative is meant to resolve.

Outcomes third means defining, concretely, what changes if the initiative works. A specific metric, a specific process that shortens, a specific handoff that stops dropping leads. That specificity is what makes it possible to actually know afterward whether the initiative delivered anything, instead of everyone agreeing it "felt like progress."

Why does the order matter more than the individual steps?

Because each step depends on the one before it. Friction is meaningless without workflow context. Outcomes are meaningless without a real understanding of the friction they're meant to resolve. Skip a step or run them out of order, and the whole exercise turns into solving a documented process gap.

This is also why the sequence is worth applying to every GTM initiative, not just AI ones. A new attribution model, a new lead scoring system, a new campaign tool, all benefit from the same discipline. The tool is never the starting point. It's what gets selected once the first two steps have actually been done.

What this looks like in practice

A team considering an AI agent for account prioritization, applying this framework, starts by mapping how accounts actually get prioritized today: who decides, what data they use, where the decision breaks down. Then it identifies the specific friction, maybe reps are prioritizing by gut feel because the data that should inform prioritization is scattered across three systems. Only then does it define the outcome: accounts prioritized consistently, using the same criteria, in under a set number of minutes instead of an afternoon of manual review.

That's a very different starting point than "we should get an AI tool for account prioritization," and it's the difference between an initiative that sticks and one that gets quietly abandoned two quarters later.

FAQ

What does "workflows first, friction second, outcomes third" mean? It's a sequencing framework for evaluating any GTM initiative. Understand the actual workflow before anything else, identify where friction genuinely disrupts that workflow next, and only then define the measurable outcome an initiative should produce. Selecting a tool or platform comes after all three steps, not before them.

Why shouldn't a team start with a specific tool or platform? Starting with a tool skips the diagnostic work that determines whether the tool solves a real problem. Teams that start with a tool tend to apply it to whatever friction is most visible, which isn't always the friction that's actually costing the business the most.

How is this framework different from typical process improvement approaches? The key difference is strict ordering. Many frameworks treat workflow mapping, friction identification, and outcome definition as parallel or interchangeable steps. Doing them in this specific sequence, workflows, then friction, then outcomes, ensures each step is grounded in the one before it rather than run in isolation.

Can this framework apply to something other than AI initiatives? Yes. It applies to any GTM investment, a new platform, a new attribution model, a new campaign process. The discipline of understanding the workflow and the friction before defining success is useful regardless of what's being evaluated.