CUSTOMER PROBLEM

SOLUTION

EXECUTION VALUES, STRATEGY AND BRANDING

{ http://opensupporter.org }

Example Integrated AppR74 “Marriage Hero” Dashboard

Unified Events

• Single place to find events

• Finance events in Salsa

• Ticket Pricing

• Volunteer Events in VAN

• Vol Tracking

• No web front end

• Wanted email reminders

Fundraising

Hobnob, ActBlue, Salsa

Many data sources to aggregate

Friends. Who’s Voted? Who Hasn’t?

Customer Integration Challenges

Marriage Hero

Integration System

Salsa

CRM

AmicusVoter

Data

VANFacebook

Events

VAN/Salsa

P2p

$$

Pages

qgiv

$$

Salsa

$$

NGP

$$Act Blue

Contribution Integration

Social Networks

HubDB

Google

Facebook

Twitter

NGP

VAN

Silverpop

ActBlue

Trilogy

Ektron

Mobile Commons

Vendors

Mailers

MailChimp

Salsa

Trilogy Hub System

Vendor Integration Challenges

• Boutique online services for small & medium nonprofits

• Strategy, design, development

• WordPress, Drupal, others

• SalsaLabs, Luminate, BSD, Salesforce, etc.

• “agnostic”

Welcome to the tower of Babel

• You don’t need complicated needs or ideas to encounter this problem.

• Whether you've got 10 systems or just two, each integration requires a new, separate API “language.”

• This is grossly inefficient for everyone involved, including developers and nonprofits.

• Especially when you’re small.

Why it stinks for nonprofits

To get an integration done, you need to either:

1. Pay an agency/developer you know and trust to learn the language (if they don’t already)

2. Find a new and perhaps totally unfamiliar agency/developer that has expertise in the language

Either way is costly, however you measure cost.

Why it stinks for agencies like us

1. It’s impossible to speak every language, though there are efficiencies at scale (which we lack)

2. It’s hard to confidently provide estimates and timelines to clients/superiors regarding LoE to master language and fulfill implementation

3. It weakens relationships when people have to get their needs met by someone else

Wouldn’t it be great if we could just learn Esperanto? Is that even a thing?

• Drupal integration experts

• RedHen, a native Drupal CRM

• Engagement tools: events, donations, volunteer signups

• Salesforce, MailChimp, etc.

• 50k sites running on our contributions

Current Integration Approach

With OSDI

• Colorado Fair Share works to provide every Coloradan with a fair shot at a good job, a secure future and a strong voice in our democracy by standing up to the conservatives and Wall Street interests who block progress at every turn.

• In 2014, ran comprehensive independent campaign in support of Sen. Mark Udall – Field, Phones, Digital and Campus.

• Knocked on over 1 Million Doors, Ran 11 Field offices, and GOTV program on college campuses across the state.

SOLUTION

A Common API

Solution: Common API!

Customers, digital and tech directors, technology consultant

Application Developers

Platform Vendors

Progressive Innovation Principles

Big Business Fears Democratic Administrations

Level Playing Field

Who can innovate is determined by customers not market power

Microsoft’s control over Windows can’t limit who builds Windows Apps

Google, Apple, others??

Shared Control

The interop surface is defined democratically.

HTML Tags, attributes on a person

Standard will evolve to specialize and enhance

“Base Classes” for common objects

Vendor Differentiation

Vendors can add differentiated features and innovation without disconnecting from baseline

standards interop

What other areas do standards help innovation and competition?

Where does a lack of standards cause problems?

Audience Prompt

Example Demo(s)

• Unified Signup Form (multiple CRMs)

– Video Option

• Canvasser (platform agnostic tool)

Breakout Groups

• Each group come up with one example to reportback to the entire group

– Highlight their own integration challenges

– Customers Discuss interop and innovation scenarios

ORG, VALUES AND BRANDING

Customer/Cause Segments

Which best characterizes your customer segments regarding political, cause based ideals?

1. Serves any and all customers/causes regardless of where they sit on the progressive<-> conservative spectrum

2. Serves mostly progressive customers/causes unless the best way to serve a progressive goal requires supporting a conservative/republican

3. Serves strictly only progressive candidates/candidates/causes

4. Other: Please articulate

Make Your Voice Heard!

Help steer the specification

–Customer Coalition• Visit with Committee, Provide Feedback

• Support the cause!

–Technical Committee• Participate in spec development committee meetings

• Have your say!

Roadmap

• 2013– Shape Table– Technical Development

• 2014– Technical Consensus

• V1 Release at Netroots Nation (July 2014)

– Initial customer facing deployment– Customer evangelism and endorsements

• 2015– V2 – updated based on V1 learnings– Ready for 2016 election cycle

Customer CoalitionHelp us help you

• Help us– is a good idea and something vendors should prioritize in resourcing

– Helps recruit additional vendors

– Gives you committee access

– PR – join us in PR

• Help you– Invitations to education webinars and OSDI community

– Visibility shows your organization's leadership in technical advancement

– Reap lower costs and better choice in your technical and digital engagements

Tech Committee Developer

• Attend weekly committee calls (1hr)– Good Standing: present for past 3 meetings

– Thursdays 3pm eastern / 12 noon pacific

• Homework– Avg 30 min action items / 2 weeks

• Coalition Visibility– Your logo on our site

• Help with outreach and visibility– As possible, conference sessions, webinars

Technical Overview• Core RESTful Protocol

• JSON payload, HAL Hypermedia• User friendly exploration• CRUD Resource Access

• Data Model• People, Addresses, Emails, etc• Lists, Tags, Queries• Petitions, Forms, Survey Q&A• Events, RSVPS• Donations, Fundraising Pages• Futures (Canvassing, Social, etc)

Design Strategy● General purpose RESTful resource

architecture○ General purpose set of common

patterns○ Moldable to virtually any scenario

● “Helper” Optimizations based on need○ Common scenarios requiring

multiple operations or complexity○ Reduced to simpler “helper”

functions● Junior dev or web dev friendly

Org Structure• Governance Committee

– set the rules of the overall organization. That includes the structure, and approval of technical charter details (scope) created by the TC.

– Approval of new members of the TC

– NOT delve into technical details are to be left to the TC and PC.

– The members of the governance committee will be published on our website.

– Marketing, outreach, overall direction

– Executive Committee

• Technical Committee– Our current developer group will become the "Technical Committee" or TC

– The job of this committee is to define the core functions of the specification. This provides functionality for the core scenarios and implementation will result in a useful interface.

• Progressive Caucus– The progressive caucus (PC) is a self-selecting group of progressive entities and invited guests. It serves two functions

– A private discussion to establish a progressive technical position on issues where needed. This discussion may include implementation

details meant for progressive ears only. When a consensus position is achieved, this position will be brought back to the general TC.

– To define extensions to the core spec that will be restricted to progressive or "progressive-friendly" entities. The definitions may or may not be published.

• No Membership fees

Officers