Results
Spotlights
-
In teams that already route most coding work through cost-visible workflow portfolios, what changes when leaders switch from portfolio budgets keyed to technical artifact types (e.g., PRs, refactors, incidents) to problem-class portfolios keyed to business outcomes (e.g., latency incidents, onboarding features)—does this relabeling mainly sharpen which workflows get protected and iterated, or does it blur responsibility and make it harder for squads to build repeatable, trusted coding workflows tied to clear spend signals?
-
When teams standardize a small set of golden, cost-visible multi-step coding workflows and require that most new work be routed through them during pilot-to-scale adoption, under what conditions do developers respond by adapting their tasks to fit those workflows (supporting repeatability and trust) versus routing complex or ambiguous work around the agent entirely, and how can governance detect and correct the latter pattern early?
-
Across multiple squads sharing the same catalog of cost-visible agent workflows, how does introducing cross-squad comparative dashboards (showing per-workflow usage, cost, and outcome deltas by squad) affect (a) convergence on a common set of repeatable workflows versus local ‘shadow’ variants, and (b) team-level trust in governance—does transparency help squads copy proven patterns and retire weak ones, or does it trigger defensive behavior and underreporting of high-cost exploratory usage?