<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Aaron Snow on Medium]]></title>
        <description><![CDATA[Stories by Aaron Snow on Medium]]></description>
        <link>https://medium.com/@aaronsnow?source=rss-a52d9a60517f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*iFqKTXn3lbJtSgIk3x-xpg.jpeg</url>
            <title>Stories by Aaron Snow on Medium</title>
            <link>https://medium.com/@aaronsnow?source=rss-a52d9a60517f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:43:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@aaronsnow/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Sharing Federal Digital Services with the Other Layers of Government]]></title>
            <link>https://medium.com/@aaronsnow/sharing-federal-digital-services-with-the-other-layers-of-government-e8a6e4f3dd24?source=rss-a52d9a60517f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8a6e4f3dd24</guid>
            <category><![CDATA[digital-government]]></category>
            <category><![CDATA[united-states]]></category>
            <category><![CDATA[canada]]></category>
            <dc:creator><![CDATA[Aaron Snow]]></dc:creator>
            <pubDate>Mon, 09 May 2022 08:24:13 GMT</pubDate>
            <atom:updated>2022-05-09T08:24:13.004Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The U.S. and Canadian governments are both considering legislation to enable it. It’s an important development that can’t happen soon enough.</em></p><p>With last week came the good news that the Government of Canada, in an omnibus budget bill, has included language granting the <a href="https://digital.canada.ca/">Canadian Digital Service</a> (and its <a href="https://www.canada.ca/en/treasury-board-secretariat.html">parent department</a>) a new and important capability: Soon, knock wood, a legislative amendment will enable CDS to provide its digital platform services like <a href="https://notification.canada.ca/">GC Notify</a>, <a href="https://articles.alpha.canada.ca/">GC Articles</a>, and <a href="https://forms-formulaires.alpha.canada.ca/en/welcome-bienvenue">GC Forms</a> not just to other federal departments, but <a href="https://www.parl.ca/DocumentViewer/en/44-1/bill/C-19/first-reading#ID0E0FK0DA">to provincial, territorial, indigenous, and local governments throughout Canada</a>, fulfilling <a href="https://budget.gc.ca/2022/report-rapport/chap9-en.html#m173">a commitment the current government made in its 2022 budget</a>.</p><p>The United States is not far behind. There’s <a href="https://www.congress.gov/bill/117th-congress/senate-bill/3890">a bill in the Senate</a> right now with bipartisan support which, if passed, will enable federal agencies — like GSA’s Technology Transformation Service, home of <a href="https://www.login.gov/">login.gov</a>, <a href="https://cloud.gov/">cloud.gov</a>, <a href="https://search.gov/">search.gov</a>, <a href="https://federalist.18f.gov/">Federalist</a>, and other valuable services — to make their technology services available to state, local, tribal, and territorial (“SLTT”) governments. The US bill predictably bows more to the private sector than Canada’s legislation, but its intent is plainly the same: “Congress must not allow agencies at various levels of government to operate in completely independent silos, especially when Federal benefits and programs are being administered at the State, local, territorial, and Tribal levels, which, in doing so, requires far greater taxpayer resources to be spent developing and maintaining systems, programs, projects, and other services that can be better delivered and managed cooperatively between jurisdictions.”</p><p>Amen. These developments are more important than they might sound. Sharing federal services with state, provincial, local, indigenous, territorial and tribal (“SPLITT”) governments is not just an exercise in cost efficiency; it’s a critical step toward creating vital working-level connections, understandings, and trust between those layers of government — the absence of which comes into sharp relief in moments of crisis.</p><p>Highly decentralized, federated governments like the US and Canada are at a fundamental disadvantage in service digitalization. Unitary governments can make decisions in one place, and impose data standards and centrally-provided platforms and tools down to the regional and local levels. We have no such luck. In a multi-layer, federated government, when a priority is national in scope (e.g., a global public health issue), but the relevant data and implementation authorities are aggressively sub-national (power devolved to the states and provinces), there are too many stakeholders in any given question to realistically expect speedy alignment. There is no such thing as a <a href="https://www.theguardian.com/technology/2018/apr/24/the-two-pizza-rule-and-the-secret-of-amazons-success">two-pizza meeting</a> to decide a multi-layer intergovernmental issue.</p><p>This played out predictably during the early days of the pandemic. Purely federal issues were quickly and impressively handled: in one pair of very public successes, the IRS and CRA both made the necessary technology adjustments in just a few weeks to enable them to successfully send money to tens of millions of people to keep their national economies afloat amidst lockdowns. But fed/state and fed/provincial issues did not go as swimmingly. Data and digital tool sharing across the layers was difficult at best and often infeasible. There was little if any <em>lingua franca </em>between the layers, and too few working-level trust relationships. States, provinces, and cities scrambled to implement their own COVID information websites, their own COVID data collection standards and mechanisms, their own vaccine appointment sign-up systems — so much so that in the U.S., an entirely new organization, <a href="https://www.usdigitalresponse.org/">US Digital Response</a>, emerged to arrange for hundreds of technology-skilled volunteers to help dozens of cities, towns, and states through those issues, one by one by one.</p><p>But we have some early evidence that as SPLITT governments start to use shared federal tools and services, this situation can improve.</p><p>Canada’s legislation has been roughly two years in the making. It springs from a successful pilot that started shortly after the pandemic struck in early 2020. CDS had only a few months earlier launched its <a href="https://notification.canada.ca/">GC Notify</a> service for federal departments. It had garnered <a href="https://www.ctvnews.ca/politics/you-ve-got-mail-feds-test-new-e-notification-service-to-save-cash-time-1.4705274">media interest</a> but only slow-and-steady adoption. The pandemic changed that: government departments responding to COVID-19 needed a good tool, quickly and easily available to them, for sending emails and text messages, and GC Notify fit the bill perfectly. The team worked overtime to accommodate overnight popularity.</p><p>But that wasn’t helping CDS’s provincial and territorial counterparts, who were also racing to deliver information and tools quickly to their constituents. A week before Canada’s first wave of lockdowns, <a href="https://twitter.com/tashclarke73/status/1235859571647713281">provinces started asking whether they could use GC Notify</a>, but CDS wasn’t yet authorized to provide services outside of the federal space. Soon after, though, Treasury Board Secretary Peter Wallace signed off on a limited time, pandemic emergency authority for CDS to do just that, and <a href="https://twitter.com/tashclarke73/status/1278808603500175361">the Nova Scotia Digital Service became the first provincial team to adopt GC Notify</a>, first for their Safe Check-In service and then for other pandemic-driven needs.</p><p>It was a big success. Nova Scotia’s team said adoption was painless and fast, users were happy, and shared data indicating the thousands of dollars and person-hours saved just in the first weeks of the Safe Check-In service. And why not? To CDS, the incremental cost of having NSDS as a GC Notify user was infinitesimal; at the time, CDS estimated it would cost only $4,000 to send 30 million emails — one to every adult in Canada — and Nova Scotia was sending thousands of messages, not millions.</p><p>It’s the kind of win-win governments should want to replicate, over and over. To be sure, some policy considerations that were set aside temporarily in light of the pandemic exigency had to be addressed eventually. (Who owns and is liable for the security of provincial data that passes through a federal system? Should the federal government charge other governments for these services?) But when CDS and its departmental colleagues began to consider how to make the authority permanent, they returned to those issues, and discovered they were eminently solvable.</p><p>I know less about the provenance of the US legislation, but doubtless it comes from a similar understanding and need. TTS has long recognized the SLTT appetite for such help. Open-source TTS projects like <a href="https://analytics.usa.gov/">analytics.usa.gov</a> and the <a href="https://designsystem.digital.gov/">US Web Design System</a> have been replicated (“forked”) and re-used by hundreds of cities, states, other nations, non-profits, and private companies; but those organizations each need in-house expertise to make use of the code. Supported online services — SaaS and PaaS — are the next frontier, potentially an order of magnitude more impactful for SLTTs. GSA and OMB have expended considerable effort over the last couple years to ensure that <a href="https://www.login.gov/">login.gov</a> can be used, for a fee, by SLTT governments; and the first state integrations with login.gov are finally underway. The current chief executive of the GSA, Administrator Robin Carnahan, was once a cabinet official in her home state of Missouri, and that experience made her a longtime proponent of better collaboration and exchange of tools between governments. In 2016 she joined 18F and established its State and Local practice; in 2020 she and 18F colleague Waldo Jaquith (now a senior advisor to Carnahan at GSA) created what is now the <a href="https://softwarecollaborative.org/">Intergovernmental Software Collaborative</a> (one of the projects I work on at <a href="https://beeckcenter.georgetown.edu/">Georgetown University’s Beeck Center</a>), to study and promote jurisdictions working together rather than independently and redundantly on software projects, on the theory that building collaboratively across jurisdictions both produces better outcomes for the public and saves governments time and money.</p><p>If there is any doubt whether SLTT services could be better delivered and managed cooperatively between jurisdictions, look no further than the tens of billions of federal dollars sent annually to states to implement federal programs. Core services to support those implementations, which could range from software modules to baseline user research to reference API implementations, are a common need for every implementing jurisdiction, and would very likely both save money and time and improve outcomes in any number of ways. Such core services could be provided by the federal government if the law so allowed, but until recently, it often did not. For example, in 2015, 18F looked into whether it could provide common software services like reference implementations to support state child welfare service implementations, but they and HHS found no authorization to spend money from the program’s administrative budget on such activities, even though the states were permitted to separately engage 18F on a fee-for-service basis using their block-granted funds.</p><p>But this tide may also be shifting. 2021 legislation providing $2 billion for the Department of Labor to distribute to states to modernize their unemployment insurance systems, many of which strained or fell over completely during the pandemic, appears to allow DOL to provide or arrange for centralized services to assist states in their UI modernizations. In-house service delivery experts at DOL are on it, with help from both USDS and TTS. It remains to be seen how this relatively new flexibility will play out in DOL’s work to help the states; there are lots of variables at play. But however things shake out there, to anyone with experience in multi-team product and service delivery, this legislative improvement is an important breakthrough and should be the go-to template in Congress for all future federal funding directed to SLTT governments for implementation of federal programs. When the federal government pushes such immense responsibilities to the states, and especially when large taxpayer-funded checks are attached, it should do more than impose and enforce cumbersome policy requirements on states; it should help them, too, if it can.</p><p>Whether federal digital services are developed pursuant to a particular program like UI modernization, or as part of a general agenda to improve how government delivers services to the public, it is nearly a no-brainer to make those services available to SPLITT governments. With any luck, the US and Canadian governments will both pass their pending legislation, and we will see what teams like TTS and CDS can do to help improve service delivery up and down all the layers in our federated governments.</p><p>This article first appeared at <a href="https://aaronsnow.net/2022/05/09/sharing-federal-digital-services-with-other-layers-of-government.html">https://aaronsnow.net/2022/05/09/sharing-federal-digital-services-with-other-layers-of-government.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8a6e4f3dd24" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Canadian Digital Service, Chapter 1]]></title>
            <link>https://medium.com/@aaronsnow/the-canadian-digital-service-chapter-1-3c5d04070b14?source=rss-a52d9a60517f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3c5d04070b14</guid>
            <category><![CDATA[government]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[digital-service-teams]]></category>
            <dc:creator><![CDATA[Aaron Snow]]></dc:creator>
            <pubDate>Wed, 13 Oct 2021 20:35:45 GMT</pubDate>
            <atom:updated>2022-05-09T08:25:30.011Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://twitter.com/aaronsnow/status/1433122521289826313">Last month I stepped down</a> as CEO of the Canadian Digital Service. Canada was in election mode, and there are <a href="https://www.canada.ca/en/privy-council/services/publications/guidelines-conduct-ministers-state-exempt-staff-public-servants-election.html">restrictions</a> on what is and isn’t appropriate for public servants to talk about in public during such periods. But the election is in the rear view mirror now, and a new cabinet will soon be appointed. This seems like a good moment to reflect openly on the last three and a half years, and to express my gratitude for an unforgettable experience.</p><h4>CDS’s first four years</h4><p>CDS was created in 2017 with a mandate “to change the way the federal government designs and delivers digital services” using best practices and best-in-class tools to improve people’s lives, by putting their needs and concerns front and centre, make services more adaptable and resilient, ensure users’ privacy and system security, and reduce the risk, frequency, and scope of project and service failures. This tall order, in short, is: Change government to serve people better.</p><p>I’m proud of what CDS has accomplished in its short lifetime. The easiest measure of CDS’s success is the catalogue of what the team has delivered and the impact those projects have had. Most recently, in response to the pandemic, and with its partners at Health Canada, the Ontario Digital Service, and Shopify, CDS rapidly shipped a secure, privacy-protective, award-winning <a href="http://canada.ca/covid-alert">COVID-19 exposure notification service</a>, downloaded by more than six million users; it arguably <a href="https://www.thestar.com/news/canada/2021/08/24/how-many-lives-did-canadas-covid-19-alert-app-save-this-new-study-did-the-math.html">saved lives</a>. With Service Canada, in just one month, CDS launched the <a href="https://canada.ca/coronavirus-benefits">Find Financial Help During COVID-19</a> service, which Canadians have used more than two million times. <a href="https://benefits-avantages.veterans.gc.ca/">Find Veterans’ Benefits and Services</a>, developed with Veterans Affairs Canada, has made it easier for many thousands of Veterans to discover benefits available to them. CDS has worked with the Canada Revenue Agency to <a href="https://claim-tax-benefits.herokuapp.com/start">help Canadians with low income file taxes and claim benefits</a>, with Natural Resources Canada on an <a href="https://github.com/cds-snc/nrcan-energuide-api-poc">home energy usage API</a>, and with Immigration, Refugees and Citizenship Canada on a <a href="https://digital.canada.ca/2018/10/23/human-story-behind-citizenship/">citizenship test appointment rescheduler</a> that in early deployments reduced phone follow-ups by 70% and was called by one user “one of the easiest parts of the whole citizenship process.” CDS has helped government offer over half a billion dollars’ worth of government <a href="https://impact.canada.ca/">innovation challenges</a> for Canadians and Canadian businesses to apply for, tracked government websites’ adherence to <a href="https://cds-snc.github.io/track-web-security-compliance/">digital security best practices</a>, prototyped ways to help Canadians more easily and quickly access the <a href="https://cds-snc.github.io/cpp-disability-documentation/">CPP Disability benefit</a>, and helped RCMP start to make it easier to report and get help with <a href="https://cds-snc.github.io/rcmp-report-a-cybercrime-alpha-documentation/home/">online scams and cybercrimes</a>. It has helped dozens of departments and programs with various forms of <a href="https://docs.google.com/document/d/1KdOyFLnDA8BY77qwRIXXPxucreYwguvGKilFJmOD3xA/edit#">partner consultations</a> and exploration engagements, working with NRCan on their <a href="https://github.com/cds-snc/exploration-documentation/blob/main/images/CDS_Exploration_Final_Report_NRCan_Flood_Mapping.pdf">flood mapping</a> program and with IRCC on <a href="https://github.com/cds-snc/exploration-documentation/blob/main/images/Final_Report_EN-IRCC_Refugee_Information_Needs.pdf">meeting refugees’ information needs</a>.</p><p>As CDS grew and learned, it also began to build out important elements of a <a href="https://ash.harvard.edu/files/ash/files/293091_hvd_ash_gvmnt_as_platform_v2.pdf">digital platform</a> for the Government of Canada. It launched <a href="https://notification.canada.ca/">GC Notify</a>, which has set the bar for easy-to-use, easy-to-integrate government digital platform services. Two years in, it has sent more than 20 million messages for more than 160 clients — including, recently, a department that needed, and got, overnight feature enhancements to Notify to help it communicate effectively with Canadians in Afghanistan. With newly available resources, the Platform unit has started to roll out its nascent <a href="https://forms-formulaires.alpha.canada.ca/en/welcome-bienvenue">GC Forms</a> service, to make it possible for departments to do away with the thousands of PDF forms that are inaccessible, inflexible, and hard or impossible for people to complete on their smartphones. They’re on their way to shipping an MVP of a page-publishing service using open source technology already in use by millions of people. More is in the works.</p><p>But the hardest work of digital transformation is more <em>how</em> than<em> what</em>. CDS was established not to build digital services all by itself, but “to change the way the federal government designs and delivers digital services.” And CDS has worked hard both to drive that change and to lead by example. It led with operational cybersecurity by example, onboarding its entire staff to both physical (FIDO) <a href="https://digital.canada.ca/2019/08/15/we-take-security-seriously-why-everyone-at-cds-has-security-keys/">security keys and a password manager</a> — a trend I hope every government organization, both in the civil service and in Parliament, will soon follow. It helped enable design research across government by landing <a href="https://digital.canada.ca/2019/06/26/scaling-design-research-in-the-government-of-canada/">important changes</a> in federal public opinion research (“POR”) guidance. It conducted the GC’s first <a href="https://digital.canada.ca/2021/02/23/reflecting-on-what-i-learned-from-working-on-design-research-operations/">design research with that compensated participants</a> for their time, per international best practice. It wrote the government’s first approved job descriptions for hiring product managers, design researchers, and content designers. It helped departments get the <a href="https://digital.canada.ca/2018/06/27/tools-to-do-good-work/">right (even if non-standard) tools for the job</a>. It worked with the Chief Human Resources Officer and departmental partners to improve how the government <a href="https://digital.canada.ca/2019/03/18/attracting-and-recruiting-top-talent-with-a-little-help-from-our-friends/">hires</a> and <a href="https://digital.canada.ca/2021/03/18/busting-talent-myths-to-hire-multidisciplinary-teams/">supports</a> digitally skilled employees. It helped <a href="https://digital.canada.ca/2021/01/07/how-people-in-government-are-making-their-research-more-inclusive/">make government design research more inclusive</a>. It helped many departments stand up their first multidisciplinary digital delivery teams, conduct their first ever design research, and procure and deploy their first cloud-hosted services. And as it has developed guidance for its own teams, CDS has published those documents openly for anyone to reuse and contribute, including its <a href="https://cds-snc.github.io/design-research-handbook/">design research handbook</a>, <a href="https://cds-snc.github.io/technical-playbook-manuel-technique/">technical playbook</a>, <a href="https://github.com/cds-snc/docs/tree/main/development">software development guides</a>, <a href="https://cds-snc.github.io/guide-product-teams-equipes-produits/">guide for product teams</a>, <a href="https://digital.canada.ca/tools-and-resources/guide-interviewing/">guide to research interviewing</a>, <a href="https://digital.canada.ca/tools-and-resources/guide-usability-testing/">guide to usability testing</a>, <a href="https://digital.canada.ca/a11y">accessibility handbook</a>, <a href="https://digital.canada.ca/tools-and-resources/evaluation-framework/">product evaluation framework</a>, <a href="https://github.com/cds-snc/exploration-documentation">how to set up and run a digital services exploration</a>, and a <a href="https://digital.canada.ca/tools-and-resources/digital-reading-list/">digital government delivery and modernization reading list</a>.</p><p>Nothing CDS has done is perfect, and not every project succeeded. I’m proud that CDS has worked in the open — respectfully, to both people and policy — <a href="https://digital.canada.ca/2018/07/31/showing-the-whole-iceberg/">showing the whole iceberg</a> whenever possible and fully embracing the ethos of “docs or it didn’t happen.” Even when products <a href="https://cds-snc.github.io/claim-tax-benefits-documentation/information-about-claim-tax-benefits/">haven’t launched</a> or have been <a href="https://github.com/cds-snc/ircc-rescheduler">shuttered</a>, the team has left behind useful artifacts to share what was done and what was learned, clearing a path for future iterations with a transparent, historical record.</p><p>But most importantly, I think, CDS’s existence and accomplishments have demonstrated that working differently is possible: that if it chooses to, the public service can build and support teams capable of rapidly shipping secure, user-friendly services to millions of people, retooling overnight to help Canadians halfway around the world, and providing unconflicted expertise to help program offices design and implement their policies and services iteratively with the users of those services. Building these capabilities, not just at CDS, but all across government, is the change we need more of.</p><h4><strong>The work ahead</strong></h4><p>CDS is no longer a term-limited experiment. This spring the federal budget included, for the first time, <a href="https://www.budget.gc.ca/2021/report-rapport/p4-en.html#268">ongoing, increased funding for CDS</a>. This will enable the team to grow and deliver more than ever, adding to its burgeoning digital platform and expanding and diversifying its capacity to help partner departments. We’re at the end of the beginning.</p><p>But there’s still a great deal to do<strong>. </strong>CDS has documented its advice about the GC’s digital transformation journey openly in the <a href="https://digital.canada.ca/roadmap-2025">“Delivering digital services by 2025” roadmap</a> and <a href="https://docs.google.com/document/d/14DtnqlYL_vwzXmC3Ia5aYwlj4dDHTn4XBvATf6YcrUk/">other</a> <a href="https://docs.google.com/presentation/d/1w5TDiybyik2VR7YJd6h49Mim3yStS_8-Buo8HvkKgIQ/">documents</a>. In one sense, all that advice comes down to this: If a government is to deliver on the promise of digital services, its leadership must hold the public service to account for building those capabilities. That’s neither easy nor comfortable. But the goal isn’t “digital adjustment,” it’s “digital transformation,” and that kind of change is never painless. Government and its leaders must work differently if they want better results.</p><p>The work to date is a start, but it is not nearly enough. The growth CDS can now undertake will enable them to get more done. But in many important places in government, change has not taken hold. Not enough departments meaningfully <a href="https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html#ds1">design with users</a>. Not enough are making the necessary changes to be able to <a href="https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html#ds2">iterate and improve frequently</a>. Nor do enough <a href="https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html#ds3">work in the open by default</a>, <a href="https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html#ds4">use open standards and solutions</a>, <a href="https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html#ds6">build in accessibility from the start</a>, or, most importantly, <a href="https://www.canada.ca/en/government/system/digital-government/government-canada-digital-standards.html#ds7">empower their teams</a>. The GC Digital Standards are not yet first-class policy citizens. They should be.</p><p>To get there, the public service still needs to build unfamiliar types of internal capabilities. And by “build,” I mean hiring and training and learning — not procuring, which undermines the exercise by outsourcing core competencies rather than accumulating them, making government a buyer in woefully asymmetric negotiations. This is not an easy problem to solve, for well documented reasons. But at minimum it requires the most senior leaders to hold their organizations to account for building those capabilities.</p><p>Canada, you are lucky to have Catherine Luelo as your new federal CIO, and Anatole Papadopoulos leading CDS. Follow them. And be bold. The work takes time and patience (it is, as Cyd Harrell says, a project measured in decades), but it is incredibly rewarding work, for the worthy mission of changing government to serve people better. The GC public service can get it done, if you <a href="https://digital.canada.ca/our-values/">choose</a> to do the hard work to make things easier, put people at the heart of services, deliver measurable outcomes, build for learning and iteration, work in the open to help clear a path, and take care of each other along the way.</p><h4><strong>Gratitude</strong></h4><p>I enjoyed the heck out of this job, and even more, this team. I learned from them, was humbled and amazed by them over and over, laughed with them, and most of all am grateful for the joy of growing close to them. A group of such dedicated, talented, kind, generous, and fun people is rare and wonderful.</p><p>Minister Scott Brison, thank you for bringing CDS to life. Minister Joyce Murray and Parliamentary Secretary Greg Fergus, thank you for your unwavering support as our Minister and Parl Sec of Digital Government these last two years. Yaprak Baltacıoğlu, thank you for offering me this once in a lifetime opportunity. And Peter Wallace, thank you for trusting CDS, and me, to demonstrate the art of the possible.</p><p>Most of all, thank you to the many Government of Canada public servants I’ve met along the way, who work every day to improve service delivery and take a chance on <a href="https://twitter.com/LauraPortal347/status/1192086651570401280">doing something differently</a> to change their organizations for the better. You inspire me. Thank you all for making me and my family feel so welcome in Canada throughout our stay.</p><p>Four years ago, the Government of Canada asked us to build the CDS ship and push it out into the water. I believe we’ve done that and more. Thank you for allowing me to write Chapter 1 of CDS with you. I <a href="https://digital.canada.ca/2018/10/19/hello-world-canada/">still</a> wake up every day excited about what you do, and about what lies ahead. I can’t wait to see how Chapter 2 turns out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NTpgiB3Qp9k_JcgBnnqCsA.jpeg" /><figcaption>One of my neighbors flies the Maryland and Ontario flags side by side every day. It always makes me smile.</figcaption></figure><p>This article should be cited as <a href="https://aaronsnow.net/2021/10/13/the-canadian-digital-service-chapter-1.html">https://aaronsnow.net/2021/10/13/the-canadian-digital-service-chapter-1.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3c5d04070b14" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Norman Snow]]></title>
            <link>https://medium.com/@aaronsnow/norman-snow-934ce6002f55?source=rss-a52d9a60517f------2</link>
            <guid isPermaLink="false">https://medium.com/p/934ce6002f55</guid>
            <category><![CDATA[medicine]]></category>
            <category><![CDATA[fathers]]></category>
            <category><![CDATA[medical-school]]></category>
            <dc:creator><![CDATA[Aaron Snow]]></dc:creator>
            <pubDate>Fri, 10 Feb 2017 00:18:54 GMT</pubDate>
            <atom:updated>2017-02-10T00:18:54.529Z</atom:updated>
            <content:encoded><![CDATA[<p>Our dad, Norman Snow ז״ל, passed away early this morning at home in Vermont. He was diagnosed with very late stage cancer only a couple weeks ago and was well-prepared with a DNR as long as his arm. He went the way he wanted to: at home, quickly, in no pain, with family. He was 72.</p><p>Forgive me if this rambles. There are so many great stories.</p><p>Dad was a cardiothoracic surgeon and saved countless lives over his 40 year career. He was larger than life to me: a big frame of a man, much more imposing than his 6 feet and 200 pounds. He spent his career in government hospitals (Cleveland MetroHealth, UIC, the VAs both in Cleveland and Chicago) because he believed fiercely that health care should be a right and not a privilege. His deep singing voice on Friday nights and at shul shaped my braided senses of music and Judaism.</p><p>Both that voice and that passion reached many hundreds of future physicians, too. He loved teaching surgery, and mentoring medical students and residents, as much as or more than the work itself, first at CWRU and later at UIC. In 1980 he and a handful of peers founded the Association for Surgical Education. Even in retirement, he kept teaching young medical students, part-time in the anatomy lab at Dartmouth’s Geisel School of Medicine. (His portrayal of President Snow in a recent class’s Hunger Games spoof was an instant legend.) Almost everywhere I go, I meet people who loved and are grateful for his influence in their lives.</p><p>He was also the founding medical director of the Life Flight helicopter service in Cleveland. That day in 7th grade when he stepped out of that helicopter on the front lawn of my elementary school for Parent Career Day, I had the coolest dad in the world.</p><p>He had huge hands. I could never figure out how those hands could tie the most intricate knots with surgical thread, but those hands provided for his family his whole life. Famously and over his half-hearted, laughing protests, their entire lives Mom would never let him near an electric carving knife.</p><p>He lived in a few different cities as an adult, but he was a Burlington boy all his life. He grew up there, went to Burlington High School, spent many happy childhood hours at Ohavi Zedek, went to UVM for college and for medical school. (He once told me he knew by the time he was 6 years old that he wanted to be a doctor, and by 10 he knew what kind.) In college, he loved and led the UVM debate team, once placing 4th in the nation. He volunteered to judge debate rounds when he could.</p><p>Of course he was also the head counselor at Lake Fairlee Camp, where he met another counselor, Renee Salzman. He was smitten and, in his words, “chased her until she caught me.” They were married 48 years, retiring five years ago to a house right across the lake from that same camp (now called Ohana). He’d have seen that camp out his bedroom window when he woke up this morning, like every morning, if not for the white-out snow that’s been falling here since dawn. He loved this place, an easy place to love.</p><p>Dad was drafted into the army in 1971. Of several thousand doctors drafted that year, most were sent overseas; Dad got sent to Cleveland — which could easily have been the subject of many “which is worse” jokes if they hadn’t fallen in love with the city and stayed, minus a brief sojourn to Louisville, for nearly 30 years. His army job was to administer physicals to draftees and enlisted men, and, much to his amusement, to inspect fancy downtown restaurants where officers might eat. (He saw too much: for years after, there were some where he’d refuse to eat.)</p><p>Boy, did he love his two grandsons. Their “Poppy” took them to Disney (and let us tag along too), took them to Israel (ditto), took them minigolfing all over the Upper Valley whenever he could. After his heart scare three years ago, he made it his mission to make it to Isaac’s Bar Mitzvah, and it brought him tremendous joy. He was terribly sad when he learned he wouldn’t live to see Ely’s. He loved listening to them play piano, loved just listening to them talk about anything and everything.</p><p>He loved his convertibles, too. Stick-shift was mandatory (“I want to drive the car, not just point it”). I still remember the early ’70s metallic blue Pontiac Firebird, the Trans-Am, the LeBaron, the Saab. And he was always a big fan of cowboy shows and movies, from the old serials (he and his cousin Lynda famously used to play Roy Rogers and Dale Evans) to Indiana Jones (watched with his grandsons just last week on their last day together).</p><p>He loved music of a certain era, too, especially the Brothers Four. Sometimes after Shabbat dinner, in between traditional songs, he’d roll into a rollicking solo a cappella rendition of Ghost Riders in the Sky. Yippie-i-o, dad.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kRueNdvqUic6-n1n4OTb5A.jpeg" /><figcaption>portrait photo © 2015 UVM Alumni Association</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=934ce6002f55" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Voter Protection]]></title>
            <link>https://medium.com/@aaronsnow/voter-protection-831f237bd79?source=rss-a52d9a60517f------2</link>
            <guid isPermaLink="false">https://medium.com/p/831f237bd79</guid>
            <category><![CDATA[politics]]></category>
            <category><![CDATA[voting-rights]]></category>
            <category><![CDATA[elections]]></category>
            <dc:creator><![CDATA[Aaron Snow]]></dc:creator>
            <pubDate>Wed, 26 Oct 2016 18:46:02 GMT</pubDate>
            <atom:updated>2016-10-26T18:46:02.841Z</atom:updated>
            <content:encoded><![CDATA[<p>This seems like a good time to mention what I’m up to while I’m on leave. Two weeks ago I drove up to Philadelphia to join Hillary For America’s Pennsylvania <a href="https://www.hillaryclinton.com/forms/protect-the-vote/">Voter Protection</a> team. I’ll be here through Election Day, helping field a team of thousands of volunteer lawyers who will fan out to polling locations all over the state on Election Day to explain and defend the rights of voters, answer their voting-related questions, and ensure that the entire Election Day process functions smoothly, fairly and in accordance with the law.</p><p>When things are quiet and uneventful, poll watchers can perform many small services that help people successfully exercise their right to vote. Our volunteer lawyers get questions about voter registration, about polling locations, about how to use voting machines. They can help when poll workers aren’t implementing the election laws and regulations correctly (a relative rarity) or call in assistance when malfunctions or delays cause long wait times and voter frustration.</p><p>Sometimes it’s not so quiet. <a href="https://www.washingtonpost.com/news/wonk/wp/2014/08/06/a-comprehensive-investigation-of-voter-impersonation-finds-31-credible-incidents-out-of-one-billion-ballots-cast/">Voter fraud is very rare</a>, but <a href="https://en.wikipedia.org/wiki/Voter_suppression_in_the_United_States">voter suppression</a> and intimidation, while blessedly not rampant, occur in pockets with depressing predictability every Election Day. Every year there are official-looking flyers posted in targeted neighborhoods declaring that Republicans vote on Tuesday and Democrats vote on Wednesday, overzealous partisan poll watchers trying to challenge the identity or residency of every voter who doesn’t look like them, yahoos hanging around outside polling places brandishing weapons, and more.</p><p>Voter protection programs shouldn’t be necessary. <a href="https://www.brennancenter.org/analysis/automatic-voter-registration">Automatic voter registration</a>, <a href="https://www.brennancenter.org/publication/early-voting-what-works">early voting options</a>, <a href="http://civicdesign.org/about/">good ballot design</a>, and other modern approaches to conducting elections can all help eliminate or diminish the need for the type of help campaigns have devoted time and energy to providing every four years for the last several cycles.</p><p>In the meantime, voter protection is an insurance policy: If the presidential election is lopsided, voter protection is unlikely to change the outcome; but in any given state where the election is close, voter protection can be the difference, guaranteeing the result the voters intended. Even when the top of the ticket is one-sided, there are always some close down-ballot races where voter protection can play an important role ensuring that the voters’ will is reflected in the result. VoPro is insurance worth buying.</p><p>Moreso than in previous cycles, I think mounting large VoPro operations is partially an exercise in deterrence. When a candidate tells his supporters to “watch other communities, because we don’t want this election stolen from us,” he’s dog-whistling for them to make trouble. But bullies are usually cowards, and the visible presence of people who are on duty specifically to help voters can put a stop to some shenanigans before they get started.</p><p>I also view fielding a voter protection team as an important demonstration of our respect for the rule of law and the processes of democracy. Our poll watchers help anyone who asks, regardless of affiliation. It reflects well on our party and its candidates that we consider this important and that we invest time and energy (if not much money) into making it happen.</p><p>If you’re a lawyer — current or recovering — or if you’re not, but you care about ensuring voters’ rights, VoPro can be a very rewarding way to spend Election Day and the days and weeks leading up to it.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FsMIrba9eDTE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DsMIrba9eDTE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FsMIrba9eDTE%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c2bc608df79c6ce456ba68b04644fc63/href">https://medium.com/media/c2bc608df79c6ce456ba68b04644fc63/href</a></iframe><p><em>Lawyerly notes: (1) These are my personal views and not necessarily the campaign’s. (2) Josh Charles is not an actual lawyer.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=831f237bd79" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>