The Advisory Council Nobody Listens To
Mercy Regional's Patient and Family Advisory Council has 14 members, meets monthly for 90 minutes, and has run for three years. Eleven members are retired women with no recent inpatient experience; average tenure is four years; three members live with chronic conditions. Staff set the agenda and a staff member chairs. Over two years, 62 recommendations were logged, 14 were implemented, and members report never hearing back on the rest. A new CEO has committed $40 million to an emergency department redesign with a nine-month design-to-construction window and has asked the council to "sign off" on the final plans next month. The council chair tells you privately that she is considering resigning.
1. Diagnose why this council has so little influence, and identify what is structurally wrong before proposing fixes.
Read the worked answer
Four failure layers, in order of importance.
- Structural - the council has no decision rights. It advises at the end of a process, its agenda is set by staff, and its chair is a staff member. Nothing it says is binding, and nothing requires a response. A body that can only recommend, at a point when plans are already fixed, will be ignored regardless of member quality.
- Relational - the loop is open. 62 recommendations and a visible 23% implementation rate, with silence on the rest, teaches members that their time has no consequence. The chair's resignation threat is the rational response, not an overreaction. Members also cannot tell the difference between "rejected for good reason" and "never read."
- Compositional - the council does not represent the patients served. Eleven retired women with no recent inpatient experience is a sampling problem, not a diversity checkbox: the people most likely to be harmed by ED design (frequent users, behavioral health, limited English proficiency, parents of pediatric patients, people with disabilities, older adults with transportation barriers) are absent. Four-year average tenure builds expertise but also drift away from current experience and blocks renewal.
- Measurement - nobody knows whether the council changes anything. No tracking of which recommendations were adopted, what changed as a result, or what patients noticed.
Also name the framing problem: "sign off on final plans next month" is tokenism by design. Asking for approval after design decisions are made converts the council into a rubber stamp, which will damage the credibility of the whole engagement program when members realize it.
2. Design an engagement approach for the ED redesign that fits a nine-month window. Specify who, when, how, and what authority the participants have.
Read the worked answer
Anchor the design to the build milestones, not to the council calendar. Work backward from concept, schematic, and final design dates and place patient input upstream of each.
Who (6-8 week rapid recruitment, 8-10 people):
- 3-4 recent ED users or family members (within 12 months), including at least one high-frequency user.
- 1 behavioral health, 1 pediatric parent, 1 older adult with mobility or sensory needs, 1 person with limited English proficiency reached through an interpreter.
- 1-2 continuing council members as continuity, not as the whole panel.
- Recruit through ED staff nominations, discharge follow-up calls, community organizations, and the patient portal - not through the council alone.
How (methods matched to stage):
- Immersion before design: patients walk their own ED journey with a staff guide and note what they see, hear, and fear. Nothing beats direct observation for generating design constraints.
- Design workshops at three decision points: flow and triage concept, waiting and communication, rooms and discharge. Use walkthroughs and simple mock-ups rather than floor plans.
- Two patient reviewers seated on the design team with explicit authority: their sign-off is required on a defined short list (wayfinding, communication touchpoints, privacy, accessibility) and their dissent is recorded in the decision log.
Practical supports that make participation real: stipends, transportation, child care, evening and virtual options, interpreters, plain-language materials, and same-week summaries.
Constraints handling: give the panel the real constraints (budget, code, square footage) up front so they design within them. When a good idea cannot be built, say why in writing and offer the closest feasible alternative. A visible decision log - adopted, adapted, not adopted and why - is what converts advice into accountability.
3. How do you close the loop on the 48 unaddressed recommendations and rebuild enough trust that the chair stays?
Read the worked answer
Treat the backlog as a trust repair job, not an administrative one.
- Triage every one of the 48 into: implemented (with evidence), will implement (with owner and date), cannot implement (with a specific reason and who decided), or needs more information (with a next step). Two members and one staff partner do this together - not staff alone.
- Write back individually. A short, plain-language response per recommendation, signed by a named senior leader. Silence is what damaged the relationship; the specific answer matters less than the fact of an answer.
- Publish a two-column account internally and, where appropriate, on the patient-facing site: "You said / We did" and "You said / We can't, and here's why." Naming the constraint - budget cycle, building code, staffing - is more respectful than a vague deferral.
- Renegotiate the charter with the chair co-leading the conversation: agenda co-set by members, member or co-chair leadership, a defined response standard (e.g., every recommendation answered within 30 days), an annual impact report, term limits with an onboarding pipeline, and a recruitment plan aimed at the populations missing today.
- Give the chair something concrete before the CEO meeting: authorship of the revised charter and co-presentation of the impact report. The resignation risk drops sharply when a member's frustration converts into visible authority.
- Say no clearly to the "sign-off next month" request and offer the milestone-based panel instead. Agreeing to rubber-stamp to protect the relationship would finish the job the backlog started.