Activity Overview — The Boardroom Brief
Module 4, Unit 1 | Tech-Trek activity guide
By the end of this activity, you will be able to:
- Apply the knowledge and skills developed across Modules 1–3 to a realistic AI and automation business case (K22, S23)
- Work collaboratively to diagnose a business problem, map a workflow, and agree a credible proposal (K22)
- Explain the likely human and organisational impact of an automation proposal using evidence from the case (S23)
- Communicate a recommendation clearly to a non-technical leadership panel (S22)
Welcome to Module 4. This is your first Tech-Trek: a collaborative, scenario-based activity where you apply Modules 1–3 to a realistic business challenge. You will work as an internal AI and automation working group, diagnose the situation, and present a proposal to a simulated leadership panel.
The discipline of this module is restraint. Most teams fail not because they cannot find a solution, but because they jump to one before they have understood the problem, talked to the people affected, or pressure-tested their assumptions.
This is not a formal assessment. The purpose is to create a safe learning environment where you can experiment with ideas, reflect critically on decision-making, and practise explaining AI and automation proposals to non-technical stakeholders.
You are not expected to build, implement, automate or demo a working technical solution. The work stops at a proposal and a clear workflow diagram.
How the Tech-Trek Works
You will be placed into a group and assigned a case scenario. Your team will analyse the business problem, map the workflow, consider human and organisational impact, and decide what you would recommend.
| Stage | What happens | What your team produces |
|---|---|---|
| Session 1 — Diagnose | Welcome, icebreaker, case launch, group breakout activities, workflow mapping, human impact analysis and main-room Q&A | A clear problem statement, early workflow map, human impact notes and a plan for the week |
| Between sessions | Collaborative team work, supported by office hours where useful | Opportunity Brief, workflow diagram, slide outline and Q&A preparation |
| Session 2 — Pitch | Short Q&A, breakout finalisation, presentations from approximately 11:00, leadership panel Q&A and debrief | 7–10 minute group presentation plus approximately 10 minutes Q&A |
What You Will Hand In
By the end of Session 2, each team should have:
- A one-page Opportunity Brief covering the problem, proposed AI or automation intervention, human impact, risks, constraints, expected outcomes and success measures.
- A simple workflow diagram or process map that helps the panel understand the current process and where your proposal would intervene.
- A concise slide deck for a 7–10 minute presentation, followed by approximately 10 minutes of Q&A.
The Three KSBs You Will Develop and Demonstrate
| KSB | What it looks like in this activity |
|---|---|
| K22 | Collaborating as a working group to explore what a responsible pilot or proof of concept could look like |
| S22 | Translating technical concepts into accessible language for a non-technical leadership panel |
| S23 | Providing evidence-based analysis of likely human impacts, including who benefits, who may be negatively affected and what support is needed |
How to Use Office Hours Between Sessions
Use office hours as Tech-Trek support. Bring your problem framing, workflow diagram, human impact analysis, slide structure or panel questions. Do not use office hours as a build clinic; the focus is proposal quality, evidence, risks and communication.
Keep the distinction clear: a proposal is not a prototype. In this activity, your job is to explain what should happen next, why it is worth doing, and what would need to be true before anyone piloted it safely.
Self-Check Before You Present
- Can you describe the business problem in one plain-language sentence?
- Have you mapped the workflow rather than just named a tool?
- Have you explained who is affected and how?
- Have you named the risks, ethical tensions and data constraints?
- Can every team member explain part of the recommendation?
Before you move into your assigned case, pause as a team and answer this in one sentence: what would count as evidence that your recommendation is solving the real problem, rather than just sounding impressive?
KSB evidence focus
- K22: Collaborative working principles to explore AI and automation solutions and implement prototypes, pilots or proof of concepts.
- S22: Present and communicate information including the translation of technical concepts into accessible materials to support clear dialogue with stakeholders.
- S23: Work with others to achieve agreed outcomes or outputs. Provide evidence-based analysis and insight to leaders on the likely human impacts of automation projects.