How to define requests, statuses, deliverables, channels and owners so marketing operations can coordinate, measure and learn precisely.
Start with the objects that run through the work
Objectives, initiatives, campaigns, requests, deliverables, assets, channels, audiences, approvals and results are not synonyms. Every object needs a definition, identifier and relationships. A campaign may contain requests; a request may produce several deliverables; an asset may appear across channels. When everything is called a task, the organization loses hierarchy and cannot reconstruct why something happened. The model must represent real work without automatically copying a tool's structure.
An operation becomes visible when teams and systems use the same names for the same things. The taxonomy defines objects, request types, statuses, priorities, channels, deliverables and owners. This is not an administrative exercise: it reveals what is happening, enables automation without confusion and compares times or results without mixing different kinds of work.
Design request types with minimum inputs
A social asset, sales proposal, paid-media campaign and PR response need different information. Each type defines mandatory fields, an initial owner, SLA, stages and closure criteria. The form should request what is needed to start without making the requester a process expert. Conditional questions reduce noise: if publication is involved, request channel and date; if spend is involved, request market, objective and confirmed budget.
Statuses should describe observable conditions
In progress often means something different to each person. Useful statuses indicate what happened and what remains: received, triage, awaiting information, prioritized, in production, internal review, client approval, scheduled, published or closed. Each transition has an owner and, where appropriate, evidence. Work should not be marked complete if it still awaits publication or measurement. Precision reveals queues without chasing updates in chat.
Separate priority from urgency and impact
Urgent describes time; impact describes consequences; priority expresses the agreed order. Mixing them turns every noisy request into critical work. A matrix can consider objectives, fixed dates, dependencies, risk, effort and value, with clear authority to resolve conflicts. Priority changes are recorded with their reasons and effects on other deliveries. The organization then sees the cost of interruption, beyond the new request.
Version the taxonomy as an internal product
Names change as new channels, products or responsibilities appear. Every modification needs an owner, date, migration and communication. Before adding a field, verify which decision it will enable; before removing one, review dependent reports and automation. Wiwo.Ops can embody the taxonomy in templates, statuses, roles and dashboards, but the system works only when people understand and use the definitions.
