Myself and Ansel attended this interesting conference that brings together a few different communities. The single hall had areas dedicated to Data, Information Security, Development Operations, Communication Technologies and Customer Experience.
It was interesting to see if there are common themes among this quite diverse set of communities.
The following are a few of the sessions that we attended
Immediately we walked into the conference we were by a talk given by Capital One on elevating data literacy. This felt very relevant to me given my recent time with NHS Supply Chain. The gentleman spoke of lots of “Lunch and Learns” There seemed a lot of polling to find skills that were being demanded. This reminded me of Steve Miranda’s adage “This is not a democracy”. The most requested skill was excel. It made me wonder whether having many more people take extracts into excel would improve decision making or create a tower of babel.
The next session that we were keen to attend was a panel discussion Governance to Guardrails. There were speakers from ITV, Pandora. While we thought it was going to focus on AI, the data theme seemed to come through most strongly. Issues mentioned included: understanding data provenance, data governance. There were some more AI themes that came through: emphasis on human involvement, emphasis on safe experiments giving visibility to the model. They mentioned a community of practice which resonated with me. Somewhere that you are comfortable to not appear silly with a question. They called it an AI Guild which seemed to combine the very new with the very old. They did talk about sharing prompts. The creating of prompts is the next artisan craft.
They also talked about build versus buy in LLM models, which seemed to misunderstand the creation of tooling on top of very few LLM’s that will exist. However, they made the point about ensuring that you understand the benefits that you are trying to achieve as well as the risks that you are absorbing as you take AI capability from suppliers.
The standout moment for me in this panel discussion was in the Q&A section, when someone made the point (rather than asked the question) that the biggest issue in LLM based development is failure modes. What do you consider an error when the objective is essentially to give your best guess?
I attended a session on crisis management. It was very much a security incident response session. It covered many aspects: business continuity, crisis communications and information supply chain risks.
The gentleman and lady that presented highlighted mistakes that companies often make.
Containment
The belief that you can disengage the company systems from the public internet.
Teams then find that all of the tools that they need are on the other side of the fence.
A scattered enterprise can't cut itself off from itself
Cutting yourself off from your customers because you are compromised yourself.
Contain and eradicate rather than bring back online.
Communications
Clients tend to be better at external Comms than Internal.
Teams using what's app when internal systems are down
Comms templates for cyber.
Channels for interfacing to outside worlds.
Not knowing the impact of the attack.
Rolls Royce has 15,000 organizations in their supply chain.
Business impact analysis
Redundancy
I attended this session because I thought it might be on the bleeding edge of user experience design, but I was really more about the history of crafts moving into new crafts in Digital. It was delivered by the University of Arts in London (UAL).
Amazing presentation taking you through design of the AV systems for learning delivery, right through to the creation of virtual environments in cinematography.
This seemed an important session for us given that most of the conferences I am at these days are in Microsoft Teams. Notable that it was standing room only.
Teams and CoPilot
Lots of the roadmap was around copilot. Voice processing was also a big component.
Teams phone. Call recap. Meeting recap.
Contact center. KPI’ s on how well call center is functioning. Call back. Failover from VoIP to analog
Voice isolation in teams. Blocks out other voices.
Places. Taking advantage of hybrid working.
VDI virtual desktop. Basically the desktop client is being wound down.
CoPilot meeting transcription options: having transcription available while the meeting is active or having a record of the event.
One feature that struck me as intriguing was the ability to ask questions of the transcript through copilot.
Msft Rooms (large conferencing). Pc joining a conference because you walk into the room.
Copilot itself.
Copilot will have different levels.
Assistant - The digital assistant model that we are already familiar with. Doing what you ask it to do.
Manager - A facilitator of a meeting, prompting people for responses, clarifying and reading back actions. A project manager - prompting for follow up on tasks, shifting priorities to ensure deadlines are achievable, sensing and alerting people to emerging risks.
Agent - Autonomous, not necessarily interacting with humans. Interfacing with other programs.
01 is a reasoning engine. Analyzing it's first answer. At the moment, I spend a lot of time refining my prompts. The next generation will be doing the refinement of the prompt.
The licensing model
Copilot
Chat (O365)
Bizchat (separate license)
Copilot in Office
The presenters gave examples of of how copilot is being embedded in the office automation products.
Excel copilot. “I am trying to solve for this”
PowerPoint copilot.”I am trying to build a deck to do this”
Word copilot. Prompts to change a document, changing text and format.
OneDrive copilot. Compare or summarize.
Copilot agents. Build a field service agent over your field service manuals.
Team copilot. Acting as a project manager. Follow up.