A website, a mobile app or a content campaign is judged on what it produces: visitors who find the information, customers who order, teams that save time. This guide presents the project method we apply to web, mobile and digital media work, from initial scoping to maintenance.
1. Scope the need before designing
Scoping comes down to a few precise questions: who is the project for, what problem must it solve, which actions must it trigger, and how will those be measured. Then you review what already exists (traffic, most viewed pages, support requests, competitors) and the content already available. The deliverable is a short scoping document approved by the sponsor: objectives, audiences, main journeys, indicators. Without that step, every choice becomes an opinion.
2. A project method in short phases
The project moves forward in deliverable batches, each ending with a demonstration:
- scoping and functional perimeter;
- design: site structure, user journeys, mock-ups of key screens;
- development in iterations, with an accessible staging environment;
- user acceptance testing, fixes, optimisation;
- go-live, follow-up and skills transfer.
Each phase ends with written approval. New requests are logged and arbitrated: they join the current batch, a later batch, or fall outside the scope.
3. Define the scope and the deliverables
The scope describes what is produced: number of page templates, features, integrations, languages, forms, admin areas. Deliverables are listed by name: mock-ups, source code and repository access, written content, administration documentation, team training, backup procedure. A project without a deliverables list always ends with a discussion about what was included.
4. Plan and steer
The schedule relies on dated milestones and real dependencies: client content and technical access often drive progress. So you identify up front what the client must provide and by when, and you keep margin for acceptance testing. Tracking stays simple: a batch table, a short weekly meeting, a decision log. Scope changes go through a supplementary quote, not through a conversation.
5. Produce the digital media
The website is not enough: it has to be fed and amplified. Content production follows an editorial calendar aligned with the offers and the key moments of the business: texts, visuals, short videos, social posts. Formats, owners and frequencies are defined in advance, and you measure what works (traffic, contact requests, subscriptions). Visual identity and tone stay consistent across channels.
6. Acceptance, go-live and maintenance
Acceptance testing checks journeys on several browsers and devices, performance, SEO basics, accessibility and redirects. Go-live comes with a backup, a valid TLS certificate and a rollback plan. Then maintenance begins: security updates, uptime monitoring, tested backups, fixes and planned small improvements. It is framed as an hours allowance or a package, to avoid one-off interventions.
