2014-07-09



Image: DOBT

After Adam Becker and Clay Johnson completed their stints as White House Presidential Innovation Fellows working together on Project RFP-EZ, they were inspired to scale IT simplicity so that governments everywhere would no longer have to deal with traditional mediocre software solutions most legacy vendors provide.

That inspiration culminated into Department of Better Technology, a startup focused simply on building “great software for government.”

DOBT recently deployed its first product, Screendoor, aimed at making it easier for governments to create online forms to better manage incoming data and engage with citizens.

Becker shares some insights into the mission behind DOBT, Screendoor and why it’s so important for government.

What’s the background and inspiration for starting DOBT?

DOBT was born from Clay’s and my experience as Presidential Innovation Fellows. We had both worked on “civic technology” before, but neither of us had worked inside of government, and when we saw first-hand the terrible software that our governments run on, we basically said to each other, “we’ve gotta figure out a way to work on this.”

There’s obviously a few different routes you can take, but we felt that we’d be the most effective if we started a company like DOBT, where our software can be used by all government agencies, big and small.

Why focus on Screendoor as your first product?

We cover this in a bit in these two blog posts.

Basically, the civic technology community has been mostly focused on engagement, and thinking about things from the perspective of the citizen. It turns out that the root of this problem, that people don’t want to engage with their government, is that the current experience of engaging with government sucks.

Most people interact with their government through the interface of a form, and a really ugly one. It often involves printing, signing, faxing and waiting. And once that form is submitted to a government agency, it’s no easier on their end to manage those incoming responses.

Our reason for focusing on Screendoor is really two-fold:

We can help government agencies create a better experience for the citizens they serve

We can save time and money for those agencies by making their review process more efficient, and helping organize their data

What are Screendoor’s key features?

Frontend

We start with all of the basic “form builder” features, similar to what you’d find inside of Wufoo or Google Forms. You can add text fields, checkboxes, file inputs, etc. For users responding to forms, we automatically save their drafts, which is nice when you’ve got a long government form that you’d like to work on over multiple sittings.

Backend

The backend “review interface” is where Screendoor really shines. We offer a bunch of ways to manage your incoming responses:

You can assign custom rating fields (like a star-rating, or 1-10 number range) and collaboratively rank responses. We’ll total up the averages automatically.

You can add statuses and labels to create a custom workflow. For example, we run our hiring process through Screendoor, and applicants flow through “Incoming,” “Interviewing,” “Offer made,” and “Hired” statuses.

You can send batch messages to subsets of your responders, automatically merging in variables from their response. Imagine you’re running an apps contest, and have just moved the winning entries to a “Won” status. Screendoor lets you easily send a personalized message to each entrant, letting them know that they’ve won your contest.

What plans do you have for the future?

We’re focused on making Screendoor more robust, easier to use, and useful for even more use cases, and we hope that by doing these things, it’ll also help us get it into the hands of more and more government agencies.

Oh, and it’s not the most exciting thing by far, but we’re looking forward to meeting more and more security & compliance regulations. It sounds boring, but it’s something that can prevent certain folks inside government from taking advantage of an app like Screendoor.

Related

Startup.civ: StreetCred

Oakland vendor API requirement a big step for municipal open government

GovFresh WP: building a government WordPress theme

Show more