What connectors do
Connectors pull evidence such as:- Delivery artifacts — tasks, tickets, projects shipped, incidents resolved
- Documentation — updates, specs, runbooks
- Stakeholder updates — status, communications, handoffs
- Operational signals — where applicable (e.g. reliability, SLA impact)
Why evidence matters
- Reduces reliance on memory — recency bias and “what did they do again?” are reduced
- Improves fairness — quiet contributors and behind-the-scenes work are visible
- Makes reviews defensible — evaluations can be tied to observable work
- Lowers admin — managers don’t have to hunt for examples; the platform surfaces them
What “evidence” is not
- Not surveillance — The goal is to support fair, accurate reviews, not to monitor activity in real time
- Not a replacement for judgment — Managers still evaluate; the platform provides context
- Not all-encompassing — Some work won’t appear in connected tools; managers can add context
How it supports the framework
Evidence feeds into:- Delivery — What was completed, shipped, resolved
- Skills — Signals from complexity, quality, unblocking others (where visible in artifacts)
- Behaviors — Where observable in docs, comms, and collaboration patterns