Business system
workshops.

• A recurring problem everyone can describe and nobody owns: the follow-up, the handoff, the approval that takes six messages.
• An AI pilot that became another meeting, because nobody agreed what job it should do.
• A capability you want to build across several teams or systems, such as one dependable customer record.

The people who do, receive, own and approve the work, in working groups of four to six. A sponsor who owns the purpose and resources, and a process owner who will maintain the result. Larger groups work in parallel and are compiled at agreed points.

• A sponsor brief: purpose, boundaries, people, decision rights, starting measures and dates.
• Participants record real work in the Human API workbook during a collection window: issues, frequency, systems, evidence and their own capacity.
• Short individual conversations to walk one recent situation from start to finish.
• A checked findings summary and kickoff pre-read about a week before the workshop.

• The group works through Pinpoint, Root, Audit, Categorize, Transition, Instruct and Choose: the situation, the causes, the whole effort, where each task belongs, the handoffs, any AI role and the test.
• Everyone writes alone before discussing. Six workshop responsibilities rotate so no one holds the only sceptical or human-centred voice all day.
• The facilitator reads back the agreed position after Root and after Instruct, and records open questions with owners.

Your process owner decides what changes and owns the implementation. Your sponsor owns time, money and decisions beyond the team. Human API owns the method and the quality of the records.

The first workshop plans a test; it does not declare a result. The agreed record is circulated for correction, the test owner carries out the plan with the check-ins included in the engagement, and at the results review the team decides whether to keep, adjust or stop. Accepted changes are documented with an owner, current instructions and a review trigger. Repeat passes return to the card a new finding affects instead of starting again.

A tailored workshop is one defined session. A full cycle adds the collection period, interviews, comparing findings across teams, test support and results review. Technical implementation is identified separately in the proposal. Scope, dates, participants and the final fee are confirmed in writing before work begins.