Blackone Holdings / AI strategy & operations
AI strategy and operating systems across a multi-company group
Led AI strategy and operations across a multi-company group, translating leadership priorities into workflow specifications, operating dashboards, SOPs, and team adoption.
Nino Amor · AI strategy & operations
The problem
The holding-company environment spanned logistics, finance, and creative-services businesses, each with different tools and working habits. My work was connecting leadership priorities to the workflows, ownership, and operating references those teams needed.
AI strategy and operations lead
As AI Strategy and Operations Lead, I worked from leadership priorities through to the way teams carried out the work. I mapped operating problems, defined AI workflow specifications, evaluated the technology stack, and built the dashboards, SOPs, and handoff standards around delivery.
Team adoption was part of that remit. The operating references had to explain who owned the next step and how different businesses could use the system within their own work.
Enterprise-wide implementation across different teams
The group needed shared operating standards without assuming that logistics, finance, and creative-services teams worked alike. My scope connected leadership priorities to each team's requirements, tool choices, ownership, and adoption.
Design the ownership alongside the workflow
I treated ownership as part of the system design. The workflow needed to show what comes in, which decisions require review, and which person or team carries the next step. A dashboard without that operating agreement would leave the coordination problem unresolved.
Tool evaluation followed the operating need. The useful question was whether a tool helped a team carry a defined responsibility, not how many AI features it offered.
What I delivered
I connected leadership decisions with implementation planning and the tools teams used to coordinate work. The delivered dashboards, SOPs, and handoff standards gave that planning a practical form; workflow specifications described what the implementation needed to do.
- Implementation planning: AI workflow specifications connecting leadership priorities to team responsibilities.
- Operating tools: dashboards and SOPs showing delivery state, ownership, and next steps.
- Team adoption: shared handoff standards and support across the multi-company environment.
From a portfolio priority to a team routine
I connected the strategy work to the things teams used to coordinate delivery. The workflow specification, dashboard, SOP, and handoff standard were parts of the same operating framework.
- Map the operating problem and turn it into a defined workflow and priority.
- Make the owner, delivery state, and next handoff visible through dashboards and standards.
- Evaluate tools against the work they need to support, then help the team adopt the process.
AI strategy & operations
From a leadership priority to a team routine
Across a multi-company group
Logistics · finance · creative servicesDefine the priority
Map the operating problem and specify the workflow.
Name the owner
Make responsibilities and the next handoff explicit.
Build the reference
Connect dashboards, SOPs, and tool choices to that work.
Support adoption
Help teams use shared standards in their own routines.
A shared operating reference across teams
Leadership priorities became defined workflows and clearer responsibilities. Teams had a common reference for what needed to happen next, rather than relying on another round of interpretation after every decision.
What I took forward
An AI implementation changes how work moves between people as well as which tools they use. This role brought together executive priorities, technical choices, and day-to-day operations across more than one business.