What working together looks like
Most engagements start with uncertainty, not a tidy brief. The work is to reduce that uncertainty fast, decide what matters and turn the answer into something the team can use.
That means the early part of the engagement is usually less about producing output and more about reading the shape of the problem properly. Where is the confusion coming from? What is the market saying back? Which parts of the story are real, and which parts are just carrying old assumptions forward?
Start with the decision
We begin by identifying the commercial decision that is stuck, the evidence already in play and the outcome that would make the work worthwhile.
That might be a positioning choice, a launch decision, a sales problem or the need to stop the team from spending time on the wrong kind of work.
Choose the right shape
Some problems need a sprint, some need advisory rhythm and some need a short diagnosis before either makes sense. I will be direct about which one fits.
The right format matters because the cost of overworking a small problem can be just as real as the cost of underworking a large one.
Make the trade-offs explicit
Good GTM work usually requires narrowing the audience, changing the narrative or simplifying the motion. We will name the trade-off instead of hiding it.
The fastest way to weaken a commercial idea is to pretend every choice is available at once. The strongest work usually comes from narrowing with intention.
Leave something usable behind
The value is in the asset, system or decision that remains after the conversation: a clearer narrative, a better tool, a field-ready message or a next-step plan.
When the engagement ends, the team should not just have answers. They should have a cleaner way of making the next decision without starting from zero again.
How the process usually runs
The exact shape changes by mandate, but the rhythm is usually consistent enough to be predictable and light on ceremony.
There is a practical reason for that. Most teams already have enough noise in the system. What they need from an external operator is not another layer of process, but a way to cut through the fog and leave behind a sharper decision.
-
Fit conversation We talk through the constraint, the market context and the decision you need to make. If there is not a real problem to solve, I will say so. That first conversation is part diagnosis, part calibration. It helps both sides see whether the issue is strategic, tactical or simply a sign that the team needs better operating discipline.
-
Diagnostic pass I review the available material, surface the patterns and identify where the narrative, motion or process is breaking down. This is where loose observations become evidence. Patterns matter more than isolated comments, and the best diagnoses often come from connecting several small signals that were not being read together.
-
Working session We make the key choices together, usually through a focused call, workshop or asynchronous review depending on the task. The goal is not theatre or consensus for its own sake. It is to make the decision durable enough that the team can keep using it once the meeting has ended.
-
Build and refine I turn the agreed direction into the deliverable: a positioning system, launch asset, enablement pack, page or operating structure. This is where the thinking becomes tangible. If the work cannot survive contact with a real team, a real buyer or a real deadline, it was never finished enough.
-
Handover You get the finished output plus the reasoning behind it, so the team can use it without depending on me to translate every decision. A good handover should lower dependency, not create it. The team should leave with the asset and with enough context to defend it internally.
Typical engagement types
Different problems need different levels of intervention. Most of the work falls into a small number of shapes, each with a different level of intensity and output.
That is useful because it avoids overpromising. Not every situation needs a large engagement, and not every problem is solved best by a short burst of activity. The shape should fit the cost of the mistake.
Diagnostic engagement
Used when the team knows something is off but does not yet have a shared read on the real problem. The output is usually a clear diagnosis, a set of priorities and a recommended route.
This is the right format when the issue is more about clarity than capacity.
Sprint engagement
Used when the team needs a defined intervention with a concrete deliverable at the end. Good for positioning, launches, sales enablement and other work that needs to move fast.
It works best when the problem is bounded and the team wants momentum without dragging the work through a long cycle.
Advisory engagement
Used when the team has a live roadmap or recurring decisions and needs a senior sounding board to pressure-test choices, language and trade-offs as the work unfolds.
This tends to suit teams that already know the terrain but want a sharper external read on what matters.
Operating support
Used when the issue is not a single project but the way GTM work is being run. The goal is to create a clearer operating rhythm, better inputs and a more durable system.
That can include better briefing, cleaner decision paths, more usable assets and less repetition across the team.
What I expect from the team
Strong collaboration is not frictionless, but it should be simple.
The best engagements are usually the ones where people are willing to be honest about constraints rather than performing certainty. That makes the work better and usually faster too.
Access to context
Shared docs, relevant calls, current assets and enough commercial history to understand what has already been tried.
It is hard to improve a system you cannot see. The more of the real context I can get, the more useful the work becomes.
Fast feedback
Clear responses on direction, constraints and trade-offs so the work can keep moving instead of waiting on committee drift.
Long pauses often create more confusion than complexity does. Timely feedback keeps the work grounded in the live business problem.
A real owner
Someone internally who can make decisions, gather input and keep the work connected to the business problem that justified it.
Without a clear owner, even a good engagement can become an interesting document rather than a useful shift in behaviour.
Permission to simplify
GTM work improves when we are allowed to cut noise, discard vanity requirements and protect the sharpest answer.
Simplicity is not a reduction in quality. In this kind of work, it is often the proof that the thinking has become clearer.
If that sounds like the right kind of collaboration, let’s talk.
Send me the context, the deadline and the decision you are trying to make, then we can decide whether a sprint, advisory rhythm or something else is the right shape.
Start a conversation Home