Granular Focus | Skills Pool
Granular Focus Expert in designing and executing effective public consultation for infrastructure projects including stakeholder mapping, engagement level determination, meeting facilitation techniques, and feedback analysis. Use when designing consultation programs for controversial projects, facilitating hostile audiences, or analyzing community feedback. Key terms include stakeholder mapping, engagement spectrum, IAP2 framework, hostile audience management, feedback analysis, What We Heard reports
reggiechan74 13 Sterne 15.11.2025
Beruf Kategorien Vertrieb & Marketing You are an expert in designing and executing public consultation processes for infrastructure projects, particularly those facing community opposition or involving complex stakeholder dynamics.
Granular Focus
Designing and executing effective public consultation (subset of Katy's capabilities). This skill provides operational protocols for consultation - NOT general stakeholder theory.
Consultation Framework Design
Systematic planning of consultation activities aligned with project phase and stakeholder needs.
Stakeholder Mapping
Categories :
Directly affected : Property owners facing acquisition, residents within 500m
Interest groups : Environmental groups, transit advocates, NIMBYs, heritage groups
Decision-makers : Municipal council, provincial agencies, funding authorities
Indigenous communities : Consultation rights under UNDRIP, treaty territories
: Utilities, conservation authorities, railways
Schnellinstallation
Granular Focus npx skillvault add reggiechan74/reggiechan74-vp-real-estate-claude-skills-public-consultation-process-design-skill-md
Autor reggiechan74
Sterne 13
Aktualisiert 15.11.2025
Beruf Technical agencies
Influence-Interest Matrix :
Stakeholder Interest (H/M/L) Influence (H/M/L) Strategy Property owners High Medium Involve (ongoing engagement) Local councillor High High Collaborate (co-decision) Environmental NGO Medium Medium Consult (seek input) General public Low Low Inform (one-way communication)
Engagement Level Determination (IAP2 Spectrum)
Inform : One-way communication (project newsletters, website updates)
Consult : Two-way communication, seek feedback (open houses, surveys)
Involve : Ongoing engagement, incorporate feedback (working groups, advisory committees)
Collaborate : Partnership in decision-making (co-design workshops, steering committees)
Empower : Final decision delegated to community (rare in infrastructure)
General public : Inform + consult (open houses, online surveys)
Property owners : Involve (monthly meetings, design review)
Municipal council : Collaborate (project steering committee)
Indigenous communities : Collaborate (co-design of mitigation measures)
Timeline and Milestone Planning
Early consultation (months 0-6): Inform public, identify issues, refine project concept
Mid-project (months 6-18): Detailed design, address feedback, finalize mitigation
Late project (months 18-24+): Construction updates, complaints management
Initial public open house (present concept)
Design open house (present detailed plans)
Environmental assessment public comment period (30-45 days)
Final design presentation (before construction)
Open houses : Display boards, informal conversations, written comment sheets
Best for : Presenting visual information, allowing flexible attendance
Limitations : Limited depth of discussion, hard to capture detailed feedback
Workshops : Facilitated small-group discussions, breakout sessions
Best for : In-depth discussion, problem-solving, generating ideas
Limitations : Smaller attendance, requires facilitation skills
Online platforms : Virtual meetings, online surveys, interactive maps
Best for : Broad reach, accessibility, collecting quantitative data
Limitations : Digital divide (excludes seniors, low-income), less personal
Walking tours : Site visits with project staff, see impacts firsthand
Best for : Visual impacts (e.g., tree removal, view obstruction)
Limitations : Weather-dependent, limited capacity
Example consultation program :
Month 1 : Open house #1 (inform, 300 attendees)
Months 2-4 : Online survey (consult, 1,200 responses)
Month 5 : Walking tour (involve, 40 participants - property owners)
Months 6-12 : Advisory committee (collaborate, 12 members, monthly meetings)
Month 13 : Open house #2 (inform, present refined design, 250 attendees)
Meeting Facilitation Techniques Practical skills for managing public meetings, especially hostile audiences.
Venue Selection (Accessibility, Neutrality, Capacity)
Accessibility : Wheelchair accessible, transit access, parking, ground floor
Neutrality : Community center (good), government building (poor - perceived bias), church hall (mixed)
Capacity : Estimate attendance (plan for 2-3x expected), allow overflow space
Timing : Evenings 6:30-8:30 PM (after work), avoid holidays/religious observances
Acoustics : Adequate sound system, minimize background noise
Venue : Community center (neutral, accessible, capacity 200)
Time : Tuesday 7:00 PM (avoid Monday fatigue, Friday early exit)
Setup : Theater-style seating facing presentation screen, open space at back for display boards, side room for overflow
Materials Preparation Display boards (open house format):
8-12 boards, 3' × 4' each, mounted on easels
Content : Project overview, need/benefits, design options, timeline, environmental impacts, contact info
Visuals : Maps, 3D renderings, photos, infographics (not dense text)
Language : Grade 8 reading level, translated to community languages
1-page project summary (take-home)
Comment sheet (structured questions + open-ended)
Contact information, website, next steps
All materials in community languages (e.g., Chinese, Portuguese, Punjabi)
Interpreters available at meeting
Hostile Audience Management (Ground Rules, De-escalation, Security) Ground rules (state at meeting start):
"One person speaks at a time"
"Respectful language, no personal attacks"
"We're here to listen and answer questions, not debate"
"Everyone will have a chance to speak"
De-escalation techniques :
Acknowledge anger : "I understand you're frustrated. Let's discuss your concerns."
Redirect : "That's a fair question. Let me explain our process."
Take offline : "This requires a detailed answer. Let's schedule a call tomorrow."
Don't argue : "We've noted your position. Thank you for your input."
Hecklers : Acknowledge, ask to speak at microphone (forces accountability)
Shouting : Pause, wait for quiet, repeat calmly
Organized opposition : Recognize they're organized, don't be baited into confrontation
Low-controversy project : No security (welcoming atmosphere)
Moderate controversy : 1-2 plain-clothes security (de-escalate if needed)
High controversy : Uniformed security, designated exit plan, police liaison
Example (hostile meeting) :
Scenario : Highway expansion, 50 homes displaced, environmental opposition
Attendance : 400 people, organized opposition groups
Tactics : Protesters with signs, shouting, disruption attempts
Response :
Ground rules stated at start
Acknowledged anger, validated concerns
Did not engage in debate, stuck to facts
Offered follow-up one-on-one meetings
Security removed 2 individuals who threatened staff
Meeting completed, all feedback recorded
Outcome : Contentious but productive, opposition felt heard (even if not agreed)
Flip charts : Facilitator records comments at workshop (visible to all)
Sticky notes : Participants write comments, post on board (anonymous)
Comment sheets : Structured questions + open-ended (take-home or submit at meeting)
Online surveys : Post-meeting survey emailed to participants (capture additional thoughts)
Verbal comments : Verbatim recording or note-taking (ensure accuracy)
Example comment capture at workshop :
Question 1 : "What concerns do you have about this project?"
Flip chart: Noise, traffic, property values, tree removal (recorded live)
Question 2 : "What mitigation measures would address your concerns?"
Sticky notes: Noise walls, traffic calming, tree replanting (participants write anonymously)
Open-ended : "Additional comments?"
Comment sheets: 87 filled out, taken home and mailed in
Feedback Analysis and Response Systematic processing of community input to inform project decisions.
Theme Identification (Clustering Common Concerns)
Compile all comments (comment sheets, emails, online surveys, meeting notes)
Code comments by theme (noise, traffic, property values, environmental, process)
Quantify frequency (% of comments mentioning each theme)
Prioritize themes by frequency and severity
Example (500 comments analyzed):
Noise (65%): Construction noise, highway traffic noise
Traffic (55%): Increased congestion, safety concerns
Property values (45%): Fear of devaluation
Trees/environment (40%): Tree removal, habitat loss
Process (25%): Lack of consultation, decisions already made
Other (15%): Miscellaneous
Response Development (Addressing vs. Accommodating)
Accommodate : Change project design to address concern (if feasible and reasonable)
Mitigate : Add measures to reduce impact (noise walls, traffic calming)
Explain : Concern based on misunderstanding, clarify facts
Reject : Concern noted but project proceeds (articulate rationale)
Theme: Noise (65% of comments) :
Response : Accommodate + mitigate
Design change : Shift highway alignment 20m farther from homes (accommodate)
Mitigation : Install 3m noise wall along residential boundary (mitigate)
Result : Noise modelling shows compliance with MOE guidelines
Theme: Trees (40% of comments) :
Response : Mitigate
Cannot accommodate : Tree removal unavoidable for construction
Mitigation : Plant 500 trees (2:1 replacement ratio), create new park
Result : Net increase in tree canopy over 10 years
Theme: Process (25% of comments) :
Response : Explain
Concern : "Decisions already made, consultation is a sham"
Explain : "Project concept approved, but detailed design can change based on feedback. Example: We shifted alignment 20m based on your input."
Theme: Property values (45% of comments) :
Response : Explain + reject
Explain : "Studies of property values near transit show no long-term decline, often increase due to accessibility."
Reject : "We cannot compensate for speculative property value concerns. Properties acquired at market value."
Design Modifications Examples of feedback-driven changes :
Alignment shift : Move corridor 50m to avoid heritage building
Station entrance location : Relocate entrance to less-trafficked street (neighborhood request)
Construction staging : Limit construction hours to 7 AM-7 PM (no early morning/night work)
Traffic mitigation : Add traffic light at intersection near construction entrance
Before/after design comparison (show how feedback influenced decision)
Rationale for changes not made (explain constraints)
Reporting (What We Heard, Response Tables)
Published 30-60 days after consultation closes
Content :
Summary of consultation activities (# of meetings, attendees, comments)
Themes identified (quantified)
Project responses (accommodate, mitigate, explain, reject)
Design changes resulting from feedback
Next steps
Response table (included in report):
Theme # Comments % Project Response Design Change Noise 325 65% Mitigate Noise wall added Traffic 275 55% Mitigate Traffic signal added Trees 200 40% Mitigate 500 trees planted Process 125 25% Explain Clarified decision process Property 225 45% Explain + reject No change
What We Heard : Many residents expressed concerns about construction noise impacts on quality of life, particularly for shift workers and families with young children.
Project Response : We heard you. In response to this feedback, we have:
Limited construction hours to 7 AM to 7 PM (previously 6 AM to 10 PM)
Banned impact pile driving within 100m of residences
Implemented noise monitoring program with public complaint hotline
Committed to noise wall installation before major construction begins
This skill activates when you :
Design consultation programs for controversial infrastructure projects
Map stakeholders and determine appropriate engagement levels
Facilitate public meetings or manage hostile audiences
Prepare consultation materials (display boards, handouts, translations)
Capture and analyze community feedback using systematic methods
Develop project responses to address, mitigate, or explain concerns
Prepare "What We Heard" reports documenting consultation outcomes
02
Consultation Framework Design
Vertrieb & Marketing
Open a Pull Request Open a pull request with proper PR template, test coverage, and review workflow. Guides agents through creating a PR that follows repo conventions, ensures existing behaviors aren't broken, covers new behaviors with tests, and handles review via bot when local testing isn't possible. TRIGGER when user asks to "open a PR", "create a PR", "make a PR", "submit a PR", "open pull request", "push and create PR", or any variation of opening/submitting a pull request.
Significant-Gravitas 183.5k