Pitching, Presentation, and Collaborative Project Work
Domain 12: Pitching, Presentation, and Collaborative Project Work
This domain tests how you explain and deliver a creative venture, and how you work with others. Expect questions on pitch structure, slide design, delivery, Q&A, roles, feedback, and project management.
Core rules
- A pitch is an argument, not a summary. Structure: problem, solution, market/customer, product or demo, traction/evidence, team, and ask. The ask can be funding, a partner, a test, or feedback.
- Lead with the audience’s problem. Features matter only when tied to a benefit.
- Slides support, not replace, the speaker. Use one idea per slide, readable type, evidence, and visuals. Avoid paragraphs.
- Delivery: rehearse aloud, time it, make eye contact, and prepare for questions. A demo should have a backup plan.
- Collaboration needs roles and norms. Assign responsibilities, set deadlines, use a shared task board, and agree on how decisions are made.
- Feedback should be specific and actionable. “Make the ask clearer” is useful; “I didn’t like it” is not.
- Manage conflict with interests, not personalities. Return to the project goal and document decisions.
Worked example
A team pitches an app connecting local artists with empty wall space. Three minutes: 20 seconds on the problem (cafés have bare walls; artists lack exhibition space), 40 on the solution and demo, 30 on the customer and pilot evidence (5 cafés, 12 artists), 30 on the model ($10 monthly listing fee), 30 on the team, and 20 on the ask (a 4-week pilot with two cafés). Reasoning: the ask is specific and the evidence is small but real. A feature list without a pilot would be weaker.
Traps that cost marks
- Filling slides with text and reading them.
- No clear ask.
- Feature dumping without customer benefit.
- Ignoring time limits or rehearsing only silently.
- Unequal teamwork with no shared record.
- Avoiding conflict until the deadline.