Who Does What, When, How and Why?

A process needs more than steps

Good process clarity answers a handful of practical questions. What needs to happen? Who owns each action? When must it happen? How should it be done? Why does it matter? Who or what does it depend on? What happens if something changes or goes wrong? If the people involved cannot answer these questions consistently, the process is not yet operationally clear.

In retail, a seasonal campaign provides a useful example. The activity may involve buying, merchandising, marketing, ecommerce, supply chain, store operations, finance and suppliers. Each team has a legitimate part to play, but a campaign only comes together if the dependencies are understood. Marketing cannot promote stock that has not been confirmed. Stores cannot execute a display without instructions and materials. Ecommerce cannot publish accurate product information if the details are still changing.

Each team may complete its own task correctly, yet the overall outcome can still fail because the work is not coordinated. That is why process design must consider the joins between activities, not just the activities themselves.

Time-critical work needs a shared calendar

Some work is particularly vulnerable to timing. Promotions, range launches, price changes, seasonal displays, compliance checks, event programmes, booking releases and supplier deadlines all rely on activity happening in the right sequence. If one milestone slips, the impact can ripple through the rest of the plan.

A shared calendar or activity planner can make those dependencies visible. It should show key dates, lead times, deadlines, decision points and the owners responsible for each milestone. It should also make clear which dates are fixed, which are provisional and what needs to be completed before the next stage can begin.

The calendar is not simply a list of dates. It is a coordination tool. It helps teams see what is coming, understand how their work affects others and raise risks early enough for someone to do something about them.

A calendar only works if it is maintained and trusted. There must be clarity about who updates it, where the authoritative version lives and how changes are communicated. If teams keep separate calendars or learn about a deadline change through an informal message after the fact, the tool becomes another version of the truth rather than a shared one.

Make dependencies and handovers visible

For every important milestone, ask what must be true before it can happen. What information, approval, stock, creative asset or decision is required? Who provides it? Who confirms it is complete? Who takes ownership next? These questions reveal the dependencies that are often invisible until something goes wrong.

A practical handover should identify the next owner, the action required, the deadline and any outstanding risks or decisions. It should not rely on someone noticing an email, remembering a conversation or assuming that another department has seen a change.

It is also worth agreeing how exceptions are handled. What happens if a supplier misses a date, stock is delayed, an approval is not forthcoming or a customer issue needs an urgent decision? A process that describes only the ideal path leaves people guessing the moment reality deviates from the plan.

Explain the why, not just the what

People are more likely to follow a process intelligently when they understand its purpose. If colleagues see a step as pointless administration, they may skip it, work around it or complete it mechanically without noticing when something is wrong.

Explaining why a task matters helps people understand the consequences of delay or error and use their judgement when circumstances change. For example, a deadline for confirming promotional prices is not an arbitrary date if it protects accurate tickets, online information, margin and customer trust. Understanding that connection helps teams make better decisions when the plan is under pressure.

This is not an argument for documenting every minor task in exhaustive detail. Over-engineered procedures can become as unhelpful as vague ones. The level of detail should match the complexity, risk and frequency of the activity. Routine work may need a simple checklist; a cross-functional, time-critical launch needs clearer milestones, dependencies and escalation routes.

Build the process with the people who use it

The people closest to the work often know where the process really breaks down. Involve them in mapping it, testing it and improving it. Ask where they wait for information, which steps are duplicated, what regularly gets missed and which decisions are unclear. This produces a more realistic process and helps build ownership rather than imposing another procedure from above.

Once agreed, make the process easy to find and use. Give it a named owner, a review date and a straightforward way for people to flag problems. When the process changes, communicate what is different, why it has changed and what people need to do as a result.

Consistency does not come from a process document alone. It comes when people understand the work, their role in it, the timing, the dependencies and the reason it matters. Clear processes and shared calendars create the structure. Clear ownership and communication make that structure work.