Presenting a technical proposal to an audience
Name:
Date:
Class:
A
Quick Questions
Shade in the A or B circle for each question.
1. You are presenting a proposed booking app to a client who runs a small business and has no IT background. Which approach is better?
2. Which order is better for presenting a technical proposal?
3. You chose a relational database over a spreadsheet for your solution. What should you say to the audience?
4. Which visual best helps an audience see how a proposed system is divided into parts?
5. Which is the better way to present the cost constraints and feature comparison of a proposal?
B
Match the Pairs
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1Adapting to the audience | AThe decision is stated with no justification. The presenter should explain why, such as linking it to user needs or constraints. | |
| 2Justifying a decision | BChoosing plain language and the right level of detail so the people listening, such as a client or manager, can understand the proposal. | |
| 3Diagrams and tables help the audience see how the proposed solution works and compare options quickly. | CQ&A: Answer 'Why this budget?' using the requirements | |
| 4After presenting, the presenter responds to the audience's questions with clear, honest answers linked back to the proposal. | DShow an IPO chart and a decision matrix on slides | |
| 5Slide text: 'Normalised relational schema with FK constraints' (for a client with no IT background) | ETechnical jargon is used without explanation, so the audience cannot follow. It should be in plain language for the audience. | |
| 6Slide: 'We will use a mobile app.' (no reason given) | FGiving reasons or evidence for a choice, such as why a database was chosen over a spreadsheet, so the audience can trust the proposal. |
C
Definitions
Presenting a proposal
D
Fill in the Blanks
Complete each line of code by filling in the missing parts.
1.
Adapt the talk to the ________'s needs
2.
Use plain language, not technical ______
3.
Justify each design choice with ________
4.
Show the structure with a _______ or table
5.
Present in a logical order, then
answer _________ from the audience
E
Spot the Error
Shade in the letter of the line that contains an error.
Question 1
A
input audience
B
print "Problem and need"
C
print "Proposed solution"
D
if audience <- "client" then
E
print "Plain summary"
F
end if
Question 2
A
decision <- "Use a database"
B
reason <- Less repeated data
C
print decision + reason
D
print "Any questions?"
Question 3
A
diagram <- "hierarchy chart"
B
table <- "requirements table"
C
print "Slide: " + diagrams
D
print "Also: " + table
Question 4
A
while questions < 0 do
B
print "Answer clearly"
C
questions <- questions - 1
D
end while
Question 5
A
input level
B
if level = "expert"
C
print "Show technical detail"
D
else
E
print "Use plain language"
F
end if
Answer Key
Presenting a technical proposal to an audience
Section A: Quick Questions
Q1
A — Explain it in plain language and define any technical term you need to use
Q2
A — Problem, proposed solution, requirements and constraints, then next steps
Q3
B — We chose a relational database because it avoids repeated data and keeps records consistent
Q4
A — A hierarchy chart showing the sub-problems
Q5
B — Put them in a clear table so the audience can compare them quickly
Section B: Match the Pairs
Q1
Adapting to the audience → Choosing plain language and the right level of detail so the people listening, such as a client or manager, can understand the proposal.
Q2
Justifying a decision → Giving reasons or evidence for a choice, such as why a database was chosen over a spreadsheet, so the audience can trust the proposal.
Q3
Diagrams and tables help the audience see how the proposed solution works and compare options quickly. → Show an IPO chart and a decision matrix on slides
Q4
After presenting, the presenter responds to the audience's questions with clear, honest answers linked back to the proposal. → Q&A: Answer 'Why this budget?' using the requirements
Q5
Slide text: 'Normalised relational schema with FK constraints' (for a client with no IT background) → Technical jargon is used without explanation, so the audience cannot follow. It should be in plain language for the audience.
Q6
Slide: 'We will use a mobile app.' (no reason given) → The decision is stated with no justification. The presenter should explain why, such as linking it to user needs or constraints.
Section C: Definitions
Q1
Presenting a proposal — Explain a proposal to its audience in plain language and logical order, using diagrams and justified decisions, then answer questions.Section D: Fill in the Blanks
Q1
Adapt the talk to the audience's needsQ2
Use plain language, not technical jargonQ3
Justify each design choice with evidenceQ4
Show the structure with a diagram or tableQ5
Present in a logical order, then
answer questions from the audienceSection E: Spot the Error
Q1
D — <- assigns a value, but this line needs to compare the audience to "client". It should use the comparison operator: if audience = "client" then.
Q2
B — The justification is text, so it must be in quotes. Without quotes the computer reads it as variable names. It should be: reason <- "Less repeated data".
Q3
C — The variable is called diagram, not diagrams. The slide line must use the variable that was set up: print "Slide: " + diagram.
Q4
A — The presenter should keep answering while questions remain, so the condition must be questions > 0. With < 0 the loop never runs and no questions are answered.
Q5
B — The if line is missing the keyword then. It should be: if level = "expert" then.