Which agent, for which work, owned by whom?

Once individuals are productive with their own assistants, teams need to decide what to share and who will maintain it.

Enabling agents is a business process first. Keeping knowledge curated, up to date, and owned is what makes the workflow dependable. The moment an agent or workflow has no owner, it can go out of date and lose the team's trust. Having the tools doesn't make the organisation successful.

This session works through private agents, shared knowledge and skills, and team agents. I walk through team-agent archetypes I call the workflow-manager archetype a workflow agent to keep attention on the process. Examples from my own harness, experiences and C4X connect these choices to maintained context, access boundaries and accountable ownership.

The focus is the very Work itself - i.e. what people need to agree, which knowledge must stay current, and who can authorise a change.

It connects practical harness engineering to the wider enterprise transformation discussion.

Takeaways:
1. Decide whether the work needs a private agent, shared knowledge and skills, or a team agent.
2. Choose the agent around a defined workflow and its access requirements.
3. Name an accountable owner for the process and its knowledge, with a way to review changes and keep it current.

30 minutes (25 + 5 Q&A). For engineering leads, architects, product and process owners, and transformation teams. Mixed technical and business audience.