Language: English

Community post

Build a Cross-Functional AI Team Without Creating Another Committee

By · Published · 2 min read

Editorial standards and corrections

A small outcome-focused team structure that combines business knowledge, technical delivery, risk, data, and frontline experience.

A successful AI team is not a room full of enthusiasts. It is a temporary structure with a business outcome, decision authority, working cadence, and a clear route into normal operations. This decision connects to Build an AI Strategy That Starts With Business Value and Turn Company Priorities Into an AI Opportunity Portfolio, which provide the strategic direction and portfolio context. Use this four-part leadership framework Core team — Keep the working group small: business owner, domain expert, technical lead, data owner, and delivery manager. Control partners — Bring privacy, security, legal, compliance, and procurement in according to risk. User participation — Include people who perform or receive the work. Operating cadence — Use weekly evidence reviews and monthly executive decisions, not status theater. A practical decision example A finance-document initiative uses a six-person core team and scheduled control reviews. Frontline analysts test representative cases; leadership receives decisions and evidence rather than tool demonstrations. This is a hypothetical example; use your own baseline, constraints, and evidence. Evidence, governance, and responsible use Use the NIST AI Risk Management Framework to connect the initiative to governance, context, measurement, and ongoing management. The companion NIST AI RMF Playbook turns those functions into questions leaders can assign and review. The GAO AI Accountability Framework is useful for examining governance, data, performance, and monitoring across the system life cycle. Compare the plan with the OECD AI Principles, particularly transparency, robustness, accountability, and respect for people affected by the system. For generative AI, review the NIST Generative AI Profile and test representative cases using OpenAI’s evaluation guidance. Use the OWASP Top 10 for LLM Applications to discuss application threats before a model can access sensitive information or take actions. Check performance statements against the FTC’s guidance on AI claims, and review information handling with the FTC’s privacy and security resources. For a broader organizational management approach, study the ISO/IEC 42001 overview. Take this to the next leadership meeting Write the team charter: outcome, scope, roles, decisions, weekly evidence, escalation path, end date, and the operational team that will inherit the capability. Record the owner, evidence source, decision date, and what would cause the company to stop. The goal is not to make the document look complete. The goal is to make the next decision explicit, measurable, and accountable. Continue with Define Decision Rights for AI-Assisted Work. Use Run a Quarterly AI Portfolio Review: Keep, Fix, Scale, or Stop to revisit the decision with current evidence.

About the author

I help businesses replace manual processes with practical AI systems—and show what changed, what it cost, and what results improved.

Comments (0)

Loading comments…

Keep exploring

All articles