11 ms·
USDS Digital Services Playbook
- ajcp 6y agoWhile this is all well and good it feels like a slick "thought leadership" campaign that provides little in the way of actual solutions to the issues USG orgs face when building/providing digital services. The challenge is not the "approach", but rather a system that constrains the ability to even begin that approach. I find #7 especially hollow: > We need talented people working in government who have experience creating modern digital services. Sure, no one would argue against that, but the solution to this can't come from the team implementing or providing the digital service. Rather the whole of USG's incredibly obtuse, opaque, and inflexible centralized hiring system needs to be addressed. This is no better than telling a USA Special Forces team commander that in order for his operators to be more effective he needs the Army to recruit better soldiers.
- brdd 6y agoI disagree — as a direct result of play #7 in this playbook, multiple large-scale initiatives were launched; most notably 18F, which is like a "startup" within the federal government: https://18f.gsa.gov/ https://18f.gsa.gov/ Another one that comes to mind is Coding It Forward, which has the express mission of creating government tech internships that rival FB/Google internships in terms of pay, experience, and mentorship: https://www.codingitforward.com/ https://www.codingitforward.com/
- heyitsguay 6y agoThanks for sharing! This is all good to know, I'll be reaching out to see if there's any possibility of these groups helping to address some of the issues within our institute at the NIH. Right now it's unclear to what extent that can assist an intramural research program.
- ajcp 6y ago18F is definitely a good start. I would also try Code for America[1], although they might only work at more of a local level. 1. https://www.codeforamerica.org/ https://www.codeforamerica.org/
- wslack 6y agoThere are digital groups of various sorts already operating at NIH. If the folks working on it are federal employees, there are groups that can help - but there has to be buy-in from decision makers. Bureaucracies have infinite ways to stop something if you don't get cover from certain people.
- ajcp 6y ago18F pre-dates the U.S. Digital Service by 6 months. Coding It Forward is a civil society initiative, not a government one, and is analogous to thinking that a weak diplomatic corps can be fixed by sponsoring more high school Model U.N. chapters. There is no lack of viable and willing candidates _outside_ of the system, the issue is getting them _inside_ and letting them inform it.
- heyitsguay 6y agoYeah this meshes with my experiences working at the NIH. Lots of interest in big data, AI, etc. etc., and even financial incentives for new hires in those areas, but absolutely no coordinated approach to recruitment, retention, or project management. A few labs or support groups end up with great teams, but mostly tech knowledge is redundantly siloed in small mediocre groups across dozens of teams institutes-wide. And that's not even touching on IT issues...
- kelnos 6y agoA big problem with hiring is just USG pay scales. Even the top pay grades come in at less than what an average (or even less than average) developer can make in industry. Much less if you also consider equity comp. Sure, there are some people who will see working for USDS or 18F as a call to serve their country, and will accept a pay cut in order to do that, but I imagine that's a pretty small slice of the pie. Beyond that, it's the bureaucracy. I would honestly consider said pay cut in order to help make dealing with government computing systems better, but what I will not deal with is layers upon layers upon layers of bureaucracy. I've watched the 50-person startup I started at 9 years ago evolve into a 3500-person public company, and even here I find the bureaucracy and hierarchy stifling at times. At a government job I imagine it'll be orders of magnitude worse. I wouldn't even last half a year in that environment. Yes, Play #4 in their list in theory suggests that they'll try to cut through all that, but I don't believe for a second that will go well.
- randmeerkat 6y agoWhat would be nice is if these government jobs had training. The military can take someone from the street and make them a specialist in something. If USDS could take someone and make them into what they needed, the lower salary might be better justified.
- ajcp 6y agoI could not agree more. If the USG wants to provide competent digital services to it's customer/shareholder then it might make more sense to get rid of the Digital Service in the WH and rather expand and go all in on 18F, where it provides a whole career progression from basic training on up through SES. I feel the absence of job training upon hiring is also why there is no concept of "company men" after the Boomer Generation; companies stopped investing in the employees they wanted and started treating them like pre-packaged commodity.
- randmeerkat 6y agoI didn’t realize 18F has a training program. That’s awesome. I agree with your frustrations about training in general too. I wish companies provided that _and_ provided real career progression goals. Instead it’s learn the tech for your job after work and some vague one page sheet from HR about what the next level is, which really comes down to a manager’s opinion more than anything really measurable.
- dan-0 6y ago> I find #7 especially hollow I think there's some confusion here on what and how the USDS works. They embed into government organizations to improve services and systems, bringing expertise that doesn't normally exist in government, while not working directly for the organization they're embedded in. USDS doesn't follow normal hiring practices either. They recruit directly for limited employment terms, max of 4 years. This helps offset the entrenched beaurocratic mindset that exists in a lot of USG organisations, and allows them to recruit current experts in a particular field. From the Special Operations analogy this would be equivalent of the Military giving them direct hiring/recruitment ability from both the Armed Services and direct from civilian #7 "Bring in experienced teams" isn't hollow, it's their core mission.
- ajcp 6y agoI think the confusion is not in what the USDS does, but rather who their Play Book is intended for. Is it prescriptive or descriptive? If it's the former (as I took it) then we're not talking about the USDS itself, but the USG. If it's the latter then I defer to you, but still don't think it solves the structural problems that makes the USDS relevant in the first place. Going back to our US Special Forces team, the US Army actually did (attempt)to solve for this by simplifying the pipeline with the 18X "X-Ray" Program.
- 0kl 6y agohttps://smeqa.usds.gov/ https://smeqa.usds.gov/ We do work on hiring as well
- ajcp 6y agoVery cool, thank you for the information!
- wslack 6y agoThis is hard for practical reasons. The civil service needs to be a place where everyone can get a job without knowing someone inside, so a lot of best practices in the private sector (referral-based hiring) don't easily translate. It's akin to the Postal Service visiting everyone's mailbox each day - not efficient, but important. THAT SAID, there are massive improvements that can happen in hiring - if agencies have incentives to pursue them!
- ajcp 6y agoI agree, this is a really tough nut to crack without completely overhauling the hiring system and making some hard decisions. USAJobs was a really good-faith effort, but it's not it.
- kqr 6y agoAs an outsider, I hold the USDS in great regard. Probably too much because of Marianne Belotti's writings from her time there, but also from what I would like to think are more nuanced perspectives. My country does not have anything like it, but what countries do?
- MattGaiser 6y agoCanada has a similar group: https://digital.canada.ca/ https://digital.canada.ca/
- wikibob 6y agoUSDS is modeled after Britain’s GDS.
- petepete 6y agoAs is Australia's. They've diverged a bit more now but when launched it was pretty much a colour change and switching some lions and unicorns for kangaroos and emus. https://designsystem.gov.au/ https://designsystem.gov.au/
- deleted 6y ago[deleted]
- jzwinck 6y agoSingapore: https://www.tech.gov.sg/ https://www.tech.gov.sg/ Australia: https://www.dta.gov.au/ https://www.dta.gov.au/
- pm 6y agoAn acquaintance worked as CTO of the DTA, and ultimately it was a joke. The skills were there, but the clout to bust through politics was not there, so nothing ever got done. He ended up leaving after less than a year.
- say_it_as_it_is 6y agoI wonder how much the government paid consultants to write this.
- shanear 6y agoI was a member of the USDS for 4 years. Every member of the USDS is a government employee with a fully transparent government salary, most of whom are taking a massive pay cut to serve their country and its citizens.
- dkhenry 6y agoNot only that, but the entire process is fairly transparent. For instance the code for this website is available here https://github.com/usds/playbook https://github.com/usds/playbook Along with full commit history.
- deleted 6y ago[deleted]
- stevesycombacct 6y agoI have a lot of heartburn reading something like this. I spent a decade in government consulting trying to implement anything resembling "data science" or "DevOps" and got repeatedly shut down by higher ups or by random bureaucrats that saw any modern practices, including any technology, as a threat. Excel macros working one day, then prohibited the next by new IT policies. Directors demanding that service line bosses meet with me to discuss "data-driven decision-making", followed by a solid week of said chiefs telling me that my job is a joke. Actual honest-to-God employees trying to make a difference in financial openness having their coworkers walk by their desks and loudly shout they "ain't doing that shit" and walking away. Two years hunting for a database to store 2 GB of data, and only finding one when a new contractor onboarded and knew a guy in the next office over who would let them have a partition of SQL Server. I wish I was making any of this up. The federal government has massive, massive employee culture issues. This list is... a nice dream.
- catillac 6y agoThe USDS doesn’t hire people through normal channels or for permanent hire, but hires people who have experience in the private sector and want to change the government. While it’s true that they hire significantly more junior people than before the trump admin (if you compare things like years of experience pre USDS then and now, or pre USDS salaries then and now), it’s still often experienced people who want to make a difference for a short period of time before leaving government.
- wslack 6y agoFWIW, I don't know if there's a significant difference along a senior vs junior axis. I think the set of people willing to consider gov employment at USDS certainly (and reasonably) changed in after the 2016 election, so USDS lost access to some talent, but there is good work happening now. Most importantly, USDS is seen as non-partisan, and so has been able to have good impact in both administrations.
- bladegash 6y agoHave certainly seen and experienced what you did, so I hear you. However, there are improvements slowly being made to be optimistic about. DevOps (or DevSecOps as they like to refer to it now...) is definitely becoming a more ingrained practice. If you’re interested, take a look at initiatives such as Cloud One, or some of the work being done by GSA (especially 18F) and USCIS (of all places). Interestingly, the 21st Century IDEA Act mandates compliance with the USWDS now (at least for publicly facing sites) and there is a maturity model built around it. We’ll see whether or not agencies comply, but it’s a step in the right direction.
- jolux 6y agoI think the biggest problem any US government agency has (federal or state) in producing services that leverage modern technology is that they cannot afford to pay people market rates. We have a mentality in the US that government cannot do anything right, but it seems of late (last 40 years or so) that we are kneecapping government's ability to execute and then complaining about it when it can't and making pronouncements about how only the private sector can understand tech. Government technology workforces are thus composed largely of either people who are below average in competence or above average and willing to take a pay cut because they care about the cause, but we shouldn't expect people to do that, and there aren't very many of them. We should give government a fighting chance.
- zippy5 6y agoIt’s one thing to pay a highly competent person 6 figures. It’s an entirely different thing if you can’t fire them. I’m not saying that the government doesn’t need more competent people but it’s not going to work if there’s a bigger carrot and no stick.
- wslack 6y agoPart of a solution for that are term-limited civil service jobs - that keeps a rotation of talent and low performers can't stay forever. That said, you raise an important problem - how do you manage poor performers without allowing a bad-faith political official to fire people unfairly?
- dodobirdlord 6y agoProvide clear mandates and then structurally separate organizations that should exist indefinitely from most interference by elected officials. Some of the most effective institutions of the US Government are the ones that were deliberately structured to be self-organizing, the military, the federal reserve system, and (until recently) the postal service.
- ryanianian 6y agoAnother conclusion based on the same facts is that the government has no business doing its own technology and should do what they do for weapons and roads: contract it out.
- random5634 6y agoThe first point would be gamechanging. Also used to do govt work. I'm sure everyone has stories. My takeaways. 1) Understand what people need -> AND LET THEM DO IT. 2) DO NOT ADD A SINGLE NEW THING with the IT / automation. If the old system doesn't have it DO NOT ADD IT. No 20 extra fields for demographics if you didn't track that before. That can be added later IF it's a MUST. If they would take away all various fifedoms and hassle - people actually would bring a lot more tech into gov. Let the local business / division people make a decision. The only requirement be that they go through a 1 hr training and be exposed to 3 packages in their space (ie, do demos no powerpoint). Take away all other requirements. Be OK with smaller failures. Govt is so scared of just letting folks try stuff out that everything turns into a 100M project that goes totally of the rails in terms of scope etc (ie, what people need / want is long forgotten, it's what MANAGERS want that gets emphasized). Result - even if successful (rarely) for downline workers the software brings TONS of extra (not less) work. ---- My own examples. The IT folks say that passwords have to change every 90 days. Google for example does not default to this (stupid) rule - they push two factor without SMS (which is better). Bam - you are out or have to pay for a "security" solution on top of whatever standard platform you are using with admin rights that can force rotate passwords (and is a MASSIVE backdoor itself vs self-serve password mgmt). Then purchasing. We need an ipad to edit some videos. OH, Apple is not supported. This is 10K employees but you can't get an apple product to use unless the city atty will sign off on a variance (no chance).
- wslack 6y ago> The IT folks say that passwords have to change every 90 days This is explicitly not the NIST recommendation (the group in gov that sets some security standards), but the word is not getting out quickly.
- random5634 6y agoFor a long time this must have been on the recommendation list - because password forms with insane complexity (12 charachters, upper, lower etc), but then non copy pastable forms and 60 day change requirements remained very common. The current IRS requirements are 90 day password changes. Ergo - many people write their passwords down in a text document next to the software launch icon. What I don't get - if your computer is hacked, and you force people to write down their passwords on the computer being hacked, they will even more easily be able to access the systems you have access to. Google seems to get this right. I have had same password for 20 years, if I login with a new device I use my MFA (no SMS). If I do a security sensitive op I need to login and do an MFA again (password reset etc). I imagine they actually monitor and rate limit bad login attempts etc. A 10 character password is really fine then in my view as an example.
- nosmokewhereiam 6y agoDoing more for less often equates to 80% security because 99% security is an order of magnitude more costly.
- ineedasername 6y agoThere's also always a trade off between usability & user friction with high security systems. Although improvements in security software usability have eliminated some of those barriers. And systems security is like physical safes/locks: It should be rated in terms of how much effort it would take to bypass it, and implemented in proportion to the value/risk of exposure of the secure objects/data. Clearly this is an idealized model though: SolarWinds has show that approaches to securing high-value assets are.... lacking.
- jschulenklopper 6y agoThere was an interesting article in Wired, in 2018: https://www.wired.com/story/obamas-us-digital-service-survives-trumpquietly/ https://www.wired.com/story/obamas-us-digital-service-surviv...
- deleted 6y ago[deleted]
- motohagiography 6y agoThis breaks govt and public service culture, but that's the point. Technology really drives those organizations, just very slowly, as they've finally got the hang of those whole "client/ server" concept, and the notion of providing "services" at all. Of course the most hilarious aspects of this are when departments foist hours of farcical forms on your projects and insist they are providing you a "service," where the service is compliance with their gating demands to fill out forms. (looking at you, infosec) Many of these organizations have evolved precisely to deflect accountability, as authority without responsibility is the ultimate measure of bureaucratic success. I am an advocate for this playbook, but change will take time, probably until we've moved on to something better...
- llimllib 6y agoAt Ad Hoc, we have a version of this that expands on the USDS one with our own experiences and opinions: https://www.adhocteam.us/playbook/ https://www.adhocteam.us/playbook/ If you want to make change in the government, and don't want to become a federal employee, being a contractor is an alternative that you might consider: https://www.adhocteam.us/join/ https://www.adhocteam.us/join/ It can be frustrating work, but it can also be enormously satisfying; I've been doing it now for ~6 years. Feel free to ask me questions if you want, I'm not a recruiter, just an engineer that's been building government products for a few years and trying to improve how they get built.
- tootie 6y agoThis is great for green field but what about replacing an ancient legacy system that's running loads of critical functions?