50 likes | 273 Views
PRSA. April 29, 2014. PSRA Transition Planning. Recognize potential conflicts Technology will work but stakeholders don’t trust it will Acknowledge the rationales for resistance It is change It may threaten the expertise of SMEs in the field
E N D
PRSA April 29, 2014
PSRA Transition Planning • Recognize potential conflicts • Technology will work but stakeholders don’t trust it will • Acknowledge the rationales for resistance • It is change • It may threaten the expertise of SMEs in the field • SMEs may be personally liable for decision and outcome • High Stakes (loss of life and or property, bad press, etc.) • Learn the environment • Operating - what does the service do and for whom • Regulatory • Code Enforcement – how developed, how enforced, by whom • Stakeholder groups – learn who has a stake and how high the stakes are for each group
PSRA Transition Planning • Address each argument with facts • During assessment of the environment determine levels and causes of potential resistance • Develop solutions that address the considerations of stakeholder groups to limit resistance to adoption • If new solution is not addressed in applicable codes, begin advocacy with code development organizations • Develop understanding of governance structure • Understand organizational culture • Consider employing consultants who came from the impacted industry • Persuade influencers to support the solution
PSRA Transition Planning • Solution development • Assure new design is more reliable than existing design • Assure design is responsive to considerations of each stakeholder constituency • Assure compliance to the underlying objective of the governing code and application • Ongoing commitment to education • Once solution is accepted and embodied in the applicable code it may be incumbent upon providers to embrace the need to provide ongoing education of Authorities Having Jurisdiction in each municipality (this is application dependent).