When marketing, sales and operations understand things differently

Listen to how each department describes the same situation

In a service company, sales may consider a delivery complete when it sends the material. Operations may await the customer’s review, while marketing needs to know whether the work can be mentioned publicly. All three people use a familiar word to describe different states. A shared view will reveal the disagreement, but will not resolve it by itself.

Ask each department to reconstruct a recent situation in its own words. Note what happened, which information it received and what it expected from the next person. Preserve the differences while investigating them. Replacing them too quickly with a shared label may hide a condition someone considers essential. If a status requires approval, specify whose; if it means a submission, identify what was sent and to whom. The aim is to recognize the fact behind each term.

Frame a question that supports a decision

A request such as we need visibility leaves several conversations open. One person may need to know what can be communicated; another, which work should continue; another, which commercial commitment remains pending. Combining these interests in one indicator may produce a seemingly clear figure that offers little help in taking action.

First write the decision: what do we want to be able to do once we have the answer? Then identify the evidence needed to make it. To decide whether a deliverable may be publicized, for example, the relevant authorization matters alongside operational progress. To plan pending work, consider commitments and reviews still requiring action. Both questions may use related information without needing exactly the same interpretation. This distinction helps prioritize the project and identify who should participate in defining it.

Turn the agreement into a reference people can consult

A useful discussion leaves examples other people can use. Describe what each relevant status means, what confirms it and which cases need review. Include one situation meeting the definition and another that does not yet meet it. This comparison often clarifies more than a definition composed only of general terms.

Also agree who will maintain this reference when the service changes. A definition may be correct initially and later stop representing what happens. If an exception becomes frequent, review the agreement with those who understand it before creating another label. Continuity depends on people being able to explain a status and find the information supporting it.

• Who can confirm the fact and what information they need.
• Where the team keeps its authoritative reference.
• How a disagreement is reviewed and a change communicated.

Bring resolved distinctions into an evaluation with Wiwo

Wiwo connects strategy, technology and operations within its offer. Bring these situations to a scoping conversation and ask for the solution to be evaluated against the agreed decisions. Depending on the need, it may make sense to review work organization in Ops, information analysis in MetriQ or specific development and integration.

Ask to distinguish what a tool can show from what your organization still needs to decide. Service definitions and commercial authorizations need owners within your team even when technology assists. When reviewing the proposal, return to the initial examples: each department should recognize what it can do with the information and when it needs to consult someone else. This shared understanding provides a more concrete basis for discussing features, permissions and deliverables.