1 / 17

Technical Innovation :

Technical Innovation :. Creative Solutions to Tight Budgets and Long-Term Sustainment. Brainstorming. What problem are you trying to solve? Focus on clarifying the core issue first Ex: “Notify teams about disasters or deployments.” What do you want?

melita
Download Presentation

Technical Innovation :

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Technical Innovation: Creative Solutions to Tight Budgets and Long-Term Sustainment

  2. Brainstorming • What problem are you trying to solve? • Focus on clarifying the core issue first • Ex: “Notify teams about disasters or deployments.” • What do you want? • Dream big; this is an exercise in creativity! • Consider new concepts regardless of how logical, or illogical, they initially seem. • Ex: “System that is not vulnerable to the same hazards as our other platforms.”

  3. Brainstorming continued… • What do you really need? • Financially sustainable • Intuitive user interface • Must not require a license to operate • Accessibility via mobile device • Ultimate deadline • Grant-year • Jurisdiction’s fiscal-year • Commencement of regulatory requirements

  4. Identify Your Resources • Developers • Technology Gurus / Software Designers • End Users / Frontline Staff • Preparedness Community • How will we pay for it? • Employee time • Federal / State grants • Pool funding from multiple agencies • Non-profit / Non-government organizations

  5. Development Philosophy Core Values of Your Project: • Inclusive • Sustainable • Accessible • Accountable • Transparent

  6. Development Philosophy • Be Inclusive • Whole community (professional and public) • Your system should work regardless of: • Jurisdictional geography • Population count / population density • Technical expertise of end-users • Funding streams (see: Sustainable) • Be Sustainable • Think long-term; avoid dependence on grants ($).

  7. Development Philosophy • Be Accessible • Consider ease-of-use for at-risk populations. Consider community members who are: • Homebound or have mobility issues • Developmentally disabled • Non-English speaking • Transient or homeless

  8. Development Philosophy • Be Accountable • Never shy away from criticism and critiques, honest feedback identifies areas of improvement and helps you build a better system • Be Transparent • Your project should always pass the “Front Page Test”. Make reports of system changes and progress available to anyone and everyone.

  9. System Attributes Technical Specifications • Compatible • Portable • Automated • Robust • Intuitive

  10. System Attributes • Compatible • Your new system should integrate with any existing system and communicate seamlessly across platforms. (Ex: New radios should be programmable for currently-used channels / frequencies • Portable • How easy is it to take your new system “on the road” or access the system from a remote location.

  11. System Attributes • Automated • Consider expediting certain processes without significant human interaction. (Ex: Monitoring software attached to CCTV cameras pings state law-enforcement database and flags reported vehicles via e-mail to host-agency dispatchers.) • Robust • Plan for interruptions and “weak links” in advance • Intuitive • System should require little to no advanced training

  12. Unanticipated Benefits • Truly Engages the Public • Clear directive with actionable task • Allows for practice during non-emergency events • Accessible anytime via website • Inclusive Regional System • D-A will work for any jurisdiction regardless of:

  13. Pro Tips • Pre-Game Success • Conduct preliminary demonstrations and build a user base prior to your official launch date • Branding is Important • Never underestimate the power of a successful marketing campaign. Work with your local public affairs team to build a launch strategy. • Say “Thank You” • No one builds these systems alone; it’s nice to give credit to those who came before you. 

  14. Pro Tips • Open-Source: Sharing is Good • Think globally, develop locally • Build Stronger Community Partnerships • Use the development process to engage your local, regional, and national partners. Their buy-in will facilitate more effective implementation. • Elevate Public Service • Your project should be an extension of your mission and goals as an agency!

  15. Technical Innovation Process • Step 1: Identify your obstacles and confront them as challenges to be overcome • Funding, staff time, training needs, etc. • Step 2: Focus on community, not ownership • Build your team based on subject matter expertise, not on daily titles or agency authority. Be inclusive. • Step 3: Create your new thing / system / process, then find people to break it and fix it accordingly • Rinse and repeat

  16. Final Thoughts With a little courage and professional curiosity we can overcome many of the obstacles common to technical projects. By tapping into previously unidentified subject matter experts and leveraging local resources we can build stronger, better, faster systems that level the playing field for our regional partners and enhance our ability to include the public in their own preparedness.

  17. Alisha Griswold Griswold.A@PortSeattle.org Pascal Schuback Schuback@uw.edu Thank You!

More Related