The direction is approved and you want the project to move. But who gathers the information? How much time will you need to give it? And what happens when people disagree? Follow a launch for a fictional provider of first-aid training for companies. The offer already exists. The work is a landing page, an inquiry form and campaign assets. This is an illustrative scenario, separate from the real projects in Work.
An engagement becomes easier to manage when everyone knows what they need to contribute, what they can decide and what must be checked before moving on.
1. Start by agreeing on what needs to be ready.
In this example, the person organizing staff training needs to understand the offer and request a suitable proposal. The page explains who the course is for, how it works and what information is needed for a quote. The form must send the inquiry to the person who will handle it.
NOT MORE. coordinates copy, design and implementation. The client appoints a coordinator and a course expert who can validate the information. At the end of the opening conversation, we record the deliverables, required access, decision-maker and completion criteria. These decisions become the working plan.
2. Client time belongs in the plan.
“Will I have to chase the whole project?” is a reasonable concern. In this scenario, NOT MORE. tracks dependencies and next actions. The client coordinator gathers source materials, answers business questions and provides one consolidated set of feedback.
To make the example tangible, we reserve one hour at the start and two 30-minute reviews. Preparing materials and the expert’s factual review take additional time. These are assumptions for this fictional project, not a universal estimate. In a real engagement, the work and people’s availability determine the schedule.
If the expert cannot review copy until the following week, production needs to account for that dependency. A credible deadline includes time for answers.
3. When opinions differ, return to the decision.
At the first presentation, sales asks for more course detail while leadership wants a shorter page. We put the question in context: what does the person choosing staff training need to know now, and what can come later in the proposal?
The team proposes a hierarchy: essential information first, practical details further down and a visible next step. The expert checks accuracy, the coordinator gathers comments and the named decision-maker approves. We record the reason for the choice so the same debate does not restart with every format.
4. A new request comes with an explicit choice.
During production, the client asks to include a course for parents. The audience, message and form may all need changes. First, we estimate the additional work and dependencies.
We could keep the company launch and schedule the new course separately. We could replace part of the agreed work if that better serves the priority. Or we could expand the project with an approved budget and timeline. The right choice depends on resources and what matters now.
If essential launch information is missing, we identify what is blocked, what can continue and how the schedule changes. Review rounds, response windows and commercial terms are agreed in the project proposal.
5. At launch, check the delivery. Then review the response.
Before publishing, we check the approved content, page across screen sizes, form delivery, confirmation and asset exports. The files and instructions are handed over with ownership of the next steps. A form that reaches its destination satisfies a delivery criterion.
Inquiry quality needs a different review. Who requested a proposal? Could they be reached? Was the course suitable? What happened after the quote? Some of that evidence comes from commercial conversations. If the response is disappointing, we examine the message, journey and offer against the available evidence before recommending a change.
Who monitors results and which improvements are included after launch are agreed separately. This example does not assume an increase in enrollments or revenue.
One launch, four decision points.
The same team can work more clearly when each stage has an agreed contribution and decision.
| Moment | NOT MORE. | Client | Decision |
|---|---|---|---|
| Start | Structures deliverables and dependencies. | Confirms offer, access and decision-maker. | What to deliver and under which conditions. |
| Prototype | Proposes the message and page structure. | Validates information and consolidates feedback. | What moves into production. |
| Handover | Checks implementation and organizes files. | Confirms content and inquiry ownership. | What is ready and who takes over. |
| Review | Analyzes evidence within the agreed engagement. | Brings commercial feedback and context. | What to keep, investigate or change. |
These roles and stages are illustrative. A smaller project may need fewer people; a more complex one may need additional reviews.
What to clarify before starting
What must exist at handover and how completion will be checked.
Who supplies information, who coordinates and who can approve.
When materials, access and people will be available for feedback.
How new requests are decided and who takes over after launch.
You may need direct execution on an approved brief, or a team that connects several disciplines. The opening conversation should establish how much responsibility we take on and what stays with you. That gives both teams a workable foundation for the engagement.