AI Leadership Weekly · Issue #73 · Tuesday 3 March 2026 · 08:00 GMT
Good morning.
Reusable workflows, image generation and cloud capacity make an unusually varied set of headlines. Anthropic expanded Cowork’s enterprise plugin story; Google launched Nano Banana 2; Amazon and OpenAI announced a wider strategic partnership. There is an opportunity in each, but not the same opportunity. This edition separates the everyday tools from the longer-term commercial and infrastructure commitments.
IN 60 SECONDS
Cowork gains enterprise plugins. Anthropic introduced organisation-specific plugin distribution and customisation, allowing teams to package connected tools and reusable skills.
Nano Banana 2 launches. Google introduced Nano Banana 2, combining image-generation capabilities with a greater emphasis on speed and broader product access.
Amazon and OpenAI expand their relationship. The companies announced a strategic partnership including investment, compute and a planned stateful runtime on Amazon Bedrock.
CEO / COO / CXO CHECKLIST
CEO: Treat a shared AI workflow as a maintained service, not an uploaded template.
COO: Separate visual provenance from factual and brand approval.
CXO: Keep announced integrations out of delivery promises until access is confirmed.
TOP STORIES
1. Cowork gains enterprise plugins
Anthropic · 24 February 2026
What happened. On 24 February, Anthropic described enterprise features for Cowork plugins, including private plugin marketplaces and organisation-specific customisation. The announcement brought reusable skills and connected tools into an administratively managed setting. It presented a way to distribute configured workflows, not evidence that a template was suitable for every team or that local operating responsibilities disappeared.
Why it matters. Our take: A private catalogue can be useful when people know what they are adopting. Include a business owner, intended users, required information and the version currently supported. Distinguish the procedure that must remain consistent from the wording a team may adapt. Otherwise a shared starting point can become many incompatible processes with the same reassuring name.
What to do. Take one workflow colleagues already copy between teams. Package its purpose, instructions, permissions, accepted examples and support contact together. Ask a second team to try it without the author present. Resolve any hidden dependency before listing it as an approved reusable option.
2. Nano Banana 2 launches
Google · 26 February 2026
What happened. Google introduced Nano Banana 2 on 26 February, identifying it as Gemini 3.1 Flash Image. It described faster image creation and editing across its product surfaces, alongside AI provenance features. Such marking can help identify how an image was made; it does not by itself verify the depicted facts or clear the right to use a brand or person.
Why it matters. Our take: For a marketing team, the test is not simply how many variants it can produce. Ask whether the variants remain faithful to the approved brief, product and audience. Separate a concept image used in an internal discussion from an asset intended for customers. Both may look finished, but they need different acceptance decisions.
What to do. Try one authorised campaign brief and request a small set of variations. Review text, product detail, brand consistency and any implied factual claim. Keep the approved asset, its source brief and its intended use together. Do not treat an AI-origin label as a substitute for the final publishing decision.
3. Amazon and OpenAI expand their relationship
OpenAI · 27 February 2026
What happened. OpenAI and Amazon announced a strategic partnership on 27 February, including expanded compute commitments and plans for a stateful runtime environment on Amazon Bedrock. The runtime was described as forthcoming in the next few months. That makes it an announced integration path, not an already available service on which a March delivery promise could safely depend.
Why it matters. Our take: The business attraction is continuity across steps: a service that can retain the relevant context instead of treating each interaction as unrelated. Before committing, ask where that state would live, how it would be inspected and how the organisation would leave the arrangement. Those are design questions even when a familiar cloud supplier is involved.
What to do. Ask the architecture and delivery owners to separate what they can use now from what has merely been announced. Put any future dependency on the project plan explicitly, with an alternative route. Request confirmation of access, supported regions and operating terms before promising the integrated outcome to a business sponsor.
SIGNALS FROM THE LAST MONTH
12 February · Codex-Spark targets fast coding. OpenAI introduced GPT-5.3-Codex-Spark as a research preview for Pro users, initially focused on text-based, low-latency coding. Source
12 February · Gemini Deep Think expands. Google offered its updated reasoning mode to AI Ultra subscribers and invited interest in early API access, not general API availability. Source
5 February · Opus 4.6 is released. Anthropic launched Opus 4.6, including a one-million-token context window in beta and updated capabilities for longer assignments. Source
5 February · OpenAI introduces Frontier. OpenAI announced an enterprise platform for developing and managing agents, initially working with a limited group of customers. Source
IN BRIEF
More dated updates from the preceding 30 days.
20 February · Claude previews code-security review. Anthropic announced a limited research preview of Claude Code Security, designed to identify vulnerabilities and propose fixes for human review. Source
19 February · Gemini 3.1 Pro enters preview. Google introduced Gemini 3.1 Pro in preview, targeting more complex reasoning tasks across its consumer and developer products. Source
17 February · Sonnet 4.6 arrives. Anthropic released Sonnet 4.6, reporting improvements in coding, computer use and reasoning while retaining the Sonnet pricing level. Source
12 February · Anthropic raises fresh capital. Anthropic announced a $30 billion Series G funding round at a $380 billion post-money valuation. Source
THE 15-MINUTE PLAYBOOK
Create a workflow release record
Minutes 0–4 · Name the service. Choose one workflow with a recognisable recipient and output. Write a one-sentence purpose and a short list of things it does not do. Identify the process owner, rather than only the person who configured the tool.
Minutes 4–8 · Capture the dependencies. Record the instructions, source locations, required permissions and model configuration. Include an accepted example and a case requiring escalation. Keep them together so a receiving team can distinguish the procedure from the surrounding assumptions.
Minutes 8–12 · Set the change boundary. State which elements another team may adapt and which require approval. Assign a version and a support contact. Decide how an old version will be withdrawn when a defect or changed business rule makes it unsuitable.
Minutes 12–15 · Test the handover. Give the record to a colleague outside the original pilot. Ask them to complete a representative task and explain the result. Use their questions to improve the release record before offering the workflow more widely.
DATA WAVE MOMENT
Build reusable capability around a recognisable outcome. A small, maintained workflow with clear boundaries is more useful than a large catalogue whose users must rediscover the original author’s assumptions every time.
QUESTION FOR READERS
What would another team need to know before it could safely reuse our best AI experiment?
Brought to you by Data Wave — your AI & Data Team as a Subscription.
