Human Network Testing Network

Read the campaign story

The source-backed story begins with a credibility problem: Vi wanted people to reconsider network quality after post-merger difficulties. Rather than relying only on another technical endorsement, it recruited people whose everyday work depended on navigating Mumbai. The published account describes testing data and calling experiences as well as entertainment uses. D&AD credits Ogilvy India and Hungry Films. Its later award entry reports a commercial improvement, but the public material does not establish a controlled causal evaluation.

Editorial interpretation: the partnership connects two meanings of network. One is technical infrastructure; the other is coordinated human knowledge. This makes an otherwise abstract service test easier to picture. The couriers are more than recognizable faces when their routes actually reveal difficult locations. That distinction is central: borrowing their reputation without collecting useful observations would leave a testimonial, not a convincing demonstration.

A second interpretation concerns the order of operations. Listening for weak spots can make the communication useful to the engineering team before it becomes useful to advertising. A marketer adapting this idea should be willing to publicize limitations and repairs, not simply edit the exercise into uniformly positive footage. A reliable service is not the same thing as a service that never fails.

A useful follow-up question is whether the partner remains involved after launch. A one-off journey can create a strong story, while ongoing feedback can expose changing conditions. For another brief, decide explicitly whether the partnership is a demonstration, a research panel or a continuing service channel. Each needs different resources and promises.

Choose witnesses with relevant exposure

Recruit people who encounter the service under conditions customers care about. For a connectivity product that means different journeys, building types and times, rather than a sample of enthusiastic fans. Define which observations are subjective and which can be logged consistently. A trusted occupation provides narrative relevance, but does not automatically create a representative sample. Ask what part of the market the witnesses cannot see. That missing coverage should shape both the next research round and the language of the eventual claim.

Make defects part of the brief

Design a route for a reported problem to reach an operational owner. Give every observation a location, approximate time, service task and resolution state without exposing personal movements publicly. The creative team should receive aggregated patterns, not unnecessary identifying data. Include unresolved issues in the internal review. Otherwise the exercise can become an expensive endorsement collection that fails to improve the experience. Credibility depends on showing that a participant can report a bad experience without being excluded from the final story.

Separate trust transfer from performance proof

A familiar partner may improve willingness to try a service even when the technical changes are modest. Measure those two effects separately. One survey can ask whether the partnership makes the test believable; another task can measure whether connectivity meets a predefined standard. Acquisition changes need comparison markets and consideration of price promotions, distribution and competitor activity. Treat an award-entry business result as a reported association unless its method supports a stronger conclusion. This distinction protects both marketing decisions and the dignity of the partner.

A small test for another brief

Proposed adaptation: a local service business could invite a small, paid panel of regular users to document one frustrating journey for two weeks. Choose a bounded service area, agree a clear consent process and provide a simple reporting form. First collect a baseline without advertising. Then fix one repeated problem and ask the same panel to repeat the task. Publish a short account of what changed, what did not and how customers can report exceptions. Do not ask participants to praise the business or make payment depend on positivity. A modest, honest operational improvement is a stronger prototype than a citywide endorsement claim.

Compare successful task completion, repeat failures, resolution time and credibility ratings before and after the fix. Keep acquisition observations separate from technical outcomes.

Pause publication if observations cannot be verified, if participants feel pressured to endorse the service, or if location data creates privacy risk.