---
id: "concept-asynchronous-information-engineering"
type: "concept"
source_timestamps: ["§ Make Sure Information Flows Both Ways", "¶16"]
tags: ["knowledge-management", "asynchronous-work", "systems-design"]
related: ["entity-unilever", "action-engineer-asynchronous-flow"]
definition: "The intentional design of structured, non-real-time communication channels to ensure peripheral market intelligence reliably reaches central decision-makers."
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"
---
# Asynchronous Information Engineering

## Asynchronous Information Engineering

**Asynchronous information engineering** is the intentional design of low-friction, *structured* communication channels that let critical market intelligence flow to headquarters **without** relying on real-time meetings or ad-hoc networking. It is especially vital for organizations spanning vastly different time zones and socio-demographics.

The canonical example is **Unilever's Shakti Project** in India (see [[entity-unilever-d1]]): rural women distributors provided real-time, *structured* feedback on consumer behavior and price sensitivity directly to area managers. This engineered flow bypassed external consulting firms and integrated rural insights directly into the regular communication flow of leaders in **London and Rotterdam**, letting HQ anticipate market shifts from structured, asynchronous updates.

This concept is the second pillar of Livermore's remedy (the first being reversing decision direction). It is operationalized by [[action-engineer-asynchronous-flow]] (pulse surveys, weekly prompts, idea channels, standardized brief updates) and institutionalized by [[action-establish-global-insight-councils]].

**Enrichment / external grounding:** Project Shakti is well documented as a rural-India distribution-and-empowerment program in which women micro-entrepreneurs supply regular feedback that helps Unilever adjust pack sizes, pricing, and promotions. **Nuance:** public sources describe Shakti primarily as *distribution + empowerment*; the article's specific claim that it “bypassed consulting firms” and fed intelligence straight to leaders is plausible but not documented in exactly those terms. Knowledge-management literature independently recommends structured, low-friction channels (dashboards, standardized reports, feedback loops) for surfacing local insight into central decisions.
