---
id: "entity-unilever-d1"
type: "entity"
entityType: "organization"
canonicalName: "Unilever"
aliases: ["Project Shakti", "Shakti Project", "Hindustan Unilever"]
source_timestamps: ["¶16"]
tags: ["consumer-goods", "case-study", "india"]
related: ["concept-asynchronous-information-engineering", "action-engineer-asynchronous-flow"]
sources: ["tail1"]
sourceVaultSlug: "hbr-seg-tail1"
originDay: 1
articleStem: "hbr-tail-108-decision-revolves-around-hq"
sourceUrl: "https://hbr.org/2026/05/what-global-companies-lose-when-decision-making-revolves-around-headquarters"
sourceTitle: "What Global Companies Lose When Decision-Making Revolves Around Headquarters"
---
# Unilever (Shakti Project)

## Unilever (Project Shakti)

**Role in this source:** *Positive case study* for engineering asynchronous information flow.

Unilever recruited a network of **rural Indian women as distributors** — the **Shakti Project**. These women provided **real-time, structured** observations on consumer behavior and price sensitivity, which flowed **directly to leaders in London and Rotterdam**, replacing reliance on external consulting firms and letting HQ anticipate market shifts.

This is the exemplar behind [[concept-asynchronous-information-engineering]] and the recommendation [[action-engineer-asynchronous-flow]].

**Enrichment / nuance:** Unilever is a global consumer-goods company; **Project Shakti** is a well-documented rural-India initiative recruiting women micro-entrepreneurs as distributors and brand promoters, yielding granular insight on rural consumer behavior that informs adjustments to **pack sizes, pricing, and promotions**. **Caveat:** public sources frame Shakti primarily as a *distribution and empowerment* program; the article's specific claim that it “bypassed consulting firms” and fed intelligence directly to HQ leaders is plausible but not documented in exactly those terms. It is a genuine example of *engineered local feedback*, but not a canonical formal “asynchronous intelligence network.”