3. Work in the open by default
- Previous - 2. Iterate and improve frequently
- 1 - Go to 1. Design with users
- 2 - Go to 2. Iterate and improve frequently
- 3 - Go to 3. Work in the open by default
- 4 - Go to 4. Use open standards and solutions
- 5 - Go to 5. Address security and privacy risks
- 6 - Go to 6. Build in accessibility from the start
- 7 - Go to 7. Empower staff to deliver better services
- 8 - Go to 8. Be good data stewards
- 9 - Go to 9. Design ethical services
- 10 - Go to 10. Collaborate widely
- Next - 4. Use open standards and solutions
3.1 Share evidence, research and decision making openly
[TODO: Add/revise introductory text]
Identify performance indicators for the service, including the 4 mandatory key performance indicators (KPIs) defined in the manual. Establish a benchmark for each metric and make a plan to enable improvements.
Setting performance indicators allows you to continuously improve your service by:
- learning its strengths and weaknesses
- using data to support improvements you make
(Digital Service Standard (UK))
Share your experiences with colleagues across the Government of Canada, other levels of government, clients and service providers. Sharing experiences and best practices helps to raise the overall service quality. It helps to reduce duplication of effort and save costs. So share ideas, share intentions, share failures and learn together. (Plan - Digital Design Playbook (ISED))
Checklist
[TODO: Add/revise checklist items]
- Procuring goods and services in the open is an important part of an open environment (Open Markets - Open First Whitepaper (GC))
- When appropriate, share your development process and progress publicly (Digital Services Playbook (US))
- Document and show your work. (Plan - Digital Design Playbook (ISED))
- If you are redesigning a service document the changes and show how these changes will enhance the client experience when using the service. (Plan - Digital Design Playbook (ISED))
- document where you're getting the data for your metrics (Digital Service Standard (UK))
- set up your analytics package to collect user journey data (Digital Service Standard (UK))
- Publish metrics externally (Digital Services Playbook (US))
- make sure all stakeholders are actively involved in promoting or supporting digital delivery of the new service (Digital Service Standard (UK))
- track people moving from using the offline service to the online one (Digital Service Standard (UK))
- Publish information on the effectiveness and efficiency of Automated Decision Systems annually on a website or service designated by the Treasury Board of Canada.
- When requested, provide information on the achievement of the expected results of the Automated Decision System and compliance with the Directive on Automated Decision-Making (draft) (GC) will be provided to the Treasury Board of Canada Secretariat.
- Publish a Service Level Agreement for each service
- Make an audit trail available for all transactions to ensure accountability and non repudiation
- Establish business and IT metrics to enable business outcomes
- Apply oversight and lifecycle management to digital investments through governance
Implementation guides
- Using data to improve your service: an introduction (Digital Service Standard (UK))
- Choosing digital analytics tools (Digital Service Standard (UK))
- Measuring digital take-up (Digital Service Standard (UK))
- Sharing data on the Performance Platform (Digital Service Standard (UK))
- Measuring success (Digital Service Standard (UK))
Similar resources
3.2 Make all non-sensitive data, information, and new code developed in delivery of services open to the outside world for sharing and reuse under an open licence
Make all source code open and reusable under an appropriate open source software licence, so that other developers can:
- benefit from your work and build on it
- learn from your experiences
- identify parts of your code for reuse which you might not have recognised yourself
This includes working in the open, sharing any and all data and information produced in developing the solution, and making the final solution available as open source software. Publishing your code and data from the beginning of your technology project or programme will encourage:
- clearer documentation, making it easier for your team to maintain the code, track changes to it and for other people to use it
- cleaner and well-structured code that is easier to maintain
- processes that will allow you to continuously publish code as it is written
- clarity around data that needs to remain protected and how that's achieved
- suggestions about how the code can be improved or where security can be improved
- others to contribute ideas as the project is in progress
Checklist
- Work in the open and make data and source code open and reusable
- Host source code publicly in an open internet source code repository
- Use an Open Source Initiative approved licence
- Offer users a mechanism to report bugs and issues, and be responsive to these reports
- Keep track of changes to it using version control
- Release the final results of Algorithmic Impact Assessments in an accessible format via Government of Canada websites and services designated by the Treasury Board of Canada Secretariat pursuant to the Directive on Open Government.
- Make available to the public all of the source code used for the Automated Decision Systems on the Open Resource Exchange.
- In cases where it is deemed that source code should not be disclosed, seek the approval of the Enterprise Architecture Review Board to exempt the disclosure. In these cases, the justification as to why code was not disclosed shall be published according to the process specified in the Directive on Open Government.
- Source code for systems that are classified SECRET or TOP SECRET are exempt from making it available to the public on the Open Resource Exchange.
- Ensure that all licenses required for the Automated Decision Systems are open licenses as listed in the Open Source Software Registry.
- Ensure that Canada maintains the right to have access to foreground intellectual property to respond to any legal challenges.
- Make source code open and reusable under an appropriate open source software license
- Expose public data to implement Open Data and Open Information initiatives
- Share code publicly when appropriate, and when not, share within the Government of Canada
Implementation guides
Similar resources
- Open Source Software Contribution (Open First Whitepaper (GC))
- Open Culture (Open First Whitepaper (GC))
- Logiciels libres et ouverts - Guide de référence (Québec)
- Politique du libre (Montréal)
- 8. Make all new source code open (Digital Service Standard (UK))
- 3. Be open and use open source (Technology Code of Practice (UK))
- DINSIC Open-source contribution policy (France)
- Open Source Software (Federal Source Code Policy (US))
- 13. Default to open (Digital Services Playbook (US))
- 18F Open Source Policy (US)
- 8. Make source code open (Digital Service Standard (AU))
- Give feedback about this page
- View content source on GitHub
- View template source on GitHub
- Show filters
- Previous - 2. Iterate and improve frequently
- 1 - Go to 1. Design with users
- 2 - Go to 2. Iterate and improve frequently
- 3 - Go to 3. Work in the open by default
- 4 - Go to 4. Use open standards and solutions
- 5 - Go to 5. Address security and privacy risks
- 6 - Go to 6. Build in accessibility from the start
- 7 - Go to 7. Empower staff to deliver better services
- 8 - Go to 8. Be good data stewards
- 9 - Go to 9. Design ethical services
- 10 - Go to 10. Collaborate widely
- Next - 4. Use open standards and solutions