concept / concept:influence-as-infrastructure@1
Influence as Infrastructure
A team’s evidence shapes other teams’ decisions through an explicit dependency, not repeated advocacy.
Influence becomes infrastructure when a team owns context that other teams’ work formally depends on.
Instead of repeating the same argument in meetings and Slack, the team maintains an evidence-backed package. Downstream teams use a reviewed release of that context in their own work.
The evidence can shape a decision even when its author is not in the room. Influence moves from personal performance into the structure of the system.