(Fixture for /clarity. This is the kind of artifact that skill's "Inputs"
section says to look for -- a charter/strategy doc/wiki page. It's
deliberately incomplete.)
Meridian Advisory is running a Q3 operations-audit engagement for Brightfield Logistics, focused on the accounts-payable (AP) function: invoice processing, three-way-match exceptions, and duplicate-payment risk. The engagement exists so Brightfield's CFO can cut AP cycle time and stop losing money to duplicate/erroneous vendor payments before the Q4 close.
Ask three engagement team members "why does this engagement exist" and you currently get:
- Partner (engagement lead): "So Brightfield stops losing money to duplicate payments and cuts AP cycle time before Q4 close."
- Senior consultant: "Cut AP cycle time and duplicate-payment losses before Q4." (matches partner)
- Analyst: "Whatever's on this week's workplan from the partner, honestly."
Two of three agree; the third has no independent read on the vision.
There is no written plan beyond the current phase (Discovery). The partner keeps a mental model of "Discovery -> Process Redesign -> Implementation Support," but none of it is written down anywhere the team can see, critique, or plan against. The team can describe this phase's fieldwork but not what happens after Discovery closes out.
A scorecard exists: the weekly client steering-committee deck tracks "AP cycle time (days)" and "duplicate-payment dollars flagged," both real and reported since kickoff -- but it's the only pair of metrics tracked; there's no scorecard entry yet for the "Process Redesign" or "Implementation Support" phases mentioned in Vision.