Technical Rigor | Bleiker Consent-Building

Clinic #119: Prevent the Public Debate from becoming Uninformed… Misinformed… downright Stupid

Communication & Crisis Communication, Technical Rigor, The Role of Politics

When your political policymakers ignore your team’s recommendation, it’s because they’ve been listening to an UNINFORMED … MISINFORMED … public debate. We’ll talk about how you can PREVENT that kind of public debate

Clinic #118: Finding Gems in Stakeholder Input

Common & Serious Errors, Communication & Crisis Communication, Technical Rigor

If your stakeholders offer you nothing but criticism that isn’t helpful, you’re doing something WRONG.

Now and then, those critics may have ideas that are absolute GEMS for your experts.

Clinic #117: ONE area where Stakeholders often CAN contribute to your Team’s Technical Work

Common & Serious Errors, Technical Rigor, Us vs. Them

With limited time and resources, which members of the vast “public” does your outreach need to focus on? If you’re uncertain, your team can get blindsided by someone you didn’t even think was a “stakeholder”. Learn how to get it right and make this the FIRST step in your public outreach.

Clinic #115: Who Is (and is Not) Your “Public”?

Getting Respect & Legitimacy, Higher Values & Democracy, Technical Rigor

With limited time and resources, which members of the vast “public” does your outreach need to focus on? If you’re uncertain, your team can get blindsided by someone you didn’t even think was a “stakeholder”. Learn how to get it right and make this the FIRST step in your public outreach.

Clinic #114 Immunize your project from damaging criticism

Getting Respect & Legitimacy, Higher Values & Democracy, Technical Rigor

Predict and prevent damaging attacks on your team and project recommendations.

Clinic #113: Your public is SO diverse, you can’t please everyone. Except – on this ONE issue

Getting Respect & Legitimacy, Higher Values & Democracy, Technical Rigor

When the “public” is made up of people with totally different ideas of what your team “should” do — how can you guide any kind of coherent, responsible, community decision?