Asthma Stepwise Management Presentation Assignment Guide

The deliverable is five to six slides for a staff development meeting, and that audience changes the writing more than the content does. Colleagues do not need asthma explained; they need the stepwise logic made usable, which means each slide should carry one decision rather than one topic. Five or six slides across three required elements is roughly two slides each once a title slide is counted, so the presentation cannot survive a background section on asthma pathophysiology. Decide early what a colleague should be able to do differently after seeing it, and cut anything that does not serve that. Speaker notes are where the detail belongs if your course permits them. A useful discipline is to write the six slide titles first as statements rather than as topics — say that reliever use tells you the controller is failing, rather than titling a slide "relievers" — because a deck whose titles are claims is already organised around decisions. Anything that will not fit under one of those six titles belongs in the notes.

The controller and reliever distinction is the first required element and it needs to be built on mechanism rather than on lists. Long-term control medications work by suppressing airway inflammation and are taken whether or not the patient feels unwell — inhaled corticosteroids principally, with long-acting beta-agonists, leukotriene modifiers and biologics in defined roles. Quick-relief medication reverses bronchoconstriction that is already happening. The clinically important consequence is that a reliever treats a symptom the controller was supposed to prevent, which is why reliever overuse is a marker of poor control rather than a solution to it — and that is the sentence the staff meeting needs. Say what counts as overuse in the framework you are presenting, since a threshold turns the point from an attitude into something a colleague can act on at the next review appointment.

There is an update here worth building the presentation around, because it separates a current presentation from one assembled out of older course material. Guidance has moved decisively away from short-acting beta-agonist monotherapy, on evidence that reliever-only treatment leaves inflammation untreated and is associated with worse outcomes, toward anti-inflammatory reliever strategies in which a combination inhaler serves as both maintenance and reliever. If your practice still uses the older stepwise table, saying so and explaining what changed is a stronger staff development message than presenting either version as settled. The practical reason it matters for a staff meeting is that colleagues will have patients on both regimens, and a presentation that pretends the older approach has vanished will not match what they are looking at on Monday. Say what you would do for a stable patient on the older regimen, since that is the first question the room will ask.

The impact of the drugs on your patient is a named requirement and it is where presentations usually go thin. Inhaled corticosteroids carry local effects — oral candidiasis, dysphonia — that are mitigated by spacer use and rinsing, and at higher doses raise questions about growth velocity in children and about adrenal suppression. Beta-agonists cause tremor, tachycardia and hypokalaemia. Adherence is itself an impact: a controller taken intermittently behaves like no controller at all. Naming two or three specific effects with what you would do about each is more useful to colleagues than a comprehensive list of adverse events. Spacer use and rinsing are worth showing rather than mentioning, because inhaler technique is the intervention most likely to change practice in the room and the least likely to be done well. Paediatric and adult impacts differ enough that the brief names both, so say which your case is.

The brief says *from your practice*, twice, and that phrasing is doing real work. The presentation is anchored to a patient you have actually managed, which means the slides should carry a concrete case — age, current step, control status, what you changed and what happened — rather than a generic adult. That is also what makes the staff development framing coherent, since colleagues learn more from a case in their own setting than from a guideline summary they could read themselves. De-identify carefully: no name, no date of birth, no detail that would identify the patient to someone in the room. One case carried through all six slides also solves the coherence problem a short deck otherwise has, since each element can be answered against the same patient rather than in the abstract.

Explaining the stepwise approach itself is the second element and it needs the *logic*, not the table. The structure is: assess severity to choose a starting step, then assess control at review and step up, step down or hold. Two features are easy to state and commonly missed. Stepping down is an explicit part of the approach rather than an afterthought, and it requires a period of sustained control first. And before stepping up, the reversible causes of apparent failure — inhaler technique, adherence, ongoing trigger exposure, comorbidity such as rhinitis or reflux — must be checked, because stepping up around an inhaler technique problem medicates a problem that was never pharmacological. Say how often review should happen at each step, because the interval is the part of the framework that turns it from a table into a process and the part most often left to drift.

The third element asks how stepwise management assists *providers and patients* in gaining and maintaining control, and it says be specific — so answer for both parties separately. For providers it supplies a shared decision rule, which reduces variation between clinicians and makes a plan legible when care transfers. For patients it turns an unpredictable condition into something with named states and named actions, which is what a written asthma action plan operationalises. The word *maintaining* matters as much as gaining: the framework's value is in scheduled review, and a presentation that stops at achieving control has answered half. A shared decision rule also makes disagreement productive: two clinicians who differ about a patient can locate the disagreement at a specific step rather than trading impressions, which is worth naming for a staff audience.

Two practical notes for the slides themselves. Because the format is a presentation, the rubric will reward clarity of design as well as content — one idea per slide, minimal text, and a table or figure for the steps rather than a paragraph. And check the citation expectation for a slide deck in your course: current guideline sources are the right backbone here, and putting the citation on the slide where the claim appears rather than only on a final reference slide is both better practice and easier for a colleague who wants to follow it up. If you are asked for speaker notes, use them for the detail the slides cannot carry — dose ranges, the full adverse effect profile, the citations — so the visible deck stays at one idea per slide.