Second-order effects
What happens after the immediate benefits?
Why it matters
The immediate result is what a team set out to change. The next effect may be a transfer of workload, a feedback loop, a changed dependency, or a gradual loss of capability. This lens follows the intervention beyond the first metric and asks where the consequences land.
Apply the lens
- Start from the intended change, then trace whose next action becomes easier, harder, faster or less visible. Mark the likely direction and timing of each effect.
- Look for effects that reinforce themselves, costs delayed beyond the reporting period, and dependencies on teams that were absent from the decision.
- Pick an early indicator for each high-impact pathway and assign an owner. Give each indicator a reason to trigger a review.
Questions to ask
- Where does the work go after it leaves this queue?
- What does the organization stop practicing if the tool works?
- Who feels the effect first, and who sees it first?
Worked example
Quicker purchase approvals may create more purchase requests. The team clearing the requests may report a gain while finance inherits a larger reconciliation queue. Its staff may also lose practice spotting unusual transactions if they see only the most obvious exceptions.
One test to run
Track reconciliation time, exception backlog and reviewer performance across the pilot and a comparison period, alongside approval time. Examine trade-offs before broadening the rollout.
What to capture
A consequence map: feedback loops and the distribution of costs and benefits.