Difference between revisions of "DCD Blogs/Washington Blog"
Jump to navigation
Jump to search
(Created page with "FR:DCN_Blogues <!--The following line of code hides the page title--> {{DISPLAYTITLE:<span style="position: absolute; clip: rect(1px 1px 1px 1px); clip: rect(1px, 1px, 1p...") |
(added content) |
||
| Line 10: | Line 10: | ||
<br> | <br> | ||
| − | <div style="line-height: 3em; font-size: 250%; text-indent: 8%; font-family:'Helvetica Neue', 'Lucida Grande', Tahoma, Verdana, sans-serif;"> | + | <div style="line-height: 3em; font-size: 250%; text-indent: 8%; font-family:'Helvetica Neue', 'Lucida Grande', Tahoma, Verdana, sans-serif;"> Insert Title Here</div> |
<div style="line-height: 2em; font-size: 125%; text-indent: 14%;font-family:'Helvetica Neue', 'Lucida Grande', Tahoma, Verdana, sans-serif;"> [https://gccollab.ca/profile/Derek.Alton/ Derek Alton] / Strategic Partnerships Team/ June 27th 2018</div> | <div style="line-height: 2em; font-size: 125%; text-indent: 14%;font-family:'Helvetica Neue', 'Lucida Grande', Tahoma, Verdana, sans-serif;"> [https://gccollab.ca/profile/Derek.Alton/ Derek Alton] / Strategic Partnerships Team/ June 27th 2018</div> | ||
| − | <div style="line-height: 2em; font-size: 125%; text-indent: 14%;font-family:'Helvetica Neue', 'Lucida Grande', Tahoma, Verdana, sans-serif;"> ''' | + | <div style="line-height: 2em; font-size: 125%; text-indent: 14%;font-family:'Helvetica Neue', 'Lucida Grande', Tahoma, Verdana, sans-serif;"> '''12 minute read'''</div> |
<br> | <br> | ||
<div style="border:1px solid #white; {{Round corners}}; text-indent: 8%; margin: 20px; margin: 0 auto; width: 700px; line-height: 2em; font-size:125%"> | <div style="border:1px solid #white; {{Round corners}}; text-indent: 8%; margin: 20px; margin: 0 auto; width: 700px; line-height: 2em; font-size:125%"> | ||
'''<span style="color:#545454; font-size:125%">On May 15, the United States Digital Service hosted its counterparts from the North: the Digital Collaboration Division of the Government of Canada.</span>''' | '''<span style="color:#545454; font-size:125%">On May 15, the United States Digital Service hosted its counterparts from the North: the Digital Collaboration Division of the Government of Canada.</span>''' | ||
| − | + | ||
These public servants are creating a single collaborative public service and encouraging new ways of working in an open, transparent, digital environment. Heather Laird and Christopher Allison came to visit USDS Headquarters and discussed their work focused on creating an Open & Accessible Digital Workspace, a collaboration tool for teams with government records retention compliance and multilingual support baked-in. USDSers queried our visitors on their use of APIs and on the broader efforts involved with behavior change work around technology adoption in government. | These public servants are creating a single collaborative public service and encouraging new ways of working in an open, transparent, digital environment. Heather Laird and Christopher Allison came to visit USDS Headquarters and discussed their work focused on creating an Open & Accessible Digital Workspace, a collaboration tool for teams with government records retention compliance and multilingual support baked-in. USDSers queried our visitors on their use of APIs and on the broader efforts involved with behavior change work around technology adoption in government. | ||
| − | <br> | + | |
| − | Even as long standing allies and friends with many shared values and priorities, service delivery in the US and Canada each have their own distinct issues, our discussion yielded insights into the parallels of our work. | + | <br>Even as long standing allies and friends with many shared values and priorities, service delivery in the US and Canada each have their own distinct issues, our discussion yielded insights into the parallels of our work. |
| − | <br> | + | |
| − | Tools for the win | + | <br>'''Tools for the win''.'''''<nowiki/>'' '' |
| + | |||
The people we serve may be different, but the tools needed to help public servants get great work done are often the same. The need for surveys and consultation tools, instant messaging and team chat, space for ad hoc, cross-team working groups, or document sharing that meets government standards seems more or less universal. Commercial tools do a lot, but open source tools can be tweaked on the fly to meet the regs & legs of governments in charge. | The people we serve may be different, but the tools needed to help public servants get great work done are often the same. The need for surveys and consultation tools, instant messaging and team chat, space for ad hoc, cross-team working groups, or document sharing that meets government standards seems more or less universal. Commercial tools do a lot, but open source tools can be tweaked on the fly to meet the regs & legs of governments in charge. | ||
| − | + | ||
| − | Our Questions: What might it look like for governments around the world to build up open source tools that can meet the needs of our employees? Could we adapt what’s already built in the open to get awesome, accessible tools? Could we understand our needs better and create better specs when we buy tools? What are the pros and cons of open source and proprietary solutions for different use cases? How might other groups working to serve the public use open tools too? How might we decentralize, build, and invest in processes to support open source projects for public benefit work around the world? | + | '''Our Questions:''' |
| − | <br> | + | * What might it look like for governments around the world to build up open source tools that can meet the needs of our employees? |
| − | Sharing the Secret Sauce | + | * Could we adapt what’s already built in the open to get awesome, accessible tools? |
| + | * Could we understand our needs better and create better specs when we buy tools? | ||
| + | * What are the pros and cons of open source and proprietary solutions for different use cases? | ||
| + | * How might other groups working to serve the public use open tools too? | ||
| + | * How might we decentralize, build, and invest in processes to support open source projects for public benefit work around the world? <br>'''Sharing the Secret Sauce''' | ||
The Digital Collaboration Division, alongside partners, has already spun up beta versions of tools that are free to use or copy-paste into a new version, right now (!). | The Digital Collaboration Division, alongside partners, has already spun up beta versions of tools that are free to use or copy-paste into a new version, right now (!). | ||
| − | + | * ''Instant Messaging for team chat and on-the-fly exchanges'' - Builds on RocketChat -https://message.gccollab.ca/ | |
| − | Instant Messaging for team chat and on-the-fly exchanges - Builds on RocketChat - | + | * ''Project Boards to manage projects and workflow'' - Builds on Wekan - https://kanban.gccollab.ca/ |
| − | Project Boards to manage projects and workflow - Builds on Wekan - | + | |
| − | Authentication to provide trusted identification across other tools - Builds on Python Django - | + | * ''Authentication to provide trusted identification across other tools'' - Builds on Python Django - https://account.gccollab.ca/ |
| − | + | The Digital Collaboration is exploring how these can connect with services created in the US, like: | |
| − | The Digital Collaboration is exploring how these can connect with services created in the US, like: | + | * Vets.gov |
| − | + | * Certify.sba.gov | |
| − | Vets.gov | + | * Move.mil |
| − | Certify.sba.gov | + | * Login.gov |
| − | Move.mil | + | * Data.gov |
| − | Login.gov | + | * Pulse.cio.gov |
| − | Data.gov | + | * Digital.gov |
| − | Pulse.cio.gov | + | * Challenge.gov |
| − | Digital.gov | ||
| − | Challenge.gov | ||
| − | |||
Any group can join in the Government of Canada instance (by invitation, for now), or adapt the open source tools independently. The US Government is already using some of these open source tools, so we are both invested in making them better. | Any group can join in the Government of Canada instance (by invitation, for now), or adapt the open source tools independently. The US Government is already using some of these open source tools, so we are both invested in making them better. | ||
| − | + | ||
| − | Our Questions: Who else might benefit from these tools? How can we increase user adoption? When needed, how can we open up approvals for these tools for government employees working in different jurisdictions? When these tools are awesome, how can we tell the story? When they need to be improved, how can we get feedback to make them better? How can we put these tools in the hands of every civil servant when they start a new job? How can the government promote wider adoption of APIs, like what USDS has done with health data access? | + | '''Our Questions:''' |
| − | + | * Who else might benefit from these tools? | |
| − | The greatest good! | + | * How can we increase user adoption? |
| − | <br> | + | * When needed, how can we open up approvals for these tools for government employees working in different jurisdictions? |
| − | Tools are one part of the story - the mission is what matters in the end. It turns out colleagues in Canada and the US Government are working on supporting Veterans, streamlining the Immigration process, giving citizens and health professionals better access to healthcare information, and much more. | + | * When these tools are awesome, how can we tell the story? |
| − | + | * When they need to be improved, how can we get feedback to make them better? | |
| − | Our Questions: How can we learn from each other to avoid repeating mistakes? How can we adopt solutions developed in different governments to leap-frog ahead? How can we take lessons back from successful missions to improve service, and change tools, human resource, onboarding, and other processes in government to make it easier next time? | + | * How can we put these tools in the hands of every civil servant when they start a new job? |
| − | + | * How can the government promote wider adoption of APIs, like what USDS has done with health data access? | |
| − | + | ||
| − | + | '''The greatest good!'''<br>Tools are one part of the story - the mission is what matters in the end. It turns out colleagues in Canada and the US Government are working on supporting Veterans, streamlining the Immigration process, giving citizens and health professionals better access to healthcare information, and much more. | |
| − | Doors open! An open invitation to take a tour up North and hotdesk with the Digital Collaboration Division. Contact @derek.alton or derek.alton@tbs-sct.gc.ca to learn more. And vice versa, any Canadians looking to visit USDS and learn more about what USDS is up to on their projects can contact @c_sethna or cyrus.l.sethna@omb.eop.gov | + | |
| − | + | '''Our Questions:''' | |
| − | Join the Partners’ Forum for the open source project to create an open and accessible digital workspace by hollering @derek.alton or derek.alton@tbs-sct.gc.ca | + | |
| − | + | How can we learn from each other to avoid repeating mistakes? | |
| − | <br> | + | |
| − | Who’s in the conversation, to name a few: @USDS @MattCutts @MarkLerner @Govloop @SteveRessler @OpenGovHub @OpenGovPartnership @LenaTrudeau @KellyOlson @PhilWenger @GrayBrooks @CDS @IRCC @18F @codeforDC @sunlightfoundation and so many more. Thanks for an amazing week! | + | How can we adopt solutions developed in different governments to leap-frog ahead? |
| + | |||
| + | How can we take lessons back from successful missions to improve service, and change tools, human resource, onboarding, and other processes in government to make it easier next time? | ||
| + | |||
| + | '''What's Next?''' | ||
| + | |||
| + | Doors open! An open invitation to take a tour up North and hotdesk with the Digital Collaboration Division. Contact '''@derek.alton''' or '''derek.alton@tbs-sct.gc.ca''' to learn more. | ||
| + | |||
| + | And vice versa, any Canadians looking to visit USDS and learn more about what USDS is up to on their projects can contact '''@c_sethna''' or '''cyrus.l.sethna@omb.eop.gov''' | ||
| + | |||
| + | Join the Partners’ Forum for the open source project to create an open and accessible digital workspace by hollering '''@derek.alton''' or '''derek.alton@tbs-sct.gc.ca''' | ||
| + | |||
| + | <br>Who’s in the conversation, to name a few: '''@USDS @MattCutts @MarkLerner @Govloop @SteveRessler @OpenGovHub @OpenGovPartnership @LenaTrudeau @KellyOlson @PhilWenger @GrayBrooks @CDS @IRCC @18F @codeforDC @sunlightfoundation''' and so many more. Thanks for an amazing week! | ||
Revision as of 15:15, 26 June 2018
Insert Title Here
Derek Alton / Strategic Partnerships Team/ June 27th 2018
12 minute read
On May 15, the United States Digital Service hosted its counterparts from the North: the Digital Collaboration Division of the Government of Canada.
These public servants are creating a single collaborative public service and encouraging new ways of working in an open, transparent, digital environment. Heather Laird and Christopher Allison came to visit USDS Headquarters and discussed their work focused on creating an Open & Accessible Digital Workspace, a collaboration tool for teams with government records retention compliance and multilingual support baked-in. USDSers queried our visitors on their use of APIs and on the broader efforts involved with behavior change work around technology adoption in government.
Even as long standing allies and friends with many shared values and priorities, service delivery in the US and Canada each have their own distinct issues, our discussion yielded insights into the parallels of our work.
Tools for the win.
The people we serve may be different, but the tools needed to help public servants get great work done are often the same. The need for surveys and consultation tools, instant messaging and team chat, space for ad hoc, cross-team working groups, or document sharing that meets government standards seems more or less universal. Commercial tools do a lot, but open source tools can be tweaked on the fly to meet the regs & legs of governments in charge.
Our Questions:
- What might it look like for governments around the world to build up open source tools that can meet the needs of our employees?
- Could we adapt what’s already built in the open to get awesome, accessible tools?
- Could we understand our needs better and create better specs when we buy tools?
- What are the pros and cons of open source and proprietary solutions for different use cases?
- How might other groups working to serve the public use open tools too?
- How might we decentralize, build, and invest in processes to support open source projects for public benefit work around the world?
Sharing the Secret Sauce
The Digital Collaboration Division, alongside partners, has already spun up beta versions of tools that are free to use or copy-paste into a new version, right now (!).
- Instant Messaging for team chat and on-the-fly exchanges - Builds on RocketChat -https://message.gccollab.ca/
- Project Boards to manage projects and workflow - Builds on Wekan - https://kanban.gccollab.ca/
- Authentication to provide trusted identification across other tools - Builds on Python Django - https://account.gccollab.ca/
The Digital Collaboration is exploring how these can connect with services created in the US, like:
- Vets.gov
- Certify.sba.gov
- Move.mil
- Login.gov
- Data.gov
- Pulse.cio.gov
- Digital.gov
- Challenge.gov
Any group can join in the Government of Canada instance (by invitation, for now), or adapt the open source tools independently. The US Government is already using some of these open source tools, so we are both invested in making them better.
Our Questions:
- Who else might benefit from these tools?
- How can we increase user adoption?
- When needed, how can we open up approvals for these tools for government employees working in different jurisdictions?
- When these tools are awesome, how can we tell the story?
- When they need to be improved, how can we get feedback to make them better?
- How can we put these tools in the hands of every civil servant when they start a new job?
- How can the government promote wider adoption of APIs, like what USDS has done with health data access?
The greatest good!
Tools are one part of the story - the mission is what matters in the end. It turns out colleagues in Canada and the US Government are working on supporting Veterans, streamlining the Immigration process, giving citizens and health professionals better access to healthcare information, and much more.
Our Questions:
How can we learn from each other to avoid repeating mistakes?
How can we adopt solutions developed in different governments to leap-frog ahead?
How can we take lessons back from successful missions to improve service, and change tools, human resource, onboarding, and other processes in government to make it easier next time?
What's Next?
Doors open! An open invitation to take a tour up North and hotdesk with the Digital Collaboration Division. Contact @derek.alton or derek.alton@tbs-sct.gc.ca to learn more.
And vice versa, any Canadians looking to visit USDS and learn more about what USDS is up to on their projects can contact @c_sethna or cyrus.l.sethna@omb.eop.gov
Join the Partners’ Forum for the open source project to create an open and accessible digital workspace by hollering @derek.alton or derek.alton@tbs-sct.gc.ca
Who’s in the conversation, to name a few: @USDS @MattCutts @MarkLerner @Govloop @SteveRessler @OpenGovHub @OpenGovPartnership @LenaTrudeau @KellyOlson @PhilWenger @GrayBrooks @CDS @IRCC @18F @codeforDC @sunlightfoundation and so many more. Thanks for an amazing week!
