myAI Scouts

~8 min

Cross-functional alignment — all approvers before you kick off

Sent to all department heads, budget holders, and senior leads who need to approve and support a major cross-functional initiative before it kicks off. Stakeholders use Jira for project tracking, Confluence for documentation, Slack for day-to-day communication, Salesforce or HubSpot for revenue tracking, and Google Docs for shared planning. The initiative spans 3–12 months and involves meaningful budget, headcount, and systems changes that touch product, engineering, marketing, finance, and operations. Findings are used to surface every team's definition of success, constraints, and unvoiced concerns before the kick-off call — so the initiative brief, governance structure, and first sprint can be designed around what's actually true across the organisation.

What this scout explores

What success looks like from their department's Salesforce or OKR dashboard

What specific metric, Jira milestone, or OKR outcome from this initiative would make it a success from your department's perspective — and how would you measure it? Not the company-level goal in the Confluence brief, but the outcome that would matter to your team's dashboard. The most important thing to align on before the first sprint.

The constraint or dependency their team brings to this

What does this initiative need to work around or accommodate from your team — a hard Jira deadline, a budget cap, a Salesforce data dependency, a compliance requirement, a headcount constraint? What would stop your team from being a full partner if it isn't addressed in the kick-off brief?

The risk they've raised in Slack but not in a planning meeting

Is there a risk, resourcing gap, or strategic concern about this initiative that you've mentioned to a colleague in Slack or a 1:1 but haven't raised in a planning meeting or Confluence comment yet?

What made a previous cross-functional initiative succeed or fail

Think about a previous cross-functional initiative at this company or a previous role — one that went well and one that went badly. What made the difference in how decisions were made, escalations were handled, and teams stayed aligned? What would you want to replicate or avoid in this one?

This scout will be copied to your account as a draft. You can customise it before activating.