BPS3012 Chap.10 Inquiry Project and Scientific Poster
Inquiry Project and Scientific Poster
Inquiry Project and Scientific Poster combines organisation research, team planning, synthesis, visual communication and oral presentation. The project profiles a pharmaceutical company or research group. Strong work converts reliable evidence into a small set of analytical messages for a defined audience rather than reproducing an organisation website.
Start by converting the brief into an evidence plan.
Define the organisation, its scientific or commercial problem, the audience and one take-home message. Divide research by questions rather than by poster panels so that the team can compare sources before committing to layout. Company material can establish stated strategy or pipeline claims, but independent and primary evidence is needed to evaluate scientific maturity, limitations and context.
Keep a shared log of source, claim, evidence level and intended use.
A useful organisation profile is analytical. It connects the unmet need, platform or products, development stage, capabilities, partnerships, constraints and strategic choices. A SWOT table earns value only when every item is specific and evidenced.
For example, a platform capability may be a strength, while dependence on a narrow delivery route may be a weakness; a growing therapeutic area may create an opportunity, while competing modalities or manufacturing limits may create threats. Generic labels such as innovative or competitive do not demonstrate analysis.
The poster should have one visual reading path.
Use a short purpose statement, a small number of evidence-led panels, legible figures and a conclusion that answers the inquiry. Headings should communicate claims, not merely name topics. Every figure needs a reason to exist and a caption that states the takeaway. Reduce detail that belongs in oral explanation, but preserve evidence boundaries.
A visually polished poster cannot compensate for unclear purpose, unsupported claims or an inconsistent account of the organisation.
Team process affects the final scientific message. Agree on definitions, citation style and decision criteria; assign owners and reviewers; record choices; and rehearse transitions so the presentation sounds integrated.
Prepare questions that challenge methods, evidence, feasibility and limitations, then practise direct answers: conclusion first, supporting evidence second, boundary last. Before submission, audit the poster and speech against the rubric for accurate content, synthesis, audience-appropriate language, cohesive delivery, supporting material and responses.
The team should be able to defend both what it included and what it deliberately left out.
What this chapter covers
- 01
Inquiry questions and reliable organisation research
- 02
Team roles, dependencies and planning
- 03
Scientific, development and organisational evidence
- 04
SWOT analysis and comparison
- 05
Poster purpose and message hierarchy
- 06
Audience, delivery and supporting visuals
- 07
Question responses, peer feedback and professional conduct
Worked example · free
Convert a research dump into a poster story
- +1Define one purpose and take-home judgement.
- +1Select the mechanism and development evidence needed for that judgement.
- +1Use one comparison to show the organisation's claimed distinction.
- +1Remove inventory that does not support the message.
- +1Design readable visuals with interpretive captions.
- +1Align the title, spoken narrative and final implication.
Key terms
- Inquiry project
- A structured investigation in which a team frames questions, gathers reliable evidence, analyses it and communicates conclusions.
- Message hierarchy
- The ordering of a central claim, supporting evidence and implications so the audience can recognise importance quickly.
- SWOT analysis
- A structured analysis of internal strengths and weaknesses and external opportunities and threats.
- Target audience
- The people for whom content selection, terminology, explanation and visual design are being tailored.
- Supporting material
- A figure, table, poster or slide used to clarify and substantiate a spoken message.
Inquiry Project and Scientific Poster FAQ
What should the organisation profile analyse?
Investigate the problem addressed, scientific capability, translation into products or research, comparative position and important scientific or operational risks. Select evidence that supports a clear judgement. Separate what the organisation says about itself from independent evidence of maturity or impact. A shared log should record each claim, source, evidence level and intended poster use.
That process helps the team reconcile inconsistent findings and prevents promotional language from becoming an unsupported analytical conclusion.
What makes a poster effective?
One purpose, one take-home message, accurate selected evidence, logical analysis, readable visual hierarchy and captions that explain the implication. Decoration should not compete with information. Headings should state claims and guide a predictable reading path. Rehearse whether a viewer can identify the purpose, main evidence and conclusion quickly, then use oral explanation for appropriate detail.
The team must keep the same evidence boundaries in the poster, presentation and answers to questions.
How should the team prepare for questions?
Write difficult questions raised by the evidence and rehearse direct answers in three moves: answer, support with evidence and state the boundary or next information needed. Include challenges to source independence, maturity, feasibility, comparison and risk. Assign another member to test whether the evidence actually supports the reply.
If the team cannot answer consistently, update the shared message or poster rather than memorising separate scripts. Cohesion comes from shared reasoning, not identical wording.
Assessment move
Maintain a shared evidence log with source, finding, claim and reviewer. Assign work by research stream and dependency, then agree on the central message before designing panels. Rehearse transitions and question responses as a whole team, and use peer feedback to update both the product and the process.
