A Two-Hour Marketing Change Can Still Take Five Days. Here’s Why. 

Imagine a campaign correction that needs two hours of active work. The request arrives on Monday morning, and the verified update is ready five calendar days later. 

This is an illustration, not an average industry. It shows why a small job and a quick job are not the same thing. Marketing change management has to account for both the work and the route the work takes. 

The wrong conclusion is that the team wasted the remaining time. The useful question is which intervals prevented the change from moving forward, and why. 

Put the task on a timeline 

The request may arrive before the offer of wording is settled. The approved change may then wait for access to the right editor. Review may happen in a scheduled batch. A final correction may need the same person who handled the original update. 

The active work across those steps can remain short while the elapsed duration grows. Non-working hours, weekends and work happening in parallel complicate the picture further. 

Do not subtract two person-hours from five calendar days and label the difference of wasted labour. They are different units. Define whether your elapsed clock uses calendar hours or agreed business hours and keep person-hours separate. 

Find the interval that blocked progress 

A workflow bottleneck is not simply the longest-looking blank space on a diagram. Ask whether another necessary activity was happening at the same time. 

If the page waited for review while essential content was still being approved, removing the review to wait alone might not have changed the launch date. If every remaining step depended on one routine update, that queue may have controlled the finish. 

This distinction keeps the discussion practical. The team needs to understand what delayed the outcome, not allocate blame for every hour on the calendar. 

Separate waiting causes 

Missing information, missing authority, and unavailable capacity need different responses. A better website update process should not treat them as one generic delay. 

• Missing information may need a clearer request.  
• Missing authority may need an agreed decision of owner.  
• A routine task waiting for scarce specialist time may be a candidate for an approved self-service route.  
• A high-risk change may still belong to a specialist, even when the wait is inconvenient. 

Use the reason for the wait to choose the intervention. ‘Work faster’ does not tell anybody what to change. 

Review the repeat pattern 

One awkward update can be an exception. A repeated category of awkward updates is more useful as evidence. Look at comparable requests: offer text, location details, existing-template variants or action-label corrections. 

Record the frequency, effort, elapsed duration, and quality outcome for each category. Avoid combining simple content edits with new functionality. Their requirements are different. 

The category that repeats often and needs predictable work is a better starting point than the change with the most memorable complaint. This helps marketing and IT agree on what can safely leave a shared queue. 

Test a shorter route, not just a faster editor 

For one bounded task, agree on approved fields, review conditions, permissions, and final checks. Then ask the intended user to complete a similar update. Count the help they need as part of the task. 

A fast edit followed by uncertainty about approval or publication is not complete in autonomy. Neither is a demonstration in which somebody from the vendor quietly resolves every obstacle. 

Compare the full route with the baseline. Keep defects and customer-team effort visible, so the improvement is not achieved by moving work elsewhere. 

Use the finding before the next campaign 

The most useful result may be a shorter request form, a clearer approval boundary, or a reusable content field. It may also reveal a task worth testing with Experience Suite. The product comes after the cause is understood. 

The next time somebody says an update will only take two hours, ask two questions: two hours of whose work, and how long until the customer sees a verified change? The answers describe different problems. Improving the right one is what makes the next campaign easier to run.