Engagement health is mostly invisible. Most of the things that matter — pod morale, knowledge accumulation, governance maturity, customer-side trust — don't show up in dashboards. By the time they show up in dashboards, they're already broken.
Three signals are reliable enough to use as early indicators. They show up before things break, they're observable without instrumentation, and they generalize across VDC engagement types. If all three are present, your engagement is working. If one is missing, intervene before the others follow.
Sign 1: Velocity is stable AND climbing
Not flat. Not bouncing. Stable + climbing. The pod's shipped-output-per-sprint shows low variance over the last 4–6 sprints AND has trended upward since month 3.
Why both matter
Stability without growth signals a pod that's optimized within its constraints but the constraints themselves are limiting. Growth without stability signals a pod that's still calibrating; you can't predict next sprint's output.
The combination — stable AND climbing — signals a pod that has settled into its operational rhythm and is still finding efficiency. The shape compounds: month-3 to month-6 is typically 1.5–2.5× growth in shipped output without the pod getting bigger.
How to observe
Sprint-level shipped-output metric (story points, completed milestones, merged PRs — whichever your team uses). Plotted over time should show low variance + upward gradient.
If it's missing
If velocity is flat or unstable at month 3+, something structural is capping the pod. Common causes: scope is too granular, pod composition is wrong, customer-side acceptance is bottlenecking. See the seven anti-patterns for which one applies.
Sign 2: The pod is shaping work, not just executing it
By month 6, healthy pods contribute to what gets built, not only how. They surface architectural questions before they become rewrites. They propose scope adjustments based on implementation reality. They raise risks early. They suggest work the customer hadn't prioritized.
Why this matters
An execution-only pod is high-grade staff augmentation. Useful, but the value is capped at "shipping what's specified." A shaping pod becomes an engineering partner — they catch errors in scope, they identify opportunities, they integrate into the architectural decision-making.
The transition from execution-only to shaping is the real maturity signal of the engagement.
How to observe
Track the ratio of pod-originated work to customer-originated work. By month 6, healthy is 15–25%. Below 10%, the pod is order-taking. Above 35%, the pod may be over-extending its mandate (rare but worth checking).
Also: the language. In monthly engagement reviews, does the pod's delivery manager describe what they think should be built next? Or do they only report what they've shipped?
If it's missing
The pod is being treated transactionally. They don't have business context to shape with — share quarterly product reviews, customer feedback summaries, strategic priorities. They don't feel safe pushing back — make explicit that pushback is welcome. They're staffed wrong — pod composition may need senior reinforcement.
Sign 3: Your engineering manager's calendar has reclaimed time
The most-overlooked signal because it's a negative one — it's about what's NOT happening on the customer side.
If your engagement is fully managed in the operational sense (see what fully managed actually means), your engineering manager's calendar should reflect it. Specifically:
- Your EM is no longer running pod standups.
- Your EM is no longer the primary code reviewer for pod PRs.
- Your EM is no longer chasing milestone reports.
- Your EM is no longer the escalation point for pod-internal issues.
Net effect: your EM has reclaimed 8–12 hours per week relative to staff augmentation. They use that time on customer's strategic work, on the in-house team's needs, on architectural decisions, on whatever they were always supposed to do but didn't have time for.
Why this matters
Engineering manager time is the most valuable resource on the customer side. If the engagement is real fully-managed, that time gets returned. If it isn't, the customer is paying VDC rates for staff-aug-shaped management overhead.
This is also the strongest internal advocate signal. Your EM is the person closest to the engagement; if their calendar tells them the pod is taking management work off their plate, they become the engagement's strongest internal supporter. If it's adding work, they become its quietest opposition.
How to observe
Ask your EM directly: "what percentage of your week is on this engagement vs. other things?" At month 3, healthy is 5–10%. By month 6, healthy is 2–5%. If it's still 25%+, governance hasn't transitioned.
If it's missing
The most common cause: governance never transitioned. Your EM kept running operations like staff augmentation. The fix is structural — formal handoff session where EM hands operational ownership to the pod's delivery manager. Awkward but necessary.
What you DON'T need to observe
Three signals that look important but don't actually tell you whether the engagement is working:
- Specific milestone hits. Hitting milestones is necessary but not sufficient. A pod can hit milestones and still be unhealthy if velocity is flat or governance hasn't transitioned.
- Pod member individual performance. Specialists rotate; the pod-level signal matters more than any specific member.
- Customer satisfaction surveys. Surveys lag the underlying signal. By the time customer satisfaction drops in surveys, the engagement has been broken for a quarter.
The three signals above lead the surveys. Watch them, fix them, and the surveys take care of themselves.
The composite signal
If all three signals are present at month 6:
- Velocity is stable + climbing.
- Pod is shaping 15–25% of incoming work.
- Your EM has reclaimed time.
The engagement is working. Compounding value is being produced. Continue.
If one signal is missing, intervene specifically on that signal. Don't generalize ("the engagement isn't working") — diagnose the specific cause and apply the specific fix.
If two or three signals are missing, the structural problem is likely upstream — bad scoping, mismatched pod composition, or governance that never transitioned. Run the structural diagnostic with the platform's engagement architect, not the pod's DM.
Frequently asked questions
What if we're at month 3 and not all three signals are showing yet?
Normal. Month 3 is when calibration is finishing; signals 2 and 3 typically emerge between month 3 and month 6. Watch the trajectory, not the absolute level.
How often should we check these signals?
Velocity: weekly (sprint-level). Pod proactivity: monthly. EM time: monthly self-report or quarterly formal review. Don't over-check — daily monitoring of these signals introduces overhead without information gain.
What if our engagement is project-shape, not capability-shape?
Signals still apply, with shorter horizons. For a 4-month project, the velocity climb compresses to month 1–3, the proactivity emergence by month 2–3, the EM time reclaim by month 2.
Can these signals be gamed?
Velocity can be inflated by smaller story-point increments. Proactivity can be performed without substance. EM time can be reclaimed by ignoring the engagement rather than transitioning it. The signals only mean what they appear to mean if the underlying behavior is real. Cross-check with the pod's delivery manager and your EM directly.
Where to start
Run the three-signal check against your in-flight engagement. If you've never explicitly looked, the data is usually clearer than expected.
For an engagement-health review with the platform, schedule a 30-minute call. For broader maturity context, see healthy VDC at month 6 and day 1 vs day 30 vs day 90.